[cisco-voip] Mask caller ID of some message senders in Unity Connection Single inbox

[Evgeny Izetov]

I'm glad it's working for you but I'm curious how it works. Modifying
calling number on the SIP trunk to CUC will work as you describe for a
forwarded call scenario but will break a direct call when a user pushes
Messages button on the phone. I did testing on 11.5 and it most definitely
was using info on the User Basics page for single inbox. Maybe you have
forward to email instead of Single Inbox? CUC does use the number and name
received over SIP trunk for single inbox but only if it didn't find the
number in the database, like it would be the case for PSTN calls.

On Sat, Mar 30, 2019 at 9:51 AM Ray Maslanka <ray.maslanka at gmail.com> wrote:

> After some more testing we ultimately found the combination of changing
> labels on the calling device itself and changing the calling party
> transformation patterns to include spoofed numbers rather than restricting
> them entirely is our solution.
>
> I assumed the name and numbers may have been dictated by CUC as Evgeny
> Isetov suggests, but that is not the case at least in this deployment
> running 12.5 and a SIP integration.
>
> Removing the Remote Party Id from the integration SIP trunk also does not
> set the caller to unknown as the design guides suggest.
>
> While setting  the calling party transformation patterns to restrict
> calling ID entirely works great in this environment for handling CLID
> during phone to phone calls, the restriction didn't apply to the CUC trunk.
> The full +E164 DN was being shown in the CUC Single inbox message.
> Changing the calling number rather than restricting it entirely does work
> on the SIP integration trunk though.
>
> As a nice bonus, after convinced the number in the inbox was dictated by
> CUCM rather than CUC, we also found relabeling the DN allowed us control
> the name display in Single Inbox as well.
>
> Hope this helps someone.  Thanks Mark and Evengy for the suggestions
> regardless.
>
>
>
> On Tue, Mar 26, 2019 at 4:03 PM Evgeny Izetov <eizetov at gmail.com> wrote:
>
>> The following kind of sort of works in my quick testing but it's a bit
>> convoluted.
>>
>> The logic that CUC uses is when a call comes in it tries to match the
>> calling number to an extension in its database. If extension is found, then
>> CUC uses the Display Name and the Extension fields on 'User Basics' page to
>> construct the email for Single Inbox. So you could move the executive's
>> real extension from the User Basics page to Alternate Extension in CUC and
>> configure a fake extension and a generic Display Name on the User Basics
>> page.
>>
>> When the executive leaves a voicemail, CUC determines the target
>> voicemail box using the first diversion header as usual (we are not messing
>> with this part). Then CUC matches the executive's calling number to the
>> alternate extension and uses the information on the 'User Basics' of the
>> executive to construct the "From" information in the email.
>>
>> The obvious caveat is the fake extension still has to be unique in CUC,
>> you can't assign a generic main number to multiple voicemail boxes.
>>
>> -E
>>
>>
>> On Tue, Mar 26, 2019 at 2:51 PM Mark H. Turpin <mturpin at covene.com>
>> wrote:
>>
>>> 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 <cisco-voip-bounces at puck.nether.net> *On Behalf Of *Ray
>>> Maslanka
>>> *Sent:* Tuesday, March 26, 2019 10:38 AM
>>> *To:* cisco-voip at puck.nether.net
>>> *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
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190330/b7ddabc5/attachment.html>