Hi,
hm the only reason why I'm playing with kamailio is that it should be
able to translate IPv6 from customer phones behind Fritz!Box (NAT) to IPv4
used by the provider (which is not able to handle IPv6).
But it looks that he accept in general the packet with 2 Via lines (also
with IPv6 as
Hello,
kamailio adds only outbound address in in a new single Via header, being
required by the next hop to send the reply back o kamailio. However, the
full Via stack has to be sent back in the reply, but the registrar
doesn't do it.
Based on the server header in reply, it is a Cirpack and it
Hi,
of course kamailio is listening on IPv4 and IPv6.
Register coming from IPv6 and goes out on IPv4:
REGISTER sip:sip.ggew-net.de SIP/2.0
Via: SIP/2.0/UDP
217.113.176.155;branch=z9hG4bK98fc.314c428d232717f129932376c83e2c02.0
Via: SIP/2.0/UDP
Am Mittwoch, 5. September 2018, 17:43:34 CEST schrieb Karlheinz Knapp:
> we want to use kamailio as a IPv6 to IPv4 proxy.
> IPv4 to IPv4 bridging with NAT works.
>
> If we come from an IPv6 address, the registration packet is send via IPv4
> to the provider.
> He answers with 401 Unauthorized and
Hi,
we want to use kamailio as a IPv6 to IPv4 proxy.
IPv4 to IPv4 bridging with NAT works.
If we come from an IPv6 address, the registration packet is send via IPv4
to the provider.
He answers with 401 Unauthorized and one Via line in the header.
On the IPv6 side was no Via line in the packet.
