Hi Patrick

Agreed, this could become an issue when we do dual stack ipv4 and ipv6 unless we use a hostname which will probably cause other issues.

But overall sip compliant component must Always follow Route ip before contact IP.

I will test how the know buggy client behaves.

While testing with topos I came across another issue.

Then I have topos enabled on a REG instance, I see this PRACK handling:

CPE <=> KAM Reg <=> KAM Core <=> IC

CPE => Invite, supported: 100rel CPE <= 180 RINGING, required: 100rel

CPE => PRACK => KAM Reg => PRACK to itself looping MANY times adding a VIA Header on each loop.

I don't understand, why in this situation, the REG is sending PRACK to itself.

As soon as I comment out topos PRACK is sent correctly to the party reqesting 100rel.

Any hint where to look?

Mit freundlichen Grüssen

-Benoît Panizzon-

Hi Patrick

Male sure record_route is used in kamailio script.

I will double check by outputing a notice to log before calling record_route but I'm quite confident this is the case for invites.

Do I need to explicitely call record_route for ACK and PRACK or even for all messages when using topos? Is this where topos hooks in?

Normally it should be used in initial invite.

Issue is not only PRACK, but also ACK. I narrowed down the issue to this:

topos active:

if (has_totag()) { # True if ( t_check_trans() ) { # False route(RELAY); } else { # discard ACK not matching transaction exit; } }

I end up discarding ACK and PRACK because they don't match a transaction.

topos commented out:

if (has_totag()) { # True if ( t_check_trans() ) { # True route(RELAY); } else { # discard ACK not matching transaction exit; } }

Ack is routed.

Any explanation why topos causes t_check_trans() to return false on ACK and PRACK?