Posted: March 31st, 2014 | Author: Michael | Filed under: UCMA 4.0 | Tags: Exchange UM, voice mail, voicemail | 4 Comments »
A while back, I wrote a post on how to call an Exchange UM voice mail box directly. The trouble with the approach described in that post is that it generates a missed call notification in the Exchange inbox of the recipient. A colleague of mine discovered a way to nix this missed call notification, and I thought I would share it.
You can get a SIP URI that goes directly to a user’s voice mail box by appending ;opaque=app:voicemail to the end of that user’s address of record. For instance, if the user has the SIP URI sip:firstname.lastname@example.org, you can get their voice mail box by calling sip:email@example.com;opaque=app:voicemail. However, this will lead to a missed call notification.
If you instead call sip:firstname.lastname@example.org;opaque=app:voicemail;local-resource-path=voicememo, you will get the user’s voice mail box but there will be no missed call notification.
Posted: December 28th, 2012 | Author: Michael | Filed under: Lync Development, UCMA 3.0, UCMA 4.0 | Tags: call forwarding, missed call, Ms-Sensitivity, Ms-Target-Class, Response Groups, team ring, voice mail, voicemail | 1 Comment »
There are some instances where a call that is sent to a Lync user really shouldn’t be going to voice mail, or to the user’s cell phone, or anywhere like that. There’s nothing that screams “good customer service” to an agitated customer like being dropped into John Smith’s cell phone voice mail (“Hi, this is John. Leave a message”) after calling the tech support line. Response Group calls seem to magically ward off UM voice mail and call forwarding, and this has led to some questions: if Response Groups can do it, why can’t we do it in UCMA applications? Actually, you can. Continue reading “Prevent Lync calls from going to voice mail” »