[cisco-voip] CUCM 10.5 and Exchange 2013 voicemail setup.

[Daniel Pagan]

Adding to list of possibilities, it could also be an unaccepted transport type... E.g. CUCM now sending SIP requests via TCP when UDP inbound is configured on Exchange.

Also if require MTP is configured but none are available, in which case I’d check MRM in SDL traces.

But my guess would be OPTIONS. If the SIP trunk is configured for OPTIONS PING and Exchange isn’t responding with anything outside a 408 Request Timeout or 503 Service Unavailable. Route List Control will not route the call and a fast busy will be experienced immediately if no backup points of egress are available. If I had to bet, it would be on this scenario considering the jump from 6.x to 10.x will most definitely introduce SIP trunk status (Full Service, No Service, Unknown) and call setup requests will not be routed to No Service trunk.

Hope this helps.

Dan

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Huff
Sent: Tuesday, October 13, 2015 7:29 PM
To: Terry Oakley <Terry.Oakley at rdc.ab.ca>; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM 10.5 and Exchange 2013 voicemail setup.

Terry,

Sounds like you have a lot going on there!

How did you move into the 10.5 environment?  Did you do a bridge migration or a 'stare and compare'?

A fast busy could be a few different things (css, partition ... etc) or dns based since you mentioned fqdn or resource based.

What codec are you trying using?

Have you pulled traces?

What is the disconnect cause code for one of the failed calls into the hunt pilot?

If you can reproduce a failed call and then send me the traces or the sip messages I can give you a much better answer.

Thanks,

Ryan


Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: Terry Oakley
Date:10/13/2015 6:24 PM (GMT-05:00)
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] CUCM 10.5 and Exchange 2013 voicemail setup.
We currently are moving from Exchange 2007 to Exchange 2013.   We have three CAS servers and 3 Mailbox servers, all virtualized.   In our test environment, before we moved from CUCM 6.1 to 10.5 we are able to at least get Exchange 2013 to answer a SIP trunk request from CUCM 6.1.   Now in CUCM 10.5 we just get a fast busy when we dial the VM pilot number.   Does anyone have experience with this and have a guide that we could follow?    We have followed a number of guides from Microsoft and they have not proven to be the magic answer.

We have a SIP trunk set to the CAS servers with all three individual servers listed in the Destination section (all FQDN) port 5060
We have three separate SIP trunks to the three mailbox servers with all three having the ports 5062 through 5068 listed and again FQDN for the destination address.
The VM pilot (route pattern) is associated with the CAS trunk.
Do we need a route list and hence a route group?

Thank you for your knowledge and wiliness to share.  And especially thanks to this forum for providing us the access.

Cheers

Terry

Terry Oakley
Telecommunications Coordinator | Information Technology Services
Red Deer College |100 College Blvd. | Box 5005 | Red Deer | Alberta | T4N 5H5
work (403) 342-3521   |  FAX (403) 343-4034

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151014/63e02f7c/attachment.html>