andresetevejob / webrtc2sip

Automatically exported from code.google.com/p/webrtc2sip
0 stars 0 forks source link

183/early media not forwarded to browser by webrtc2sip #182

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Register to an Asterisk server
2. Call to an extension which plays an early media and hangsup
3. No early media is played
4. Connect directly to asterisk server by webrtc (not webrtc2sip)
5. Call to an extension which plays an early media and hangsup
6. Early media is audible

What is the expected output? What do you see instead?

Early meida should be audible, but it is not. Asterisk sends the SIP 183 
response to webrtc2sip, but webrtc2sip is not forwarding it to the browser

No problems with the call audio in firefox, when connected to asterisk via 
webrtc2sip, but no early media.

When chrome is connected to asterisk via webrtc2sip,there won't be any audio(I 
already reported it as Issue #180 : 
https://code.google.com/p/webrtc2sip/issues/detail?id=180 ), but audio OK when 
chrome is directly connected to asterisk, including early media

What version of the product are you using? On what operating system?

Firefox 37.0.1
Sipml5
Chrome  42.0.2311.90 (64-bit)

Asterisk 13.3.2 on Ubuntu 14.04.2 as amazon ec2 instance (54.xxx.xxx.xxx)
Webrtc2sip 2.5.0 on Ubuntu 12.04.5 as amazon ec2 instance (54.yyy.yyy.yyy)

Please provide server logs with DEBUG level equal to INFO

webrtc2sip log : webrtc2sip.log

Please provide browser logs

Firefox log : firefox.log (firefox was connected to asterisk server via 
webrtc2sip)

Chrome Log : chrome_asterisk_direct_connect.log (chrome was connected directly 
to asterisk server, without webrtc2sip).

Original issue reported on code.google.com by Sachin.d...@gmail.com on 30 Apr 2015 at 10:48

Attachments: