Hello,
On 2015-01-15 17:16 , Sourav Dhar Chaudhuri wrote:
Hi, Please refer the below example.
+381114400301 is getting registered. All Mandatory header is not mentioned in
the below example
REGISTER request of +381114400301
From: <sip:[email protected]:5060>;tag=h7g4Esbg_3a16584d1dTo:
sip:[email protected]:5060Contact: "+381114400301"
<sip:[email protected]:5060;transport=udp;EriBindingId=10619742;eribind-generated-at=10.135.1.65>;expires=3600;+sip.instance="<urn:uuid:00000000-0000-1000-8000-00085D32A297>"
[Please see the IP details in Contact Header]
200OK for REGISTER request
From: <sip:[email protected]:5060>;tag=h7g4Esbg_3a16584d1dTo:
<sip:[email protected]:5060>;tag=003a51df065cb2f0b76e2a1bddc7acContact: "+381114400301"
<sip:[email protected]:5060;transport=udp;EriBindingId=10619742;eribind-generated-at=10.135.1.65>;expires=3600;+sip.instance="<urn:uuid:00000000-0000-1000-8000-00085D32A297>"P-Associated-URI:
sip:[email protected]: tel:+381114400301
[Please see the IP details in Contact Header]
+381114400301 is sending INVITE request
From: "+381114400301" <sip:[email protected]:5060>;tag=h7g4Esbg_ff3f9b5416To: "063430208"
sip:[email protected]:5060Contact: "+381114400301"
<sip:[email protected]:5060;transport=udp>;+sip.instance="<urn:uuid:00000000-0000-1000-8000-00085D32A297>";isfocusP-Preferred-Identity:
sip:[email protected]
Line breaks are missing from your examples.
[Here the IP details in Contact header is different than REGISTER request]
The above INVITE is getting 403 Failure response telling Calling user is not
registered.
Can this because of IP is different in Contact header?
The protocol does not mandate that a caller needs to be registered. So
this 403 error is a result of "policies" adopted on that server.
Registration is necessary to receive calls and the Contact URI in the
REGISTER requests specifies where the registering entity expects
incoming calls to be sent to.
The Contact URI in the outgoing INVITE request specifies the physical
address of the caller entity that will participate in the SIP dialog
being set up. And that physical address may be different from the very
same entity when it uses it in Contact URI of a 200-INVITE response,
answering an incoming call request.
Thus, Contact URI can be different in all three cases: REGISTER, INVITE
or 200-INVITE. If some implementation requires them to be the same, it's
a policy of that server rather than protocol requirement. As easy that
server may require that Contact URI has particular format, like
sip:phone@ip_address, or pose any additional requirements. But then it's
better to ask that server's administrators...
--
Best regards,
Dmitry Akindinov -- Stalker Labs
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
