s outbound flow
routing (RFC 5626) it will leave the private IP in the Contact header and
the check will false trigger and corrupt the path. I ended up implementing
flow-routing within opensips instead.
Regards,
Kennard
From: Doug
To: users@lists.opensips.org
Date: 10/12/2010 11:36 AM
To: OpenSIPS
users mailling list
Date: 10/12/2010
08:47 AM
Subject: [OpenSIPS-Users]
NAT and Re-INVITE
Sent by: users-boun...@lists.opensips.org
Hi All,
I've got a problem I'm
response to A's re-INVITE? This contact address will become the R-URI of
all subsequent in-dialog messages from A (e.g., INFO, MESSAGE, BYE).
Regards,
Kennard
From: Doug
To: OpenSIPS users mailling list
Date: 10/12/2010 08:47 AM
Subject: [OpenSIPS-Users] NAT and Re-INV
Hi All,
I've got a problem I'm not 100% sure how to resolve.
Ok the scenario is, client A is on a public interface, Client B is on a
private IP address and has cflag 6 set in the location table.
Client A calls Client B via Opensips.
Now during the initial INVITE, opensips locates Client B, l
