Routing digit "9" from BCM to CS1000K

[mrraymond]

I am routing digits from BCM 3.0 to CS1000K via VOIP trunks.

I want my BCM users to dial 9 for making PSTN calls via the CS1000K as calls on this route are most cost effective.

Route 000 and destination code 9 are built as a system default configuration and cannot be changed or deleted, this according to the NTP.

Is there a work around that will allow my BCM users to simply dial 9 and the outside number just as though they were at the Main office (CS1000K)?

Should the BCM users need to place calls with their own building PSTN trunks they will do so with direct trunk line select on their phoneset.

As always thanks for the help.
Ray

 

[mrraymond]

Please disregard the "K" at the end of CS1000K It is a "CS1000E" that I am working with.

 

[Firebird Scrambler]

I think you may be able to insert a "9" against the route 000?.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[mrraymond]

Yes, you are correct 9 can be used against route 000 but it is defaulted against Pool A (analog trunks 61-64)

I want 9 to got out against BlocA (Voip 1-4)

Route 00O Pool type can not be changed, and when an attempt is made to delete the line am prompted with " Error Route 000 can not be modified or removed."

Hope this better clarifies my problem.

 

[morenot]

Delete Destination code "9"
add new route
add new destination code "9" and assigne to new route
insert 9 to route

 

[mrraymond]

Delete Destination code "9"
add new route
add new destination code "9" and assigne to new route
insert 9 to route

Yes, I have also tried this suggestion. The 9 destination code can be entered under a new route but it still will not pass to the VOIP trunks. Only if I use an access code then will 9 then pass and be received on the CS1000 side.

I can route every other needed digit over VOIP including 0, its only 9 that has a problem. The only thing I can associate this problem with is the BCM system analog trunk default setting.

Has anybody ever seen 9 passed on VOIP trunks without an access code?

 

[bluemr2]

It shouldn't be a problem. destination code 9A, use route of IP trunks, absorb 0. If you aren't using a gatekeeper, enter 9 as a destination digit in your ip trunk routing table.

 

[morenot]

check if you have "9" in line pool/access code
if yes, then delete it.
in Routing/route:add voip route
in Routing/destination code: add 9 with voip route and absorved lengh="0"
Check with Monitor what happend when you dial 9xxxxx
you must see 9xxxxx

Saludos...

JLMT//

 

[mrraymond]

Appreciate the thought and efforts you all have provided in finding a solution to this problem.

This is a new machine with no programming other than what I am doing now, thus there are hidden trunks pools built somewhere deep inside.

As i mentioned I am already passing digits to the CS1000 without problem and without access codes, in this case 2,3,4,5,7,8 and even 0 which can not be built as a destination code.

For those who are not familiar with BCM VOIP trunk configuration: after building your routes and destination codes it is also necessary to place those leading digits under the IP trunk routing table, otherwise the digits will never leave your system.

If and when I find a final solution I will surely post it for all to read.

 

[mrraymond]

Delete all default appearances of 9 from the routing table and line pools

build a new route and using VOIP trunks BlocA

under DN type select Special International.

Build the destination code with 9A absorb 0

If the NRS is programmed correctly full dialing will now take place using "9"