Hi,
I don't understand the trouble: Wouldn't the following lead to the exact example:
listen=tls:1.2.3.4:8007 advertise teams.tutpro.com:8007 listen=tcp:1.2.3.4:5070
As soon as you do: $fs = "tcp:1.2.3.4:5070"; record_route(); (or put the other socket into $fs)
This results into two record-route headers, one with the hostname and one with the IP.
We use the Hostnames in all kinds of Record-Route and Via-Headers by doing exactly this.
Thanks, Carsten
-- Carsten Bock I CTO & Founder
ng-voice GmbH
Trostbrücke 1 I 20457 Hamburg I Germany T +49 40 524 75 93-40 | M +49 179 2021244 I www.ng-voice.com
Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock
Am Do., 11. Feb. 2021 um 09:45 Uhr schrieb Juha Heinanen jh@tutpro.com:
Sergey Safarov writes:
Maybe need to move into more global changes...
How about DNS hostname usage for all headers? "Via", "Record-Route" maybe "Contact" when Kamailio with extra modules play media?
how about global directive like header_with_hostname=tue
I'm not sure if that is a good idea, since, for example, I would like to keep on using IP address 127.0.0.1:
Record-Route: sip:teams.tutpro.com:8007;transport=tls;r2=on;lr;pm=0 Record-Route: sip:127.0.0.1:5070;transport=tcp;r2=on;lr;pm=0
-- Juha
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users