DID number that starts with 9 "not a valid Pub. Received $"

[QueBall780]

I have 7 digits coming from the phone company on our PRI. One of our DID numbers starts with 9 so it always gives an error when trying to program the system for 7 digits.

Error message is "Error Detail: 944XXXX is not a valid Pub. Received #"

So the previous programmer set the BCM Public Network Dialing plan to 6 digits so that he only had to enter in "44XXXX" as the Pub. Received # to get around the issue.

Now we have a new block of DID numbers which start with 395XXXX and the fun starts again.

Why isn't this system smart enough to allow both the Pub. Received number starting with 9 AND a routing code of 9 at the same time?

Are there any tricks I can use to allow 9 to appear as the first digit?

We have DIDs in the following ranges:
468-1XXX
485-82XX
944-2XXX
395-80XX

We use the digit 9 to access a line pool
local extensions start with 8.
We have remote IP Trunks with destination digits of:
3
5
7

So I guess that means I cannot use 3,5,7,9 as the first digit. So if I set the Public network length to 7 I get a conflict on the digit 9. If I set it to 6 I conflict with the digit 9 again with the new set of DID numbers. If I set it to 5 I conflict with the first digit 5. Length of 4 doesn't conflict but is very short and doesn't give me much hope of future expansion without further conflicts.

 

[notme11]

that has always been an issue with any system, the best way around for us has been to always ask the CO for a did range not to include 9, if they must than we change the loop or detination codes to another number.
in other systems we have done digit convertions to change the incoming number from a 9 to some other number. what I dont understand is why you need to have all 7 or even 6 digits. I have a pool of 2000 DIDS and only use 4 digits between 9 sites, what I have done with the destination codes is split and use for example 70-75 to one site, 76-79 to another and so on, having a BCM I doubt you will need more that 100 or 200 DIDs per site, so why dedicate a whole digit to a site and you can go lower if you need it to 710-719,720-739,742-770 and so on depending on the size of the branch you have, you can always estimate future growth up to a point.

 

[bcmfiftyfan]

Hello When we're faced with number conflicts like you mention often times we'll have the phone company do what they call a "drop and insert" or "index". For example, if we're receiving 7 digits and the DID is 944-1234 instead of sending us a 9 the phone company will "drop and insert" another digit(like 2 or 4). So instead of programming our system with rec'd digits 944-1234 we program 244-1234 or 444-1234. Of course the public stills dials 944-1234. Hope this helps.

 

[DigitelD]

If the carrier is sending you, for example, 955-5555 you can program 555555 in the received digits field. I have done this with no issues. Or, you can also follow the advice above and have the carrier send another digit other than the 9.

SHK Certified (School of Hard Knocks)
NCSS

 

[telcodog]

I think yu can accommodate for that by using wildcards in the routing table. If I remember correctly, you put in 9A as your destination code, then you can uncheck all the secondary digits you want to use. Haven't done it in a while but I'm sure it will allow you to enter 9 as your first digit in the received digits field of the target line.

Give it a try and let us know if it works for you.

 

[cook1082]

You can do that with absorb 1 but in the wild card it will show the digits that are not avaliable. So when you dial 9 and that number you will get an invalid number tone.You could get lucky,try it.