What steps will reproduce the problem?
1.Make a call from a web page with JsSIP stack to webrtc2sip
What is the expected output? What do you see instead?
When use sipML5, webrtc2sip changes the .invalid headers corretly:
Sent by browser:
Via: SIP/2.0/WS
df7jal23ls0d.invalid;branch=z9hG4bKBoeMgsDeuwTdMg86fuqc2puedf1KR4p2;rport
Contact: <sip:webrtc.1858@df7jal23ls0d.invalid;transport=ws>;+sip.ice
After webrtc2sip:
Via: SIP/2.0/TCP
177.135.168.30:47279;branch=z9hG4bKBoeMgsDeuwTdMg86fuqc2puedf1KR4p2;rport=47279;
received=177.135.168.30
Contact:
<sip:webrtc.1858@10.171.74.130:5060;transport=udp;ws-src-ip=177.135.168.30;ws-sr
c-port=47279>;+sip.ice
But when using JsSIP, it does not change it:
Sent by browser:
Via: SIP/2.0/WS 22rbepokr2v8.invalid;branch=z9hG4bK5215428;rport
Contact: <sip:webrtc@22rbepokr2v8.invalid;transport=ws>;+sip.ice
After webrtc2sip:
Via: SIP/2.0/WS
22rbepokr2v8.invalid;branch=z9hG4bK5215428;rport=5866;received=177.135.168.30
Contact: <sip:webrtc@22rbepokr2v8.invalid;transport=ws>;+sip.ice
Please provide any additional information below.
From the technical guide:
"This request contains an invalid IP address in the Contact
(df7jal23ls0d.invalid) and Via headers because there is no way for the browser
to retrieve its local binding IP:Port address. The transport type is WebSocket
(ws)... The header is patched to use a well-known protocol (TCP) and to use
the IP address and port (192.168.0.9:55210) from which the request has been
received (WebSocket connection). The SIP Proxy adds it’s own Via header
(66.66.66.66:5060) there it’s willing to receive the response. The same
address is used in the Contact header for incoming requests"
Original issue reported on code.google.com by diego.cd...@gmail.com on 15 Feb 2013 at 6:12
Original issue reported on code.google.com by
diego.cd...@gmail.comon 15 Feb 2013 at 6:12