Kamailio 5.8.6 confusing ip protocol version of $nh(d) - where does siptrace capture the packet?

Benoit Panizzon via sr-users <[email protected]>
Newsgroups gmane.comp.voip.ser
Organization ImproWare AG
Message-ID <[email protected]>
Hi Gang

I have come across an strange issue.

To make rtpengine use the same IP protocol as signaling I examine:

ip_type($nh(d))

Now I have encountered a very strange case involving Kamailio with topos
and Asterisk.

Initial INVITE was performed via IP6 from Asterisk to Kamailio.

Then two Re-Invites were performed Kamailio => Asterisk to refresh the
session.

The first one happened via IPv6 and the $nh(d) ip_type was IPv6 as
rtpengine got hinted to use IPv6

On the second one, something went wrong:

According to what Kamailio sent to Homer via siptrace module, the
Invite was sent to the IPv6 address of the Asterisk machine.

rtpengine got hinted IP4, so $nh(d) must have contained an ipv4
address! But the R-URI (provided by topos) contains the IPv6 address of
the Asterisk machine.

The HEP capture on Asterisk did not record that Re-Invite sent from
Kamailio. Neiter via IPv4 nor via IPv6.

Has anyone else seen such issues?

At which level does the siptrace module work? Is it capturing 'on wire'
or is it capturing what kamailio believes it is sending which might be
altered when sent out on the wire?

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 -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.