[cisco-voip] strange message notification behavior - UCONN 9.1

[Jason Aarons (AM)]

Does this match? Test it out after hours.


Be great if this Service Parameter could be set for CTI Applications only, or on a per number basis.

Service Parameters > Cisco CallManager > Advanced

Always Display Original Dialed Number: Required Field This parameter determines whether phones always display the number that the caller originally dialed (which may not match the final connected number). If Cisco CallManager routes the call from the originally dialed number to the connected number using a call forwarding directive, a translation pattern, route pattern, a redirection by a CTI application, or other means, this parameter determines whether the connected number or the originally dialed number is exposed. Note that when the Conference List feature is invoked, the connected number always displays regardless of the setting in this parameter. Valid values specify True (display the originally dialed number) or False (display the connected number).

This is a required field.
Default: False

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Erick Wellnitz
Sent: Tuesday, March 11, 2014 11:27 AM
To: cisco-voip
Subject: [cisco-voip] strange message notification behavior - UCONN 9.1


I've done some looking but can't seem to find the cause for this one.

Call comes in on line A to user A.  User B picks up the call on shared lineA.  User B transfers caller direct to voicemail.

Email notification shows the mesage being from user A.

This is the only user this happens to.  Nothing is configured different that I can tell.

Any ideas?




itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140311/0f37cc28/attachment.html>