- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Sampath
Let me update the current progress. According to your log, we did find the defect on sip-portal which is responsible for scheduling sip working node to serve sip room. During frequent sip working node initialization progress, some fail, some success, then the sip-portal state will be deranged, and fail to respond to the further update requests. This issue will be fixed in next patch release. But we still can't reproduce the sip working node initialize fail. Question to you is when did you find the issue, at the beginning or after running some time? And what's the purpose of the frequently sip room updates? If you can provide the detailed error reproducing steps, then it will help the diagnosis much.
And currently we haven't log analysis guide, will consider this option in future. And now we don't open source to public due to corporate policy. If you have special business requirement, please try to contact webrtc_support@intel.com.
Best wishes,
Zhai Lei
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Sampathkumar, could you please provide the log: sip-xxxx.log?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
we are checking this issue, thanks for reporting it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi He Z.,
Please let us know if you have any updates on this issue.
Is there any documents available in guiding the users of Intel MCU to analyse the log files ?
Is it possible to open-soure/share the code to debug the root cause of the issues faced (Issues may be either in Intel MCU / end-users code)
Thanks,
Sampath
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Sampath
Let me update the current progress. According to your log, we did find the defect on sip-portal which is responsible for scheduling sip working node to serve sip room. During frequent sip working node initialization progress, some fail, some success, then the sip-portal state will be deranged, and fail to respond to the further update requests. This issue will be fixed in next patch release. But we still can't reproduce the sip working node initialize fail. Question to you is when did you find the issue, at the beginning or after running some time? And what's the purpose of the frequently sip room updates? If you can provide the detailed error reproducing steps, then it will help the diagnosis much.
And currently we haven't log analysis guide, will consider this option in future. And now we don't open source to public due to corporate policy. If you have special business requirement, please try to contact webrtc_support@intel.com.
Best wishes,
Zhai Lei
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
关于MCU 房间，能主动去SIP 呼叫 终端吗？目前看，好像都只能由终端向MCU发起呼叫。
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Currently we just support SIP terminal call MCU room, don't support MCU room call SIP terminal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Lei Zhai,
Thank you for the response.
Please let us know the following details
1. Does Intel have plans to support MCU room call SIP terminal in future ?
2. If yes, Then what would be the approximate timelines ?
3. It will be very helpful, if you can share any document / link which provides details on the known limitations of Intel CS for WebRTC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, the MCU room call SIP terminal feature in our future road map, should be in the next half of this year if everything runs according to the plan. But please be aware that this is not the commitment, just the estimation. Thanks for your patience.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Hi,
We were evaluating the Intel CS for WebRTC for our MCU requirement and we observed the following issue with SIP agent
We see the SIP calls are getting failed frequently and whenever it happens, we see, there is jump in SIP packet captured in PC with Intel CS(SIP agent) from 16:16:58 to 16:17:14 – almost 16 seconds, no SIP packets captured in PC even though, remote SIP endpoint kept sending the SIP messages like INVITE (though other RTP packets/ipv6 packets are received in PC with SIP agent, during this time). During this time, remote SIP endpoint received ICMP Destination unreachable response.
Hence I suspect in PC with Intel MCU, sip Agent wasn’t responsive or crashed during this interval. Please let me know if you need any further details from me. We need support from Intel MCU team to further investigate this issue.
Logs around this time:
woogeen-sip-agent.stdout.1
2017-01-24 16:13:18.531 - INFO: ErizoAgent - message from worker ee94140e-b3a7-e146-2180-a2fa6ca36ce0 : READY
2017-01-24 16:17:04.566 - INFO: ErizoAgent - ce2d2062-eed5-e66e-58f8-49f5ddc0dcd8 exit with null
woogeen-sip-portal.stdout.1
2017-01-24 16:13:18.373 - INFO: SipPortal - Sip node init successfully.
2017-01-24 16:17:15.656 - INFO: SipErizoHelper - ErizoJS[ ce2d2062-eed5-e66e-58f8-49f5ddc0dcd8 ] check alive timeout!
intelMCU-logs.tgz log files are uploaded for your reference
Thanks in Advance,
Sampath