[cisco-voip] UCCX Call Redirect and Called Address Reset

[Anthony Holloway]

Well, I guess that all depends on your configuration, but what I'm getting
at, transcends than that even.

Imagine any CSS configuration scenario, by way in which there is no match
to the pattern 1000 anywhere.  This is how the Call Redirect from UCCX to
CUC, while resetting the Called Address should work, and it does work like
that.  You do not need a pattern in CUCM to match against, in order for
1000 to be a valid target on the CUC system.  The only thing CUCM needs to
concern itself with, is where I am redirecting the call to, which is the VM
Pilot number.  For all intents and purposes, the 1000 is meta data for CUC
to know where to route the call internally to.

However, now imagine a scenario wherein your CTI Port CSS, as you've
mentioned, can match a Route Pattern of 1XXX, which prefixes an 8, and then
has a RL/RG/Gateway to a 3rd party PBX.  Would you expect CUCM to perform
digit manipulation on 1000, which is not even the number you're redirecting
to, ignore the routing aspects of the Route Pattern (E.g., the
RL/RG/Gateway), and then perform another DA on the VM pilot, only to screw
up the delivery of the call?  This is what's happening, and I cannot
believe this is the first time I've ever seen this.

On Tue, Sep 11, 2018 at 5:16 PM Charles Goldsmith <wokka at justfamily.org>
wrote:

> Anthony, wouldn't your CSS on cti ports (via the call control group)
> determine what transformation is applied to the call?
>
>
> On Tue, Sep 11, 2018 at 4:58 PM Anthony Holloway <
> avholloway+cisco-voip at gmail.com> wrote:
>
>> I didn't know this, and so I thought I'd share, but who knows, maybe it
>> was common knowledge.
>>
>> If you use the Call Redirect step in UCCX to send a call directly to a
>> mailbox/call handler in CUC, and thus, your Destination is the VM Pilot,
>> while your target object in CUC is your Called Adddress, like so:
>>
>> [image: image.png]
>>
>> Then either one of two things will happen (only one of them I'm ok with):
>>
>> 1) If there is a pattern in CUCM for which 1000 will match; say a Route
>> Pattern such as 1XXX which prefixes an 8 and route calls to a 3rd Party
>> PBX, then CUCM will use the Called Number Transformations on this Route
>> Pattern to prefix the 8 on your 1000, and then send the call to CUC with
>> 81000 as the Redir number, and you'll be all messed up.  Actually, you'll
>> just get the opening greeting, but still...grrrr
>>
>> 2) If there is no pattern in CUCM for which 1000 will match, then CUCM
>> sends the call to CUC, and the redir is 1000 and everything works fine.
>>
>> I'll let you guess which one I'm ok with, and which one I'm not.
>>
>> Why in the hell is CUCM performing number transformations on this call
>> flow like that?  It makes no sense.  What am I missing here?
>> _______________________________________________
>> 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/20180911/06cc2b70/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 14899 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180911/06cc2b70/attachment.png>