Broadvox SIP trunks using static IP authentication

[nurban]

We recently swapped out our systems from a Samsung OfficeServ 7100 to an IP Office running 7.0(12).

We've adjusted our router to forward traffic from 5060 as well as the ports set on the RTP fields the VOIP tab. Our trunks register via Static IP, and that hasn't changed.

I've followed the guide put out from Avaya/Broadvox during testing, and reviewed settings both with vendor tech support, and it appears that everything is set as it needs to be... The system status app is resolving the IP address from the domain name, so we know that network connectivity isn't an issue, but the trunks show Out of Service and Broadvox reports that they arent seeing any traffic from us.

One thought poised to us was to use "Run STUN" - that cleared out the Public address and port but left the firewall settings as Static Port Block.

Does anyone have any ideas? We've probably played with the settings for well over 6 hours at this point

 

[tlpeter]

Set the network topology to none and make an iproute to the provider.



BAZINGA!

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

 

[nurban]

I have an IP route built that points all the traffic from the control unit to our router... That should cover it, shouldn't it?

The provider uses a DNS name as they change their IP addresses often when switching out gear.


IPO Implement
ACSS

 

[tlpeter]

When there is no RX traffic then you do not reach the provider.
That is what they are telling you too so it must be something on your site.

Open System Status and go to iproutes and do a ping.


BAZINGA!

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

 

[kholladay]

Launch Monitor. Click on the Clear All button then select the SIP tab. At the bottom enable SIP Rx and SIP Tx then post the results here.

Kyle Holladay
ACSS & APSS SME Communications
MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA

"I have one speed, I have one gear...GO!!!" - Charlie Sheen

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[nurban]

Have outbound routing working fine... needed to add an IP Route of 0.0.0.0 and point that towards our gateway.

Inbound is reaching us and we're returning a 200OK, but we're signaling that audio should stream on port 44152, but we start sending on 19657, which isn't matching the header info we're sending the carrier...

5 minutes later...
Turns out that I needed to put in our Public IP address under the Network Top tab, not the local IP address.

All is working - Thanks for all your input.


IPO Implement
ACSS