Sending calls to a voice mail box in UCMA without a missed call notification
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:user@example.com, you can get their voice mail box by calling sip:user@example.com;opaque=app:voicemail. However, this will lead to a missed call notification.
If you instead call sip:user@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.
Hi,
How does ucma applications handle presence for users homed to an SBS? Since the ucma app is registered against the main pool and relys on presence to to determine if the user is available to bring into a conference call.
They handle presence for those users just as they would for any other users. Unless there is a connectivity failure between sites, the UCMA application will receive presence updates from the users via the pool it is registered against.
Hi,
i use an application to parse all SIP messages (MSPL + dispatcherHandler in c#) but if the receiver of the message has the voice mail enabled, the message is blocked with the error 486.
Have you ever experienced this problem?
I forward the message using these commands:
eventArgs.Request.SimpleProxy = true;
eventArgs.ServerTransaction.EnableForking = false;
ClientTransaction ct = eventArgs.ServerTransaction.CreateBranch();
ct.SendRequest(request);
Thank you
Mauro ,
try
eventArgs.ServerTransaction.CreateBranch();
eventArgs.ServerTransaction.SendRequest(request);