<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>I guess your UAC freezes when receiving back in the 200 OK
REGISTER the "received" hdr param in Contact ??<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 18.11.2016 16:33, Bogdan-Andrei
Iancu wrote:<br>
</div>
<blockquote
cite="mid:6117be99-edd6-cb33-d58c-a22469b5ce2f@opensips.org"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<tt>HI Miha,<br>
<br>
Sorry, but I'm not able to follow the case you mentioned with
Innovaphone PBX - maybe you can post (to see the differences)
the sent and returned contact hdrs in the REGISTER request +
reply for the 2 cases (OpenSIPS and Innovaphone PBX).<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 18.11.2016 11:20, Miha wrote:<br>
</div>
<blockquote
cite="mid:a830ad7f-afd9-839f-2998-f7f2a2d52d4d@softnet.si"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<font face="Calibri Light">I do not know if this is the case.
But from what I can see what I register it on some Innovaphone
PBX, innovaphone sends back in contact (200 ok) just ip of
IPBX and also when INVITE is send in contact there is URI of
PBX and only and it works.<br>
<br>
i tried this but did not have any luck.<br>
<br>
br<br>
miha<br>
</font><br>
<div class="moz-cite-prefix">On 18/11/2016 09:48, Bogdan-Andrei
Iancu wrote:<br>
</div>
<blockquote
cite="mid:3d864dde-2b07-f872-e7bd-181627c3a653@opensips.org"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<tt>Hi Miha,<br>
<br>
You mean the UAC does not like the multi-URI Contact header
in the 200 OK ???? If so, that UAC is really broken as 1)
breaks the SIP syntax (which allows it) and 2) breaks the
the SIP Registration as per RFC3261.<br>
<br>
What about the second contact (the one already existing in
usrloc when this registration comes) ? can it be discarded ?
If YES, you can try passing the "c1f" flags to save() :<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.opensips.org/html/docs/modules/2.2.x/registrar.html#id294033">http://www.opensips.org/html/docs/modules/2.2.x/registrar.html#id294033</a><br>
<br>
That will make OpenSIPS to accept only 1 contact per
AOR/user and any new contact will override the existing one.<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 18.11.2016 10:15, Miha wrote:<br>
</div>
<blockquote
cite="mid:c80e9a24-0b74-01be-2f96-a5c1bc698592@softnet.si"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<font face="Calibri Light">Hi Bogdan<br>
<br>
I did few more test. </font><font face="Calibri Light">This
contact bothers UAC. Is there anything i can do in this
case in OpenSIPS so that it will only reply with one URI
in contact?<br>
</font><br>
<pre wrap="">Contact: <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="sip:38618308980@opsp.kabelnet.net;transport=udp"><sip:38618308980@opsp.kabelnet.net;transport=udp></a>;expires=1518
;received=<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="sip:84.41.125.21:5060">"sip:84.41.125.21:5060"</a>, <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="sip:38618308980@84.41.125.21:5060"><sip:38618308980@84.41.125.21:5060></a>;
expires=180.
tnx so much!
MIha
</pre>
<br>
<div class="moz-cite-prefix">On 17/11/2016 12:11,
Bogdan-Andrei Iancu wrote:<br>
</div>
<blockquote
cite="mid:b503439a-2fae-36ee-f545-4179aad9f5d3@opensips.org"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<tt>Hi Miha,<br>
<br>
yes, that is parallel forking (you may have more than 2
contacts only).<br>
<br>
Are you sure your DB was sync'ed? OpenSIPS is
periodically flushing the memory cache into the location
table (see the "state" of the contact (as per "ul show")
if marked as DIRTY).<br>
<br>
In regards to RFC, I think you quote the wrong section
(maybe about callings?) - for REGISTERs, any number of
URIs are allowed AFAIK. <br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 17.11.2016 12:35, Miha
wrote:<br>
</div>
<blockquote
cite="mid:2610b8d4-1cb3-804f-2fce-8d24c129ffb5@softnet.si"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<font face="Calibri Light">Bodan<br>
<br>
so this is dual forking...?<br>
So if you have one account and you have two phones on
it and first will try to register, 200 ok will will
have contact of both phones?<br>
In location table I can see only one registration for
this user but for "opensipsctl ul show" it shows me
two contacts, which is strange? (When i do trace only
one invite is send) and UAC replay with Busy all the
time due to two contacts (this what i have been told).<br>
<br>
Ok, but if you look at rfc there is only one URI
allowed in contact if I understand this right?<br>
<br>
</font><br>
<pre style="color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; white-space: pre-wrap;">The Contact header field MUST be present and contain exactly one SIP
or SIPS URI in any request that can result in the establishment of a
dialog
<font face="Calibri Light">Please correct me if I am wrong.
tnx so much!
Miha</font><font face="Calibri Light">
</font></pre>
<br>
<div class="moz-cite-prefix">On 17/11/2016 11:22,
Bogdan-Andrei Iancu wrote:<br>
</div>
<blockquote
cite="mid:02477e55-9520-dd33-a8e3-19b49783228e@opensips.org"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<tt>Hi Miha,<br>
<br>
OpenSIPS returns in the 200 OK for a REGISTER all
the valid registrations for that user (for all the
devices the user may have).<br>
<br>
I guess your user has 2 registrations, so the 200 OK
will report back both of them. You can check via
"opensipsctl ul show"<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 17.11.2016 12:13, Miha
wrote:<br>
</div>
<blockquote
cite="mid:1a3ae947-f9e7-c5b3-bbbe-4fabe1b648e2@softnet.si"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<font face="Calibri Light">Hello Bogdan<br>
<br>
i changed this and it works in all cases, only in
one I noticed today this (Opensips reply only in
this case with two URI on contact):<br>
<br>
<font size="-1"> UAC:5060 ->OpenSIPS:5060<br>
REGISTER <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="sip:opsp.test.net:5060">sip:opsp.test.net:5060</a>
SIP/2.0.<br>
Via: SIP/2.0/UDP
opsp.test.net;branch=z9hG4bKa40225bd7495297c6.<br>
Max-Forwards: 70.<br>
From: 042335040 <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:99942335040@opsp.test.net"><sip:99942335040@opsp.test.net></a>;tag=1f62205074.<br>
To: 042335040 <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:99942335040@opsp.test.net"><sip:99942335040@opsp.test.net></a>.<br>
Call-ID: 61c67f739bef5a2e.<br>
CSeq: 1804289391 REGISTER.<br>
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER,
OPTIONS, UPDATE,<br>
PRACK, INFO.<br>
Authorization: Digest<br>
username="99942335040",realm="opsp.test.net",nonce="582d810c000058b<br>
d73adccf0d455c2a2159b3a3403c1f7a3",uri=<a
moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:opsp.test.net:5060">"sip:opsp.test.net:5060"</a>,res<br>
ponse="bc0c757c17f9b0976af35ec633dd83ca".<br>
Contact: 042335040 <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:99942335040@opsp.test.net;transport=udp"><sip:99942335040@opsp.test.net;transport=udp></a>;ex<br>
pires=3600.<br>
Privacy: none.<br>
Supported: path.<br>
User-Agent: Brcm-Callctrl/v1.10.3 M5T SIP
Stack/4.1.2.2.<br>
Content-Length: 0.<br>
<br>
UOpenSIPS:5060 -> UAC:5060<br>
SIP/2.0 401 Unauthorized.<br>
Via: SIP/2.0/UDP<br>
opsp.test.net;received=UAC;rport=5060;branch=z9hG4bKa4022<br>
5bd7495297c6.<br>
From: 042335040 <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:99942335040@opsp.test.net"><sip:99942335040@opsp.test.net></a>;tag=1f62205074.<br>
To: 042335040 <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:99942335040@opsp.test.net"><sip:99942335040@opsp.test.net></a>;tag=0c7ff67d927afc274<br>
b272138ce65100a.ac4d.<br>
Call-ID: 61c67f739bef5a2e.<br>
CSeq: 1804289391 REGISTER.<br>
WWW-Authenticate: Digest realm="opsp.test.net",<br>
nonce="582d811300005a88b92d0287a7460acce0a84e5d2a200b33", stale=true.<br>
Server: OpenSIPS (1.10.0beta-tls
(x86_64/linux)).<br>
Content-Length: 0.<br>
<br>
<br>
U UAC:5060 ->OpenSIPS:5060<br>
REGISTER <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="sip:opsp.test.net:5060">sip:opsp.test.net:5060</a>
SIP/2.0.<br>
Via: SIP/2.0/UDP
opsp.test.net;branch=z9hG4bKb5f2bbbf80e346f48.<br>
Max-Forwards: 70.<br>
From: 042335040 <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:99942335040@opsp.test.net"><sip:99942335040@opsp.test.net></a>;tag=1f62205074.<br>
To: 042335040 <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:99942335040@opsp.test.net"><sip:99942335040@opsp.test.net></a>.<br>
Call-ID: 61c67f739bef5a2e.<br>
CSeq: 1804289392 REGISTER.<br>
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER,
OPTIONS, UPDATE,<br>
PRACK, INFO.<br>
Authorization: Digest<br>
username="99942335040",realm="opsp.test.net",nonce="582d811300005a8<br>
8b92d0287a7460acce0a84e5d2a200b33",uri=<a
moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:opsp.test.net:5060">"sip:opsp.test.net:5060"</a>,res<br>
ponse="9ce3622addeedf74622a23697e6f3728".<br>
Contact: 042335040 <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:99942335040@opsp.test.net;transport=udp"><sip:99942335040@opsp.test.net;transport=udp></a>;ex<br>
pires=3600.<br>
Privacy: none.<br>
Supported: path.<br>
User-Agent: Brcm-Callctrl/v1.10.3 M5T SIP
Stack/4.1.2.2.<br>
Content-Length: 0.<br>
.<br>
<br>
<br>
UOpenSIPS:5060 -> UAC:5060<br>
SIP/2.0 200 OK.<br>
Via: SIP/2.0/UDP<br>
opsp.test.net;received=UAC;rport=5060;branch=z9hG4bKb5f2b<br>
bbf80e346f48.<br>
From: 042335040 <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:99942335040@opsp.test.net"><sip:99942335040@opsp.test.net></a>;tag=1f62205074.<br>
To: 042335040 <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:99942335040@opsp.test.net"><sip:99942335040@opsp.test.net></a>;tag=766e4f757c55b3450<br>
c9992a50fb64799-9163.<br>
Call-ID: 61c67f739bef5a2e.<br>
CSeq: 1804289392 REGISTER.<br>
Contact: <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:99942335040@opsp.test.net;transport=udp"><sip:99942335040@opsp.test.net;transport=udp></a>;expires=3600<br>
;received=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:UAC:5060">"sip:UAC:5060"</a>, <<a
moz-do-not-send="true"
class="moz-txt-link-freetext"
href="sip:99942335040@UAC:1024">sip:99942335040@UAC:1024</a><br>
> ;expires=119.<br>
Server: OpenSIPS (1.10.0beta-tls
(x86_64/linux)).<br>
Content-Length: 0.</font><br>
<br>
Do you see where could be an issue?<br>
<br>
<br>
tnx<br>
miha<br>
<br>
</font><br>
<div class="moz-cite-prefix">On 16/11/2016 08:11,
Miha wrote:<br>
</div>
<blockquote
cite="mid:17de93ae-ea15-7818-24a3-4dc31342893a@softnet.si"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<font face="Calibri Light">Hello Bogdan<br>
<br>
yes this was the case...<br>
<br>
thank you!<br>
<br>
<br>
br<br>
miha<br>
</font><br>
<div class="moz-cite-prefix">On 15/11/2016 18:35,
Bogdan-Andrei Iancu wrote:<br>
</div>
<blockquote
cite="mid:1e9cd559-d277-0fb0-6b1d-d4dd54e45059@opensips.org"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<tt>Hi Miha,<br>
<br>
When you handle REGISTER requests (from behind
NAT) most probably you use fix_nated_contact()
instead of fix_nated_register().<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 15.11.2016
09:11, Miha wrote:<br>
</div>
<blockquote
cite="mid:1f44deec-ac09-9de3-c938-e18a9b4171fa@softnet.si"
type="cite">
<meta http-equiv="content-type"
content="text/html; charset=windows-1252">
<font face="Calibri Light">Hello<br>
<br>
i need one info.<br>
I have one phone behind NAT and it is
registered on OpenSIPS. IN register packet,
which is send to OpenSIPS I can see
contact: <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:11181600519@192.168.0.101:5060;transport=UDP">"sip:11181600519@192.168.0.101:5060;transport=UDP"</a><br>
<br>
and let says that the public ip for this
device is xxx.xxx.xxx.xxx.<br>
<br>
<br>
When opensips sends INVITE it send to right
public ip and right port (source ip and
source port generated by router). The issue
is this:<br>
Invite is like: "<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="sip:11181600519@">sip:11181600519@</a></font><font
face="Calibri Light"><font face="Calibri
Light">xxx.xxx.xxx.xxx</font>:5060;transport=UDP"
and this request is then fw to this UAC
behind router. The UAC replays to this
INVITE with 404 Not found as it is waiting
to receive the same URI which was written in
contact (the userpart is ok, put the ip is
public, not private and this is the
issue).From what I can see in RFC this is
the case.<br>
<br>
<br>
Till now Idid not have any issues with this,
but now I found first phone which replays
with 404 and from RFC point of view there
should be private ip request :) . So is
there anything I can do :)?<br>
<br>
<br>
tnx<br>
miha<br>
</font> <br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>