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!

Trouble networking 5 BCMs

Status
Not open for further replies.

Crowtalks

Technical User
Mar 19, 2005
1,523
US
Here is my scenario:
Networking 5 BCMs using VoIP Trunking and CDP. BCM 400 has 8 trunk license, the BCM 50 satellites have two VoIP trunk license apiece. The satellites 50s can call the 400 and visa-versa, but the 50s cannot call each other. I have all the IP Addresses to the remote units built into each one's remote gateway (4 total at each location).
The 400 has 4 different routes with 4 different destination codes pointing toward each satellite. Should I just build 1 common route at the 400 for all 8 trunks? They will want fallback and centralized VM also, but I want to get this working first. Any help or suggestions will be appreciated.
Jim
 
Maybe a stupid question, but are you able to ping the other BCM 50's from a BCM 50 site? Almost sounds to me like an IP networking problem with the remote networks not speaking to each other.
 
I had failed to change the default private DN length from 3 to 4 on the one BCM50 that I was testing to. After I changed that, all was well. Now I'm havibg trouble tandeming the 50s to allow them to use the 400's PRI to make and receive calls.
 
Check the remote access packages on both the BCM 400 - For example, IP trunks in pool F need to have access to PRI-A on the 400, the BCM 50 will need to have a public route defined that points to it's IP trunk pool (bloca for example). You'll want to send 9+numbers to the 400, so you may need to build a public DN prefix of 91 with a length of 12, otherwise the system will send the call when only 11 digits have been dialed.

To get calls from the 400 to the 50, build a destination code for the received digits on the PRI, and point that to the IP trunk pool on the 400. Don't forget to add those digits under the IP trunk remote gateway section to point the digits to the correct BCM 50.

Hopefully that gets you started.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top