[Kamailio-Users] SIP proxy is expecting "Route:" header to be filled information from the last "Contact:" header ?
Hi all, first thank you for maintaining this list and free/Open source SIP proxy software.
I am working on one interco problem with a remote SIP proxy running on Kamailio.
Cisco(U1) --> Opensips(P1) --> Internet --> Kamailio(P2) --> Asterisk(U2)
The remote proxy(P2) is expecting us to fill the "Route:" header taking information from the "Contact:" header, according to my research the "Route:" header as to be filled using the information found in the last "Record-route:" header.
Note that the "Contact:" header IP address is the one of U2, as it is the destination UA.
I think our partner using Kalamailio only interconnected UA not Proxy, since they never faced this problem.
Of course I do not suspect Kalamailio to be doing something wrong, I just want to validate what we should expect, and investigate further from there.
I will have to contact the technicien that as configured the Kalamailio server to validate why face this behavior.
--------------------------------------------------------------------------
" 16.12.1.3 Rewriting Record-Route Header Field Values " http://www.ietf.org/rfc/rfc3261.txt -------------------------------------------------------------------------- We found a temporary solution to make it worko, where we hardcoded the replacement of the IP address in the "Route:" header with the one of the U2
subst('/^Route: <sip:P2;(.*)$/Route: <sip:U2;\1/');
El Martes, 12 de Enero de 2010, Julien Chavanton escribió:
Hi all, first thank you for maintaining this list and free/Open source SIP proxy software.
Crossposintg is not good: http://en.wikipedia.org/wiki/Crossposting
The senario involve both Opensip and Kalamailio, I did see a problem to post on both list.
________________________________
From: users-bounces@lists.kamailio.org on behalf of Iñaki Baz Castillo Sent: Tue 12/01/2010 7:30 PM To: users@lists.kamailio.org Subject: Re: [Kamailio-Users] SIP proxy is expecting "Route:" header to befilled information from the last "Contact:" header ?
El Martes, 12 de Enero de 2010, Julien Chavanton escribió:
Hi all, first thank you for maintaining this list and free/Open source SIP proxy software.
Crossposintg is not good: http://en.wikipedia.org/wiki/Crossposting
-- Iñaki Baz Castillo ibc@aliax.net
_______________________________________________ Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
I take this as an answer :
"(Route set is filled with Record-Route values of the INVITE - 200)."
Case closed, sorry but reading RFC about SIP proxy is not always 100% clear for me, for example there is no ACK in the example.
________________________________
From: users-bounces@lists.kamailio.org on behalf of Iñaki Baz Castillo Sent: Tue 12/01/2010 7:30 PM To: users@lists.kamailio.org Subject: Re: [Kamailio-Users] SIP proxy is expecting "Route:" header to befilled information from the last "Contact:" header ?
El Martes, 12 de Enero de 2010, Julien Chavanton escribió:
Hi all, first thank you for maintaining this list and free/Open source SIP proxy software.
Crossposintg is not good: http://en.wikipedia.org/wiki/Crossposting
-- Iñaki Baz Castillo ibc@aliax.net
_______________________________________________ Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Hi Julien,
On 1/12/10 8:46 PM, Julien Chavanton wrote:
I take this as an answer : "(Route set is filled with Record-Route values of the INVITE - 200)." Case closed, sorry but reading RFC about SIP proxy is not always 100% clear for me, for example there is no ACK in the example.
indeed, Route headers are built out of Record-Route headers found in INVITE and 200ok.
Note that Kamailio is doing by default loose routing, you may find some devices still doing the old specs with strict-routing.
When it is the case of strict routing you find Contact address in last Route header, otherwise, with loose routing, contact address is in Request URI and Route headers only with addresses from Record-Route.
If you are involved in a scenario with strict and loose routers, then it is a bit more complex. However Kamailio deals very well with both separately or in a mixture.
Cheers, Daniel
By the way, a short description of record-routing, strict vs loose:
http://sip-router.org/docbook/sip-router/branch/master/sip/sip_introduction....
If you have kamailio 3.0.0 source tree, you find it under doc/sip/ directory as well.
Hope it helps. Cheers, Daniel
On 1/12/10 9:04 PM, Daniel-Constantin Mierla wrote:
Hi Julien,
On 1/12/10 8:46 PM, Julien Chavanton wrote:
I take this as an answer : "(Route set is filled with Record-Route values of the INVITE - 200)." Case closed, sorry but reading RFC about SIP proxy is not always 100% clear for me, for example there is no ACK in the example.
indeed, Route headers are built out of Record-Route headers found in INVITE and 200ok.
Note that Kamailio is doing by default loose routing, you may find some devices still doing the old specs with strict-routing.
When it is the case of strict routing you find Contact address in last Route header, otherwise, with loose routing, contact address is in Request URI and Route headers only with addresses from Record-Route.
If you are involved in a scenario with strict and loose routers, then it is a bit more complex. However Kamailio deals very well with both separately or in a mixture.
Cheers, Daniel
-- Daniel-Constantin Mierla *http://www.asipto.com/
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
The real source of my problem was caused by a missuse of
fix_nated_contact();
This was causing the creation of a wrong "request uri" in the ACK
Thank you Daniel for finding it in the trace
________________________________
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Tue 12/01/2010 8:04 PM To: Julien Chavanton Cc: users@lists.kamailio.org Subject: Re: [Kamailio-Users] SIP proxy is expecting "Route:" header to befilled information from the last "Contact:" header ?
Hi Julien,
On 1/12/10 8:46 PM, Julien Chavanton wrote:
I take this as an answer : "(Route set is filled with Record-Route values of the INVITE - 200)." Case closed, sorry but reading RFC about SIP proxy is not always 100% clear for me, for example there is no ACK in the example.
indeed, Route headers are built out of Record-Route headers found in INVITE and 200ok.
Note that Kamailio is doing by default loose routing, you may find some devices still doing the old specs with strict-routing.
When it is the case of strict routing you find Contact address in last Route header, otherwise, with loose routing, contact address is in Request URI and Route headers only with addresses from Record-Route.
If you are involved in a scenario with strict and loose routers, then it is a bit more complex. However Kamailio deals very well with both separately or in a mixture.
Cheers, Daniel
On 1/13/10 7:06 AM, Julien Chavanton wrote:
The real source of my problem was caused by a missuse of fix_nated_contact(); This was causing the creation of a wrong "request uri" in the ACK Thank you Daniel for finding it in the trace
welcome!
:-) and that problem was not in kamailio which did all ok :-D.
Cheers, Daniel
*From:* Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Sent:* Tue 12/01/2010 8:04 PM *To:* Julien Chavanton *Cc:* users@lists.kamailio.org *Subject:* Re: [Kamailio-Users] SIP proxy is expecting "Route:" header to befilled information from the last "Contact:" header ?
Hi Julien,
On 1/12/10 8:46 PM, Julien Chavanton wrote:
I take this as an answer : "(Route set is filled with Record-Route values of the INVITE - 200)." Case closed, sorry but reading RFC about SIP proxy is not always 100% clear for me, for example there is no ACK in the example.
indeed, Route headers are built out of Record-Route headers found in INVITE and 200ok.
Note that Kamailio is doing by default loose routing, you may find some devices still doing the old specs with strict-routing.
When it is the case of strict routing you find Contact address in last Route header, otherwise, with loose routing, contact address is in Request URI and Route headers only with addresses from Record-Route.
If you are involved in a scenario with strict and loose routers, then it is a bit more complex. However Kamailio deals very well with both separately or in a mixture.
Cheers, Daniel
-- Daniel-Constantin Mierla *http://www.asipto.com/
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
-
Daniel-Constantin Mierla -
Iñaki Baz Castillo -
Julien Chavanton