- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
I installed the CS MCU 3.2.1 & the SIP GW 3.2.1 on my server. I also have the latest Kamailio SIP Server v4.4.3 installed on the same server.
The SIP GW works great. I can dial from my SIP Endpoint and accept the call on the webRTC page. Audio transcode (G722) and Video transcode (H264), all is perfect.
The CS MCU works great with webRTC clients, but I cannot connect a SIP endpoint to a conference. When I try to connect my SIP Endpoint to the CS MCU, it connects, but chokes on the video and audio codec negotiation (see Attached Log).
Any help would be much appreciated!
Thanks
-VR
- Tags:
- HTML5
- JavaScript*
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Seems MCU hasn't got SIP endpoint audio codec and video codec types explicitly for stream subscription, so the call exit. We will check the enhancement point for your case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you Lei. Let me know if you need more info from my side and/or if there is something I can do to make it work. What is weird is that the gateway on the same machine works great.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Vincent
I think we got the root cause. We found the there is one additional space character in front of the SIP caller id, like [space]sip:XT5000@192.168.1.236:5060 in your example log. But in the following SIP call update events, there are no such space in caller id. We have some internal map to hold the SIP call info which uses caller id as its key. So there occurs the key id mismatch during runtime logic. We can add the enhancement logic in next release to remove trailing space of SIP caller id, do you have some approach to correct this behavior on your side to make it work now?
2016-10-09 16:41:38.390 - INFO: SipNode - IncommingCall: sip:XT5000@192.168.1.236:5060
Best wishes,
Zhai Lei
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Lei.
Thanks a lot for the answer, great finding. I did a trace with the Jitsi client and saw the same extra space issue in front of the caller id, so I am guessing Kamailio is the one adding it... I will investigate if I can do anything on Kamailio, but removing the trailing space of SIP caller id in your next release seems a good idea :)
Thanks again,
-VR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Lei
I tried different SIP clients, different SIP registrars, and I always saw this extra space before the caller id.
I don’t know what else to try so I’ll wait for a fix / patch from you.
Thanks a lot
-VR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, seems that was not the real issue according to your findings. We will provide a patch version for you soon to collect more data for further diagnosis.Thanks for your support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Vicent
Can you please get the patch for SIP connectivity part log enhancement from http://pan.baidu.com/s/1bpl5gj9 and use them to replace the following files in MCU binary? Please open the DEBUG log level, go through the scenario and send back your log folder again. Thanks a lot!
sip_agent/woogeen_sip
sip_agent/lib/libsip_gateway.so
sip_agent/sipIn/build/Release/sipIn.node
Best wishes,
Zhai Lei
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Lei,
I applied the patch. Unfortunately the woogeen-sip-agent fails to start. Please see the log below.
Thanks for the help
-VR
2016-10-18 10:35:16.702 - INFO: AMQPER - Exchange rpcExchange is open
2016-10-18 10:35:16.705 - INFO: AMQPER - Exchange broadcastExchange is open
2016-10-18 10:35:16.707 - INFO: AMQPER - ClientQueue amq.gen-ohq3PQ418BhXaq77eeom8g is open
2016-10-18 10:35:16.709 - INFO: ErizoAgent - Adding agent to cloudhandler, purpose: sip
2016-10-18 10:35:16.719 - INFO: ErizoAgent - sip agent join cluster ok.
2016-10-18 10:35:16.723 - ERROR: AMQPER - Error processing response: { [Error: spawn EACCES] code: 'EACCES', errno: 'EACCES', syscall: 'spawn' }
Error: spawn EACCES
at exports._errnoException (util.js:874:11)
at ChildProcess.spawn (internal/child_process.js:298:11)
at exports.spawn (child_process.js:339:9)
at launchErizoJS (/root/intel_mcu/sip_agent/index.js:1:4238)
at fillErizos (/root/intel_mcu/sip_agent/index.js:1:4969)
at /root/intel_mcu/sip_agent/index.js:1:8497
at o (/root/intel_mcu/sip_agent/index.js:1:6751)
at o (/root/intel_mcu/sip_agent/clusterWorker.js:1:1265)
at /root/intel_mcu/sip_agent/clusterWorker.js:1:1124
at Object.t.callRpc.callback (/root/intel_mcu/sip_agent/makeRPC.js:1:288)
2016-10-18 10:35:16.731 - INFO: AMQPER - Queue sip-b054fcb2-70fe46a9b1b4 is open
2016-10-18 10:35:16.732 - INFO: ErizoAgent - rpcID: sip-b054fcb2-70fe46a9b1b4
2016-10-18 10:35:21.361 - WARN: ErizoAgent - process undefined not found
2016-10-18 10:35:21.362 - ERROR: ErizoAgent - getNode error: { [Error: spawn EACCES] code: 'EACCES', errno: 'EACCES', syscall: 'spawn' }
Error: spawn EACCES
at exports._errnoException (util.js:874:11)
at ChildProcess.spawn (internal/child_process.js:298:11)
at exports.spawn (child_process.js:339:9)
at launchErizoJS (/root/intel_mcu/sip_agent/index.js:1:4238)
at fillErizos (/root/intel_mcu/sip_agent/index.js:1:4969)
at Object.getNode (/root/intel_mcu/sip_agent/index.js:1:6277)
at /root/intel_mcu/sip_agent/amqper.js:1:1747
at Message.<anonymous> (/root/intel_mcu/sip_agent/node_modules/amqp/lib/queue.js:193:28)
at emitNone (events.js:67:13)
at Message.emit (events.js:166:7)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I forgot to ask your OS, is that Ubuntu or CentOS? The patch I provided is for Ubuntu.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My OS is Ubuntu 14.04.5 LTS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's wired. Please try this http://pan.baidu.com/s/1kU5XuGf patch again. If still not work, we will provide you a whole fresh binary. Thanks for your effort.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Lei
I added this new patch and got the same error. The issue is with the woogeen_sip file. The sipIn.node and libsip_gateway.so files from your patch are ok. So I only updated those last 2 on my server and run the test again, hoping it will give you enough information.
See log attached
Thanks
-VR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Vincent
Thanks for your support. I think we probably got real root cause according to your new log. Will update you a new patch soon once ready.
Best wishes,
Zhai Lei
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Vicent
Patch has been prepared well at the following location. Please use it to replace sip_agent/lib/libsip_gateway.so. Let us know whether it can help you out.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
I applied the patch on my MCU (3.2.1 / Ubuntu 14.04) and I am now getting the error:
2016-10-25 17:57:14.313 - INFO: SipPortal - sip-portal up!
2016-10-25 17:57:14.315 - INFO: SipPortal - Start to get SIP rooms
2016-10-25 17:57:14.558 - INFO: SipErizoHelper - Successully schedule sip node 5bc42988-21af-5e9f-2b96-d87cf9453534 for { session: '57fa47f1625fa20e1b519e99',
consumer: '57fa47f1625fa20e1b519e99' }
2016-10-25 17:57:14.560 - INFO: SipPortal - allocateSipErizo { id: '5bc42988-21af-5e9f-2b96-d87cf9453534',
addr: '91.202.168.174' }
2016-10-25 17:57:19.563 - ERROR: SipPortal - Init sip node fail, try to de-allocate it.
The MCU fails to register to Kamailio SIP Server
-VR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How about replace all three files in the following link? If still not work, please help open the debug info and send back to us. Thanks!
http://pan.baidu.com/s/1pLB548b
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
I still had the same issue as before with the woogen_sip file (see attached woogeen-sip-agent.log). So i replaced it with the original file and the server started, it registered to the SIP server. And when I joined the MCU conference from my SIP endpoint, it worked ! See log for details (sip_ok.log).
I will wait for the official patch update before doing more tests...
Thanks a lot
-VR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Vincent
Nice to hear that your problem solved. Yes, we will provide the official fix in next major version. Thanks for your effort during the diagnosis.
For the woogeen_sip file, we forgot to share with you that the execution permission need to be added (+x) on this file before running. But that file is not mandatory to this bug fix, so no more action is needed.
Best wishes,
Zhai Lei
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Lei,
We are also facing similar issue when we use ubuntu software accelerated MCU, when will be the official patch will be release for this fix?
Thanks
Naresh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Naresh
The official fix will be provided around December in v3.3 release. But if that fix is urgent for your case, http://pan.baidu.com/s/1pLB548b can help, which has passed our internal test process. Thanks for your patience.
Best wishes,
Zhai Lei

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page