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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BCM50 External Call forwarding on PRI 1

Status
Not open for further replies.

EKirsch

IS-IT--Management
Sep 23, 2017
21
US
I'm a total newbie when it comes to the BCM50 but the issue I'm having is we just moved to fiber service on our voice and data side.
We have a PRI with our carrier and when I attempt to forward calls to an outbound number, it rings fast busy.

From what I can see, the BCM is trying to pass inbound caller ID and the internal outbound number to the adtran and the adtran is rejecting the callout. I'm attempting to figure out how to only pass our internal main number on the call forward and not pass the callers cid info. the main line has an OLI of our primary outbound number. So bing a newbie to this system, how would I block the callers CID?
 
I've been playing with the public OLI settings on my digital phone that I forward to my cell phone when I leave the office. Whatever number I put into the OLI field is what shows on my cell phone on forwarded calls. I really think this is a configuration problem with the Adtran unit. I found the following document on an Adtran forum:
One of the options mentioned is for ANI substitution on trunk. I think this must be what's going on. I can't get my BCM50 to send anything but what's in the OLI field. If I blank out the OLI for my extension the forwarded call shows as unknown caller on my cell phone. As David wrote, this problem didn't start until you changed providers. I'm guessing this is a SIP circuit being converted to PRI onsite, so this is a problem with SIP headers.

I forgot to mention that if I set my SIP trunks for Last Redirect, then I will see the caller ID of the original caller instead of what's programmed into the OLI field of my phone. There's no option like this for PRI. So if I can control the caller ID my cell phone receives on forwarded calls I think the provider can also control this parameter in the Adtran.

Brian Cox
Georgia Telephone
 
After fighting with Wow for a few days, I got them to stamp all outbound calls with our primary DID to fix the issues. It's a temporary fix until I replace this aging phone system.
 
If it was "Wide Open West" that provided the new service, then they should have been more helpful. The BCM system isn't in my opinion the cause of your problems.

It's just doing it's job as before. You might be able to get it upgraded to 6.0 that has a whole bunch of improvements such as SIP trunks, call recording etc.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
The PRI circuit is a SIP to PRI. The way they build the adtran is their "Standard" setup so they wouldn't make changes with out a few days of complaining. I've had SIP on PRI with other phone systems and never ran into this much trouble. We are at the point that we will be replacing the system in probably the next 12 months and going with IP phones and an asterisk setup. My goal is to have all 3 of our offices phones routed to our main building then routed over the network to the proper office. Once that happens, I'll have to have Wow remove the custom config and go back to standard. I understand there is a multitude of option on these older BCM's, but with everything else I manage day to day, I don't have the time learn all the ins and outs of something that is essential "dead" technology since Nortel went out of business. I know Avaya bought them, and I'm very familiar with Avaya phone systems, but the nortel just feels old and can not do all the bells and whistles our owner wants.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top