From: "Tapan Kumar Biswal" <[EMAIL PROTECTED]>
I get "404 Not Found " , when i am making call from X-lite 3.0 SIP soft
phone to SNOM 360.
To summarize what others have found:
The actual contact URI of a Snom phone looks like this:
sip:[EMAIL PROTECTED]:2082;line=boaj0kyl
Notice the "line" URI parameter -- that is part of the URI and calls
that come into the Snom phone must bear that URI parameter in order to
be accepted. (I believe it is an anti-spam technique.)
The Snom phone registers this URI as it should:
REGISTER sip:172.16.10.124 SIP/2.0
Via: SIP/2.0/UDP 172.16.10.103:2085;branch=z9hG4bK-pi37fowo4d1w;rport
From: "ansuman" <sip:[EMAIL PROTECTED]>;tag=p518t58ltb
To: "ansuman" <sip:[EMAIL PROTECTED]>
Call-ID: [EMAIL PROTECTED]
CSeq: 2 REGISTER
Max-Forwards: 70
Contact: <sip:[EMAIL PROTECTED]:2085;line=jpw6wl0r>;q=1.0
;flow-id=1
;+sip.instance="<urn:uuid:4783ef4f-d5eb-487c-8d46-bd5169ac03f2>"
;audio
;mobility="fixed"
;duplex="full"
;description="snom360"
;actor="principal"
;events="dialog"
;methods="I
User-Agent: snom360/6.5.2
Supported: gruu
Allow-Events: dialog
X-Real-IP: 172.16.10.103
WWW-Contact: <http://172.16.10.103:80>
WWW-Contact: <https://172.16.10.103:443>
Authorization: Digest
username="ansuman"
,realm="VALIDATIONLAB"
,nonce="eb5ad60232ae440af12ed3d68b689fcec3738a83"
,uri="sip:172.16.10.124"
,response="9d1db5e584a966b4aa1cffead2305941"
,algorithm=md5
Expires: 3600
Content-Length: 0
And the registrar returns a 200 OK response, with the correct contact:
Contact: <sip:[EMAIL PROTECTED]:2085;line=jpw6wl0r>
;expires=3600
;q=1.0
;flow-id=1
;+sip.instance="<urn:uuid:4783ef4f-d5eb-487c-8d46-bd5169ac03f2>"
;audio
;mobility="fixed"
;duplex="full"
;description="snom360"
;actor="principal"
;events="dialo ???
When you look at your INVITE, the initial invite generated by
X-Lite is OK:
INVITE sip:[EMAIL PROTECTED] SIP/2.0
But the proxy translates it incorrectly for forwarding to the Snom
phone:
INVITE sip:[EMAIL PROTECTED]:2072 SIP/2.0
The IP address is right, but the port number is wrong. (That may be
due to these packet traces being from different test runs.) But most
importantly, the "line" URI parameter is missing -- it should be
retained by the registrar and applied by the proxy, giving something
like this:
INVITE sip:[EMAIL PROTECTED]:2085;line=jpw6wl0r SIP/2.0
So it looks like you have a problem in your proxy.
Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
