[OpenSIPS-Users] opensips 1.9 and sipml5

Jason Sia jsia18 at gmail.com
Sat Aug 10 17:51:23 CEST 2013


I tried to use opensips 1.9 and sipml5 with oversip on registration I am
already receiving 400 Bad Request

REGISTER sip:192.x.x.x SIP/2.0.
Path: <sip:198.x.x.x:5063;transport=udp;lr;ovid=2898ca59>.
Path: <sip:64dd13612d at 198.x.x.x:10080;transport=ws;lr;ovid=2898ca59;ob>.
Via: SIP/2.0/UDP
198.x.x.x:5063;branch=z9hG4bK0275781c25c9e78fce5a602efe45717696d3f4a4;rport.
Via: SIP/2.0/WS
df7jal23ls0d.invalid;branch=z9hG4bKau2hnl0UWw2OKXXTmKtrHSPPAp7LpNKb;rport.
From: "1234"<sip:1234 at 192.x.x.x>;tag=Z4oDahIguMSIU3GuqqO3.
To: "1234"<sip:1234 at 192.x.x.x>.
Contact: "1234" <sip:1234 at df7jal23ls0d.invalid
;rtcweb-breaker=yes;transport=ws;ov-ob=64dd13612d>;expires=200;click2call=no;+g.oma.sip-im;+audio;language="en,fr".
Call-ID: dc23063c-2b13-c293-e9e8-002bba116fba.
CSeq: 45509 REGISTER.
Content-Length: 0.
Max-Forwards: 10.
Authorization: Digest username="1234",realm="192.x.x.x",uri="sip:192.x.x.x".
User-Agent: IM-client/OMA1.0 sipML5-v1.2013.08.10.
Organization: Doubango Telecom.
Supported: path.
.

198.x.x.x = oversip IP

SIP/2.0 400 Bad Request.
Via: SIP/2.0/UDP
198.x.x.x:5063;received=198.x.x.x;branch=z9hG4bK0275781c25c9e78fce5a602efe45717696d3f4a4;rport=5063.
Via: SIP/2.0/WS
df7jal23ls0d.invalid;branch=z9hG4bKau2hnl0UWw2OKXXTmKtrHSPPAp7LpNKb;rport.
From: "1234"<sip:1234 at 192.x.x.x>;tag=Z4oDahIguMSIU3GuqqO3.
To: "1234"<sip:1234 at 192.x.x.x>;tag=3037d939dfa8e27f790ae45e96f178b5.3092.
Call-ID: dc23063c-2b13-c293-e9e8-002bba116fba.
CSeq: 45509 REGISTER.
Server: OpenSIPS (1.9.1-notls (x86_64/linux)).
Content-Length: 0.

Anyone has any idea why this is happening?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20130810/92f32fd6/attachment.htm>


More information about the Users mailing list