MgcpCommandException in media server when trying the conference-demo-1.7.0.war
321 views
Skip to first unread message
Dennis Hu
Jun 3, 2012, 6:17:22 AM6/3/12
to mobicents-public
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-
confe...@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/cnf/$@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/cnf/5...@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/cnf/5...@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/cnf/4...@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/cnf/5...@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/cnf/4...@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/cnf/5...@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
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-
confe...@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/cnf/$@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/cnf/5...@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/cnf/5...@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/cnf/4...@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/cnf/5...@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/cnf/4...@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/cnf/5...@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
Dennis Hu
Jun 4, 2012, 4:42:19 AM6/4/12
to mobicents-public
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".
> mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
> mobicents/cn...@192.168.0.106:2427, call agent = CNPC0186-
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-
>
> 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-
> 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
> 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-
> 18:05:56,368 INFO [MGCP] tx=831178961 was executed norma ly
> 18:05:56,399 INFO [MGCP] tx=831178962 Started, message= CRCX
> 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-
> 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 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-
> 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 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-
> 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
Dennis Hu
Jun 4, 2012, 5:34:17 AM6/4/12
to mobicents-public
I saw that the following message replaced the "@" with "at".
[MGCP] tx=847806577 Started, message= CRCX mobicents/cnf/
$at192.168.0.106:2427
[MGCP] tx=847806578 Started, message= CRCX mobicents/cnf/
5at192.168.0.106:2427
[MGCP] tx=847806579 Started, message= MDCX mobicents/cnf/
5at192.168.0.106:2427
[MGCP] tx=847806580 Started, message= MDCX mobicents/cnf/
4at192.168.0.106:2427
After that, the following exception is output.
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
[MGCP] tx=847806577 Started, message= CRCX mobicents/cnf/
$at192.168.0.106:2427
[MGCP] tx=847806578 Started, message= CRCX mobicents/cnf/
5at192.168.0.106:2427
[MGCP] tx=847806579 Started, message= MDCX mobicents/cnf/
5at192.168.0.106:2427
[MGCP] tx=847806580 Started, message= MDCX mobicents/cnf/
4at192.168.0.106:2427
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
at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd
$Modifier.perform(ModifyConnectionCmd.java:106)
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
Dennis Hu
Jun 4, 2012, 7:26:54 AM6/4/12
to mobicents-public
When i use mms-server2.2.0-final, the following exception is found.
19:23:09,184 INFO [MGCP] tx=857391584 Started, message= CRCX
mobicents/ivr/$at192.168.0.106:2427, call agent = CNPC0186-
CD.cnt01.local/192.168.0.106:2921
19:23:09,277 INFO [MGCP] tx=857391584 was executed normaly
19:23:09,324 INFO [MGCP] tx=857391585 Started, message= MDCX
mobicents/ivr/1at192.168.0.106:2427, call agent = CNPC0186-
CD.cnt01.local/192.168.0.106:2921
19:23:09,324 INFO [MGCP] tx=857391586 Started, message= MDCX
mobicents/cnf/1at192.168.0.106:2427, call agent = CNPC0186-
CD.cnt01.local/192.168.0.106:2921
19:23:09,356 INFO [MGCP] tx=857391585 was executed normaly
19:23:09,387 ERROR [MGCP] tx=857391586 Failed
org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd
$Modifier.perform(ModifyConnectionCmd.java:111)
at org.mobicents.media.server.scheduler.Task.run(Task.java:130)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
19:23:09,184 INFO [MGCP] tx=857391584 Started, message= CRCX
mobicents/ivr/$at192.168.0.106:2427, call agent = CNPC0186-
CD.cnt01.local/192.168.0.106:2921
19:23:09,277 INFO [MGCP] tx=857391584 was executed normaly
19:23:09,324 INFO [MGCP] tx=857391585 Started, message= MDCX
mobicents/ivr/1at192.168.0.106:2427, call agent = CNPC0186-
CD.cnt01.local/192.168.0.106:2921
19:23:09,324 INFO [MGCP] tx=857391586 Started, message= MDCX
mobicents/cnf/1at192.168.0.106:2427, call agent = CNPC0186-
CD.cnt01.local/192.168.0.106:2921
19:23:09,356 INFO [MGCP] tx=857391585 was executed normaly
19:23:09,387 ERROR [MGCP] tx=857391586 Failed
org.mobicents.media.server.mgcp.tx.cmd.MgcpCommandException
at org.mobicents.media.server.mgcp.tx.cmd.ModifyConnectionCmd
$Modifier.perform(ModifyConnectionCmd.java:111)
at org.mobicents.media.server.scheduler.Task.run(Task.java:130)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Dennis Hu
Jun 5, 2012, 3:52:40 AM6/5/12
to mobicents-public
I am appreciated your help. Anyone do me a favor? I have spent several
days on this problem.
days on this problem.
yulian_o
Jun 5, 2012, 6:31:31 AM6/5/12
to mobicent...@googlegroups.com
Hello
Exception in 2.2.0-Final means that you are using invalid call id. ( raw 111 ).
Please check the example code for correct call id usage.
Best regards
Yulian Oifa
Exception in 2.2.0-Final means that you are using invalid call id. ( raw 111 ).
Please check the example code for correct call id usage.
Best regards
Yulian Oifa
thangtq
Jun 5, 2012, 10:41:08 AM6/5/12
to mobicents-public
Hi Dennis,
which tools ? do you use to setup the conference demo ?
for:eclipse ...
which tools ? do you use to setup the conference demo ?
for:eclipse ...
Martin Bayly
Jul 6, 2012, 8:11:34 PM7/6/12
to mobicent...@googlegroups.com
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?
Jean Deruelle
Aug 2, 2012, 3:17:51 PM8/2/12
to mobicent...@googlegroups.com
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
Jean
yulian_o
Oct 26, 2012, 11:50:00 AM10/26/12
to mobicent...@googlegroups.com
Hello Please use latest mss and latest mms release and post the error you are having ( MMS should be 3.0.0.CR1 )
Best regards
Yulian Oifa
Best regards
Yulian Oifa
Soto Man
Oct 30, 2012, 10:42:46 PM10/30/12
to mobicent...@googlegroups.com
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/bridge/$@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/bridge/5...@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/bridge/5...@192.168.1.100:2427, call agent = /192.168.1.100:2921
22:29:11,878 INFO [MGCP] tx=815448569 Started, message= MDCX mobicents/cnf/1...@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/bridge/5...@192.168.1.100:2427, call agent = /192.168.1.100:2921
22:29:11,939 INFO [MGCP] tx=815448571 Started, message= DLCX mobicents/cnf/1...@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.
George Vagenas
Oct 31, 2012, 6:24:27 AM10/31/12
to mobicent...@googlegroups.com
Hi,
I will check the application "conference-demo-jsr309" and i will come back to you with my update.
George
--
George Vagenas
George Vagenas
Soto Man
Nov 3, 2012, 11:04:59 AM11/3/12
to mobicent...@googlegroups.com
Thanks, post a message once you are done.
George Vagenas
Nov 5, 2012, 9:59:43 AM11/5/12
to mobicent...@googlegroups.com
Hi,
Please check out the application again (http://code.google.com/p/sipservlets/source/browse/#git%2Fsip-servlets-examples%2Fconference-demo-jsr309) and build it. It should be working fine now.
Please report back if everything is ok or you see any problems.
George
--
George Vagenas
George Vagenas
Soto Man
Nov 7, 2012, 10:41:54 PM11/7/12
to mobicent...@googlegroups.com
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-SNAPSHOT: 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?
Jean Deruelle
Nov 8, 2012, 6:54:37 AM11/8/12
to mobicent...@googlegroups.com
You can get the latest binary from https://oss.sonatype.org/content/repositories/snapshots/org/mobicents/servlet/sip/examples/conference-demo-jsr309/2.1.0-SNAPSHOT/
Jean
For manual mvn building, The 2.1.0-SNAPSHOT artifacts were not yet deployed, I updated the CI Job, this should be fixed by tuesday
Jean
Soto Man
Nov 9, 2012, 8:39:04 AM11/9/12
to mobicent...@googlegroups.com
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?
Thanks all.
Soto Man
Nov 9, 2012, 8:44:25 AM11/9/12
to mobicent...@googlegroups.com
08:16:42,420 INFO [org.mobicents.servlet.sip.core.dispatchers.InitialRequestDispatcher] (Mobicents-SIP-Servlets-UDPMessageChannelThread-0) Request event dispatched to org.mobicents.servlet.sip.example.SimpleApplication
08:18:53,449 INFO [gov.nist.javax.sip.stack.SIPTransactionStack] (Mobicents-SIP-Servlets-UDPMessageChannelThread-1) <message
from="192.168.1.100:5042"
to="192.168.1.100:5080"
time="1352467133447"
isSender="false"
transactionId="z9hg4bk-d8754z-8e57be5d5264a542-1---d8754z-"
callId="OWJiNDBmNTNlMzBiNjdjY2ViMTc4OWI0ZGM0MDI2ZjQ."
firstLine="INVITE sip:sip-servlet...@192.168.1.100 SIP/2.0"
>
<![CDATA[INVITE sip:sip-servlet...@192.168.1.100 SIP/2.0^M
Via: SIP/2.0/UDP 192.168.1.100:5042;branch=z9hG4bK-d8754z-8e57be5d5264a542-1---d8754z-;rport=5042;received=192.168.1.100^M
Max-Forwards: 70^M
Contact: <sip:xl...@192.168.1.100:5042>^M
To: <sip:sip-servlet...@192.168.1.100>^M
From: "hchin" <sip:xl...@192.168.1.100>;tag=7f544355^M
Call-ID: OWJiNDBmNTNlMzBiNjdjY2ViMTc4OWI0ZGM0MDI2ZjQ.^M
CSeq: 1 INVITE^M
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,MESSAGE,SUBSCRIBE,INFO^M
Content-Type: application/sdp^M
Supported: replaces^M
User-Agent: X-Lite release 5.0.0 stamp 67285^M
Content-Length: 424^M
^M
v=0^M
o=- 1352467133438149 1 IN IP4 192.168.1.100^M
s=CounterPath X-Lite 5.0.0^M
c=IN IP4 192.168.1.100^M
b=AS:4096^M
t=0 0^M
a=ice-ufrag:229934^M
a=ice-pwd:d1a0f17b7288f5598a498f1136da7c9c^M
m=audio 5016 RTP/AVP 0 8 101^M
a=rtpmap:101 telephone-event/8000^M
a=fmtp:101 0-15^M
a=sendrecv^M
a=rtcp:5017 IN IP4 192.168.1.100^M
a=candidate:1 1 UDP 659136 192.168.1.100 5016 typ host^M
a=candidate:1 2 UDP 659134 192.168.1.100 5017 typ host^M
]]>
</message>
08:18:53,451 INFO [org.mobicents.servlet.sip.conference.server.ConferenceServlet] (Mobicents-SIP-Servlets-UDPMessageChannelThread-1) MediaPlaybackServlet: Got request:
INVITE
08:18:53,488 INFO [gov.nist.javax.sip.stack.SIPTransactionStack] (Mobicents-SIP-Servlets-UDPMessageChannelThread-1) <message
from="192.168.1.100:5080"
to="192.168.1.100:5042"
time="1352467133488"
isSender="true"
transactionId="z9hg4bk-d8754z-8e57be5d5264a542-1---d8754z-"
callId="OWJiNDBmNTNlMzBiNjdjY2ViMTc4OWI0ZGM0MDI2ZjQ."
firstLine="SIP/2.0 180 Ringing"
>
<![CDATA[SIP/2.0 180 Ringing^M
To: <sip:sip-servlet...@192.168.1.100>;tag=55252124_8a1e29b3_55f1375a-a046-49f0-851e-22e05e7b5872^M
Via: SIP/2.0/UDP 192.168.1.100:5042;branch=z9hG4bK-d8754z-8e57be5d5264a542-1---d8754z-;rport=5042;received=192.168.1.100^M
CSeq: 1 INVITE^M
Call-ID: OWJiNDBmNTNlMzBiNjdjY2ViMTc4OWI0ZGM0MDI2ZjQ.^M
From: "hchin" <sip:xl...@192.168.1.100>;tag=7f544355^M
Contact: <sip:192.168.1.100:5080>^M
Content-Length: 0^M
^M
]]>
</message>
08:18:53,569 INFO [org.mobicents.servlet.sip.core.dispatchers.InitialRequestDispatcher] (Mobicents-SIP-Servlets-UDPMessageChannelThread-1) Request event dispatched to Conference
08:18:57,568 WARN [org.mobicents.protocols.mgcp.stack.TransactionHandler] (TransactionHandlerTimer) message =
CRCX 554860667 mobicents/bridge/$@192.168.1.100:2427 MGCP 1.0
C: 12c4ed893ec09b80
M: confrnce
v=0^M
o=- 1352467133438149 1 IN IP4 192.168.1.100^M
s=CounterPath X-Lite 5.0.0^M
c=IN IP4 192.168.1.100^M
b=AS:4096^M
t=0 0^M
a=ice-ufrag:229934^M
a=ice-pwd:d1a0f17b7288f5598a498f1136da7c9c^M
m=audio 5016 RTP/AVP 0 8 101^M
a=rtpmap:101 telephone-event/8000^M
a=fmtp:101 0-15^M
a=sendrecv^M
a=rtcp:5017 IN IP4 192.168.1.100^M
a=candidate:1 1 UDP 659136 192.168.1.100 5016 typ host^M
a=candidate:1 2 UDP 659134 192.168.1.100 5017 typ host^M
<![CDATA[SIP/2.0 200 OK^M
To: <sip:sip-servlet...@192.168.1.100>;tag=55252124_8a1e29b3_55f1375a-a046-49f0-851e-22e05e7b5872^M
Via: SIP/2.0/UDP 192.168.1.100:5042;branch=z9hG4bK-d8754z-8e57be5d5264a542-1---d8754z-;rport=5042;received=192.168.1.100^M
CSeq: 1 INVITE^M
Call-ID: OWJiNDBmNTNlMzBiNjdjY2ViMTc4OWI0ZGM0MDI2ZjQ.^M
From: "hchin" <sip:xl...@192.168.1.100>;tag=7f544355^M
Contact: <sip:192.168.1.100:5080>^M
Content-Type: application/sdp^M
Content-Length: 0^M
^M
]]>
</message>
08:18:59,553 INFO [gov.nist.javax.sip.stack.SIPTransactionStack] (Mobicents-SIP-Servlets-UDPMessageChannelThread-2) <message
from="192.168.1.100:5042"
to="192.168.1.100:5080"
time="1352467139551"
isSender="false"
transactionId="z9hg4bk-d8754z-4d58974e91342657-1---d8754z-"
callId="OWJiNDBmNTNlMzBiNjdjY2ViMTc4OWI0ZGM0MDI2ZjQ."
firstLine="ACK sip:192.168.1.100:5080 SIP/2.0"
>
<![CDATA[ACK sip:192.168.1.100:5080 SIP/2.0^M
Via: SIP/2.0/UDP 192.168.1.100:5042;branch=z9hG4bK-d8754z-4d58974e91342657-1---d8754z-;rport=5042;received=192.168.1.100^M
Max-Forwards: 70^M
Contact: <sip:xl...@192.168.1.100:5042>^M
To: <sip:sip-servlet...@192.168.1.100>;tag=55252124_8a1e29b3_55f1375a-a046-49f0-851e-22e05e7b5872^M
From: "hchin" <sip:xl...@192.168.1.100>;tag=7f544355^M
Call-ID: OWJiNDBmNTNlMzBiNjdjY2ViMTc4OWI0ZGM0MDI2ZjQ.^M
CSeq: 1 ACK^M
User-Agent: X-Lite release 5.0.0 stamp 67285^M
Content-Length: 0^M
^M
]]>
</message>
08:18:59,554 INFO [gov.nist.javax.sip.stack.SIPTransactionStack] (Mobicents-SIP-Servlets-UDPMessageChannelThread-3) <message
from="192.168.1.100:5042"
to="192.168.1.100:5080"
time="1352467139553"
isSender="false"
transactionId="z9hg4bk-d8754z-142db52c4eea8c5f-1---d8754z-"
callId="OWJiNDBmNTNlMzBiNjdjY2ViMTc4OWI0ZGM0MDI2ZjQ."
firstLine="BYE sip:192.168.1.100:5080 SIP/2.0"
<![CDATA[BYE sip:192.168.1.100:5080 SIP/2.0^M
Via: SIP/2.0/UDP 192.168.1.100:5042;branch=z9hG4bK-d8754z-142db52c4eea8c5f-1---d8754z-;rport=5042;received=192.168.1.100^M
Max-Forwards: 70^M
Contact: <sip:xl...@192.168.1.100:5042>^M
To: <sip:sip-servlet...@192.168.1.100>;tag=55252124_8a1e29b3_55f1375a-a046-49f0-851e-22e05e7b5872^M
From: "hchin" <sip:xl...@192.168.1.100>;tag=7f544355^M
Call-ID: OWJiNDBmNTNlMzBiNjdjY2ViMTc4OWI0ZGM0MDI2ZjQ.^M
CSeq: 2 BYE^M
User-Agent: X-Lite release 5.0.0 stamp 67285^M
Content-Length: 0^M
^M
]]>
</message>
08:18:59,563 INFO [org.mobicents.servlet.sip.conference.server.media.Conference] (Thread-161) Adding user sip:xl...@192.168.1.100
08:18:59,564 INFO [org.mobicents.servlet.sip.conference.server.ConferenceServlet] (Mobicents-SIP-Servlets-UDPMessageChannelThread-3) MediaPlaybackServlet: Got BYE request:
BYE sip:192.168.1.100:5080 SIP/2.0^M
Via: SIP/2.0/UDP 192.168.1.100:5042;branch=z9hG4bK-d8754z-142db52c4eea8c5f-1---d8754z-;rport=5042;received=192.168.1.100^M
Max-Forwards: 70^M
Contact: <sip:xl...@192.168.1.100:5042>^M
To: <sip:sip-servlet...@192.168.1.100>;tag=55252124_8a1e29b3_55f1375a-a046-49f0-851e-22e05e7b5872^M
From: "hchin" <sip:xl...@192.168.1.100>;tag=7f544355^M
Call-ID: OWJiNDBmNTNlMzBiNjdjY2ViMTc4OWI0ZGM0MDI2ZjQ.^M
CSeq: 2 BYE^M
User-Agent: X-Lite release 5.0.0 stamp 67285^M
Content-Length: 0^M
^M
Note there is error afterwards about NullPointerException but that is because the user was never added to conference to begin with.
HC.
Soto Man
Nov 12, 2012, 6:59:00 AM11/12/12
to mobicent...@googlegroups.com
Would appreciate any feedback, thanks in advance.
On Friday, November 9, 2012 8:39:04 AM UTC-5, Soto Man wrote:
On Friday, November 9, 2012 8:39:04 AM UTC-5, Soto Man wrote:
George Vagenas
Nov 12, 2012, 12:11:54 PM11/12/12
to mobicent...@googlegroups.com
Hi,
I will check the logs you sent and I will let you know.
George
Soto Man
Nov 12, 2012, 9:55:56 PM11/12/12
to mobicent...@googlegroups.com
Thanks, when will 2.1.SNAPSHOT artifacts be available for manual build?
Regards
Soto Man
Nov 12, 2012, 9:58:40 PM11/12/12
to mobicent...@googlegroups.com
Thanks, when will updated artifacts for 2.1.0.SNAPSHOT be available?
On Monday, November 12, 2012 12:11:58 PM UTC-5, gvag wrote:
Regards.
On Monday, November 12, 2012 12:11:58 PM UTC-5, gvag wrote:
Soto Man
Nov 15, 2012, 11:25:34 PM11/15/12
to mobicent...@googlegroups.com
Hi,
On Monday, November 12, 2012 12:11:58 PM UTC-5, gvag wrote:
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?
Regards,
On Monday, November 12, 2012 12:11:58 PM UTC-5, gvag wrote:
Soto Man
Nov 15, 2012, 11:29:44 PM11/15/12
to mobicent...@googlegroups.com
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.
Soto Man
Nov 15, 2012, 11:35:54 PM11/15/12
to mobicent...@googlegroups.com
The package-info.java file has annotation
@javax.servlet.sip.annotation.SipApplication(name="Conference",sessionTimeout=1000)
The sessionTimout is set to 1000 minutes, so this is not the problem.
Regards,
Jean Deruelle
Nov 20, 2012, 10:23:14 AM11/20/12
to mobicent...@googlegroups.com
Can you share the full log at DEBUG Level ? It may be a bug where the javax.servlet.sip.annotation.SipApplication is not taken into account. Did you try with sip.xml session-timeout as well ?
Jean
Jean
Soto Man
Nov 22, 2012, 11:50:07 PM11/22/12
to mobicent...@googlegroups.com
I decided to register SipApplicationSessionListener to get notify when sip application session is about to be invalidated. Here is a section of the logs:
Wondering if the expires timer in sip application session is not program correctly.
Regards,
21:06:41,646 INFO [org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl] (Timer-16) The following sip application session 393eb8d0-ed71-4e38-8c35-93238859e0df:Conference has been invalidated
21:06:56,894 INFO [org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl] (Timer-16) Invalidating the following sip application session 9a0cfcf1-c3d9-4247-9089-ba4310b45c34:Conference
21:06:56,895 INFO [org.mobicents.servlet.sip.core.session.SipSessionImpl] (Timer-16) Invalidating the sip session (7gXQT6MACqYNWtvf-V6KJ9N415ihocHm:9qL78bSN0.mD0rMBKxbsBJ9Lsc3TN4jl:9a0cfcf1-c3d9-4247-9089-ba4310b45c34:Conference)
21:06:56,895 INFO [org.mobicents.servlet.sip.conference.server.MyApplicationSessionListener] (Timer-16) Logging stacktrace for javax.servlet.sip.SipApplicationSessionEvent[source=9a0cfcf1-c3d9-4247-9089-ba4310b45c34:Conference] thread=192: java.lang.RuntimeException
at org.mobicents.servlet.sip.conference.server.MyApplicationSessionListener.sessionDestroyed(MyApplicationSessionListener.java:21) [classes:2.1.0-SNAPSHOT]
at org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl.notifySipApplicationSessionListeners(SipApplicationSessionImpl.java:198)
at org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl.invalidate(SipApplicationSessionImpl.java:671)
at org.mobicents.servlet.sip.core.timers.StandardSasTimerTask.tryToExpire(StandardSasTimerTask.java:90)
at org.mobicents.servlet.sip.core.timers.StandardSasTimerTask.run(StandardSasTimerTask.java:70)
at java.util.TimerThread.mainLoop(Timer.java:512) [classes.jar:1.6.0_37]
at java.util.TimerThread.run(Timer.java:462) [classes.jar:1.6.0_37]
Wondering if the expires timer in sip application session is not program correctly.
Regards,
Soto Man
Nov 29, 2012, 11:43:31 PM11/29/12
to mobicent...@googlegroups.com
OK tested with specific sip.xml file and set session-timeout to 60 minutes. The sip application session still gets invalidated after 5 minutes. Trying to set debug level but things have changed with latest JBOSS, how do I set DEBUG level for mobicents sip servlet? Can someone look into why sip application timer is killing the sip app session, thanks.
On Tuesday, November 20, 2012 10:23:36 AM UTC-5, Jean Deruelle wrote:
On Tuesday, November 20, 2012 10:23:36 AM UTC-5, Jean Deruelle wrote:
Jean Deruelle
Jan 11, 2013, 7:59:03 PM1/11/13
to mobicents-public
Sorry for the very late reply here.
Makes sure your application doesn't call invalidate
For DEBUG,
In mss-2.0.0.FINAL-jboss-as-7.1.2.Final/standalone/configuration/standalone-sip.xml, under <subsystem xmlns="urn:jboss:domain:logging:1.1">, please add a new logger
<logger category="org.mobicents">
<level name="DEBUG"/>
</logger>
PLease attach the log
Jean
Reply all
Reply to author
Forward
0 new messages