What R U Doing For DIDs to Diff DN

[TheMitelGuy]

Hello people,

I have a question. Let's say you have customer with "Norstar Extensions" (221-275). They are moving to the 3300 and want DID's. They have enough trunks to convert to T1 at the same time. Based on the concept of getting 4 digits from the CO, and them not matching the DN range of the users, what are you people doing in the field to route the customers DIDs to their old DN numbers?

Example:
Ext 225, aquires a DID of 312 555-1234. I don't have extension 1234, but DN: 225 wants to keep 225 and have that DID.

I'm thinking the easist way is to make a speed dial for 1234 and route it to 225. I can't see why that won't work, not can I think of a different way to do that.

 

[MitelInMyBlood]

In the 3300 or SX2K you are correct. Use system speed call entries to translate the incoming DID digits to the actual extensions. If there was a perfectly linear translation you could translate the outbound calls using CPN substitution.

On the 200ICP with rls 3 it's a little different because there you have form 55 the digit translation table. I haven't studied this, but I believe form 55 is for exactly this situation.

 

[TheMitelGuy]

Yes, I have successfully used form 55. It works like a beach. You take your DID and route it to *ANY* answer point, including ABR. DIAL. I love it. Our customers love it. It saves so many physical and phantom resources. They need to do that on the 3300. Do you think that would be a feature other people would use on the 3300 too?

 

[TheMitelGuy]

beach should = peach.

 

[MitelInMyBlood]

Hard to speculate how something like form 55 would help the 3300 user since the SYS SP table accomplishes pretty much the same thing. Of course in those cases where the client is short on resources due to an unusually large number of SYS SP entries a separate incoming digit translation table at the trunk level for his DID's might be welcomed. ANYTHING would be better than having to resort to Flex Dims. Been there.