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

Voip trunk networking two BCM50s

Status
Not open for further replies.

kpzan

Technical User
May 14, 2016
173
US
I've got a BCM50 installation coming up where I'll be using voip trunks to network a new BCM50 to an existing BCM50. I've networked a few MICS systems and BCMs together using T-1 trunks but this is my first experience with voip networking.

After studying the BCM Networking Configuration Guide and Tek-Tips search forum at length, I've made a list of the steps I plan to take to implement my voip network.

Can the experts here at Tek-Tips point out any problems or holes in my set up?


Two BCM50 6.0 systems

Site A start DN 200.
Site B start DN 300.

4 voip trunk keycodes in each system. No MCDN keycode.


Site A
--------

Routing table:

Name: Site B
Destination digits: 3
IP: 192.168.11.50 (Site B ip address)
GW type: BCM
MCDN protocol: none
Voip protocol: H323

H323 settings: Default

H323 media parameters: Default


Dial plan:

Route: 001
Use Pool: Bloc A (voip)
DN type: Public

Destination Code: 3A
Normal route: 001
Absorb length: 0


Target lines:

Target line 125 in Site B system programed with public received digits 3300.
Target line 125 prime set extension 300.
Assign target line 125 as ring only at extension 300.



Site B
--------

Routing table:

Name: Site A
Destination digits: 2
IP: 192.168.10.50 (Site A ip address)
GW type: BCM
MCDN protocol: none
Voip protocol: H323

H323 settings: Default

H323 media parameters: Default


Dial plan:

Route: 001
Use Pool: Bloc A (voip)
DN type: Public

Destination Code: 2A
Normal route: 001
Absorb length: 0


Target lines:

Target line 125 in Site A system programed with public received digits 2200.
Target line 125 prime set - extension 200.
Assign target line 125 as ring only at extension 200.


Users at Site A dial 3300 to reach extension 300, Users at Site B dial 2200
to reach extension 200.


 
VoIP trunks on BCM do work well and its better as you have done to have the systems at the same release.
Either H323 or SIP will be OK.

Firebird Scrambler
Nortel and Avaya Meridian 1 / Succession and BCM / Norstar Programmer

Very advance high level knowledge on the Linux BCM phone system.

Website
 
Thanks FirebirdScrambler.

If I set my absorb length to 1 can the users dial 200 for extension 200 and 300 for extension 300?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top