<div dir="ltr"><div>Hi guys,</div><div><br></div><div>i have yet to finish my readings on the websocket standards but just wanted to fire away with this question. </div><div><br></div><div>is the behavior of protocol conversions between UDP and TCP the same as if you include websockets?</div>
<div><br></div><div>i have this twinkle issue (an old SIP stack)</div><div><br></div><div><div>Received from: udp:<a href="http://192.168.122.100:5060" target="_blank">192.168.122.100:5060</a></div><div>INVITE <a href="mailto:sip%3Akelvin@192.168.122.1" target="_blank">sip:kelvin@192.168.122.1</a> SIP/2.0</div>
<div>Record-Route: <sip:192.168.122.100;r2=on;lr=on></div><div>Record-Route: <sip:192.168.122.100:8080;transport=ws;r2=on;lr=on></div><div>Via: SIP/2.0/UDP 192.168.122.100;branch=z9hG4bKed9e.8b1b2fa61a90a9031e17b393657df31b.0</div>
<div>Via: SIP/2.0/WS z173czhz21tk.invalid;rport=54765;received=192.168.122.1;branch=z9hG4bK3818745</div><div>Max-Forwards: 16</div><div>To: <a href="mailto:sip%3Akelvin@192.168.122.100" target="_blank">sip:kelvin@192.168.122.100</a></div>
<div>From: <a href="mailto:sip%3Akelvin2@192.168.122.100" target="_blank">sip:kelvin2@192.168.122.100</a>;tag=lmf8ofkxwq</div><div>Call-ID: 69hbgnng64at9p07r2j4</div><div>CSeq: 9406 INVITE</div><div>Contact: <sip:kelvin2@z173czhz21tk.invalid;alias=192.168.122.1~54765~5;transport=ws;ob></div>
<div>Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, MESSAGE, SUBSCRIBE</div><div>Content-Type: application/sdp</div><div>Supported: path, outbound, gruu</div><div>User-Agent: JsSIP 0.2.1</div><div>Content-Length: 2103</div><div>
<br></div><div>v=0</div><div>o=- 3148117784 2 IN IP4 127.0.0.1</div><div>s=-</div><div>t=0 0</div><div>a=group:BUNDLE audio</div><div>m=audio 55736 RTP/SAVPF 103 104 111 0 8 106 105 13 126</div><div>c=IN IP4 192.168.122.1</div>
<div>a=rtcp:55736 IN IP4 192.168.122.1</div><div>a=candidate:2625852906 1 udp 2113937151</div><div><br></div><div><cut off></div><div><br></div><div>---</div><div><br></div><div>+++ 16-3-2013 10:41:25.584732 INFO SIP ::send_sip_udp</div>
<div>Send to: udp:<a href="http://192.168.122.100:5060" target="_blank">192.168.122.100:5060</a></div><div>SIP/2.0 100 Trying</div><div>Via: SIP/2.0/UDP 192.168.122.100;branch=z9hG4bKed9e.8b1b2fa61a90a9031e17b393657df31b.0,SIP/2.0/WS z173czhz21tk.invalid;received=192.168.122.1;rport=54765;branch=z9hG4bK3818745</div>
<div>To: <<a href="mailto:sip%3Akelvin@192.168.122.100" target="_blank">sip:kelvin@192.168.122.100</a>></div><div>From: <<a href="mailto:sip%3Akelvin2@192.168.122.100" target="_blank">sip:kelvin2@192.168.122.100</a>>;tag=lmf8ofkxwq</div>
<div>
Call-ID: 69hbgnng64at9p07r2j4</div><div>CSeq: 9406 INVITE</div><div>Server: Twinkle/1.4.2</div><div>Content-Length: 0</div><div><br></div><div><br></div><div>---</div><div><br></div><div>+++ 16-3-2013 10:41:25.589231 INFO SIP ::send_sip_udp</div>
<div>Send to: udp:<a href="http://192.168.122.100:5060" target="_blank">192.168.122.100:5060</a></div><div>SIP/2.0 488 Not Acceptable Here</div><div>Via: SIP/2.0/UDP 192.168.122.100;branch=z9hG4bKed9e.8b1b2fa61a90a9031e17b393657df31b.0,SIP/2.0/WS z173czhz21tk.invalid;received=192.168.122.1;rport=54765;branch=z9hG4bK3818745</div>
<div>To: <<a href="mailto:sip%3Akelvin@192.168.122.100" target="_blank">sip:kelvin@192.168.122.100</a>>;tag=pxtmo</div><div>From: <<a href="mailto:sip%3Akelvin2@192.168.122.100" target="_blank">sip:kelvin2@192.168.122.100</a>>;tag=lmf8ofkxwq</div>
<div>Call-ID: 69hbgnng64at9p07r2j4</div><div>CSeq: 9406 INVITE</div><div>Server: Twinkle/1.4.2</div><div>Warning: 302 X340precise "Incompatible transport protocol"</div><div>Content-Length: 0</div></div><br clear="all">
<div>Kelvin Chua</div>
</div>