Hi,
I do not think that record_route() uses the advertised_address
variables. We have been using the advertised_address / advertised_port
variables in the config file and although they are used in the Via
headers, they are not substituted into the Record Route lines.
record_route_advertised_a
Take a look at set_advertised_address:
http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:3.1.x#set_advertised_address
Set it and then record_route() will properly fill the Record-Route header.
Regards,
Ovidiu Sas
--
VoIP Embedded, Inc.
http://www.voipembedded.com
On Fri, Dec 2, 2011 at 2
Hi,
I wouldn't say it a bug then, since its ok from specs poiint of view. The
real issue was that we had Asterisk realtime previously which had the same
extension set enabled in DB.
So the users with same extensions registering on Kamailio making calls via
asterisk had trouble because asterisk st
The fact that there is a function in the source code does not mean you can use
it in the route script; functions have to be properly defined and
exposed/exported to make that happen. Indeed, there are far more functions in
the C source than in the modules' exported parameters list.
Check the '
Hello,
I have Kamailio 3.1.0 behind a NAT. We need the Firewall for sip-security
reasons.
Currently I'm using record_route_preset("advertised_Address") for keeping the
advertised address in the record-route header. This works for fine when I have
all clients running on UDP protocol.
I currentl
