« Exchange 2010 - Updating when using DAG | Main | DNSSEC & Cisco ASA & Windows Server DNS Changes »

04/30/2010

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Keith Beahm

When we tested this against another device (e.g. 3rd party fax server) we witnessed that the failover between selected trunks did not occur automatically. It seemed at the time of testing that the fact that one of the trunks was down was not communicated back to CM so the failover did not occur. We did find that manually re-ordering the trunks in the Route Group could achieve the effect (i.e. first device listed was the only one used). Have you also seen this behavior, or does your RG behave correctly?

My environment is CM 7.1.3.32900-4 with Exchange 2010 SP1 RU3v3 and 2007 SP1 RU5 (migration in progress).

DW Hunter

Hey Keith--

I noticed that failover worked properly on my end. I wonder if this is environmental - particular to your situation?

I've tried this setup in a few different CUCM->(other) integrations, and have always had the RG order behave as expected.

--DW

Chris

Hi Daryl - Great articles by the way. Have a ? for you. We currently are running CCUM 6.1 and a Exchange UM server (standalone) not in a cluster with our other Exchange Servers. Everything seems to be working great. Every once in a while a user will hit the messages button on phone and the number will ring and go right into Exchange voice mail.Other times, a user may do the same sequence but it will just ring. The user may hang up and then try again, same results. One more time, they may get into voice mail. Any suggestions? Thanks for your thoughts!

DW Hunter

Hi Chris, probably the best thing to do is to turn on Diagnostic Logging on Exchange UM to make sure the call makes it to Exchange. Does this happen to some, one, or all users? When you created your route pattern for the voicemail pilot, you have it going to a single trunk right? Not a route list or route group?

--DW

Garry

Hi Daryl,

Thanks for the good posts.

We are also planning to move from unity to exchange 2010. As unity had 48 voicemail ports, do we create these in CUCM as well or only Hunt pilot in cucm and point it to sip trunk and then create hunt pilot and voice mail ports in exchange 2010.

The little confusion i am having is around how it works?? if someone dials voicemail pilot it goes to CUCM and which is routed directly to SIP Trunk instead of any hunting in CUCM and then hunts throough the voice mail ports in excahnge? Is that rite? Which step involves crreating these voice mail ports in excahnge? Forgive me if i missed anything from your posts.

Thanks,
GR

DW Hunter

Garry--

That's a great question. I'm a little rusty, so take this with a grain of salt. I have not created any "voicemail ports" in Exchange. All I have done (and I've done this several times) is great your CUCM trunk, pilot, route pattern and point it to Exchange.

The SIP Trunk can handle multiple "paths" or "ports" so to speak.

Your second paragraph is right... you dial the pilot, it goes to CUCM, which is routed directly to SIP Trunk (at which point CUCM hangs up and Exchange takes over) and then Exchange handles the call from that point.

--DW

James

Thank you for the article. I just implemented Exchange UM using two servers in different sites. This article was helpful in setting up redundancy between the servers and CUCM.

One thing that I ran into is that on failover it appears the second link is not available. What I discovered is, due to default SIP timers in CUCM, it will take a long time for the second SIP trunk to be used. To the user it looks like nothing is happening.

The fix is to change the timers as described in a Cisco doc at the link below. With your guide and the timer change, it all works perfectly.

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_configuration_example09186a008082d76a.shtml

The comments to this entry are closed.

Twitter Updates

    follow me on Twitter