Ray, I haven’t tested this, but a back of the napkin design might be:
Use a route next hop by calling party translation for your VM pilot. If a call matches the extensions of executives, then it could goto a different route pattern, like *XXXX. Then you can mask at the route pattern or RL/RG level. From: cisco-voip <[email protected]> On Behalf Of Ray Maslanka Sent: Tuesday, March 26, 2019 10:38 AM To: [email protected] Subject: [cisco-voip] Mask caller ID of some message senders in Unity Connection Single inbox *** EXTERNAL EMAIL - DO NOT CLICK LINKS *** Gents, Running CUCM and a SIP integration to Unity Connection with Single Inbox to O365. Normally if a CUC user is forwarded to a voice mailbox of another CUC user, the Identified User Messaging feature provides the name and number of the caller in the Outlook message. The ask is now to have the numbers of a small subset of users masked in the Outlook message when they leave voice messages. The use case is when executives, support staff, call center agents, etc. want to make calls and leave voicemail but avoid providing direct call back information. Caller ID is masked currently from phone to phone using Calling Party Transformation Patterns in CUCM, but this doesn't mask caller information when the call reaches Unity Connection. The Remote Party Id on the integration SIP trunk can be removed to make all callers over that trunk unknown, but we only want a small subset of users to be masked. Alternatively, the Identified User Messaging feature can be turned off to prevent name and number in the message, but that is system wide. Does anyone have a decent solution to mask the caller ID of a relatively few users in Unity Connection Single Inbox messages?
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
