[cisco-voip] Translation pattern in CUCM6.1
Ryan Ratliff
rratliff at cisco.com
Wed Jan 7 10:17:18 EST 2009
Agreed, this is a bit strange.
Normally you can use the CCM service parameters to prefix digits to
inbound calls (Advanced parameters, search for prefix). Those
parameters are very dumb though and can't insert digits mid-string.
-Ryan
On Jan 7, 2009, at 10:11 AM, Justin Steinberg wrote:
are you doing this so that people can use their missed/received/
placed call lists ? if so, perhaps you could deal with this on
the outbound call.
create a route pattern
9.!
predot discard
prefix 90
Also, I'm just curious, your telco is prefixing a 9 to each inbound
call? this seems weird, especially if you are in a region where you
need to return the call prefixed with 0.
Justin
On Wed, Jan 7, 2009 at 8:54 AM, Jacky Cai <jackycxh at gmail.com> wrote:
It is incoming call from PSTN thru a MGCP gateway. only one CSS can be
assigned to the MGCP gateway. If I create more then one translation
pattern in this CSS. These translation patterns is nothing regard the
called ID, but only manipulate the caller ID. then how Call manager can
decide to use which translation pattern? How can we let call manager to
select the correct translation pattern for the call?
example: two calls, the caller ID are 91234567 and 912345678 both call
to an extension 555. I create two Translation pattern(the calling party
number mask is XXXXXXX and XXXXXXXX and put them to the CSS of mgcp
gateway. How can we let call manager use the translation pattern
(XXXXXXX) for 91234567 and (XXXXXXXX) for 912345678?
Thanks a lot.
在 2009-01-07三的 14:35 +0200，Ahmed Elnagar写道：
>
> If the calling number is a specific 2 or 3 pattern "say 4 digits
and 5
> digits" you could replicate your dial-plan to have one set per
calling
> number pattern and each number pattern has its CSS and PT to hit the
> required route pattern which has the correct transaltion for this
> calling number...however this could be a little bit complicated but
> you could have it as a last resort solution.
>
>
> Thanks,
> Ahmed Elnagar
>
>
>
>
>
>
>
>
______________________________________________________________________
> Date: Wed, 7 Jan 2009 13:04:34 +0800
> From: jackycxh at gmail.com
> To: ahmed_elnagar at hotmail.com
> Subject: Re: [cisco-voip] Translation pattern in CUCM6.1
> CC: cisco-voip at puck.nether.net
>
> Thanks. but the problem is that the calling number is not fixed
> length and can not use a mask to drop the first digit.
>
> 2009/1/7 Ahmed Elnagar <ahmed_elnagar at hotmail.com>
>
> Provided that the first digit is fixed you could make it on
> the calling party transforamtion on the route pattern or the
> route list "if using" by making a mask to remove first digit
> only...if the calling number is 90108899 use a mask of xxxxxx
> this will result in 0108899 then prefix two digits one is the
> first digit and the second is the one you want to add...so if
> the digit you want to insert is 0...prefix 90 so the number
> will be 900108899
>
>
> Thanks,
> Ahmed Elnagar
>
>
______________________________________________________________
> Date: Wed, 7 Jan 2009 12:07:19 +0800
> From: jackycxh at gmail.com
> To: TimothyEstes at spherion.com; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Translation pattern in CUCM6.1
>
>
>
> Yes. that's the case. but unforturnally I am using
> MGCP... :-(. Any idea on the CUCM side?
>
> Thanks a lot.
>
>
>
> 2009/1/7 Jacky Cai <jackycxh at gmail.com>
> Yes. that's the case. but unforturnally I am using
> MGCP... :-(. Any idea on the CUCM side?
>
> Thanks a lot.
>
>
> 2009/1/7 Estes, Timothy <TimothyEstes at spherion.com>
>
>
> If you have H.323 gateways the following
> config will work. Basically if the number is
> in the local area code we translate the
> calling number to 9XXXXXXXXXX. If the number
> is not in the local area code its becomes
> 91XXXXXXXXXX. This makes the caller ID
display
> on the phone show the correct dialable
pattern
> for call-back purposes.
>
> The following basic config on a 323 GW should
> work for the Ft. Lauderdale area where 954
and
> 754 are the local overlay area codes.
>
>
> voice translation-profile TP1
> translate calling 1
>
> voice translation-rule 1
> rule 1 /^\(954[2-9]......\)/ /9\1/
> rule 2 /^\(754[2-9]......\)/ /9\1/
> rule 3 /^\([2-9]..[2-9]....../)\ \91\1/
>
> dial-peer voice 101 pots
> description PSTN - PRI
> translation-profile incoming TP1
> direct-inward-dial
> port 0/0/1:23
>
>
>
> Timothy Estes
> Affiliated Computer Services (ACS) @ Spherion
> Ft. Lauderdale FL
> timothyestes at spherion.com
>
>
>
>
>
>
______________________________________________
> From: cisco-voip-bounces at puck.nether.net
> [cisco-voip-bounces at puck.nether.net] On
Behalf
> Of Jacky Cai [jackycxh at gmail.com]
> Sent: Tuesday, January 06, 2009 9:57 PM
> To: cisco-voip at puck-nether.net List
> Subject: [cisco-voip] Translation pattern in
> CUCM6.1
>
>
>
>
> Hi,
>
> In CUCM 6.1, do you have any idea on how to
> add a digit to calling party number just
after
> the first digits?
>
> For example: translate the calling party
> number from 9! to 90!.
>
> Thanks.
>
>
>
>
>
>
______________________________________________________________
> Get news, entertainment and everything you care about at
> Live.com. Check it out!
>
>
>
>
______________________________________________________________________
> Add maps and directions to your party Show them the way!
_______________________________________________
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/20090107/cb16f296/attachment.html>
More information about the cisco-voip
mailing list