DID to existing station#

[RazorbackHog]

I would like to ask for advice. My boss who has an existing extension of say 2007 would like to have a DID number which would be 2341 but wishes to keep his old extension#. What's the easiest but best way to route 2341 to 2007. This may become a recurring theme for all my manager folks. That's why I want the easiest to setup and maintain method.

Thanks.

 

[98Converter]

Just put a bridged appearance of 2341 on 2007. Or change the coverage path of 2341 and have it point to 2007, or change the INCOMING CALL HANDLING TREATMENT on the Trunk Group form... There's a few other ways.

Keep in mind, theres quite a few different ways to skin a cat.

Thanks,
CJH

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[RazorbackHog]

Thanks. You are correct in saying there are several ways to skin this cat. I think I'm liking the incoming call handling treatment for the trunk group. One single place I could go to catch anyone who I might assign one of these DID numbers to and the internal station#'s could stay as they are.

 

[RazorbackHog]

I used the Incoming Call Handling Treatment on the trunk method and it seems to work just great. Am I limited to only 18 possible entries in this list? That could certainly be a limiting factor in using this method.

 

[DAVIDPAYNE]

You could also request that your carrier change the DNIS digits he is sending you for each of the DID’s, and match that up with your dial plan.

 

[phoneguy55]

I would change the extension. It will get very confusing quickly when the extension doesn't match the DID. Yea it is a pain for the user to get a new extension. But in the long run, it is easier to manage and easier for everyone to understand.

 

[SF0751]

I agree with phoneguy55; I'd change the extension as well. I'd also use 98Converter's suggestion, but in the other direction - make the (old) non-DID station an X-port station, with a coverage path that points to the (new) DID station. Or just call-forward the old station to the new station. And let the customer know that he/she has 60 days or so to tell everyone about the new phone number. After the waiting time has passed, remove the old non-DID number from your switch altogether.

Susan
"'I wish life was not so short,' he thought. 'Languages take such a time, and so do all the things one wants to know about.'"
- J. R. R. Tolkien, The Lost Road

 

[RazorbackHog]

Thanks for the suggestions. I agree, now just have to convince the boss he needs a new extension.

 

[d00kie]

The best way I found is here; thread690-903527

 

[RazorbackHog]

Thanks d00kie. That's very useful information.

 

[mikeydidit]

I have a couple of new buildings that I am moving some of our people to. To free up some of our main DID range, I am giving them all new numbers on a new DID range at the remote sites.

For the most part and letting them know in advance they would be getting new numbers when they move, it has gone better than I expected it to. You will always have the few that are difficult to work with so I have come up with several things for them that you too might be able to use.

1. I x ported their old extension numbers and had the first point of cover go to Audix. I had the users redo their recording stating that their number has changed to xxx-xxxx and also had them put that you can hang-up and dial xxx-xxxx or press "0" to be connected now. In Audix I set up their new number as the covering extension. It also announces the new number again when they hit "0". I will leave this in place for a month or 2 and then just remove their old number altogether.

2. Like is mentioned in earlier post, just x port the old number and either call forward their calls or create a coverage path to the new number on the first ring.


Mike Jones
Louisiana State University Health Sciences center