I am having a problem with a target number entry in the BCM. We have a PRI with DID's. Our received length is 4 digits. One of our public numbers is 9935. When I try to enter this I am getting a Not valid public number. Our PRI-A access code is 9. How could I fix this without changing our access code? Thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Target number
- Thread starter t3chhelp
- Start date
lowradiation
Technical User
I have run across this before as well - either get the digits sent changed to 5, 6 , or 7 - meaning you'll have to reprogram all your target lines again, or change your access code to 8 (if possible) or you can do a large amount of destination code programming:
ex. dest. codes 90 to 98 - grabs PRI-A - absorb 1
dest. code 990 - grabs PRI-A - absorb 1
dest. code 991 - grabs PRI-A - absorb 1
dest. code 992 - grabs PRI-A - absorb 1
dest. code 9930 - grabs PRI-A - absorb 1
dest. code 9931 - grabs PRI-A - absorb 1
dest. code 9932 - grabs PRI-A - absorb 1
dest. code 9933 - grabs PRI-A - absorb 1
dest. code 9934 - grabs PRI-A - absorb 1
dest. code 99350 - grabs PRI-A - absorb 1 (all the way to 99359)
dest. code 9936 - grabs PRI-A - absorb 1 (all the way to 9939)
...and hope that you don't get any other DID's that start with 9
ex. dest. codes 90 to 98 - grabs PRI-A - absorb 1
dest. code 990 - grabs PRI-A - absorb 1
dest. code 991 - grabs PRI-A - absorb 1
dest. code 992 - grabs PRI-A - absorb 1
dest. code 9930 - grabs PRI-A - absorb 1
dest. code 9931 - grabs PRI-A - absorb 1
dest. code 9932 - grabs PRI-A - absorb 1
dest. code 9933 - grabs PRI-A - absorb 1
dest. code 9934 - grabs PRI-A - absorb 1
dest. code 99350 - grabs PRI-A - absorb 1 (all the way to 99359)
dest. code 9936 - grabs PRI-A - absorb 1 (all the way to 9939)
...and hope that you don't get any other DID's that start with 9
- Thread starter
- #3
This is a fairly common problem with incoming DID's. Here is what you might want to do.
When the telco assigns DID digits to a trunk, they build a "route index" which tells their switch what digits to send.
What they do for us is they have a different route index built for all DIDs starting with 9's. They switch the 9 to an 8 and send me an 8 instead of a nine.
In other words if the incoming DID number is 9956, they send me 8856 instead, so the user would dial 9956 but I would receive 8856 which does not interfere with my routing tables. Then, I map the 8856 digits to whatever target line I want to and all is well.
That is how it is done.
When the telco assigns DID digits to a trunk, they build a "route index" which tells their switch what digits to send.
What they do for us is they have a different route index built for all DIDs starting with 9's. They switch the 9 to an 8 and send me an 8 instead of a nine.
In other words if the incoming DID number is 9956, they send me 8856 instead, so the user would dial 9956 but I would receive 8856 which does not interfere with my routing tables. Then, I map the 8856 digits to whatever target line I want to and all is well.
That is how it is done.
- Thread starter
- #6
I accomplished the target number problem with the suggestion lowradiation provided. We have 10 digit local dialing so I just inserted destination codes to match my local area codes. Whenever requesting new DID's I make sure they don't start with 9's or 0's but we had one exec who wanted to keep his old private line. This is my first Nortel install. I usually install the Avaya products. Thank-you for your help.
- Status
Similar threads
- Locked
- Question
- Locked
- Question