Hi out there!
While experimenting with the listen and adverize 'hostname' option I came across a voice switch, which I suppose fails if the Via header is not an IPv4 address.
There is a record_route_advertised_address(address) in the RR module, to set a customer Record-Route Header.
Is there something similar for the Via header so I could try if having an IP address instead of a hostname in the top-most Via would solve the issue?
Or is there a way to remove all via header? Remove_hf("Via") in the branch route trigger garbles the From: HF.
Mit freundlichen Grüssen
-Benoît Panizzon-
Are you talking about the proxy's own Via hop?
If your "advertised" address is an IP rather than a DNS name, that should be mimicked in the Via headers inserted by the proxy.
On Dec 22, 2022, at 10:10 AM, Benoit Panizzon benoit.panizzon@imp.ch wrote:
Hi out there!
While experimenting with the listen and adverize 'hostname' option I came across a voice switch, which I suppose fails if the Via header is not an IPv4 address.
There is a record_route_advertised_address(address) in the RR module, to set a customer Record-Route Header.
Is there something similar for the Via header so I could try if having an IP address instead of a hostname in the top-most Via would solve the issue?
Or is there a way to remove all via header? Remove_hf("Via") in the branch route trigger garbles the From: HF.
Mit freundlichen Grüssen
-Benoît Panizzon-
I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________
Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________ __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hi Alex
Are you talking about the proxy's own Via hop?
Exactly...
If your "advertised" address is an IP rather than a DNS name, that should be mimicked in the Via headers inserted by the proxy.
Well the issue is, that we operate two kamailio proxy with DMQ synced states so that if one fails, the other will get the traffic.
But that does not work, if the Via contains the IP address of the proxy. So I added a hostname in the advertised config to have a hostname pointing to both ip addresses in the Via.
This works towards our IC SBC and towards other kamailio instances we use as registrar, but not towards one of our older 'commercial' voice switches.
So towards some 'endpoints' I would need an IP in the Via and towards others I would need a hostname.
But I realised, we most probably have to re-consider our idea to run all our kamailio instances in a load-balanced DMQ master-master set-up.
A CPE, even when the NAPTR entry or DNS Hostname it registers to points to multiple registrar instances, in the end registers to ONE ip address. In a NAT scenario, this is the IP which the SIP ALG on the customer firewall handles.
In a Master-Master registrar scenario, the INVITE towards a CPE might originate from the IP of the registrar that CPE did not register to and therefore the SIP ALG not knowing about and never make it through NAT.
PS: Still looking for ideas, how this could be solved.
Depending on where and how you are setting this up, you could leverage floating IPs and if one node fails the IP is "moved" to the good node…
On Thu, Dec 22, 2022 at 23:21 Benoît Panizzon benoit.panizzon@imp.ch wrote:
Hi Alex
Are you talking about the proxy's own Via hop?
Exactly...
If your "advertised" address is an IP rather than a DNS name, that should be mimicked in the Via headers inserted by the proxy.
Well the issue is, that we operate two kamailio proxy with DMQ synced states so that if one fails, the other will get the traffic.
But that does not work, if the Via contains the IP address of the proxy. So I added a hostname in the advertised config to have a hostname pointing to both ip addresses in the Via.
This works towards our IC SBC and towards other kamailio instances we use as registrar, but not towards one of our older 'commercial' voice switches.
So towards some 'endpoints' I would need an IP in the Via and towards others I would need a hostname.
But I realised, we most probably have to re-consider our idea to run all our kamailio instances in a load-balanced DMQ master-master set-up.
A CPE, even when the NAPTR entry or DNS Hostname it registers to points to multiple registrar instances, in the end registers to ONE ip address. In a NAT scenario, this is the IP which the SIP ALG on the customer firewall handles.
In a Master-Master registrar scenario, the INVITE towards a CPE might originate from the IP of the registrar that CPE did not register to and therefore the SIP ALG not knowing about and never make it through NAT.
PS: Still looking for ideas, how this could be solved.
-- Mit freundlichen Grüssen
-Benoît Panizzon- @ HomeOffice und normal erreichbar
I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________
Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________ __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hi,
On Dec 23, 2022, at 2:15 AM, Benoît Panizzon benoit.panizzon@imp.ch wrote:
So towards some 'endpoints' I would need an IP in the Via and towards others I would need a hostname.
Could this dimension of the problem, at least, perhaps be solved with two listeners, albeit on different ports, which have different 'advertised' addresses?
listen=udp:1.1.1.1:5060 advertised 2.2.2.2:5060 listen=udp:1.1.1.1:5070 advertised dns.fqdn.host:5060
But I realised, we most probably have to re-consider our idea to run all our kamailio instances in a load-balanced DMQ master-master set-up.
A CPE, even when the NAPTR entry or DNS Hostname it registers to points to multiple registrar instances, in the end registers to ONE ip address. In a NAT scenario, this is the IP which the SIP ALG on the customer firewall handles.
In a Master-Master registrar scenario, the INVITE towards a CPE might originate from the IP of the registrar that CPE did not register to and therefore the SIP ALG not knowing about and never make it through NAT.
I do agree that this approach is a bit idealistic, mostly because of NAT.
This is the problem SIP Outbound (RFC 5626) was created to solve, but it requires rather explicit support on the CPE, which, at the last time I last looked into it, did not seem to be widespread.
-- Alex
-
Alex Balashov -
Benoit Panizzon -
Joel Serrano