I can see the temptation, but that’s actually looking at it backwards.
If you have multiple listeners, e.g.
or multiple listeners on the same interface with multiple ports, if it’s NAT’d AWS-style, e.g.
listen=udp:x.x.x.x:5060
listen=udp:x.x.x.x:5080 advertise “y.y.y.y:5080”
you can steer the traffic by manipulating the $fs pseudovar:
or, in the case of bridging between two disparate networks as formerly, just make use of automated outgoing interface discovery behaviour:
Assuming you have the ‘enable_double_rr’ parameter enabled, which you should:
you will find that the Record-Route headers automatically contain the correct ingress and egress listener addresses in the right directions at the right times, and you don’t need to do any byzantine management of their content. :-)
—
Sent from mobile, with due apologies for brevity and errors.
Do you have: mhomed=1 ?
Thank you for the reply. It little help for me, Right now probably I have to make logic which change record route depends on it where Kamailio send packets internal / outside
Hi,
You may wish to have a look at the ‘advertise’ directive to the core listen= parameter:
For more fine-grained control, record_route_preset() takes an argument:
But the first approach is better and more comprehensive for your situation, since it also covers Via.
— Alex
—
Sent from mobile, with due apologies for brevity and errors.
Hi,
I have some issue and dont have enought knowledge to fix it. I have simple infrastructure.
Internet -> router (NAT) -> kamailio
-> asterisk
Kamailio and Asterisk are inside the network and Kamailio places his own private address in the "record-route" headers instead of who's public. There is configuration to said to him what IP is proper ?
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users