Hi All,
Given a situation where there are multiple registrars, behind a single load balancer, sharing the same location table in DB, I understand that Path can be used to ensure everything works nicely with clients behind NAT. So, if UA1 is registered on P1, UA2 on P2, and UA1 calls UA2... P1 performs lookup, sees path and sends via P2.
What about situations where the distribution between registrars is being handled client-side through DNS SRV, not a load balancer? Path cannot be used then, right? As I understand it, in this instance add_path() will do nothing, is this correct?
Thanks in advance,
Charles
Hi,
you cannot use add_path(), but by creating your own Path header this works, e.g.:
append_hf("Path: sip:term@HOSTNAME:"+PORT+";lr\r\n"); (from our P-CSCF config)
Then your Proxy should also evaluate the DNS-SRV records.
Kind regards, Carsten -- Carsten Bock CEO (Geschäftsführer)
============================================================= Die ng-voice GmbH ist auf der Kamailio World 2013, 16./17. April 2013 => http://conference.kamailio.com/k01/=========================================...
ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany
http://www.ng-voice.com mailto:carsten@ng-voice.com
Office +49 40 34927219 Fax +49 40 34927220
Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/ Hi All,
Given a situation where there are multiple registrars, behind a single load balancer, sharing the same location table in DB, I understand that Path can be used to ensure everything works nicely with clients behind NAT. So, if UA1 is registered on P1, UA2 on P2, and UA1 calls UA2... P1 performs lookup, sees path and sends via P2.
What about situations where the distribution between registrars is being handled client-side through DNS SRV, not a load balancer? Path cannot be used then, right? As I understand it, in this instance add_path() will do nothing, is this correct?
Thanks in advance,
Charles
www.sipcentric.com
Follow us on twitter @sipcentric http://twitter.com/sipcentric
Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Unit 10 iBIC, Birmingham Science Park, Holt Court South, Birmingham B7 4EJ. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi,
Thanks for your reply.
I did try that, but the path is still not stored in location table on save. I have "use_path" parameter of registrar module enabled.
On 21 February 2013 23:17, Carsten Bock carsten@ng-voice.com wrote:
If the add the Path header manually, then it is not seen by the registrar/usrloc module, asthe header will only be added when generating the "to be forwarded" message - and this never happens as the message terminates on the registrar. You could try msg_apply_changes() after adding the Path header.
regards Klaus
http://kamailio.org/docs/modules/3.3.x/modules/textopsx.html#textopsx.msg_ap...
On 22.02.2013 00:33, Charles Chance wrote:
Hi Klaus,
That worked perfectly, thanks!
One thing I've noticed - nathelper is sending OPTIONS pings to all contacts, regardless of the incoming socket. So both servers are sending pings to all clients. I am assuming this is because in our tests the clients and servers are on the same subnet - do you think this is the case? Obviously, in a production environment where clients are behind NAT, it only makes sense to send keep-alives from the server a client is registered on.
Thanks again,
Charles
On 22 February 2013 07:43, Klaus Darilion klaus.mailinglists@pernau.atwrote:
-
Carsten Bock -
Charles Chance -
Klaus Darilion