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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya CM6.2 and Microsoft Unified Messaging (Exchange 2013)

Status
Not open for further replies.

demanding

IS-IT--Management
Jan 7, 2008
631
US
We are currently using Modular Messaging for our voicemail system but will be migrating to Unified Messaging. Our CM6.2 has a feature access code of #89 to transfer calls to voicemail - X111234 is bridged on secretary's station X115555. If someone calls x111234 and the secretary answers, she will transfer the caller to her boss's voicemail by pressing #89-it goes right into his voicemail. So, when tested on Unified Messaging, it goes to the secretary's voicemail box instead of his...thoughts?
 
I haven't played with exch UM, but check a couple of wiresharks. Certainly something will be a little different in history/diversion info. Maybe you can work with exchange um to treat it differently. Or perhaps use a vdn/vector of 'messaging split 99 for extension 115555'.

Otherwise, what integration note are you following? There's stuff in sip trunk groups and sig groups that you can play with.
 
Actually, the voicemail box it is going into is not the one to leave messages - or should I say it's the option to access the box for checking messages. So integration is off. I have been comparing the MM setup against the setup to UM and there are differences - figured it can't hurt to make UM mirror MM (hunt groups, AAR, UDP, route patterns, Session Manager) and see if it changes. What I find odd/don't understand is how an extension behaves when I simply dial #89 from their extension - it goes to that person's greeting so I can leave a message but if I dial the number associated with #89/AAR, it goes to the prompts to access the box.
 
Right. #89 in your instance is the CM feature of "transfer to voicemail" How that feature manifests itself in a SIP message to your Exchange UM may not necessarily be something standards based that applies to 3rd party voicemail systems.


The config note above mentions nothing of using features like you're trying to use being supported. Not to be anal, but there may not be a reference configuration to do what you're trying to do. That said, (and I'm not a Lync guy) what's the equivalent feature in Lync? How does that feature usage affect SIP messaging into MS UM, and would you be able replicate that from CM in some fashion? Otherwise, maybe the "messaging split 99 for extension 115555" would get you closer. In any case, it seems you'll need to play under the hood of something to make the SIP talk nicely and do the advanced stuff you're looking for.
 
Thanks much. We are not using Lync yet. I'm not very familiar with setting up messaging splits...
I was able to set up a system speed dial and cut down the amount of buttons pressed to 10 (that's 5 more than now). :)
 
Well, a messaging split is pretty simple.

Example: VDN 1000 points to vector 1. Vector 1 reads "messaging split 99 for extension 12345"

If voicemail is hunt group 99, then that vector tries to send that call across hunt 99 to voicemail for extension 12345. Its a common way to route calls to a particular mailbox.
 
But that mailbox only? How would we do this for all users?
 
Yeah, my example works for your specific example above, but not everything.

There's also "messaging split 99 for extension active", but the active extension in that case would be the vdn in question that pointed to your number.

Here's a link I found: that shows how to do it in pure Lync.
It has a link to MS's implementation of the feature:
And even then, with Lync you "transfer" and then select a contact, and in the contact's properties, click "that guy's voicemail box" So its still ugly unless you're in the Lync client and mousing around.

That said, a speed dial to the voicemail pilot number could allow you to press "transfer", then the voicemail hunt speed dial, then key in the extension. It could potentially bring you down to 2 keys, and then 5 digits, and then xfer again to complete or maybe hang up depending on what's in system-parameters features.

All to say that you're looking an old feature in a new product, and I could go on for hours on a broad topic like that :)
 
Actually, rethinking that whole setup with a receptionist that might have a sidecar with speed dials of people, you might even be able to "transfer" "voicemail speed dial" "user speed dial extension" if they have a key to call that user bringing it down to 3 keys total if its someone they already have a speed dial for. Give it a shot.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top