atcomsystems.ca/forum Forums TDM Business Telephone Systems Toshiba Telephones & Systems BRI direct access? call forward issue...

I have a BRI line on one of my phone systems. For various reasons, I have installed some analog lines on the same system. I want to forward the BRI number to the analog number - and I want the telco to do it. The telco tells me I need to use the call forward variable to accomplish this - by dialing *72<number to forward to>.

So, I pick up the phone, dial 9 (which grabs the BRI line), and dial *72. And I have problems - specifically I get there error recording 'your call cannont be completed as dialed, please try the call again'. The telco thinks the phone sysem is not recognizing the star and is just dialing 72<number>.

Is there any reason I would not be able to dial a '*' after dialing 9?

Is there anyway to directly grab a BRI channel (which would be similar to directly grabbing a PRI channel)?

You have to add *72 to the dialing plane to dial 3 digits. I think if you do that, you will be good to go.

Even though you are dialing "9" and getting dial tone, it is still system dial tone, not tone from the provider.

Hmm. I setup a new Route Plan, but I can only a number, N, or X. N is 2-9 and X is 0-9. I can't put in a * or #.

I tested, and the error I get is the same if I call *72<number> or 72<number>. So, I agree with the telco (Qwest) that the system is not seeing the *.

What do I need to do to get the system to regonnize the star? Some dial plan magic? COS (or some other permission) setup so the user can dial *? Is there a direct access number I can dial to directly access the BRI line?

How about bypassing LCR. If you create a number (say 6) that access the outoing line group directly, this actually grabs a line, rather than provides system D/T waiting for LCR information.

I have tried in the past to actually choose the BRI channel I want, with no success. If you only have one BRI service, this should do the trick.

I set #68 to be a "Line Group access Code" for OLG 1 (which is the BRI OLG). It's still not picking up the *. Either it's not picking up the star, or the Telco is lying when they say they have the feature enabled (they're SURE it's enabled, but perhaps it's broken).

I don't know what it is like in the US, but codes on BRI are a pain in the ass here.I know from one system I used to work on, you need to dial a system code prior to sending the digits to the ISDN. The codes need to go to the BRI on a deeper level than just a DTMF code. You may find the Tosh can't do it, or can't do it easy. I know half a dozen systems that just can't send system codes to ISDN, and twice that amount that I wouldn't even bother on. I would try contacting you higher level support for Tosh and see what they say.

For my sites, I just don't bother, I just ask the carrier to do it for me. They have a small charge for it, but it is always cheaper than my charge to the customer to f around.

Seems to me that I've used #7 for BRI direct access so as to directly dial ISDN CO feature codes, but it was kinda tricky to get the right trunk numbers and such...

I feel that OzTech is on the the right path.

At least while we continue to try to isolate and correct the dialing conflict, you should try accessing that BRI with an ISDN set (or a TPI/550B+ BRI test set, etc) from outside of your local system, then attempt to update and activate the BRI's forwarding variable directly with the provider via your normal *7x dialing.

Edit: If nothing else (and especially in a circumstance like this), it may be best to do like OzTech did and simply have the provider update and activate the BRI's call forwarding variable feature to forward the calls to the analog line for you. They should be able to accomplish that within a few minutes.