[cisco-voip] UCCX Call Redirect and Called Address Reset
Bill Talley
btalley at gmail.com
Tue Sep 11 18:49:46 EDT 2018
I’ve been doing this that way for years and haven’t come across this flaw. Is it happening because it’s matching a “route pattern” or because it’s matching a called party transformation pattern? I will have to test this out to see if I’ve just been lucky. What version of CUCM are you running?
Sent from an iOS device with very tiny touchscreen input keys. Please excude my typtos.
> On Sep 11, 2018, at 4:57 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.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/070223ea/attachment.html>
More information about the cisco-voip
mailing list