Hi guys, i have a kamailio running on the wan (my central kamailio) and i have phones on a private network range 172.20.0.0/16 behind a NAT. i also run another kamailio locally to collect all sip phones on my network and this one use the DB of the remote central kamailio. the local kamailio does t_relay_to() the ip of the central kamailio
route { if (uri==myself) {
if (method=="REGISTER") { route(2); exit; };
route[2] { rewritehost("public_remote_kamailio"); if(!t_relay_to("udp:public_remote_kamailio:5060")) { sl_reply_error(); }; exit; }
the bad thing is once the phones get registered with non-routable ip (like in the attached picture) trying to INVITE them directly by requesting public_kamailio_ip result in non-working situation.
how should I rewrite my dst_domain when registring in a way INVITE triggers to the local kamailio.
My local kamailio runs with the listen udp:private_local_kamailio advertise udp:public_local_kamailio
I try to be explicit but my understanding is not perfect, it would be nice you could give me a hand.
I put my local kamailio.cfg attached.
thx
On Thu, May 12, 2016 at 03:54:12PM +0200, Sébastien Brice wrote:
the bad thing is once the phones get registered with non-routable ip (like in the attached picture) trying to INVITE them directly by requesting public_kamailio_ip result in non-working situation.
how should I rewrite my dst_domain when registring in a way INVITE triggers to the local kamailio.
My local kamailio runs with the listen udp:private_local_kamailio advertise udp:public_local_kamailio
I'm not sure but I think you might want to use Path to resolve this.
When a phone REGISTERs, use http://www.kamailio.org/docs/modules/stable/modules/path.html#idp3019976 and relay.
On the public kamailio enable path support in the registrar module: http://www.kamailio.org/docs/modules/stable/modules/registrar.html#idp194230...
You might have to parse headers during INVITE to the natted phones to figure out the received header with the local adres.
-
Daniel Tryba -
Sébastien Brice