search

synergycns / webrtc2sip

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

Via header not stripped by webrtc2sip in 200ok response #53

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. REGISTER with a sipml5 endpoint through webrtc
2. 200ok response contains an extra Via header (not stripped by webrtc2sip)
Via: SIP/2.0/UDP 
92.11.169.63:10060;rport=10060;received=92.11.169.63;branch=z9hG4bK0AP8Pm9NAxnT3
KgqxSaOm7Mhqmd0cLpq
3.

What is the expected output? What do you see instead?
200ok should only have a single Via header when it reaches the sipml5 endpoint

SEND: REGISTER sip:ims.t.com SIP/2.0 
Via: SIP/2.0/WS 
df7jal23ls0d.invalid;branch=z9hG4bK0AP8Pm9NAxnT3KgqxSaOm7Mhqmd0cLpq;rport
From: <sip:+16302706808@ims.t.com>;tag=UvZprT5J6340U2pfi027
To: <sip:+16302706808@ims.t.com>
Contact: 
"6302706808"<sip:+16302706808@df7jal23ls0d.invalid;rtcweb-breaker=yes;transport=
ws>;expires=300;+g.oma.sip-im;+audio;language="en,fr"
Call-ID: f8a5f2a2-6b67-758c-68fe-0673b98b928c
CSeq: 44664 REGISTER
Content-Length: 0
Route: <sip:92.11.169.28:5060;lr;transport=udp>
Max-Forwards: 70 
Authorization: Digest 
username="6302706808",realm="ims.t.com",nonce="b7c9036dbf3054aea940e9703d511c5ec
ec8f84c2608",uri="sip:ims.t.com",response="56d11ffa70cf114864bb2d85bd8ecef1",alg
orithm=MD5,cnonce="69a970a387cf9430c0c56348bc4065e9",opaque="ALU:QbkRBthOEgEQAkg
VEwwHRAIBHgkdHwQCQ1lFRkdWEBcybCchKClpKSUpKjgoImI8JDE2OiF4NDc0YAQCBAQ_",qop=auth,
nc=00000001
User-Agent: IM-client/OMA1.0 sipML5-v1.2013.01.14
Organization: Doubango Telecom
Supported: path 

tsk_utils.js:110
==session event = sent_request call.htm:720
__tsip_transport_ws_onmessage tsk_utils.js:110
recv=SIP/2.0 200 OK
Via: SIP/2.0/UDP 
92.11.169.63:10060;rport=10060;received=92.11.169.63;branch=z9hG4bK0AP8Pm9NAxnT3
KgqxSaOm7Mhqmd0cLpq
From: <sip:+16302706808@ims.t.com>;tag=UvZprT5J6340U2pfi027
To: <sip:+16302706808@ims.t.com>;tag=511baa48-1360813774386278
Contact: 
"6302706808"<sip:+16302706808@92.11.169.63:10060;transport=udp;rtcweb-breaker=ye
s;ws-src-ip=35.245.10.2;ws-src-port=35992;ws-src-proto=ws>;expires=300;+g.oma.si
p-im;language="en,fr" Call-ID: f8a5f2a2-6b67-758c-68fe-0673b98b928c
CSeq: 44664 REGISTER
Content-Length: 0
Via: SIP/2.0/TCP 
35.245.10.2:35992;rport;branch=z9hG4bK0AP8Pm9NAxnT3KgqxSaOm7Mhqmd0cLpq;ws-hacked
=WS
Allow-Events: reg 
Date: 14 Feb 2013 3:49:34 GMT;14
Path: 
<sip:pcsf-stdn.imsgroup0-000.t.com:5060;lr;ottag=ue_term;bidx=1391;access-type=A
DSL>
P-Associated-URI: "+16302706808 "<sip:+16302706808@ims.t.com>
P-Associated-URI: "+16302706808 "<tel:+16302706808>
Server: Alcatel-Lucent-HPSS/3.0.3
Service-Route: <sip:pcsf-stdn.imsgroup0-000.ims.t.com:5060;lr;bidx=0>
Service-Route: 
<sip:scsf-stdn.imsgroup0-000.ims.t.com:5070;lr;ottag=ue_orig;bidx=454>

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

Please provide any additional information below.

Original issue reported on code.google.com by saket...@gmail.com on 15 Feb 2013 at 3:07

GoogleCodeExporter commented 9 years ago 
Any update on this issue? This via below inserted by the webrtc2sip proxy needs 
to be removed before it sends it towards the UE

Via: SIP/2.0/UDP 
92.11.169.63:10060;rport=10060;received=92.11.169.63;branch=z9hG4bK0AP8Pm9NAxnT3
KgqxSaOm7Mhqmd0cLpq

Original comment by saket...@gmail.com on 6 Aug 2013 at 3:45

GoogleCodeExporter commented 9 years ago 
This is sure bug. When is fix coming ?

Original comment by vipul.ra...@temasys.com.sg on 28 Dec 2014 at 12:20