[OpenSIPS-Devel] [ opensips-Bugs-3551339 ] b2b uses socket instead of advertised address in Contact

[SourceForge.net]

Bugs item #3551339, was opened at 2012-07-29 07:10
Message generated for change (Comment added) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3551339&group_id=232389

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: trunk
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Eric Tamme ()
Assigned to: Nobody/Anonymous (nobody)
Summary: b2b uses socket instead of advertised address in Contact

Initial Comment:
I have been using the built in B2B scenario "top hiding" while running on Amazon EC2 with an associated Elastic IP.  EC2 uses a 1 to 1 nat, So I have set the opensips advertised_address to my public elastic IP address.

When b2b init request is used, the proxy sends out a new invite and uses the advertised address in the Via header, but it uses the locally bound socket IP in the Contact header.  This obviously causes problems because the local socket IP is a private ip address within EC2.

I have captured a SIP trace of this behaviour which you can find here.

http://pastie.org/private/ury9whe8twzp7dguznsea

I have tested this against 1.8 tarball, and opensips_head from svn as of 7/29/2012

----------------------------------------------------------------------

>Comment By: Eric Tamme ()
Date: 2012-08-01 09:23

Message:
NOTE:  Because this is a 1 to 1 NAT situation, not a multi NIC setup, I can
not call force_send_socket with the public IP address, because it does not
exist on the box.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3551339&group_id=232389