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

SIP trunk from SM to AudioCodes. 1

Status
Not open for further replies.
Nov 22, 2013
600
US
Looking to see if anyone has had any experience with configuring a SIP trunk from an Avaya session manager 6.3 to a audiocodes mediant 800 box.

The audiocodes vendor tells me they see their side as up, but on the avaya side I am still down.

I configured the SIP Entity as a "Other" with all basic settings that typically work for sip trunks to no avail.
In the trace logs I see I get a server internal error with the error "Reason SIP ;cause=500text="Classification Failure"
Not sure what this error is or if it is even the issue.

I cannot post the actual trace but basically it is this

ASM --> Options --> Audiocodes
ASM <-- Options <-- Audiocodes
ASM --> Server internal error --> AudioCodes
ASM <-- Server internal error <-- Audiocodes.

Server internal error on both is "Reason SIP ;cause=500text="Classification Failure"

I am using port 5060/tcp as well to keep it simple, any suggestions would be helpful and thank you in advance.




 
Likely a lack of config of how the audiocodes should reply to that OPTIONS ping. Check in SM's entity link monitoring. Normally, any response to an OPTIONS ping is interpreted as "hey! I'm here and alive!" even if that's a 404, 500, whatever. SIP proxies use that to know that if there is no response to mark the trunk down.

That way, if a call were to need to route out that link, it wouldn't send it, wait 4 seconds for a timeout, and then go to the next choice. It would do it right away if regular options pings got no answer.

Sounds like whatever you're doing, you're still a little short on config to get calls working.
 
Thanks Kyle, going to get more info on this next week from the AudioCodes vendor.



 
Solved.

The Session manager side was configured correctly, however after some research and testing we found that on the AudioCodes side, "Classify by Proxy Set" was left unchecked. As soon as this was checked I got "200 OK"

Kyle, if I ever bump into you in real life, I am buying you a coffee or a beer..




 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top