Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.


BCM50 PRI Outgoing Calls

BCM50 PRI Outgoing Calls

Hello. I am currently playing around with a second-hand BCM50 (in a labish type environment). I am unable to make calls over T1-PRI. However, I am able to receive calls. The T1 link is active. The system software version is, and I am using Avaya Business Element Manager 62.0.5.

The BCM50 is connecting via a T1-PRI to an Total Access 908e which is connecting to FreeSwitch. (I have a similar setup using an MICS using 2 T1-PRI, and it is working fine over another Total Access 908e.) In the FreeSwitch log, it is stating that the user cannot be found. (I experienced this same problem when I was initially setting up the MICS, and that was solved by entering the OLI number.)

Unfortunately, this is not working with the BCM50. The attempted outgoing call from the BCM50 is making it to my soft-switch, and is being dropped because the user/OLI number is not being passed. The release reason text is user reject call. (When receiving a call the reason text is normal clearing.)

My configuration captures should be attached as a PDF. Any assistance would be appreciated. To me, everything looks correct, but I think I am obviously missing something that I am not quite understanding. However, if the configuration looks OK, I think I might have to perform a clean reconfiguration. I think I know how to do one, but would appreciate some pointers if it comes to that. I have performed a backup, and I have found where the license file is, but I am a little concerned about how to reapply the license file. (Do I need to modify the file or file name?)

Again, thank you for taking the time to look at this issue that I am having.

RE: BCM50 PRI Outgoing Calls

Hello Ryan

I've taken a look at the PDF file and so far, it seems to look OK. I have a few questions that might need to be checked out.

You mentioned that incoming calls are OK. This would indicate that the circuit programming is fine as most of the problems with these kind of configurations tend to be incoming related or nothing at all.

I think your BCM 50 is at release 3.0. Can you confirm this please.

Also have you tried using the BCM monitor tool when testing the lines as this can be a good indication on what is happening. For some time, I have been "playing" with SIP trunks and found that the public receive number length had to be increased to 11 digits when I couldn't make outgoing calls.

You also mentioned connecting to a soft switch. I'm guessing that you mean something such as a Asterisx Server?. The BCM 50 I have at 6.0 is able to connect using SIP or H323 VOIP trunks which means bypassing the need for any physical trunks.

Firebird Scrambler

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

Website =

RE: BCM50 PRI Outgoing Calls

You can refer to your BCM as Rls 3 instead of

Shouldn't the Absorb be set to 1? (Absorb the 9)
Open Monitor and see if it shows 9 as being dialed, it should not if Absorb is set to 1.

"is being dropped because the user/OLI number is not being passed"
However it seems your error logs are not the same as with the MICS?
user cannot be found- MICS
user reject call - BCM
Just trying to see if it's actual OLI issue on BCM, yours it set to 1300.

Are you only dialing 91300 to get to the other user? maybe your Public Network DN length (in Dialing Plan)should be set to 4 for the Dest code of 9 in this case I wonder.
Did you program a 9 in Public Network DN length? you did not provide screen shot.

Example for me is 94 is my dest code and Absorb is at 2
Public Network DN length DN prefix 9 is set to 12
My OLI is 10 digits


Add me to LinkedIN

Toronto, CAN

RE: BCM50 PRI Outgoing Calls

Hello FirebirdScrambler and curlycord: Thank you for your replies.


The PEC code is NT9T6502E5, and from what I can gather from this code it is a BCM 50 R3. BCM connects via T1 to a device that acts as a bridge between T1 and SIP. FreeSwitch is similar to Asterisk.


The weird thing about the absorb length is that the only option is 0 or All. I tried setting to 94, then I had the choice of 0, 1, All. In my case, I tried All and it seems to work fine.

Update: I’ve been working on trying to figure what is going on with my setup. This is what I have found out. For some reason, using the Public route did not work. However, when I changed the route 001 to DN Type: Private and Service Type: Tie, I was able to dial out normally. The only answer that I can come up with is that there are some configuration options I have not configured properly somewhere. When the route DN Type was set to Public, the section "6C CALLING PARTY" was missing.

For comparison, I will include what is output when requesting the isdn i2-formatted output from the 908e’s that are connected to the MICS and BCM50 at the end of this post. Note that Ph #’s are extensions in my setup (1222 is on the MICS and 1303 is on the BCM 50; 5000 is a Demo FreeSwitch IVR). (Essentially, anything destined for the PSTN is routed through the FreeSwitch box and to an ATA-FXO.)

Thank you Firebird and curlycord for your assistance. I will probably be posting a couple of other queries later on...


01:55:48.409 ISDN.L2_FMT PRI  2  ==============================================
01:55:48.409 ISDN.L2_FMT PRI  2  R Sapi:00 C/R:R Tei:00 INFO Ns:119 Nr:58  P:0
01:55:48.409 ISDN.L2_FMT PRI  2    Prot:08  CRL:2  CRV:0001
01:55:48.409 ISDN.L2_FMT PRI  2    M - 05 SETUP       
01:55:48.410 ISDN.L2_FMT PRI  2     IE - 04 BEARER CAPABILITY   Len=3 
01:55:48.410 ISDN.L2_FMT PRI  2          80 Xfer Cap.:SPEECH            
01:55:48.410 ISDN.L2_FMT PRI  2          90 Xfer Rate:64k   
01:55:48.410 ISDN.L2_FMT PRI  2          A2 Layer 1:G.711 U-Law    
01:55:48.410 ISDN.L2_FMT PRI  2     IE - 18 CHANNEL ID          Len=3 
01:55:48.411 ISDN.L2_FMT PRI  2          A1 Primary Rate
01:55:48.411 ISDN.L2_FMT PRI  2             Intfc ID:IMPLICIT
01:55:48.411 ISDN.L2_FMT PRI  2             Pref/Excl:PREFERRED
01:55:48.411 ISDN.L2_FMT PRI  2             D-Chan Indicated:NO
01:55:48.411 ISDN.L2_FMT PRI  2             Chan. Sel:FOLLOWS
01:55:48.411 ISDN.L2_FMT PRI  2          83 Numb/Map:NUMBER
01:55:48.411 ISDN.L2_FMT PRI  2          81 Channel:1
01:55:48.411 ISDN.L2_FMT PRI  2     IE - 6C CALLING PARTY #     Len=6 
01:55:48.411 ISDN.L2_FMT PRI  2          00 Numb. Type:UNKNOWN       
01:55:48.411 ISDN.L2_FMT PRI  2             Numb. Plan:UNKNOWN        
01:55:48.412 ISDN.L2_FMT PRI  2          80 Presentation:ALLOWED     
01:55:48.412 ISDN.L2_FMT PRI  2             Screening:USER PROVIDED 
01:55:48.412 ISDN.L2_FMT PRI  2             Ph.# 1222
01:55:48.412 ISDN.L2_FMT PRI  2     IE - 70 CALLED PARTY #      Len=5 
01:55:48.412 ISDN.L2_FMT PRI  2          80 Numb. Type:UNKNOWN       
01:55:48.412 ISDN.L2_FMT PRI  2             Numb. Plan:UNKNOWN        
01:55:48.412 ISDN.L2_FMT PRI  2             Ph.# 5000
01:55:48.413 ISDN.L2_FMT PRI  2  ==============================================
BCM 50:
02:20:12.355 ISDN.L2_FMT PRI  1  ==============================================
02:20:12.355 ISDN.L2_FMT PRI  1  R Sapi:00 C/R:R Tei:00 INFO Ns:31  Nr:16  P:0
02:20:12.355 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:0004
02:20:12.355 ISDN.L2_FMT PRI  1    M - 05 SETUP       
02:20:12.355 ISDN.L2_FMT PRI  1     IE - 04 BEARER CAPABILITY   Len=3 
02:20:12.355 ISDN.L2_FMT PRI  1          80 Xfer Cap.:SPEECH            
02:20:12.355 ISDN.L2_FMT PRI  1          90 Xfer Rate:64k   
02:20:12.355 ISDN.L2_FMT PRI  1          A2 Layer 1:G.711 U-Law    
02:20:12.355 ISDN.L2_FMT PRI  1     IE - 18 CHANNEL ID          Len=3 
02:20:12.355 ISDN.L2_FMT PRI  1          A1 Primary Rate
02:20:12.356 ISDN.L2_FMT PRI  1             Intfc ID:IMPLICIT
02:20:12.356 ISDN.L2_FMT PRI  1             Pref/Excl:PREFERRED
02:20:12.356 ISDN.L2_FMT PRI  1             D-Chan Indicated:NO
02:20:12.356 ISDN.L2_FMT PRI  1             Chan. Sel:FOLLOWS
02:20:12.356 ISDN.L2_FMT PRI  1          83 Numb/Map:NUMBER
02:20:12.356 ISDN.L2_FMT PRI  1          97 Channel:23
02:20:12.356 ISDN.L2_FMT PRI  1     IE - 20 NETWORK SPECIFIC    Len=2 
02:20:12.356 ISDN.L2_FMT PRI  1       00 E5
02:20:12.356 ISDN.L2_FMT PRI  1     IE - 6C CALLING PARTY #     Len=6 
02:20:12.357 ISDN.L2_FMT PRI  1          49 Numb. Type:SUBSCRIBER    
02:20:12.357 ISDN.L2_FMT PRI  1             Numb. Plan:PRIVATE        
02:20:12.357 ISDN.L2_FMT PRI  1          80 Presentation:ALLOWED     
02:20:12.357 ISDN.L2_FMT PRI  1             Screening:USER PROVIDED 
02:20:12.357 ISDN.L2_FMT PRI  1             Ph.# 1303
02:20:12.357 ISDN.L2_FMT PRI  1     IE - 70 CALLED PARTY #      Len=5 
02:20:12.357 ISDN.L2_FMT PRI  1          C9 Numb. Type:SUBSCRIBER    
02:20:12.357 ISDN.L2_FMT PRI  1             Numb. Plan:PRIVATE        
02:20:12.357 ISDN.L2_FMT PRI  1             Ph.# 5000
02:20:12.358 ISDN.L2_FMT PRI  1  ==============================================

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close