[cisco-voip] CUCM 10.5 and Exchange 2013 voicemail setup. RESOLVED
Terry Oakley
Terry.Oakley at rdc.ab.ca
Fri Oct 16 11:04:37 EDT 2015
Well did some call traces and I get this on the try to the hunt pilot
Line 1 11:14:05.430|CC|OFFERED|66715124|66715125|3521|1803|1803|SEPA45630BA4343|Exchange2013CASTrunk
Line 2 11:14:05.517|SIPT|66715125|TCP|OUT|xxx.16.xxx.12|5060|Exchange2013CASTrunk|xxx.28.x.xxx|5060|3
100
13
2806.1^*^*|11508701|f79c7200-61e18d5d-35cac-cc910ac at 172.16.xxx.12|INVITE
Line 3 11:14:05.518|SIPT|66715125|TCP|IN|xxx.16.xxx.12|5060|Exchange2013CASTrunk|xxx.28.x.222|5060|3
100
14
1874917.2^xxx.28.x.222^*|11508702|f79c7200-61e18d5d-35cac-cc910ac at xxx.16.xxx.12|100
Trying
Line 4 11:14:05.545|SIPT|66715125|TCP|IN|xxx.16.xxx.12|5060|Exchange2013CASTrunk|xxx.28.x.222|5060|3
100
14
1874917.3^xxx.28.x.222^*|11508703|f79c7200-61e18d5d-35cac-cc910ac at xxx.16.xxx.12|403
Forbidden
IP addressed masked to protect the less than innocent.
Then on looking at the Exchange side and the event viewer there was a telltale event there, that I should have asked the admin earlier. “The Unified Messages server cannot find a valid UM hunt group associate with the UM IP gateway. Pilot 1803”
So after attempts to modify the UM dial plan to add the hunt group we removed it and started again. This time making the URI type Telephone extension instead of SIP URI. We were able to add the hunt group and voila an answered call from CUCM 10.5 to Exchange 2013.
BTW there is a problem with Play on Phone in Office 2013 that requires a KB to be added for the Play on Phone to work. The KB is 2880477. https://support.microsoft.com/en-us/kb/2880477
Thanks for all of the support and a special thanks to Ryan and Aaron
Terry
From: Ryan Huff [mailto:ryanhuff at outlook.com]
Sent: October 13, 2015 5: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/20151016/3401ecba/attachment.html>
More information about the cisco-voip
mailing list