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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Issues with SIP Trunk on R11.0.4.1.0, "Waiting for Line" and then Connects 2

Status
Not open for further replies.

dsm600rr

IS-IT--Management
Nov 17, 2015
1,444
US
All,

Having intermittent issues with my NexVortex SIP Trunk.

From what I can tell, this is only on Outbound calls. All testing is to the same outbound TN

Most of the time, when I place an outbound call, it connects right away as it should.

Other times, I will get "Waiting for Line" and the "Beep-Beep-Beep".

If I get the "Waiting for Line" and wait for: "Beep-Beep-Beep"-"Beep-Beep-Beep"...."Beep-Beep-Beep" and then it connects.

Thoughts?

I did not see anything much in SSA:

12651485mS SIP Rx: UDP 104.219.163.73:5060 -> 172.30.20.1:5060
SIP/2.0 407 Proxy Authentication Required


ACSS
 
That all depends on how you have the SIP URI setup. If you have use internal data then yes you need the SIP tab filled out for users. If you just put the main callerID in under the SIP URI it will present that number for everyone and the SIP tab doesn't need filled out (shouldn't even open). If you use * or auto for both in and out you "should" be able to use a shortcode to set the outbound callerID like PRI... but I have had issues with some US providers making that work.

The truth is just an excuse for lack of imagination.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top