In working with a 3rd party VM system integration to SM once the first set of server ports are fully utilized the next call is supposed to traverse to the next set of server ports. That system is sending back a SIP 486 msg to SM and SM doesn't seem to act upon it and the call just keeps going fast busy. It's a SM6.3 and haven't really found any sold info on this topic. The CM is an Evolution Server in this setup with SIP trunks to SM.
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 486 Handling
- Thread starter wpetilli
- Start date
4XX is a failure code and 300 is a redirect. I don't think CM is going to be able to guess what to do with that.
Consider having a trunk group in CM for each far end voicemail server, and an entity link for each SIP server in that voicemail cluster. Consider using a far end subdomain for each of those sig/trunk groups in CM. Like, server1.vmcluster.com for your first trunk, server2.voicemailcluster.com, etc.
Were SM to receive "vmpilot"@"server1.vmcluster.com", it should pick the routing policy to the sip entity correlating to server1 with an adaptation to manipulate the source/destination domains to "voicemaildomain.com"
By building out those trunks in CM and SM, you ought to be able to put em in a route pattern with things like LAR and REHU to make CM try subsequent servers if the first ones don't answer.
Consider having a trunk group in CM for each far end voicemail server, and an entity link for each SIP server in that voicemail cluster. Consider using a far end subdomain for each of those sig/trunk groups in CM. Like, server1.vmcluster.com for your first trunk, server2.voicemailcluster.com, etc.
Were SM to receive "vmpilot"@"server1.vmcluster.com", it should pick the routing policy to the sip entity correlating to server1 with an adaptation to manipulate the source/destination domains to "voicemaildomain.com"
By building out those trunks in CM and SM, you ought to be able to put em in a route pattern with things like LAR and REHU to make CM try subsequent servers if the first ones don't answer.
- Status
