[cisco-voip] CUCM translation pattern postfix digits

[Dave Goodwin]

I tried creating a dummy CTIRP with a DN of *5XXX and set it to CFA to
8XXX3101. That appears to be configurable (I did it on a test 10.5 box),
and when I check DNA it seems to indicate the correct pattern for the CFA.
However, when I did a quick test dialing out to *5123, I didn't get it to
ring 81233101. Unfortunately I don't have any more time at the moment to
try digging through the trace to see if I can see why it didn't work, but I
at least thought I would share that this strange way of doing it at least
gives you the appearance it could work. :-\

On Mon, Jul 20, 2015 at 9:29 PM, Ryan Huff <ryanhuff at outlook.com> wrote:

> Well Lelio, that is what you get for trying to do digit manipulation on a
> napkin in between wings! Lol
>
> Thanks,
>
> Ryan
>
>
> -------- Original Message --------
> From: Lelio Fulgenzi <lelio at uoguelph.ca>
> Sent: Monday, July 20, 2015 09:22 PM
> To: Ryan Huff <ryanhuff at outlook.com>,nateccie at gmail.com
> Subject: Re: [cisco-voip] CUCM translation pattern postfix digits
> CC: cisco-voip at puck.nether.net
>
> In v9, translation pattern does not accept X as valid character for prefix
> field. :(
>
> Since the purposes are similar, I'm guessing route patterns wouldn't allow
> it either.
>
> This is a good one.
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst, Network Infrastructure
> Computing and Communications Services (CCS)
> University of Guelph
>
> 519‐824‐4120 Ext 56354
> lelio at uoguelph.ca
> www.uoguelph.ca/ccs
> Room 037, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
>
> ------------------------------
> *From: *"Ryan Huff" <ryanhuff at outlook.com>
> *To: *nateccie at gmail.com
> *Cc: *cisco-voip at puck.nether.net
> *Sent: *Monday, 20 July, 2015 9:13:07 PM
> *Subject: *Re: [cisco-voip] CUCM translation pattern postfix digits
>
> Xlate : *5XXX (CPTM: 8XXX)
>
> Route Pattern: 8XXX (CPTM: 3101 Prefix: 8XXX) <-> Route list/group to
> h.323 gateway that uses a ccm call processing node as the ip address of the
> gateway.
>
> It could be the IPA talking but that sounds like it should work?
>
> Thanks,
>
> Ryan
>
>
> -------- Original Message --------
> From: NateCCIE <nateccie at gmail.com>
> Sent: Monday, July 20, 2015 08:39 PM
> To: Ryan Huff <ryanhuff at outlook.com>
> Subject: Re: [cisco-voip] CUCM translation pattern postfix digits
> CC: cisco-voip at puck.nether.net
>
> Called party transformation mask seem to match the XXX to the last digits.
>
> So with a pattern of XXX the XXX can only be in the last 3 digits of the
> mask   , DNA shows ? And won't route the call if you have Xs to early in
> the pattern.
>
> Sent from my iPhone
> +1 801 718 2308
>
> On Jul 20, 2015, at 6:27 PM, Ryan Huff <ryanhuff at outlook.com> wrote:
>
> Nate,
>
> I am not by my Linux machine (refuse to use winblows) to vet this but
> could you do:
>
> *5XXX with a CPTM of XXX3101 with a prefix of 8?
>
> Thanks,
>
> Ryan
>
>
> -------- Original Message --------
> From: NateCCIE <nateccie at gmail.com>
> Sent: Monday, July 20, 2015 08:08 PM
> To: 'Cisco VOIP' <cisco-voip at puck.nether.net>
> Subject: [cisco-voip] CUCM translation pattern postfix digits
>
> I want to do some system wide speed dials in CUCM.
>
>
>
> *5XXX to call 8XXX3101.
>
>
>
> I tried Called Party Transform Mask on the translation pattern of
> 8XXX3101, but it doesn’t allow the post fixing of digits and still use the
> XXX, it needs to be the last digits.
>
>
>
> I know I could do this in IOS, but I really want a CUCM only solution,
> without creating an individual TP for each XXX.
>
>
>
> Thanks,
>
> -Nate
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> 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/20150720/a6ad4408/attachment.html>