Hi all,
I am trying the conference demo based on Sip Servlet1.7.0 and media
server 2.1.0.BETA2. All are setup, the following exception output on
media server log when i use a sip phone send invite "sip:sip-servlets-
confere...@192.168.0.106:5080".
Who can do me a favor for this problem? Thanks a lot.
18:02:59,087 INFO [MainDeployer] [[[[[[[[[ Mobicents Media Server:
release.version=${pom.version} Started ]]]]]]]]]
18:05:56,321 INFO [MGCP] tx=831178961 Started, message= CRCX
mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
CD.cnt01.local/192.168.0.106:2921
18:05:56,368 INFO [MGCP] tx=831178961 was executed norma ly
18:05:56,399 INFO [MGCP] tx=831178962 Started, message= CRCX
mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
CD.cnt01.local/192.168.0.106:2921
18:05:56,430 INFO [MGCP] tx=831178962 was executed normaly
18:05:56,446 INFO [MGCP] tx=831178963 Started, message= MDCX
mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
CD.cnt01.local/192.168.0.106:2921
18:05:56,446 INFO [MGCP] tx=831178964 Started, message= MDCX
mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
CD.cnt01.local/192.168.0.106:2921
18:05:56,446 ERROR [MGCP] tx=831178964 Failed
org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd
$Modifier.perform(ModifyConnectionCmd.java:106)
at org.mobicents.media.server.scheduler.Task.run(Task.java:109)
at org.mobicents.media.server.scheduler.Scheduler
$CpuThread.run(Scheduler.java:241)
18:05:56,446 INFO [MGCP] tx=831178963 was executed normaly
18:05:56,446 INFO [MGCP] tx=831178964 Rolled back
18:05:56,462 INFO [MGCP] tx=831178965 Started, message= DLCX
mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
CD.cnt01.local/192.168.0.106:2921
18:05:56,462 INFO [MGCP] tx=831178966 Started, message= DLCX
mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
CD.cnt01.local/192.168.0.106:2921
18:05:56,462 ERROR [MGCP] tx=831178966 Failed
org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
at org.mobicents.media.server.mgcp.tx.cmd.DeleteConnectionCmd
$Delete.perform(DeleteConnectionCmd.java:117)
at org.mobicents.media.server.scheduler.Task.run(Task.java:109)
at org.mobicents.media.server.scheduler.Scheduler
$CpuThread.run(Scheduler.java:241)
18:05:56,462 INFO [MGCP] tx=831178966 Rolled back
18:05:56,462 INFO [MGCP] tx=831178965 was executed normaly
Drop packet
Drop packet
18:06:05,321 INFO [MGCP] tx=831178967 Started, message= DLCX
mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
CD.cnt01.local/192.168.0.106:2921
18:06:05,337 INFO [MGCP] tx=831178967 was executed normaly
> Hi all,
> I am trying the conference demo based on Sip Servlet1.7.0 and media
> server 2.1.0.BETA2. All are setup, the following exception output on
> media server log when i use a sip phone send invite "sip:sip-servlets-
> confere...@192.168.0.106:5080".
> Who can do me a favor for this problem? Thanks a lot.
> 18:02:59,087 INFO [MainDeployer] [[[[[[[[[ Mobicents Media Server:
> release.version=${pom.version} Started ]]]]]]]]]
> 18:05:56,321 INFO [MGCP] tx=831178961 Started, message= CRCX
> mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> CD.cnt01.local/192.168.0.106:2921
> 18:05:56,368 INFO [MGCP] tx=831178961 was executed norma ly
> 18:05:56,399 INFO [MGCP] tx=831178962 Started, message= CRCX
> mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> CD.cnt01.local/192.168.0.106:2921
> 18:05:56,430 INFO [MGCP] tx=831178962 was executed normaly
> 18:05:56,446 INFO [MGCP] tx=831178963 Started, message= MDCX
> mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> CD.cnt01.local/192.168.0.106:2921
> 18:05:56,446 INFO [MGCP] tx=831178964 Started, message= MDCX
> mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> CD.cnt01.local/192.168.0.106:2921
> 18:05:56,446 ERROR [MGCP] tx=831178964 Failed
> org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
> at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd
> $Modifier.perform(ModifyConnectionCmd.java:106)
> at org.mobicents.media.server.scheduler.Task.run(Task.java:109)
> at org.mobicents.media.server.scheduler.Scheduler
> $CpuThread.run(Scheduler.java:241)
> 18:05:56,446 INFO [MGCP] tx=831178963 was executed normaly
> 18:05:56,446 INFO [MGCP] tx=831178964 Rolled back
> 18:05:56,462 INFO [MGCP] tx=831178965 Started, message= DLCX
> mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> CD.cnt01.local/192.168.0.106:2921
> 18:05:56,462 INFO [MGCP] tx=831178966 Started, message= DLCX
> mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> CD.cnt01.local/192.168.0.106:2921
> 18:05:56,462 ERROR [MGCP] tx=831178966 Failed
> org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
> at org.mobicents.media.server.mgcp.tx.cmd.DeleteConnectionCmd
> $Delete.perform(DeleteConnectionCmd.java:117)
> at org.mobicents.media.server.scheduler.Task.run(Task.java:109)
> at org.mobicents.media.server.scheduler.Scheduler
> $CpuThread.run(Scheduler.java:241)
> 18:05:56,462 INFO [MGCP] tx=831178966 Rolled back
> 18:05:56,462 INFO [MGCP] tx=831178965 was executed normaly
> Drop packet
> Drop packet
> 18:06:05,321 INFO [MGCP] tx=831178967 Started, message= DLCX
> mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> CD.cnt01.local/192.168.0.106:2921
> 18:06:05,337 INFO [MGCP] tx=831178967 was executed normaly
After that, the following exception is output.
org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd
$Modifier.perform(ModifyConnectionCmd.java:106)
I don't understand that why mobicents/cn/$ and mobicents/cn/5 are
created. What does it mean?
I saw the following configuraion in mobicents-media-server\mms-server
\deploy\server-beans.xml.
<property name="namePattern">mobicents/cnf/[1..5]</property>
What is the mean of "mobicents/cnf/[1..5]" ?
Who can give some comments for it?
Thanks a lot.
Dennis
On Jun 4, 4:42 pm, Dennis Hu <dennis.hu...@gmail.com> wrote:
> who can give some comments to me? Thanks a lot. If you need more
> information about this problem, please let me know.
> Thanks a lot.
> Dennis
> On Jun 3, 6:17 pm, Dennis Hu <dennis.hu...@gmail.com> wrote:
> > Hi all,
> > I am trying the conference demo based on Sip Servlet1.7.0 and media
> > server 2.1.0.BETA2. All are setup, the following exception output on
> > media server log when i use a sip phone send invite "sip:sip-servlets-
> > confere...@192.168.0.106:5080".
> > Who can do me a favor for this problem? Thanks a lot.
> > 18:02:59,087 INFO [MainDeployer] [[[[[[[[[ Mobicents Media Server:
> > release.version=${pom.version} Started ]]]]]]]]]
> > 18:05:56,321 INFO [MGCP] tx=831178961 Started, message= CRCX
> > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > CD.cnt01.local/192.168.0.106:2921
> > 18:05:56,368 INFO [MGCP] tx=831178961 was executed norma ly
> > 18:05:56,399 INFO [MGCP] tx=831178962 Started, message= CRCX
> > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > CD.cnt01.local/192.168.0.106:2921
> > 18:05:56,430 INFO [MGCP] tx=831178962 was executed normaly
> > 18:05:56,446 INFO [MGCP] tx=831178963 Started, message= MDCX
> > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > CD.cnt01.local/192.168.0.106:2921
> > 18:05:56,446 INFO [MGCP] tx=831178964 Started, message= MDCX
> > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > CD.cnt01.local/192.168.0.106:2921
> > 18:05:56,446 ERROR [MGCP] tx=831178964 Failed
> > org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
> > at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd
> > $Modifier.perform(ModifyConnectionCmd.java:106)
> > at org.mobicents.media.server.scheduler.Task.run(Task.java:109)
> > at org.mobicents.media.server.scheduler.Scheduler
> > $CpuThread.run(Scheduler.java:241)
> > 18:05:56,446 INFO [MGCP] tx=831178963 was executed normaly
> > 18:05:56,446 INFO [MGCP] tx=831178964 Rolled back
> > 18:05:56,462 INFO [MGCP] tx=831178965 Started, message= DLCX
> > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > CD.cnt01.local/192.168.0.106:2921
> > 18:05:56,462 INFO [MGCP] tx=831178966 Started, message= DLCX
> > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > CD.cnt01.local/192.168.0.106:2921
> > 18:05:56,462 ERROR [MGCP] tx=831178966 Failed
> > org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
> > at org.mobicents.media.server.mgcp.tx.cmd.DeleteConnectionCmd
> > $Delete.perform(DeleteConnectionCmd.java:117)
> > at org.mobicents.media.server.scheduler.Task.run(Task.java:109)
> > at org.mobicents.media.server.scheduler.Scheduler
> > $CpuThread.run(Scheduler.java:241)
> > 18:05:56,462 INFO [MGCP] tx=831178966 Rolled back
> > 18:05:56,462 INFO [MGCP] tx=831178965 was executed normaly
> > Drop packet
> > Drop packet
> > 18:06:05,321 INFO [MGCP] tx=831178967 Started, message= DLCX
> > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > CD.cnt01.local/192.168.0.106:2921
> > 18:06:05,337 INFO [MGCP] tx=831178967 was executed normaly
> After that, the following exception is output.
> org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
> at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd
> $Modifier.perform(ModifyConnectionCmd.java:106)
> I don't understand that why mobicents/cn/$ and mobicents/cn/5 are
> created. What does it mean?
> I saw the following configuraion in mobicents-media-server\mms-server
> \deploy\server-beans.xml.
> <property name="namePattern">mobicents/cnf/[1..5]</property>
> What is the mean of "mobicents/cnf/[1..5]" ?
> Who can give some comments for it?
> Thanks a lot.
> Dennis
> On Jun 4, 4:42 pm, Dennis Hu <dennis.hu...@gmail.com> wrote:
> > who can give some comments to me? Thanks a lot. If you need more
> > information about this problem, please let me know.
> > Thanks a lot.
> > Dennis
> > On Jun 3, 6:17 pm, Dennis Hu <dennis.hu...@gmail.com> wrote:
> > > Hi all,
> > > I am trying the conference demo based on Sip Servlet1.7.0 and media
> > > server 2.1.0.BETA2. All are setup, the following exception output on
> > > media server log when i use a sip phone send invite "sip:sip-servlets-
> > > confere...@192.168.0.106:5080".
> > > Who can do me a favor for this problem? Thanks a lot.
> > > 18:02:59,087 INFO [MainDeployer] [[[[[[[[[ Mobicents Media Server:
> > > release.version=${pom.version} Started ]]]]]]]]]
> > > 18:05:56,321 INFO [MGCP] tx=831178961 Started, message= CRCX
> > > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > > CD.cnt01.local/192.168.0.106:2921
> > > 18:05:56,368 INFO [MGCP] tx=831178961 was executed norma ly
> > > 18:05:56,399 INFO [MGCP] tx=831178962 Started, message= CRCX
> > > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > > CD.cnt01.local/192.168.0.106:2921
> > > 18:05:56,430 INFO [MGCP] tx=831178962 was executed normaly
> > > 18:05:56,446 INFO [MGCP] tx=831178963 Started, message= MDCX
> > > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > > CD.cnt01.local/192.168.0.106:2921
> > > 18:05:56,446 INFO [MGCP] tx=831178964 Started, message= MDCX
> > > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > > CD.cnt01.local/192.168.0.106:2921
> > > 18:05:56,446 ERROR [MGCP] tx=831178964 Failed
> > > org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
> > > at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd
> > > $Modifier.perform(ModifyConnectionCmd.java:106)
> > > at org.mobicents.media.server.scheduler.Task.run(Task.java:109)
> > > at org.mobicents.media.server.scheduler.Scheduler
> > > $CpuThread.run(Scheduler.java:241)
> > > 18:05:56,446 INFO [MGCP] tx=831178963 was executed normaly
> > > 18:05:56,446 INFO [MGCP] tx=831178964 Rolled back
> > > 18:05:56,462 INFO [MGCP] tx=831178965 Started, message= DLCX
> > > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > > CD.cnt01.local/192.168.0.106:2921
> > > 18:05:56,462 INFO [MGCP] tx=831178966 Started, message= DLCX
> > > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > > CD.cnt01.local/192.168.0.106:2921
> > > 18:05:56,462 ERROR [MGCP] tx=831178966 Failed
> > > org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
> > > at org.mobicents.media.server.mgcp.tx.cmd.DeleteConnectionCmd
> > > $Delete.perform(DeleteConnectionCmd.java:117)
> > > at org.mobicents.media.server.scheduler.Task.run(Task.java:109)
> > > at org.mobicents.media.server.scheduler.Scheduler
> > > $CpuThread.run(Scheduler.java:241)
> > > 18:05:56,462 INFO [MGCP] tx=831178966 Rolled back
> > > 18:05:56,462 INFO [MGCP] tx=831178965 was executed normaly
> > > Drop packet
> > > Drop packet
> > > 18:06:05,321 INFO [MGCP] tx=831178967 Started, message= DLCX
> > > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> > > CD.cnt01.local/192.168.0.106:2921
> > > 18:06:05,337 INFO [MGCP] tx=831178967 was executed normaly
> > After that, the following exception is output.
> > org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
> > at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd
> > $Modifier.perform(ModifyConnectionCmd.java:106)
> > I don't understand that why mobicents/cn/$ and mobicents/cn/5 are
> > created. What does it mean?
> > I saw the following configuraion in mobicents-media-server\mms-server
> > \deploy\server-beans.xml.
> > <property name="namePattern">mobicents/cnf/[1..5]</property>
> > What is the mean of "mobicents/cnf/[1..5]" ?
> > Who can give some comments for it?
> > Thanks a lot.
> > Dennis
> > On Jun 4, 4:42 pm, Dennis Hu <dennis.hu...@gmail.com> wrote:
> > > who can give some comments to me? Thanks a lot. If you need more
> > > information about this problem, please let me know.
> > > Thanks a lot.
> > > Dennis
> > > On Jun 3, 6:17 pm, Dennis Hu <dennis.hu...@gmail.com> wrote:
> > > > Hi all,
> > > > I am trying the conference demo based on Sip Servlet1.7.0 and media
> > > > server 2.1.0.BETA2. All are setup, the following exception output on
> > > > media server log when i use a sip phone send invite "sip:sip-servlets-
> > > > confere...@192.168.0.106:5080".
> > > > Who can do me a favor for this problem? Thanks a lot.
> > > After that, the following exception is output.
> > > org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
> > > at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd
> > > $Modifier.perform(ModifyConnectionCmd.java:106)
> > > I don't understand that why mobicents/cn/$ and mobicents/cn/5 are
> > > created. What does it mean?
> > > I saw the following configuraion in mobicents-media-server\mms-server
> > > \deploy\server-beans.xml.
> > > <property name="namePattern">mobicents/cnf/[1..5]</property>
> > > What is the mean of "mobicents/cnf/[1..5]" ?
> > > Who can give some comments for it?
> > > Thanks a lot.
> > > Dennis
> > > On Jun 4, 4:42 pm, Dennis Hu <dennis.hu...@gmail.com> wrote:
> > > > who can give some comments to me? Thanks a lot. If you need more
> > > > information about this problem, please let me know.
> > > > Thanks a lot.
> > > > Dennis
> > > > On Jun 3, 6:17 pm, Dennis Hu <dennis.hu...@gmail.com> wrote:
> > > > > Hi all,
> > > > > I am trying the conference demo based on Sip Servlet1.7.0 and media
> > > > > server 2.1.0.BETA2. All are setup, the following exception output on
> > > > > media server log when i use a sip phone send invite "sip:sip-servlets-
> > > > > confere...@192.168.0.106:5080".
> > > > > Who can do me a favor for this problem? Thanks a lot.
I'm also getting this exception using the mss 1.7.0 FINAL distribution and either the bundled MMS 2.1.0 Beta3 or a separately downloaded MMS 2.1.0 beta4.
Should these demos work on Windows? (Windows 7). Or might they only work on Linux?
On Sunday, June 3, 2012 3:17:22 AM UTC-7, Dennis Hu wrote:
> Hi all, > I am trying the conference demo based on Sip Servlet1.7.0 and media > server 2.1.0.BETA2. All are setup, the following exception output on > media server log when i use a sip phone send invite "sip:sip-servlets- > confere...@192.168.0.106:5080".
> Who can do me a favor for this problem? Thanks a lot.
> 18:02:59,087 INFO [MainDeployer] [[[[[[[[[ Mobicents Media Server: > release.version=${pom.version} Started ]]]]]]]]] > 18:05:56,321 INFO [MGCP] tx=831178961 Started, message= CRCX > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186- > CD.cnt01.local/192.168.0.106:2921 > 18:05:56,368 INFO [MGCP] tx=831178961 was executed norma ly > 18:05:56,399 INFO [MGCP] tx=831178962 Started, message= CRCX > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186- > CD.cnt01.local/192.168.0.106:2921 > 18:05:56,430 INFO [MGCP] tx=831178962 was executed normaly > 18:05:56,446 INFO [MGCP] tx=831178963 Started, message= MDCX > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186- > CD.cnt01.local/192.168.0.106:2921 > 18:05:56,446 INFO [MGCP] tx=831178964 Started, message= MDCX > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186- > CD.cnt01.local/192.168.0.106:2921 > 18:05:56,446 ERROR [MGCP] tx=831178964 Failed > org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException > at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd > $Modifier.perform(ModifyConnectionCmd.java:106) > at org.mobicents.media.server.scheduler.Task.run(Task.java:109) > at org.mobicents.media.server.scheduler.Scheduler > $CpuThread.run(Scheduler.java:241) > 18:05:56,446 INFO [MGCP] tx=831178963 was executed normaly > 18:05:56,446 INFO [MGCP] tx=831178964 Rolled back > 18:05:56,462 INFO [MGCP] tx=831178965 Started, message= DLCX > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186- > CD.cnt01.local/192.168.0.106:2921 > 18:05:56,462 INFO [MGCP] tx=831178966 Started, message= DLCX > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186- > CD.cnt01.local/192.168.0.106:2921 > 18:05:56,462 ERROR [MGCP] tx=831178966 Failed > org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException > at org.mobicents.media.server.mgcp.tx.cmd.DeleteConnectionCmd > $Delete.perform(DeleteConnectionCmd.java:117) > at org.mobicents.media.server.scheduler.Task.run(Task.java:109) > at org.mobicents.media.server.scheduler.Scheduler > $CpuThread.run(Scheduler.java:241) > 18:05:56,462 INFO [MGCP] tx=831178966 Rolled back > 18:05:56,462 INFO [MGCP] tx=831178965 was executed normaly > Drop packet > Drop packet > 18:06:05,321 INFO [MGCP] tx=831178967 Started, message= DLCX > mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186- > CD.cnt01.local/192.168.0.106:2921 > 18:06:05,337 INFO [MGCP] tx=831178967 was executed normaly
On Sat, Jul 7, 2012 at 2:11 AM, Martin Bayly <mar...@parkbayly.net> wrote:
> I'm also getting this exception using the mss 1.7.0 FINAL distribution and
> either the bundled MMS 2.1.0 Beta3 or a separately downloaded MMS 2.1.0
> beta4.
> Should these demos work on Windows? (Windows 7).
> Or might they only work on Linux?
> On Sunday, June 3, 2012 3:17:22 AM UTC-7, Dennis Hu wrote:
>> Hi all,
>> I am trying the conference demo based on Sip Servlet1.7.0 and media
>> server 2.1.0.BETA2. All are setup, the following exception output on
>> media server log when i use a sip phone send invite "sip:sip-servlets-
>> confere...@192.168.0.106:5080"**.
>> Who can do me a favor for this problem? Thanks a lot.
>> 18:02:59,087 INFO [MainDeployer] [[[[[[[[[ Mobicents Media Server:
>> release.version=${pom.version} Started ]]]]]]]]]
>> 18:05:56,321 INFO [MGCP] tx=831178961 Started, message= CRCX
>> mobicents/cn...@192.168.0.106:**2427 <http://192.168.0.106:2427>, call
>> agent = CNPC0186-
>> CD.cnt01.local/192.168.0.106:**2921 <http://192.168.0.106:2921>
>> 18:05:56,368 INFO [MGCP] tx=831178961 was executed norma ly
>> 18:05:56,399 INFO [MGCP] tx=831178962 Started, message= CRCX
>> mobicents/cn...@192.168.0.106:**2427 <http:/...@192.168.0.106:2427>, call
>> agent = CNPC0186-
>> CD.cnt01.local/192.168.0.106:**2921 <http://192.168.0.106:2921>
>> 18:05:56,430 INFO [MGCP] tx=831178962 was executed normaly
>> 18:05:56,446 INFO [MGCP] tx=831178963 Started, message= MDCX
>> mobicents/cn...@192.168.0.106:**2427 <http:/...@192.168.0.106:2427>, call
>> agent = CNPC0186-
>> CD.cnt01.local/192.168.0.106:**2921 <http://192.168.0.106:2921>
>> 18:05:56,446 INFO [MGCP] tx=831178964 Started, message= MDCX
>> mobicents/cn...@192.168.0.106:**2427 <http:/...@192.168.0.106:2427>, call
>> agent = CNPC0186-
>> CD.cnt01.local/192.168.0.106:**2921 <http://192.168.0.106:2921>
>> 18:05:56,446 ERROR [MGCP] tx=831178964 Failed
>> org.mobicents.media.server.**mgcp.tx.cmd.**MgcpCommandException
>> at org.mobicents.media.server.**mgcp.tx.cmd.**ModifyConnectionCmd
>> $Modifier.perform(**ModifyConnectionCmd.java:106)
>> at org.mobicents.media.server.**scheduler.Task.run(Task.java:**109)
>> at org.mobicents.media.server.**scheduler.Scheduler
>> $CpuThread.run(Scheduler.java:**241)
>> 18:05:56,446 INFO [MGCP] tx=831178963 was executed normaly
>> 18:05:56,446 INFO [MGCP] tx=831178964 Rolled back
>> 18:05:56,462 INFO [MGCP] tx=831178965 Started, message= DLCX
>> mobicents/cn...@192.168.0.106:**2427 <http:/...@192.168.0.106:2427>, call
>> agent = CNPC0186-
>> CD.cnt01.local/192.168.0.106:**2921 <http://192.168.0.106:2921>
>> 18:05:56,462 INFO [MGCP] tx=831178966 Started, message= DLCX
>> mobicents/cn...@192.168.0.106:**2427 <http:/...@192.168.0.106:2427>, call
>> agent = CNPC0186-
>> CD.cnt01.local/192.168.0.106:**2921 <http://192.168.0.106:2921>
>> 18:05:56,462 ERROR [MGCP] tx=831178966 Failed
>> org.mobicents.media.server.**mgcp.tx.cmd.**MgcpCommandException
>> at org.mobicents.media.server.**mgcp.tx.cmd.**DeleteConnectionCmd
>> $Delete.perform(**DeleteConnectionCmd.java:117)
>> at org.mobicents.media.server.**scheduler.Task.run(Task.java:**109)
>> at org.mobicents.media.server.**scheduler.Scheduler
>> $CpuThread.run(Scheduler.java:**241)
>> 18:05:56,462 INFO [MGCP] tx=831178966 Rolled back
>> 18:05:56,462 INFO [MGCP] tx=831178965 was executed normaly
>> Drop packet
>> Drop packet
>> 18:06:05,321 INFO [MGCP] tx=831178967 Started, message= DLCX
>> mobicents/cn...@192.168.0.106:**2427 <http:/...@192.168.0.106:2427>, call
>> agent = CNPC0186-
>> CD.cnt01.local/192.168.0.106:**2921 <http://192.168.0.106:2921>
>> 18:06:05,337 INFO [MGCP] tx=831178967 was executed normaly
Hi everyone,
I am using the demo conference app (conference-demo-jsr309-1.7.0.FINAL.war) with latest version of mobicents sip servlet v1.7-FINAL and media server v2.4.0.CR1. I also replace jsr309 implementation with 2.4.0.CR1, but I get the same error in media server logs reported in this post.
org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd$Modifier.perform (ModifyConnectionCmd.java:111)
I have tested with numerous other versions (MSS v1.7 + MMS v3.0.CR1, MSS v1.6 + MMS v2.0.GA) and get similar problems, the signalling connects both parties but fails to connect media due to error in MMS.
Can someone recommend the tested version of MSS + MMS using conference-demo-jsr309-1.7.0.FINAL.war working successfully?
Thanks.
On Thursday, August 2, 2012 3:17:51 PM UTC-4, Jean Deruelle wrote:
> Can you try with the 2.4.0.CR1 release of MMS from http://mediaserver.googlecode.com/files/mms-server-2.4.0.CR1.zip and use the mobicents-jsr309-impl-2.4.0.CR1.jar bundled with it and use it to compile your app and put it in the application WEB-INF/lib directory
> Jean
> On Sat, Jul 7, 2012 at 2:11 AM, Martin Bayly <mar...@parkbayly.net> wrote:
> I'm also getting this exception using the mss 1.7.0 FINAL distribution and either the bundled MMS 2.1.0 Beta3 or a separately downloaded MMS 2.1.0 beta4.
> Should these demos work on Windows? (Windows 7).
> Or might they only work on Linux?
> On Sunday, June 3, 2012 3:17:22 AM UTC-7, Dennis Hu wrote:
> Hi all,
> I am trying the conference demo based on Sip Servlet1.7.0 and media
> server 2.1.0.BETA2. All are setup, the following exception output on
> media server log when i use a sip phone send invite "sip:sip-servlets-
Hi, I am using the latest MSS v2.0 with the bundled MMS v3.0.CR1 release. I also downloaded conference-demo-jsr309-2.0.0-FINAL.war file. To test things I ran a quick test with media-jsr309-servlet.war to make sure audio and call processing is working fine. I can dial 1010 and hear audio prompt for DTMF number that I press, so at this point everything is working fine. Next I deploy conference-demo-jsr309-2.0.0-FINAL.war file on MSS. I register two sip clients and place a call to "sip-servlets-conference" from one of the sip clients. Signalling looks fine with standard INVITE, 200 OK, ACK response. I do notice the following logs from MMS after connecting with sip client:
22:29:11,758 INFO [MGCP] tx=815448566 Started, message= CRCX mobicents/bridg...@192.168.1.100:2427, call agent = /192.168.1.100:2921 22:29:11,779 INFO [RtpConnectionImpl] FormatsRTPFormats{0 AudioFormat[PCMU,8000,8,mono],8 AudioFormat[PCMA,8000,8,mono],3 AudioFormat[GSM,8000,mono],104 AudioFormat[iLBC,8000,mono],96 AudioFormat[telephone-event,8000,mono]} 22:29:11,798 INFO [MGCP] tx=815448566 was executed normaly 22:29:11,819 INFO [MGCP] tx=815448567 Started, message= CRCX mobicents/bridg...@192.168.1.100:2427, call agent = /192.168.1.100:2921 22:29:11,860 INFO [MGCP] tx=815448567 was executed normaly 22:29:11,878 INFO [MGCP] tx=815448568 Started, message= MDCX mobicents/bridg...@192.168.1.100:2427, call agent = /192.168.1.100:2921 22:29:11,878 INFO [MGCP] tx=815448569 Started, message= MDCX mobicents/cn...@192.168.1.100:2427, call agent = /192.168.1.100:2921 22:29:11,898 INFO [MGCP] tx=815448568 was executed normaly 22:29:11,899 ERROR [MGCP] tx=815448569 Failed org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd$Modifier.perform (ModifyConnectionCmd.java:113) at org.mobicents.media.server.scheduler.Task.run(Task.java:134) at org.mobicents.media.server.scheduler.Scheduler$WorkerThread.run(Scheduler.j ava:352) 22:29:11,918 INFO [MGCP] tx=815448569 Rolled back 22:29:11,938 INFO [MGCP] tx=815448570 Started, message= DLCX mobicents/bridg...@192.168.1.100:2427, call agent = /192.168.1.100:2921 22:29:11,939 INFO [MGCP] tx=815448571 Started, message= DLCX mobicents/cn...@192.168.1.100:2427, call agent = /192.168.1.100:2921 22:29:11,959 ERROR [MGCP] tx=815448571 Failed org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException at org.mobicents.media.server.mgcp.tx.cmd.DeleteConnectionCmd$Delete.perform(D eleteConnectionCmd.java:154) at org.mobicents.media.server.scheduler.Task.run(Task.java:134) at org.mobicents.media.server.scheduler.Scheduler$WorkerThread.run(Scheduler.j ava:352) 22:29:11,979 INFO [MGCP] tx=815448570 was executed normaly 22:29:11,980 INFO [MGCP] tx=815448571 Rolled back
I then proceed to use a second sip client and issue a similar call to "sip-servlets-conference". Again the media server shows similar messages and second sip client establishes a connection. The two parties are essentially connected from a signalling point of view but no media is being sent to either party.
Can someone explain what is happening with media server logs and why there seems to be a problem setting up a conferencing between two parties.
On Wed, Oct 31, 2012 at 4:42 AM, Soto Man <soto.netwo...@gmail.com> wrote:
> Hi,
> I am using the latest MSS v2.0 with the bundled MMS v3.0.CR1 release. I
> also downloaded conference-demo-jsr309-2.0.0-FINAL.war file. To test
> things I ran a quick test with media-jsr309-servlet.war to make sure audio
> and call processing is working fine. I can dial 1010 and hear audio prompt
> for DTMF number that I press, so at this point everything is working fine.
> Next I deploy conference-demo-jsr309-2.0.0-FINAL.war file on MSS. I
> register two sip clients and place a call to "sip-servlets-conference" from
> one of the sip clients. Signalling looks fine with standard INVITE, 200
> OK, ACK response. I do notice the following logs from MMS after connecting
> with sip client:
> 22:29:11,758 INFO [MGCP] tx=815448566 Started, message= CRCX
> mobicents/bridg...@192.168.1.100:2427, call agent = /192.168.1.100:2921
> 22:29:11,779 INFO [RtpConnectionImpl] FormatsRTPFormats{0
> AudioFormat[PCMU,8000,8,mono],8 AudioFormat[PCMA,8000,8,mono],3
> AudioFormat[GSM,8000,mono],104 AudioFormat[iLBC,8000,mono],96
> AudioFormat[telephone-event,8000,mono]}
> 22:29:11,798 INFO [MGCP] tx=815448566 was executed normaly
> 22:29:11,819 INFO [MGCP] tx=815448567 Started, message= CRCX
> mobicents/bridg...@192.168.1.100:2427, call agent = /192.168.1.100:2921
> 22:29:11,860 INFO [MGCP] tx=815448567 was executed normaly
> 22:29:11,878 INFO [MGCP] tx=815448568 Started, message= MDCX
> mobicents/bridg...@192.168.1.100:2427, call agent = /192.168.1.100:2921
> 22:29:11,878 INFO [MGCP] tx=815448569 Started, message= MDCX
> mobicents/cn...@192.168.1.100:2427, call agent = /192.168.1.100:2921
> 22:29:11,898 INFO [MGCP] tx=815448568 was executed normaly
> 22:29:11,899 ERROR [MGCP] tx=815448569 Failed
> org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
> at
> org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd$Modifier.perform (ModifyConnectionCmd.java:113)
> at org.mobicents.media.server.scheduler.Task.run(Task.java:134)
> at
> org.mobicents.media.server.scheduler.Scheduler$WorkerThread.run(Scheduler.j ava:352)
> 22:29:11,918 INFO [MGCP] tx=815448569 Rolled back
> 22:29:11,938 INFO [MGCP] tx=815448570 Started, message= DLCX
> mobicents/bridg...@192.168.1.100:2427, call agent = /192.168.1.100:2921
> 22:29:11,939 INFO [MGCP] tx=815448571 Started, message= DLCX
> mobicents/cn...@192.168.1.100:2427, call agent = /192.168.1.100:2921
> 22:29:11,959 ERROR [MGCP] tx=815448571 Failed
> org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
> at
> org.mobicents.media.server.mgcp.tx.cmd.DeleteConnectionCmd$Delete.perform(D eleteConnectionCmd.java:154)
> at org.mobicents.media.server.scheduler.Task.run(Task.java:134)
> at
> org.mobicents.media.server.scheduler.Scheduler$WorkerThread.run(Scheduler.j ava:352)
> 22:29:11,979 INFO [MGCP] tx=815448570 was executed normaly
> 22:29:11,980 INFO [MGCP] tx=815448571 Rolled back
> I then proceed to use a second sip client and issue a similar call to
> "sip-servlets-conference". Again the media server shows similar messages
> and second sip client establishes a connection. The two parties are
> essentially connected from a signalling point of view but no media is being
> sent to either party.
> Can someone explain what is happening with media server logs and why there
> seems to be a problem setting up a conferencing between two parties.
On Wednesday, October 31, 2012 6:24:29 AM UTC-4, gvag wrote:
> Hi,
> I will check the application "conference-demo-jsr309" and i will come back > to you with my update.
> George
> On Wed, Oct 31, 2012 at 4:42 AM, Soto Man <soto.n...@gmail.com<javascript:> > > wrote:
>> Hi, >> I am using the latest MSS v2.0 with the bundled MMS v3.0.CR1 release. >> I also downloaded conference-demo-jsr309-2.0.0-FINAL.war file. To test >> things I ran a quick test with media-jsr309-servlet.war to make sure audio >> and call processing is working fine. I can dial 1010 and hear audio prompt >> for DTMF number that I press, so at this point everything is working fine. >> Next I deploy conference-demo-jsr309-2.0.0-FINAL.war file on MSS. I >> register two sip clients and place a call to "sip-servlets-conference" from >> one of the sip clients. Signalling looks fine with standard INVITE, 200 >> OK, ACK response. I do notice the following logs from MMS after connecting >> with sip client:
>> 22:29:11,758 INFO [MGCP] tx=815448566 Started, message= CRCX >> mobicents/bridg...@192.168.1.100:2427, call agent = /192.168.1.100:2921 >> 22:29:11,779 INFO [RtpConnectionImpl] FormatsRTPFormats{0 >> AudioFormat[PCMU,8000,8,mono],8 AudioFormat[PCMA,8000,8,mono],3 >> AudioFormat[GSM,8000,mono],104 AudioFormat[iLBC,8000,mono],96 >> AudioFormat[telephone-event,8000,mono]} >> 22:29:11,798 INFO [MGCP] tx=815448566 was executed normaly >> 22:29:11,819 INFO [MGCP] tx=815448567 Started, message= CRCX >> mobicents/bridg...@192.168.1.100:2427, call agent = /192.168.1.100:2921 >> 22:29:11,860 INFO [MGCP] tx=815448567 was executed normaly >> 22:29:11,878 INFO [MGCP] tx=815448568 Started, message= MDCX >> mobicents/bridg...@192.168.1.100:2427, call agent = /192.168.1.100:2921 >> 22:29:11,878 INFO [MGCP] tx=815448569 Started, message= MDCX >> mobicents/cn...@192.168.1.100:2427, call agent = /192.168.1.100:2921 >> 22:29:11,898 INFO [MGCP] tx=815448568 was executed normaly >> 22:29:11,899 ERROR [MGCP] tx=815448569 Failed >> org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException >> at >> org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd$Modifier.perform (ModifyConnectionCmd.java:113) >> at org.mobicents.media.server.scheduler.Task.run(Task.java:134) >> at >> org.mobicents.media.server.scheduler.Scheduler$WorkerThread.run(Scheduler.j ava:352) >> 22:29:11,918 INFO [MGCP] tx=815448569 Rolled back >> 22:29:11,938 INFO [MGCP] tx=815448570 Started, message= DLCX >> mobicents/bridg...@192.168.1.100:2427, call agent = /192.168.1.100:2921 >> 22:29:11,939 INFO [MGCP] tx=815448571 Started, message= DLCX >> mobicents/cn...@192.168.1.100:2427, call agent = /192.168.1.100:2921 >> 22:29:11,959 ERROR [MGCP] tx=815448571 Failed >> org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException >> at >> org.mobicents.media.server.mgcp.tx.cmd.DeleteConnectionCmd$Delete.perform(D eleteConnectionCmd.java:154) >> at org.mobicents.media.server.scheduler.Task.run(Task.java:134) >> at >> org.mobicents.media.server.scheduler.Scheduler$WorkerThread.run(Scheduler.j ava:352) >> 22:29:11,979 INFO [MGCP] tx=815448570 was executed normaly >> 22:29:11,980 INFO [MGCP] tx=815448571 Rolled back
>> I then proceed to use a second sip client and issue a similar call to >> "sip-servlets-conference". Again the media server shows similar messages >> and second sip client establishes a connection. The two parties are >> essentially connected from a signalling point of view but no media is being >> sent to either party.
>> Can someone explain what is happening with media server logs and why >> there seems to be a problem setting up a conferencing between two parties.
On Sat, Nov 3, 2012 at 5:04 PM, Soto Man <soto.netwo...@gmail.com> wrote:
> Thanks, post a message once you are done.
> On Wednesday, October 31, 2012 6:24:29 AM UTC-4, gvag wrote:
>> Hi,
>> I will check the application "conference-demo-jsr309" and i will come
>> back to you with my update.
>> George
>> On Wed, Oct 31, 2012 at 4:42 AM, Soto Man <soto.n...@gmail.com> wrote:
>>> Hi,
>>> I am using the latest MSS v2.0 with the bundled MMS v3.0.CR1 release.
>>> I also downloaded conference-demo-jsr309-2.0.0-**FINAL.war file. To
>>> test things I ran a quick test with media-jsr309-servlet.war to make sure
>>> audio and call processing is working fine. I can dial 1010 and hear audio
>>> prompt for DTMF number that I press, so at this point everything is working
>>> fine. Next I deploy conference-demo-jsr309-2.0.0-**FINAL.war file on
>>> MSS. I register two sip clients and place a call to
>>> "sip-servlets-conference" from one of the sip clients. Signalling looks
>>> fine with standard INVITE, 200 OK, ACK response. I do notice the following
>>> logs from MMS after connecting with sip client:
>>> 22:29:11,758 INFO [MGCP] tx=815448566 Started, message= CRCX
>>> mobicents/bridg...@192.168.1.**100:2427 <http://192.168.1.100:2427>,
>>> call agent = /192.168.1.100:2921
>>> 22:29:11,779 INFO [RtpConnectionImpl] FormatsRTPFormats{0
>>> AudioFormat[PCMU,8000,8,mono],**8 AudioFormat[PCMA,8000,8,mono],**3
>>> AudioFormat[GSM,8000,mono],104 AudioFormat[iLBC,8000,mono],96
>>> AudioFormat[telephone-event,**8000,mono]}
>>> 22:29:11,798 INFO [MGCP] tx=815448566 was executed normaly
>>> 22:29:11,819 INFO [MGCP] tx=815448567 Started, message= CRCX
>>> mobicents/bridg...@192.168.1.**100:2427 <http:/...@192.168.1.100:2427>,
>>> call agent = /192.168.1.100:2921
>>> 22:29:11,860 INFO [MGCP] tx=815448567 was executed normaly
>>> 22:29:11,878 INFO [MGCP] tx=815448568 Started, message= MDCX
>>> mobicents/bridg...@192.168.1.**100:2427 <http:/...@192.168.1.100:2427>,
>>> call agent = /192.168.1.100:2921
>>> 22:29:11,878 INFO [MGCP] tx=815448569 Started, message= MDCX
>>> mobicents/cn...@192.168.1.100:**2427 <http:/...@192.168.1.100:2427>,
>>> call agent = /192.168.1.100:2921
>>> 22:29:11,898 INFO [MGCP] tx=815448568 was executed normaly
>>> 22:29:11,899 ERROR [MGCP] tx=815448569 Failed
>>> org.mobicents.media.server.**mgcp.tx.cmd.**MgcpCommandException
>>> at org.mobicents.media.server.**mgcp.tx.cmd.**
>>> ModifyConnectionCmd$Modifier.**perform(ModifyConnectionCmd.**java:113)
>>> at org.mobicents.media.server.**scheduler.Task.run(Task.java:**134)
>>> at org.mobicents.media.server.**scheduler.Scheduler$**
>>> WorkerThread.run(Scheduler.**java:352)
>>> 22:29:11,918 INFO [MGCP] tx=815448569 Rolled back
>>> 22:29:11,938 INFO [MGCP] tx=815448570 Started, message= DLCX
>>> mobicents/bridg...@192.168.1.**100:2427 <http:/...@192.168.1.100:2427>,
>>> call agent = /192.168.1.100:2921
>>> 22:29:11,939 INFO [MGCP] tx=815448571 Started, message= DLCX
>>> mobicents/cn...@192.168.1.100:**2427 <http:/...@192.168.1.100:2427>,
>>> call agent = /192.168.1.100:2921
>>> 22:29:11,959 ERROR [MGCP] tx=815448571 Failed
>>> org.mobicents.media.server.**mgcp.tx.cmd.**MgcpCommandException
>>> at org.mobicents.media.server.**mgcp.tx.cmd.**
>>> DeleteConnectionCmd$Delete.**perform(DeleteConnectionCmd.**java:154)
>>> at org.mobicents.media.server.**scheduler.Task.run(Task.java:**134)
>>> at org.mobicents.media.server.**scheduler.Scheduler$**
>>> WorkerThread.run(Scheduler.**java:352)
>>> 22:29:11,979 INFO [MGCP] tx=815448570 was executed normaly
>>> 22:29:11,980 INFO [MGCP] tx=815448571 Rolled back
>>> I then proceed to use a second sip client and issue a similar call to
>>> "sip-servlets-conference". Again the media server shows similar messages
>>> and second sip client establishes a connection. The two parties are
>>> essentially connected from a signalling point of view but no media is being
>>> sent to either party.
>>> Can someone explain what is happening with media server logs and why
>>> there seems to be a problem setting up a conferencing between two parties.
Thanks for update. I just checked out the files from git and running "mvn clean install" at command line but getting the following error:
[WARNING] The requested profile "jboss-deprecated-repository" could not be activated because it does not exist. [WARNING] The requested profile "jboss-public-repository-group" could not be activated because it does not exist. [ERROR] Failed to execute goal on project conference-demo-jsr309: Could not resolve dependencies for project org.mobicents.servlet.sip.examples:conference-demo-jsr309:war:2.1.0-SNAPSHO T: The following artifacts could not be resolved: org.mobicents.servlet.sip:sip-servlets-spec:jar:2.1.0-SNAPSHOT, org.mobicents.servlet.sip:sip-servlets-client:jar:2.1.0-SNAPSHOT: Failure to find org.mobicents.servlet.sip:sip-servlets-spec:jar:2.1.0-SNAPSHOT in http://gwt-maven.googlecode.com/svn/trunk/mavenrepo/ was cached in the local repository, resolution will not be reattempted until the update interval of gwt-maven has elapsed or updates are forced -> [Help 1]
> Please report back if everything is ok or you see any problems.
> George
> On Sat, Nov 3, 2012 at 5:04 PM, Soto Man <soto.n...@gmail.com<javascript:> > > wrote:
>> Thanks, post a message once you are done.
>> On Wednesday, October 31, 2012 6:24:29 AM UTC-4, gvag wrote:
>>> Hi,
>>> I will check the application "conference-demo-jsr309" and i will come >>> back to you with my update.
>>> George
>>> On Wed, Oct 31, 2012 at 4:42 AM, Soto Man <soto.n...@gmail.com> wrote:
>>>> Hi, >>>> I am using the latest MSS v2.0 with the bundled MMS v3.0.CR1 release. >>>> I also downloaded conference-demo-jsr309-2.0.0-**FINAL.war file. To >>>> test things I ran a quick test with media-jsr309-servlet.war to make sure >>>> audio and call processing is working fine. I can dial 1010 and hear audio >>>> prompt for DTMF number that I press, so at this point everything is working >>>> fine. Next I deploy conference-demo-jsr309-2.0.0-**FINAL.war file on >>>> MSS. I register two sip clients and place a call to >>>> "sip-servlets-conference" from one of the sip clients. Signalling looks >>>> fine with standard INVITE, 200 OK, ACK response. I do notice the following >>>> logs from MMS after connecting with sip client:
>>>> 22:29:11,758 INFO [MGCP] tx=815448566 Started, message= CRCX >>>> mobicents/bridg...@192.168.1.**100:2427 <http://192.168.1.100:2427>, >>>> call agent = /192.168.1.100:2921 >>>> 22:29:11,779 INFO [RtpConnectionImpl] FormatsRTPFormats{0 >>>> AudioFormat[PCMU,8000,8,mono],**8 AudioFormat[PCMA,8000,8,mono],**3 >>>> AudioFormat[GSM,8000,mono],104 AudioFormat[iLBC,8000,mono],96 >>>> AudioFormat[telephone-event,**8000,mono]} >>>> 22:29:11,798 INFO [MGCP] tx=815448566 was executed normaly >>>> 22:29:11,819 INFO [MGCP] tx=815448567 Started, message= CRCX >>>> mobicents/bridg...@192.168.1.**100:2427 <http:/...@192.168.1.100:2427>, >>>> call agent = /192.168.1.100:2921 >>>> 22:29:11,860 INFO [MGCP] tx=815448567 was executed normaly >>>> 22:29:11,878 INFO [MGCP] tx=815448568 Started, message= MDCX >>>> mobicents/bridg...@192.168.1.**100:2427 <http:/...@192.168.1.100:2427>, >>>> call agent = /192.168.1.100:2921 >>>> 22:29:11,878 INFO [MGCP] tx=815448569 Started, message= MDCX >>>> mobicents/cn...@192.168.1.100:**2427 <http:/...@192.168.1.100:2427>, >>>> call agent = /192.168.1.100:2921 >>>> 22:29:11,898 INFO [MGCP] tx=815448568 was executed normaly >>>> 22:29:11,899 ERROR [MGCP] tx=815448569 Failed >>>> org.mobicents.media.server.**mgcp.tx.cmd.**MgcpCommandException >>>> at org.mobicents.media.server.**mgcp.tx.cmd.** >>>> ModifyConnectionCmd$Modifier.**perform(ModifyConnectionCmd.**java:113) >>>> at org.mobicents.media.server.**scheduler.Task.run(Task.java:**134) >>>> at org.mobicents.media.server.**scheduler.Scheduler$** >>>> WorkerThread.run(Scheduler.**java:352) >>>> 22:29:11,918 INFO [MGCP] tx=815448569 Rolled back >>>> 22:29:11,938 INFO [MGCP] tx=815448570 Started, message= DLCX >>>> mobicents/bridg...@192.168.1.**100:2427 <http:/...@192.168.1.100:2427>, >>>> call agent = /192.168.1.100:2921 >>>> 22:29:11,939 INFO [MGCP] tx=815448571 Started, message= DLCX >>>> mobicents/cn...@192.168.1.100:**2427 <http:/...@192.168.1.100:2427>, >>>> call agent = /192.168.1.100:2921 >>>> 22:29:11,959 ERROR [MGCP] tx=815448571 Failed >>>> org.mobicents.media.server.**mgcp.tx.cmd.**MgcpCommandException >>>> at org.mobicents.media.server.**mgcp.tx.cmd.** >>>> DeleteConnectionCmd$Delete.**perform(DeleteConnectionCmd.**java:154) >>>> at org.mobicents.media.server.**scheduler.Task.run(Task.java:**134) >>>> at org.mobicents.media.server.**scheduler.Scheduler$** >>>> WorkerThread.run(Scheduler.**java:352) >>>> 22:29:11,979 INFO [MGCP] tx=815448570 was executed normaly >>>> 22:29:11,980 INFO [MGCP] tx=815448571 Rolled back
>>>> I then proceed to use a second sip client and issue a similar call to >>>> "sip-servlets-conference". Again the media server shows similar messages >>>> and second sip client establishes a connection. The two parties are >>>> essentially connected from a signalling point of view but no media is being >>>> sent to either party.
>>>> Can someone explain what is happening with media server logs and why >>>> there seems to be a problem setting up a conferencing between two parties.
On Thu, Nov 8, 2012 at 4:41 AM, Soto Man <soto.netwo...@gmail.com> wrote:
> Thanks for update. I just checked out the files from git and running "mvn
> clean install" at command line but getting the following error:
> [WARNING] The requested profile "jboss-deprecated-repository" could not be
> activated because it does not exist.
> [WARNING] The requested profile "jboss-public-repository-group" could not
> be activated because it does not exist.
> [ERROR] Failed to execute goal on project conference-demo-jsr309: Could
> not resolve dependencies for project
> org.mobicents.servlet.sip.examples:conference-demo-jsr309:war:2.1.0-SNAPSHO T:
> The following artifacts could not be resolved:
> org.mobicents.servlet.sip:sip-servlets-spec:jar:2.1.0-SNAPSHOT,
> org.mobicents.servlet.sip:sip-servlets-client:jar:2.1.0-SNAPSHOT: Failure
> to find org.mobicents.servlet.sip:sip-servlets-spec:jar:2.1.0-SNAPSHOT in
> http://gwt-maven.googlecode.com/svn/trunk/mavenrepo/ was cached in the
> local repository, resolution will not be reattempted until the update
> interval of gwt-maven has elapsed or updates are forced -> [Help 1]
> Is the pom.xml file missing repository location?
> On Monday, November 5, 2012 9:59:45 AM UTC-5, gvag wrote:
>> Please report back if everything is ok or you see any problems.
>> George
>> On Sat, Nov 3, 2012 at 5:04 PM, Soto Man <soto.n...@gmail.com> wrote:
>>> Thanks, post a message once you are done.
>>> On Wednesday, October 31, 2012 6:24:29 AM UTC-4, gvag wrote:
>>>> Hi,
>>>> I will check the application "conference-demo-jsr309" and i will come
>>>> back to you with my update.
>>>> George
>>>> On Wed, Oct 31, 2012 at 4:42 AM, Soto Man <soto.n...@gmail.com> wrote:
>>>>> Hi,
>>>>> I am using the latest MSS v2.0 with the bundled MMS v3.0.CR1
>>>>> release. I also downloaded conference-demo-jsr309-2.0.0-**F**INAL.war
>>>>> file. To test things I ran a quick test with media-jsr309-servlet.war to
>>>>> make sure audio and call processing is working fine. I can dial 1010 and
>>>>> hear audio prompt for DTMF number that I press, so at this point everything
>>>>> is working fine. Next I deploy conference-demo-jsr309-2.0.0-**F**INAL.war
>>>>> file on MSS. I register two sip clients and place a call to
>>>>> "sip-servlets-conference" from one of the sip clients. Signalling looks
>>>>> fine with standard INVITE, 200 OK, ACK response. I do notice the following
>>>>> logs from MMS after connecting with sip client:
>>>>> 22:29:11,758 INFO [MGCP] tx=815448566 Started, message= CRCX
>>>>> mobicents/bridg...@192.168.1.**1**00:2427 <http://192.168.1.100:2427>,
>>>>> call agent = /192.168.1.100:2921
>>>>> 22:29:11,779 INFO [RtpConnectionImpl] FormatsRTPFormats{0
>>>>> AudioFormat[PCMU,8000,8,mono],****8 AudioFormat[PCMA,8000,8,mono],****3
>>>>> AudioFormat[GSM,8000,mono],104 AudioFormat[iLBC,8000,mono],96
>>>>> AudioFormat[telephone-event,**80**00,mono]}
>>>>> 22:29:11,798 INFO [MGCP] tx=815448566 was executed normaly
>>>>> 22:29:11,819 INFO [MGCP] tx=815448567 Started, message= CRCX
>>>>> mobicents/bridg...@192.168.1.**1**00:2427<http:/...@192.168.1.100:2427>,
>>>>> call agent = /192.168.1.100:2921
>>>>> 22:29:11,860 INFO [MGCP] tx=815448567 was executed normaly
>>>>> 22:29:11,878 INFO [MGCP] tx=815448568 Started, message= MDCX
>>>>> mobicents/bridg...@192.168.1.**1**00:2427<http:/...@192.168.1.100:2427>,
>>>>> call agent = /192.168.1.100:2921
>>>>> 22:29:11,878 INFO [MGCP] tx=815448569 Started, message= MDCX
>>>>> mobicents/cn...@192.168.1.100:****2427 <http:/...@192.168.1.100:2427>,
>>>>> call agent = /192.168.1.100:2921
>>>>> 22:29:11,898 INFO [MGCP] tx=815448568 was executed normaly
>>>>> 22:29:11,899 ERROR [MGCP] tx=815448569 Failed
>>>>> org.mobicents.media.server.**mgc**p.tx.cmd.**MgcpCommandException
>>>>> at org.mobicents.media.server.**mgc**p.tx.cmd.**ModifyConnectionCmd$*
>>>>> *Modifier.**perform(**ModifyConnectionCmd.**java:113)
>>>>> at org.mobicents.media.server.**sch**eduler.Task.run(Task.java:**134)
>>>>> at org.mobicents.media.server.**sch**eduler.Scheduler$**WorkerThread.*
>>>>> *run(Scheduler.**java:352)
>>>>> 22:29:11,918 INFO [MGCP] tx=815448569 Rolled back
>>>>> 22:29:11,938 INFO [MGCP] tx=815448570 Started, message= DLCX
>>>>> mobicents/bridg...@192.168.1.**1**00:2427<http:/...@192.168.1.100:2427>,
>>>>> call agent = /192.168.1.100:2921
>>>>> 22:29:11,939 INFO [MGCP] tx=815448571 Started, message= DLCX
>>>>> mobicents/cn...@192.168.1.100:****2427 <http:/...@192.168.1.100:2427>,
>>>>> call agent = /192.168.1.100:2921
>>>>> 22:29:11,959 ERROR [MGCP] tx=815448571 Failed
>>>>> org.mobicents.media.server.**mgc**p.tx.cmd.**MgcpCommandException
>>>>> at org.mobicents.media.server.**mgc**p.tx.cmd.**DeleteConnectionCmd$**
>>>>> Delete.**perform(**DeleteConnectionCmd.**java:154)
>>>>> at org.mobicents.media.server.**sch**eduler.Task.run(Task.java:**134)
>>>>> at org.mobicents.media.server.**sch**eduler.Scheduler$**WorkerThread.*
>>>>> *run(Scheduler.**java:352)
>>>>> 22:29:11,979 INFO [MGCP] tx=815448570 was executed normaly
>>>>> 22:29:11,980 INFO [MGCP] tx=815448571 Rolled back
>>>>> I then proceed to use a second sip client and issue a similar call to
>>>>> "sip-servlets-conference". Again the media server shows similar messages
>>>>> and second sip client establishes a connection. The two parties are
>>>>> essentially connected from a signalling point of view but no media is being
>>>>> sent to either party.
>>>>> Can someone explain what is happening with media server logs and why
>>>>> there seems to be a problem setting up a conferencing between two parties.
I am testing the latest binary build base on link provided before.
When I connect sip client (xlite) to the conference service the INVITE comes in to MSS follow by outbound 180 Ringing and 200 OK message to sip client, but sip client just sends back ACK and immediately sends BYE back to MSS. I think the problem is 200 OK does not have SDP to identify media negotiation. No errors or warning in media server logs. I attach the server.log file from MSS to review, but is there something that needs to be setup in order for the connection to be establish?
On Friday, November 9, 2012 8:39:04 AM UTC-5, Soto Man wrote:
> I am testing the latest binary build base on link provided before.
> When I connect sip client (xlite) to the conference service the INVITE > comes in to MSS follow by outbound 180 Ringing and 200 OK message to sip > client, but sip client just sends back ACK and immediately sends BYE back > to MSS. I think the problem is 200 OK does not have SDP to identify media > negotiation. No errors or warning in media server logs. I attach the > server.log file from MSS to review, but is there something that needs to be > setup in order for the connection to be establish?
On Friday, November 9, 2012 8:39:04 AM UTC-5, Soto Man wrote:
> I am testing the latest binary build base on link provided before.
> When I connect sip client (xlite) to the conference service the INVITE > comes in to MSS follow by outbound 180 Ringing and 200 OK message to sip > client, but sip client just sends back ACK and immediately sends BYE back > to MSS. I think the problem is 200 OK does not have SDP to identify media > negotiation. No errors or warning in media server logs. I attach the > server.log file from MSS to review, but is there something that needs to be > setup in order for the connection to be establish?
> Would appreciate any feedback, thanks in advance.
> On Friday, November 9, 2012 8:39:04 AM UTC-5, Soto Man wrote:
>> I am testing the latest binary build base on link provided before.
>> When I connect sip client (xlite) to the conference service the INVITE
>> comes in to MSS follow by outbound 180 Ringing and 200 OK message to sip
>> client, but sip client just sends back ACK and immediately sends BYE back
>> to MSS. I think the problem is 200 OK does not have SDP to identify media
>> negotiation. No errors or warning in media server logs. I attach the
>> server.log file from MSS to review, but is there something that needs to be
>> setup in order for the connection to be establish?
On Monday, November 12, 2012 12:11:58 PM UTC-5, gvag wrote:
> Hi,
> I will check the logs you sent and I will let you know.
> George > On Nov 12, 2012 1:59 PM, "Soto Man" <soto.n...@gmail.com <javascript:>> > wrote:
>> Would appreciate any feedback, thanks in advance.
>> On Friday, November 9, 2012 8:39:04 AM UTC-5, Soto Man wrote:
>>> I am testing the latest binary build base on link provided before.
>>> When I connect sip client (xlite) to the conference service the INVITE >>> comes in to MSS follow by outbound 180 Ringing and 200 OK message to sip >>> client, but sip client just sends back ACK and immediately sends BYE back >>> to MSS. I think the problem is 200 OK does not have SDP to identify media >>> negotiation. No errors or warning in media server logs. I attach the >>> server.log file from MSS to review, but is there something that needs to be >>> setup in order for the connection to be establish?
On Monday, November 12, 2012 12:11:58 PM UTC-5, gvag wrote:
> Hi,
> I will check the logs you sent and I will let you know.
> George > On Nov 12, 2012 1:59 PM, "Soto Man" <soto.n...@gmail.com <javascript:>> > wrote:
>> Would appreciate any feedback, thanks in advance.
>> On Friday, November 9, 2012 8:39:04 AM UTC-5, Soto Man wrote:
>>> I am testing the latest binary build base on link provided before.
>>> When I connect sip client (xlite) to the conference service the INVITE >>> comes in to MSS follow by outbound 180 Ringing and 200 OK message to sip >>> client, but sip client just sends back ACK and immediately sends BYE back >>> to MSS. I think the problem is 200 OK does not have SDP to identify media >>> negotiation. No errors or warning in media server logs. I attach the >>> server.log file from MSS to review, but is there something that needs to be >>> setup in order for the connection to be establish?
Hi, So I've gotten past the problem of connecting sip clients to conference server. Now I have two sip clients connected in the conference service and each client can hear each other talk :) However, if I leave the conference open for more than 3 minutes the logs show
[org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl] (Timer-16) Invalidating the following sip application session afb50070-e267-4d99-a598-d58bdfc6e390:Conference
In fact the logs show the invalidate message exactly 3 mins after the conference is establish. I looked over the code for conference service and do not see any servlet timers or specific code that invalidates the sip app session after a certain duration. So I am wondering if there is a special configuration that I am not aware that invalidates sip app session after a certain period? What about sip servlet management console server settings?
On Monday, November 12, 2012 12:11:58 PM UTC-5, gvag wrote:
> Hi,
> I will check the logs you sent and I will let you know.
> George > On Nov 12, 2012 1:59 PM, "Soto Man" <soto.n...@gmail.com <javascript:>> > wrote:
>> Would appreciate any feedback, thanks in advance.
>> On Friday, November 9, 2012 8:39:04 AM UTC-5, Soto Man wrote:
>>> I am testing the latest binary build base on link provided before.
>>> When I connect sip client (xlite) to the conference service the INVITE >>> comes in to MSS follow by outbound 180 Ringing and 200 OK message to sip >>> client, but sip client just sends back ACK and immediately sends BYE back >>> to MSS. I think the problem is 200 OK does not have SDP to identify media >>> negotiation. No errors or warning in media server logs. I attach the >>> server.log file from MSS to review, but is there something that needs to be >>> setup in order for the connection to be establish?
One more thing to note, after the sip application session is invalidated, then either client cannot hear any audio (dead silence). Sending a BYE from client results in log message indicating that the sip application session has been invalidated.