SIP Trunk - Works most of the time... 3

[dsm600rr]

Hello all,

Just looking for a bit of guidance on an Intermediate Issue I am having with our SIP Trunk. The Trunk works 95% of the time. The other 5% I get "Waiting for Line".

The Truck is going through a Edgewater 4550 to our 500V2

Suggestions on what may be causing this?

Thank you.

 

[mforrence]

Fire up Monitor, set to capture SIP call transactions, log to a file and let it run until you get a failure. Then look at log and it will tell the tale.


Mike Forrence

http://www.goteamvox.com

 

[MBridgman]

Sounds like you do not have enough channels for the number of calls you are trying to make.

If you can post the sys mon trace for when the waiting for line is displayed we should be able to see what is wrong.Default filter plus SIP, SIP call TX and RX

worth checking SSA for resource errors as well

 

[dsm600rr]

Thank you for the suggestions. SSA reports no errors - we have plenty of Channels.

Log is running now - of course the trunk is working perfectly. I will post when we get "Waiting for Line"

Thank you!

 

[snowman50]

I'm am not very hot on diagnosing sip issues but the first thing I saw was 401 error.unauthorised
Usually caused by Authentication name or password in SIP Credentials is incorrect.

Is the trunk showing as registered in SSA at the time off the error.
Could be the trunk is dropped and the system is waiting on registration to give you a line back.

Is the issue from 1 user or all users.

If you are using internal data then make sure all the users have a correct sip ID programmed in the user sip tab.

13:05:35 3721105876mS Sip: Find End Point2 ac1e14440001c347 17.115527.0 2088 SIPTrunk Endpoint (f17c7c5c) Sip CallId 7363229bc0d39fbadc4366f335f83cd2
13:05:35 3721105876mS SIP Call Rx: 17
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.1.10.20:5060;rport=5060;branch=z9hG4bKcec6fe1e252af5c68c4554db51fd7764;received=10.1.10.20
From: "Unknown" <sip:5862262080@10.1.10.150>;tag=5e524f4ef4d65f07
To: <sip:15864885440@10.1.10.150>
Call-ID: 7363229bc0d39fbadc4366f335f83cd2
CSeq: 1160803430 INVITE

http://WWW-Authenticate:

Digest realm="fe-4a2b-6w.coredial.com", nonce="1b049a8b", algorithm=MD5
Content-Length: 0

13:05:35 3721105876mS Sip: ac1e14440001c347 17.115527.0 2088 SIPTrunk Endpoint(f17c63b0) Ignoring Q.850 Reason dialog f17c63b0, method INVITE, CodeNum 401 in state SIPDialog::INV_PROV_RESP_RCVD(5)
13:05:35 3721105876mS Sip: ac1e14440001c347 17.115527.0 2088 SIPTrunk Endpoint(f17c63b0) Process SIP response dialog f17c63b0, method INVITE, CodeNum 401 in state SIPDialog::INV_PROV_RESP_RCVD(5)
13:05:35 3721105877mS Sip: ac1e14440001c347 17.115527.0 2088 SIPTrunk Endpoint(f17c63b0) SIP-EP: Decoding of 401 (challenge) RESPONSE
13:05:35 3721105877mS Sip: ac1e14440001c347 17.115527.0 2088 SIPTrunk Endpoint(f17c63b0) UpdateSIPCallState SIPDialog::INV_PROV_RESP_RCVD(5) -> SIPDialog::INV_FINAL_RESP_RCVD(17)
13:05:35 3721105878mS Sip: ac1e14440001c347 17.115527.0 2088 SIPTrunk Endpoint(f17c63b0) ACK SENT TO 10.1.10.150 5060

 

[fieldtechonIR]

I didn't read all the posts or the trace, but do you have pots lines on that system? Or a card that has pots on it? are the unused pots in the same group as the SIP? if so get them out. See it all the time.

 

[dsm600rr]

fieldtechonIR - I do not. I do have a PRI in the system. We are using the SIP Trunk only for outbound until all the issues are resolved.

I do have 2 combo cards in the system, however, all of the Analog Trunks are set to "Out of Service".

 

[dsm600rr]

snowman50:

"first thing I saw was 401 error. unauthorized Usually caused by Authentication name or password in SIP Credentials is incorrect." If the credentials were incorrect - wouldn't it not work at all?

"Is the trunk showing as registered in SSA at the time off the error" - It usually only happens maybe once/twice a day and comes back up rather quickly. I will try and catch this next time

"Is the issue from 1 user or all users." - This is not User Specific

"If you are using internal data then make sure all the users have a correct sip ID programmed in the user sip tab." - We are not using Internal Data

 

[dsm600rr]

Side note: To get it to finally error "waiting for line" I had to pound 15 calls out rapidly, so this trace may not be accurate. I did not however go over SIP Trunk Channels (Verified via SSA)

 

[janni78]

If you post a trace post it as an attachment, I don't even consider reading a post that is over a page long and not in Courier New.

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

 

[dsm600rr]

[URL unfurl="true"]https://res.cloudinary.com/engineering-com/raw/upload/v1489095329/tips/SipErrors_mwsodb.txt[/url]

 

[biv343]

Any chance the carrier is restricting the maximum number of outbound calls that can be sent with the same outbound caller ID?

Windstream used to be famous for only allowing 5 outbound calls on SIP trunks for one particular number. Caused all sorts of fun if phones sent out the main number. They could adjust it to allow more, but you had to request that change.

 

[mforrence]

Regarding SIP URI, We only use "*" for Local URI/Display/Contact fields for an incoming path. For outbound, we either use the primary telephone number or Internal Data, and assign them different group numbers to better route via ARS. In a standard install, we'll have three SIP URI entries, one with main number, one with Internal data, and one with * (for inbound routing via ICR).

Mike Forrence

http://www.goteamvox.com

 

[edlee321]

I had this same issue, and i resolved it by changing back the Sip Line Settings, under Transport tab, change "Use Network Topology Info" to None

 

[dsm600rr]

edlivian: Thank you for the suggestion - I currently have it set to: "Use Network Topology Info": None

mforrence: Are you able to elaborate on your post a bit more? Or point me in the correct direction. I am obviously new to SIP Trunking. Possibly screen shots of what you are saying?

Thank you!

 

[janni78]

Do you only have 5 channels on your SIP trunk?

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

 

[dsm600rr]

Janni78 - Correct. Small Company however. 6 of us in the office.

 

[edlee321]

it shouldn't make a difference can you try these changes:

for "Local URI" Use Credentials User Name
for "PAI" None

voip.ms has a good sip trunk setup guide for IP Office you can look at

[URL unfurl="true"]https://wiki.voip.ms/article/Avaya_IP_office[/url]

 

[dsm600rr]

Had some "Waiting for Line" Errors this morning. Attached is the log. Thoughts?

[URL unfurl="true"]https://res.cloudinary.com/engineering-com/raw/upload/v1489414368/tips/SIP_Errors_03-13-17_pozdfl.txt[/url]

 

[dsm600rr]

SIP Trunk at the providor is showing as Registered. Trunk on the IPO is saying "Not Registered"