Re: [OpenSIPS-Users] IPv6 causing problems with HEP in siptrace

2017-02-05 Thread Bogdan-Andrei Iancu

Hi Jeff,

I suspect that this report is related to the second one you made - a 
wrong traced SRC interface for the replies will generate a mixture of 
IPv4 and IPv6 for same packet.

Please apply that fix and let's see if it fixes this one too.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 02/05/2017 01:12 AM, Jeff Pyle wrote:

Hi Bogdan,

Yes, but they do ingress and egress different families.

In this case the UAC's src IP is IPv6, talking to the proxy's IPv6 
interface address (no NAT64).  In the script there is a sethostport() 
to an IPv4 address, and a force_send_socket() to the proxy's IPv4 
interface address. Then a t_relay().


I have a sip_trace("tid", "d") right after create_dialog() for initial 
invites.  In a pure IPv4 flow this captures all ingress and egress 
traffic (except for t_relay's '100 Giving a try').  In this mixed IPv6 
-> IPv4 flow, I see the error, and capture only the egress IPv4 leg.


The HEP target is IPv4 at the moment.  The HEP capture server is also 
dual-stack, if this is relevant.



- Jeff


On Sat, Feb 4, 2017 at 12:58 PM, Bogdan-Andrei Iancu 
mailto:bog...@opensips.org>> wrote:


Hi Jeff,

That error is generated when the src and dst IP have different AF
families - which of course is impossible :)

I guess you get the error when you have an incoming SIP packet
over IPv6 (so both SRC and DST should be IPv6), right ?

Best regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com 

On 02/04/2017 03:58 AM, Jeff Pyle wrote:
Hello, I have a simple dual-stack OpenSIPS 2.2.2 configuration. 
It includes a registrar and basic routing between locally

registered users.  These users have a mix of IPv4 and IPv6
contacts.  All is well.  I recently added Homer to the mix.  The
siptrace module is acting as a capture agent, duplicating
messages over HEPv3 to an upstream Homer capture server. When one
of the clients is IPv6, duplication fails.  I see this message:
ERROR:siptrace:trace_send_hep_duplicate: ERROR:
trace_send_hep_duplicate: interworking detected ?
ERROR:siptrace:save_siptrace: Failed to duplicate with hep to <:>
I'd like to duplicate messages regardless whether they've IPv4 or
IPv6, as many dialogs are both.  The Homer capture server is
IPv6-enabled and can receive HEP messages either (I think).  I've
tried to configure the siptrace trace_id with an IPv6 address but
it doesn't look like it's able to parse it.
What am I missing?
- Jeff

___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] IPv6 causing problems with HEP in siptrace

2017-02-04 Thread Bogdan-Andrei Iancu

Hi Jeff,

That error is generated when the src and dst IP have different AF 
families - which of course is impossible :)


I guess you get the error when you have an incoming SIP packet over IPv6 
(so both SRC and DST should be IPv6), right ?


Best regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 02/04/2017 03:58 AM, Jeff Pyle wrote:

Hello,

I have a simple dual-stack OpenSIPS 2.2.2 configuration.  It includes 
a registrar and basic routing between locally registered users.  These 
users have a mix of IPv4 and IPv6 contacts.  All is well.  I recently 
added Homer to the mix.  The siptrace module is acting as a capture 
agent, duplicating messages over HEPv3 to an upstream Homer capture 
server.


When one of the clients is IPv6, duplication fails.  I see this message:

ERROR:siptrace:trace_send_hep_duplicate: ERROR: 
trace_send_hep_duplicate: interworking detected ?

ERROR:siptrace:save_siptrace: Failed to duplicate with hep to <:>

I'd like to duplicate messages regardless whether they've IPv4 or 
IPv6, as many dialogs are both.  The Homer capture server is 
IPv6-enabled and can receive HEP messages either (I think).  I've 
tried to configure the siptrace trace_id with an IPv6 address but it 
doesn't look like it's able to parse it.


What am I missing?



- Jeff





___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] IPv6 causing problems with HEP in siptrace

2017-02-03 Thread Jeff Pyle
Hello,

I have a simple dual-stack OpenSIPS 2.2.2 configuration.  It includes a
registrar and basic routing between locally registered users.  These users
have a mix of IPv4 and IPv6 contacts.  All is well.  I recently added Homer
to the mix.  The siptrace module is acting as a capture agent, duplicating
messages over HEPv3 to an upstream Homer capture server.

When one of the clients is IPv6, duplication fails.  I see this message:

ERROR:siptrace:trace_send_hep_duplicate: ERROR: trace_send_hep_duplicate:
interworking detected ?
ERROR:siptrace:save_siptrace: Failed to duplicate with hep to <:>

I'd like to duplicate messages regardless whether they've IPv4 or IPv6, as
many dialogs are both.  The Homer capture server is IPv6-enabled and can
receive HEP messages either (I think).  I've tried to configure the
siptrace trace_id with an IPv6 address but it doesn't look like it's able
to parse it.

What am I missing?



- Jeff
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users