Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IPOSE R11.1 in AWS - SIP trunk media address 1

Status
Not open for further replies.

telfire

Vendor
Dec 18, 2008
118
US
I have had a IPOSE in AWS with a SIP trunk from Flowroute with no issues for some time. Somewhat recently I am getting no audio on calls. When I opened a ticket with Flowroute, they no longer like that the AWS private IP address that is LAN1 is showing up in the Contact field. They want the public IP address to appear. I have already tried adding my public IP as the local domain on the SIP line tab. I have the Network topology setup as a One-to-One NAT with the public IP address filled in. I don't have any idea where I would manipulate this... I have attached the email snippet from the provider.


Upon investigating this further, we are seeing a NAT issue on the destination end. We see that the call is going to <AWS PUBLIC IP>, we see in the contact field the <IPO private IP at LAN1>. While some calls may go through, others will not have audio or will go through, but then drop at some point. To fix this change, you'll need make sure that the NAT setting in your PBX is using <AWS PUBLIC IP>. This may be under the advanced setting of the trunk or under network settings. However, as we are not a PBX vendor, we could not tell you where to make this change. You'll want to reach out to them to fix this. Once this is done, it will resolve your issue. Thank you!






APSS-Midmarket
ACIS-Midmarket
ACSS-Midmarket
ACDS-Midmarket
 
The public IP goes into the lan1 network topo, and then set the trunk to use LAN1 instead of none in the transport tab of the sip line.
Also, be sure to run stun, or find out how it is setup. They may have done a 1:1 NAT instead of a port forward (annoying), in which case the firewall topo needs to be correct. You can use stunserver.org port 3478 to try to have stun figure it out.

-Austin
I used to be an ACE. Now I'm just an Arse.
qrcode.png
 
So the part that apparently fixed this was changing the topology to use LAN1 instead of the default. Everything else that you suggested was already in place.
Thanks AACon!

APSS-Midmarket
ACIS-Midmarket
ACSS-Midmarket
ACDS-Midmarket
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top