I am ordering pri for magix, any bad did's

[rmktech]

Hello, I am about to order a pri with 50/100 did #'s.

New install.

Should I stay away from any numbering plan?

Thanks

Ron K.

 

[franke]

This depends on the number of digits they will be sending you and the number of digits in your Merlin. Basicly, with a "Setup Space" configuration you'll want to stay away from ranges starting with "0" (the Operator) "7" (the default number for extensions, adjuncts, calling groups & paging groups, though the range 7500-7699 is available) "8" (the default number for LDN,trunks, pools, call park) and "9" (the ARS dial out code). With the exception of "0", you could renumber any of the other banks to match your needs. Or be creative, for instance, say you DID range is 8100 thru 8199, you could renumber the default trunks (801-880) to 8900-8979 thus freeing up the ranges 8100-8899.

franke

 

[merlinman]

Well, franke would be right if it were not PRI.

The number ranges he quoted can be problematic in a regular "DID" scenario, but with PRI, you can "MASSAGE" things around to fit, MOSTLY!

With PRI you have the option to get one number(OR RANGE) from the Vendor and TRANSLATE IT to another NUMBER (OR RANGE).

It would be best to get your D-I-D's ending in 00 to 99 for a given 100 range.

Just don't let them force a bunch of NON-SEQUENTIAL D-I-D numbers on you.

For example, I just implemented a system whose extensions are 100 - 159.

Their D-I-D's are XXX-YYY-1800 to 1859.

With PRI translations in the MAGIX, I was able to make 1800 go to 100, 1801 go to 101, 1820 go to 120 and on and on...

That way, the mail system did not have to be changed, the end users could then publish their D-I-D and get their calls on their extension as normal.

The big draw back is with Legend/Magix there are only 16 tables you can use for this "MASSAGE" process.

But usually, that's plenty.

 

[franke]

PRI or not, the default number ranges are still the default number ranges and if you want to avoid having to do some renumbering, it's easier to request numbers that don't conflict with those ranges.

franke

 

[merlinman]

Oh contrair mon ami!

I can have a 9 or a ZERO as a leading number and soak it up in the PRI config.

If you would like, I can post a copy of one (or THREE) I have done recently.

 

[merlinman]

Actually, a sample looks like this:

Dial Plan Routing Table

Entry Number: 0 1 2 3
NtwkServ: Any service Any service Any service Any service
Expected Digits: 4 4 4 4
Pattern to Match: 0 9620 9822 0830
Digits to Delete: 1 4 4 4
Digits to Add: 301 302 303



What we are doing here is getting a "USUALLY" Bad number, one that starts with 0 in pattern 0, and getting rid of that guy with the Digits to DELETE, and just making it go away.

Our 4 digits the vendor is sending are 0210 (i.e.) but our extension is 210.

With entry 2, we are just getting rid of the entire 4 digits, 9620, and sending them to extension 301 (a fax extension), same with the rest in this example.

I trust this will clear it up for everyone.

 

[franke]

I'm not saying you can't renumber to your hearts content, but the original post was for a new PRI and ..."Should I stay away from any numbering plan?". The plain and simple answer is yes, try and stay away from numbers that are already in use.

franke

 

[rmktech]

Thank you all. I appreciate all of your responses. The range of #'s sbc gave me were too spread out to make anything out of. So I have requested a new block.


ron k

 

[merlinman]

Like I said earlier, don's let 'ed try to force a bunch of NON-SEQUENTIAL D-I-D's on you!

Sounds like that was what they were attempting.

That can work if you have UNLIMITED CONVERSION TABLES, but the LEGEND/MAGIX only has 16, so you must be very very careful...