PRI with two DID #s

[RickChaisse]

Legend 7.0

One DID group is xxx-50xx that is currently routed to the 3xx extensions.
The new DID group is xxx-51xx that I want to route to the 4xx extensions.

Under the DID programming I see Delete Digit, block 1 & 2 and the Expect Digit, block 1 & 2, and the Add Digit, Block 1 & 2.

Rather than play with this and possibly cause problems, can someone tell me what I really need to do ?

Thank You all

 

[nuklhead]

I just went through a similar situation. I had the telco transpose the digits for me. A caller would dial xxx-51xx but the C.O. would send 4xx in place of the actual DID. Easy for you...You are paying them the big bucks...Make them figure it out. Most are happy to take care of this for you. Or you can do digit substitution in your switch. Which sounds like what you are hinting around.

 

[RickChaisse]

Thanks for the info, but they don't do that here.

By the way, they are currently sending me 3 digits.

Is that going to be a problem ?

 

[SYQUEST]

Change your station dial plan to 4-digits. Then have the service provider send a 4-digit feed. That will eliminate the zero problem! Zero as the first DID digit sent is unacceptable in the Legend/Magix systems. This way you don't have to add or change any digit translations.

Hope this helps!

....JIM....

 

[RickChaisse]

These people will never let me change to 4 digits.. they whined about having to add a 5xx extension numbering.

Any other thoughts on how to deal with this ?

What about telco sending 4 digits ? Could I sort out a 50xx and a 51xx ?

 

[SYQUEST]

Yes, I understand that can be a problem.

Are the 50xx numbers permanent? If not, have the Telco give you a different block that would not be x0xx. This way you can have the 3-digit station dial plan as you have now and keep your DID translations simple with NO changes in digits sent.

Don't let the Telco bully you with number excuses. Number blocks are easy for them to add or remove from the DID trunk group in the CO switch. You want numbers that match the last three of your station dial plan. That keeps things simple and organized.

....JIM....

 

[RickChaisse]

This is a real estate office that is well established and their DID #'s are on there business cards, etc.

I guess what I'm asking is, with the previous info above, where do I make the entries to add this second group.

I know you said that zero as a first number can't be used, but it's been established and working for years.

 

[merlinman]

PRI has NO PROBLEM with Zero as the First number.

You can (and probably someone already has) build a table to strip the ZERO.

I would suggest you print out the PRI Info and figure out how they massaged the 50xx to 3xx, and then you can do the same for the 51xx to 4xx.

It shouldn't be much of a trick, really.

 

[Telecomboy]

You should be able to create a new table 3 (it sounds like 1 and 2 are already taken). Expect digit should be set to 3, Delete 1 digit, (strips 1 off the number), and digit 4 (making the new number 4xx). The only issue you might run into is if the 50xx and 51xx overlap on the xx digits.

BUT FIRST, I would do a print of the PRI to see/compare how they are routing the current 50xx numbers as Merlinman suggests.

 

[RickChaisse]

hmmm..

It's making more sense now, but tell me.. are we identifying the 3rd digit as a zero and changing it to a 4 ( which is already occurring ), as well as identifying the 3rd digit as a 1 and changing IT to a 5 ?

or is that impossible ? ( I was told it could be done )

 

[SYQUEST]

What are your 50xx, 51xx, 52xx; xx digits? Do you have a hundred numbers each? Example : xxx-5000 thru 5099, 5100 thru 5199, etc. This is where the overlap would occur.

If you are swapping digits how do you handle the hundred number blocks?

I am trying to understand what the overlap problem is. I don't see why you should have one. The digits sent from Telco should still be unique regardless of the xx digits.

Please explain!

....JIM....

 

[RickChaisse]

the existing DID #'s are xxx-5000 thru -5099.
The company had one hundred+ extensions.. 400 thru 499.
They have added 20 more employees so I created extensions 500 thru 519. Telco has added the -5100 thru -5119 to the DIDs to accomidate the new extensions. I need to set up the translation(?) so the new extensions can be called via DID.

 

[SYQUEST]

This is only my opinion, but I always try to keep things like this simple. So I would check with Telco and find out if the xxx-5500 thru 55xx are numbers are available and swap the blocks.

Also I like to plan ahead. If cost is not prohibitive I would take the whole 100 number block, xxx-5500-5599. This will make future additions simple!

Broken blocks are NO fun! I talk from much experience. I used to work for a paging company and took care of all the CO codes and DID numbers and Telco orders.

So I know what I taking about....

I reread the previous posts and I am wondering, can you number your new stations 100 thru 119?

Then you would not have to translate anything. Telco would be sending the switch a three digit feed, 100 thru 199, as they are now. Correct?

....JIM....

 

[RickChaisse]

That will be great, if it'll work. I'll be going out there tommorrow, so I'll check it then.

I wish someone would explain to me what's really happening with the tables as I asked before..

"are we identifying the 3rd digit as a zero and changing it to a 4 ( which is already occurring ), as well as identifying the 3rd digit as a 1 and changing IT to a 5 ?

or is that impossible ? ( I was told it could be done )"

It would really help me with my decision process.

 

[SYQUEST]

The first thing you need is a printout of all the PRI data and the Numbering Plan of the Legend, as suggested by Merlinman. It would be nice if you would post it on Tek-Tips. Then we can all see it. That way we can all view the translations and know more about what is taking place.

At that point someone can further explain what may be changed to get the result you need.

If you have not checked the manuals, look in the System Programming, System Planning, and Network Reference documents. These can be downloaded from the AVAYA website.

I am still trying to locate which section deals with digit translations for DIDs. I found stuff about deleting, length, and adding, but nothing specific about how they can be substituted in regards to your requirements.

....JIM....

 

[RickChaisse]

Thank you, Jim
Here's the print out..
A PRI INFORMATION


A Pattern 4: 4
A Pattern 5: 5
A Pattern 6: 6
A Pattern 7: 7
A Pattern 8: 8
A Pattern 9: 9
A Call Type: BOTH BOTH BOTH BOTH BOTH
A NtwkServ: No Service
A DeleteDigits: 0 0 0 0 0

A Entry Number: 5 6 7 8 9
A Call Type: BOTH BOTH BOTH BOTH BOTH
A NtwkServ:
A DeleteDigits: 0 0 0 0 0

A Dial Plan Routing Table

A Entry Number: 0 1 2 3
A NtwkServ: Any service
A Expected Digits: 3 0 0 0
A Pattern to Match:
A Digits to Delete: 1 0 0 0
A Digits to Add: 3

A Entry Number: 4 5 6 7
A NtwkServ:
A Expected Digits: 0 0 0 0
A Pattern to Match:
A Digits to Delete: 0 0 0 0
A Digits to Add:

A Entry Number: 8 9 10 11
A NtwkServ:
A Expected Digits: 0 0 0 0
A Pattern to Match:
A Digits to Delete: 0 0 0 0
A Digits to Add:

A Entry Number: 12 13 14 15
A NtwkServ:
A Expected Digits: 0 0 0 0
A Pattern to Match:
A Digits to Delete: 0 0 0 0
A Digits to Add:

I hope that helps..
Thank you for the info on what documents to review.. I've checked some of them before, but without having someone to explain some of it, it's difficult.. I'll review them again.
Rick

 

[RickChaisse]

Thanks to all who tried to help on this.

By looking at the print out for PRI and then taking the terms and searching the PDF's, I was able to figure it out.
So, I figure some of you might want to know what I did to make it work..

This programming is performed under System/ Lines & Trunks/ PRI/ Dial Plan Routing

the original config:

Entry Number: 0 1
NtwkServ: Any service
Expected Digits: 3 0
Pattern to match:
Digits to Delete: 1 0
Digits to Add: 3 0

What finally worked:

Entry Number: 0 1
NtwkServ: Any service
Expected Digits: 3 3
Pattern to match: 1 0
Digits to Delete: 1 1
Digits to Add: 4 3

 

[merlinman]

You can fix it this way:

Change:

Entry 0

A Pattern to Match:
A Digits to Delete: 1
A Digits to Add: 3

TO THIS:

Entry 0

A Pattern to Match: 0
A Digits to Delete: 1
A Digits to Add: 3

AND ADD THIS:

Entry 1

A Pattern to Match: 1
A Digits to Delete: 1
A Digits to Add: 4

Based on what you've shown us, this should fix it.