New SIP Line

[84Mike]

I am setting up a new SIP line from a provider on IPO 9. I am able to complete calls inbound and outbound, but there is no talk path. The provider tells me they are seeing the internal IP address of my IPO instead of the public IP address. There must be some way to fix this in IPO? Please help! Thanks! (It is behind a firewall)

 

[amriddle01]

Crap provider, they don't have a SBC. You need too look at using STUN and/or port forwarding

 

[84Mike]

Thanks for the response...can you expand a little? I'm fairly green at this, but I have been trying and researching.

 

[capthoward]

A lot of times, there's a compatibility document for the provider that details the IPO config. Which provider are you connecting with? I typically google that provider and IP Office and most times there's a document.

 

[DavidCT]

What firewall?

Find in the firewall something like sip alg or sip transformations. Turn it on. Reboot IPO.

 

[janni78]

What are you're Network Topology setting under System -> LANx -> Network Topology tab?

You can set there which IP you show to the provider.
Also set which topology to use on the SIP line.

"Trying is the first step to failure..." - Homer

 

[84Mike]

I am using a Cisco ASA 5512 firewall...seems to not matter what I do, I cannot get the IP Office to use the public IP. Always sends the private IP. The call sets up just fine, but there is one-way or no-way talk path, depending on the direction of the call.

07:13:55 218004mS SIP Tx: UDP 10.1.50.4:5060 -> 216.xx.xxx.xxx:5060
BYE sip:+1724xxxxxxx@67.xxx.xx.xxx:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.50.4:5060;rport;branch=z9hG4bK3975843078fb585799430265e2348b58
Route: <sip:216.xx.xxx.xxx:5060;lr;ftag=a87381fb37d0e545>
From: "Extn201" <sip:+1724xxxxxxx@216.xx.xxx.xxx>;tag=a87381fb37d0e545
To: <sip:+1724xxxxxxx@216.xx.xxx.xxx>;tag=gK04c23499
Call-ID: a185fd203de41ae0c4b5381518b24973
CSeq: 305243401 BYE
Contact: "Extn201" <sip:201@10.1.50.4:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Reason: Q.850;cause=16;text="Normal call clearing"
User-Agent: IP Office 9.0.3.0 build 941
Content-Length: 0

 

[tlpeter]

As told before program a STUN server.

BAZINGA!

I'm not insane, my mother had me tested!

 

[84Mike]

I used a public STUN server...it yielded results. Changed the settings to Full Cone Nat, and also updated the public IP. Still same result. Call connects, no talk path.

 

[amriddle01]

So then you need the "and/or port forwarding"

Seriously though find a provider with SBCs and allows registered trunks

 

[84Mike]

We got this working. Used SIP ALG in the firewall to solve our issue. Thanks for all the responses.

 

[amriddle01]

Cool, that usually breaks stuff and port forwarding is required