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

BCM400 & BCM50 Link Problems

Status
Not open for further replies.

pleskuk

IS-IT--Management
Mar 3, 2008
108
GB
Hi all!
I've attempted to to network BCM400 (rel. 4.0.2.03) and BCM50 (Ver. 1.00.2.04.j) together but ran into a bunch of problems.

First of all, is it possible to link these 2 together considering that I have Keycodes for 4 "SIP GW Trunk on the BCM400" and 2 "VoIP GW Trunk on BCM50". Regarding this i saw I can chose between SIP and H.323 settings on BCM400 and just H.323 on BCM50. Just as a reminder i can not get SIP trunk Keycodes for this version of BCM50 so I think i would just try with this i have. I also have one SIP trunk on one of my VoIP lines on BCM400 system up and running, connected to an asterisk server for international calls.

Whats bother me is that I tried everything but can not set up link between my systems. For simplicity, I got both systems on the same LAN.

ON BCM400 settings are:
PRIVATE NETWORK:
Private and received numbers set to 3
Private network type is UDP
Private Network ID 1
Location Code: 070
Private DN Length: 3
Virtual Private Network ID: 1
ROUTING:
VoIP lines are added to the same pool
The Route I need is using VoIP Pool
DN Type: Private
ROUTING TABLE:
Dest. digits: 7
Destination IP: IP of the BCM50
GW Type: BCM
VoIP Protocol: H323
GW Protocol: CSE

ON BCM50 settings are:
PRIVATE NETWORK:
Private and received numbers set to 3
Private network type is UDP
Private Network ID: 2
Location Code: 071
Private DN Length: 3
Virtual Private Network ID: 2
ROUTING:
VoIP lines are added to the same pool
The Route I need is using VoIP Pool
DN Type: Private
REMOTE GATEWAYS:
Dest. digits: 7
Destination IP: IP of the BCM400
GW Type: BCM36 (I've had BCM25, 30, 35, 36 to choose and was not sure which one to use for my version)
VoIP Protocol: H323
GW Protocol: CSE

I have target lines defined on both systems.

After this setup the result was:
From the BCM400, when i dial 7 and dial the DN on the other system like 222, it said " The number You have Dialed is Invalid". And if i try with some invalid extension it give me busy tone as it should.

From the BCM50, it doesn't matter what DN i dial, after i get exit with 7 and dial 3 digit DN i give me error: Network Unavailable 3.

Based on you experience, what could be the problem? Does it even possible to link those systems with the License Codes I have?

Thanks in advance for your advises


 
Just an Update, as I mentioned i have a SIP trunk setup on my BCM400 with the Dest. Code: 8 which lead to a VoIP provider.
On the other hand the supposed H323 link to the BCM50 is setup with Dest. Code: 7.
However I just noticed that it doesn't matter if I dial 7 or 8 as a Dest. Code, it always goes out through the SIP trunk. Only the VoIP lines are switching depending on the Pool.

This made me think that maybe I'm unable to use the VoIP lines as SIP and H323 at once, even though i have 4 available Trunks in BCM400.
 
You can't use SIP to talk to H323. You would need some H323 keys on the 400 to talk to the 1.0 50.
 
Hi cook and thanx for your reply. I'm aware I cannot use SIP to talk to H323, but I'm confused about the SIP and/or H323 setting from which I can choose in BCM400 system. This lead me to a conclusion that i can chose what protocol I want to use.
 
Ok looks like a routing problem...

First check your routes and destination codes

it should be like this

Dest code = 7
Route = your voip route
Absorbed = All

Your voip gate way settings should look like this

N BCM400 settings are:
PRIVATE NETWORK:
Private and received numbers set to 3
Private network type is NONE
Private DN Length: 3
Virtual Private Network ID: 1
ROUTING:
VoIP lines are added to the same pool
The Route I need is using VoIP Pool
DN Type: Private
ROUTING TABLE:
Dest. digits: First digit of DNs on BCM50 ie 2 or 3
Destination IP: IP of the BCM50
GW Type: BCM
VoIP Protocol: H323
GW Protocol: CSE

ON BCM50 settings are:
PRIVATE NETWORK:
Private and received numbers set to 3
Private network type is NONE
Private DN Length: 3
Virtual Private Network ID: 2
ROUTING:
VoIP lines are added to the same pool
The Route I need is using VoIP Pool
DN Type: Private
REMOTE GATEWAYS:
Dest. digits: First digit of DNs on BCM400 ie 2 or 3
Destination IP: IP of the BCM400
GW Type: BCM36 (I've had BCM25, 30, 35, 36 to choose and was not sure which one to use for my version)
VoIP Protocol: H323
GW Protocol: CSE

Also check the all the DNs on both site have target lines with private received numbers set correctly



 
Just a side note ...
The BCM will always attempt to setup a VoIP trunk call as SIP unless you configure it otherwise.

TLDuk has the proper setup for you posted.

Do you have a Private Networking keycode?

-SD-
 
Hi guys and thanks for your support. TLduk i tried with the your config but it didn't worked, I still got same error.
BCM400 works fine with the SIP trunk but H323 is out of question, it just wont communicate at all.

SUpportDude, I must admit I'm confused with the KeyCodes licensing systems. I receive contradictory information every time i post some problem. Thats why i made a screen shots of my BCM400 and BCM50 ACTIVE key codes. Can you please take a look if I got all the necessary codes to achieve my goal?


Thanks in advance,
Ivo
 
I've never seen the keycode on the 400, of course I've been away 10 months. Th keycodes for H323 had the same keycode as you have on the 50, VoIP Gateway Trunk. You need to know if H323 is available with a SIP keycode? I'm guessing, no.

Adversity is Opportunity
 
Didn't know there was a separate key code for sip trunks on the V4.0 400 been doing so many BCM 50s recently
 
It appears you have what you need to the best of my knowledge.
The keycodes are confusing! Some are self explanatory, but others are misleading. Nortel really needs to document each keycode and its operational function.

Did you configure a valid prime set on your VoIP trunks at each location?

Did you configure Private Recvd Numbers for the target lines at each location?

Have you used BCM monitor to watch your call setup?

-SD-
 
Ok Guys, I got the solution. It was the Key Codes.

On BCM400 System i got SIP GW Trunk keycodes, and beside I've got an H323 option I could only use it for SIP trunks.

On BCM50 (rel. 1.0) I've got VoIP GW Trunk keycodes and could use it for H323 only. Also SIP codes cannot be added to rel. 1.0, only H323. I've got BCM50 rel. 3.0 with SIP keycodes and worked well.

However I have one more question. I networked both PBXs and use routing destination codes. I have 3 digit num. plans on both locations and i Use 7 on both systems as a routing number to the other PBX. Ok i can dial extensions with these setting.
However i have ISDN BRI trunks on BCM400 and i want to be able to use those trunks from the BCM50 side. For ex. i dial 7 from the BCM50 and after that when i dial 9 followed by the number (which is my exit number on BCM400 for the ISDN) i got error.
Any idea how to setup this?

Thanks in advance,
Ivo

 
Now you're talking about toll-bypass routing.
Try creating a different route and setting the DN type to public. Make your Des code a 9x and point it at the new route while absorbing 0. Set your Default public DN prefix to match the number of digits you're dialing, or build a new prefix to match a part of your dial string and set the appropriate value. This should allow you to get all of your digits across to the 400 at which point it will take over, based upon the digits you've sent, and send the call out the BRI.
Note: This does require the use of remote access packages on the 400 to tandem from the VoIP trunk to the BRI trunk.

-SD-
 
pleskuk


did you get this working from supportdudes post? I'm trying to setup the similar thing voip to PSTN for calls out.


It's only dialtone-VZ
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top