Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

DID and extension conflict

We just purchased 50 new DID numbers, ***-***-4000 to 4049. We also have some internal extensions in the 4000 to 4049 range. When I tried to set up new Translation Patterns incoming calls were sent to the extension that has the same last 4 numbers as the last 4 of the DID, not the extension I put into the Called Party Transform Mask field. I have been told that by setting up new Partitions and Calling Search Spaces we can work around this, but even then there are some issues calling internally from one Partition to another.

I am new to this, so I am wondering if there is an easier solution, or if I would be better off just changing internal extensions that conflict with DID numbers.

We are using

  • IP Telephony
New Member

Re: DID and extension conflict

It is much easier to have your DID's and extensions match. If not here's what you can do.

Create a Gateway partition for the incoming DID #s.

Create CSS to hit the GW Xlate partition first. Note only the GW Xlate CSS should have access to this partition.

Use that CSS on your gateway that the DID#'s come in on.

Create your translation patterns and place in the GW Xlate Partition.

If this helps, please rate post. Thanks.

Hall of Fame Super Red

Re: DID and extension conflict

Hi Andy,

I agree with Jay (+5 points here Jay :)

If at all possible I would change the Internal Extensions to something new so that the new DID's can match (fully). You are just setting yorself up for a world of pain and confusion otherwise. Don't forget there may be Voicemail considerations here as well.

Hope this helps! Just my thoughts here :)


"May your heart always be joyful And may your song always be sung May you stay forever young " - Dylan
This widget could not be displayed.