BCM 50's on VPN

[bjamrok]

Hello all!,

I'm new here on the forums and looking for some guidance. I'm far from a nortel expert, but as the IT manager, I'm expected to configure our sytems so I'm coming here for some guidance. So here is my current (and working setup):

3 seperate BCM 50's running software ver. 6.0.2.05.237.
They currently have 4 digit dialing between sites working well. Sites are 11xx, 22xx, 33xx for numbering plan. The sites are currently on a MPLS WAN which works very well. In the IP trunks section, I see the routes between sites and all Voip protocols are set to SIP. I am considering changing this to H323 and can't get it to work. The reason for considering the change is we lose an MPLS link more than we would like and have installed a VPN tunnel on seperate ISP as a backup network. When we've tested moving to the backup network, all our services work well with the exception of the Nortel voice traffic. Call connection is inconsistent and many times we get the fast busy tone when no other calls are in progress. Can any of you verify that moving to H323 might make be a better idea on a VPN? If so, I would appreciate any help you all can give me with getting the H323 working.

Thanks,

Brian

 

[Firebird Scrambler]

H323 is the older protocal that uses "nodes". Check that you have the licences. I've added a few useful links for you below.

http://www.ghtrout.com/files/BCM50_Troubleshooting_Guide.zip

http://www.ghtrout.com/files/BCM_to_Gatekeeper.zip

or try..

http://www.ghtrout.com/bcm/index.html

and look through for any files to download.



All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[atcom]

I doubt H323 would fair any better in the failover scenario. It should, however, by fairly easy to setup since H323 is usually the native VoIP protocol for Nortel.

-----------------------------------
Telephone & computer wiring/Cat 5E/Cat 6/Fibre Optic cabling in Calgary, AB

 

[bjamrok]

Hello again and thanks for the replies. I have found out that we do not have active keycodes for the H323 protocol, only SIP. I am still looking for suggestions in running in our backup configuration. Is there a codec that is more forgiving? I know that in our failover I'm at the mercy of the public internet speed, and there is no guarantee of speed for real-time apps, but my BCMs are configured for G.729, G.723, G.711 ulaw and last G.711 alaw. Enable voice activity detection is not checked, Jitter buffer is auto, G.729 payload is 30, G.723 Payload is 30, G.711 payload is 30ms Fax transport is T.38, Provide inband ringback is not checked.

I was wondering if changing any of these settings would give us better results when using the internet VPNs?

Thanks,

Brian