[cisco-voip] External Phone Number Mask Question

[Adam Piasecki]

Yup, 8.6, thanks this is probably going be fine for now, Unfortunately it’s applied to the trunk and I have some route patterns that require different caller IDs.  For example some route patterns would include an area code while others don’t for the caller id. I didn’t really explain that part in my first message but this is definitely better then what I had. 

 

It would be awesome if they expanded transformation patterns to include matching a route pattern.

 

Thanks!,

Adam

 

From: avholloway at gmail.com [mailto:avholloway at gmail.com] On Behalf Of Anthony Holloway
Sent: Friday, May 30, 2014 9:09 AM
To: Adam Piasecki
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] External Phone Number Mask Question

 

You could use outbound calling party transformations on the trunks. You can be specific about which calling parties transform to what numbers as well as supplying a default for the trunk.

 

Think of these transformations as being more powerful, because they are conditionally transforming numbers as opposed to transforming all numbers blindly. 

 

E.g., The implicit transformation of a RP/RL/RG will transform any and all numbers. Using an explicit calling party transformation pattern allows you to say: "if the calling number is 2001 then transform it to 8888; otherwise transform it to 7777" by way of using patterns to match numbers for which you wish to apply your transformations. 

 

Hopefully you're on a CUCM version which supports Xforms. 

On Thursday, May 29, 2014, Adam Piasecki <apiasecki at midatlanticbb.com <mailto:apiasecki at midatlanticbb.com> > wrote:

I have two trunks, the caller ID on each trunk needs to be different. All phones will have the same caller ID depending on the trunk they choose. This is easily enough done in the route patterns. 

 

Now I have a case where one phone has a DID and needs it’s caller ID to be different then all the other. So I set the External Phone mask in the phone. but the route patterns are overwriting it. It will have the same caller ID for both trunks.

 

I thought checking the box “Use Calling Party's External Phone Number Mask” in the route pattern would use the phones external phone mask as a precedence first, and then if the phone didn’t have a external phone number mask it would default to what is set in the route pattern. If CUCM doesn’t have this feature, is there any reason why it couldn’t?

 

The only solution I have found is to create separate partitions, calling search spaces, and route patterns for just this one phone.

 

I can’t put the external phone number mask in all the phones because of the 1st requirement of different caller IDs for each trunk.


Thanks,

Adam

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140530/70c749f4/attachment.html>