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:email@example.com, you can get their voice mail box by calling sip:firstname.lastname@example.org;opaque=app:voicemail. However, this will lead to a missed call notification.
If you instead call sip:email@example.com;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: March 20th, 2014 | Author: Michael | Filed under: UCMA 4.0 | Tags: impersonation, SIP URI, troubleshooting | 1 Comment »
For a development platform that abstracts away a whole lot of underlying activity, UCMA really does a pretty good job of letting you know the cause when a problem occurs. But there are a few cases where errors in UCMA applications can be utterly bewildering, and probably the most frustrating of these are the ones that result from typos in SIP URIs. Missing a character or misspelling a part of a SIP URI can lead to errors that seem to have no relationship to what is actually going wrong. I wanted to cover a couple of those errors here in the hope of preventing others from tearing their hair out for multiple days trying to troubleshoot these sneaky problems. Continue reading “SIP URI typos and the misleading errors they cause” »