[cisco-voip] Unified Messaging

[Walenta, Philip]

One thing to check is that exchange did not default to TLS for its UM SIP connection to CUCM.  It has a bad habit of sneaking TLS into the settings.

I am fairly certain that CUCM 6 does not have the certificate capability to interop with Exchange TLS.

Sent from my iPhone

On Feb 12, 2015, at 4:15 PM, Terry Oakley <Terry.Oakley at rdc.ab.ca<mailto:Terry.Oakley at rdc.ab.ca>> wrote:

Currently we are in the process of moving to Call Manager 10.x but unfortunately we are still on 6.1 for a little while yet.   Or should that be sadly we are still there.   The other push is to more our Exchange environment to 2013 from 2007.     Exchange 2007 currently handles our voicemail.

Has anyone out there done something like this and if so how did you configure your Call Manager and Exchange 2013?   From examples we have configured our SIP trunk to point to destination address of the new 2013 Exchange box on port 5060.   We have moved a user from 2007 over to 2013 and set there UM to point to the new voicemail dialplan.    We keep getting a fast busy after the call hits the No answer limit.   Messaging button produces the same effect but with a significant delay.

Second question is would you stay with Exchange as your UM or would you use Unity?   Of course money is always an issue for education but if there are valid reasons to go either way I would appreciate your expertise and guidance.

Thanks

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

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150212/e7ea3d58/attachment.html>