Difference between VoIP trunk keycode & SIP GW keycode

[ccarmock]

I need to enable SIP trunking on a BCM 50. I thought the keycode I needed to buy was the SIP GW keycode. However one supplier has said I should get the VoIP trunk keycode which will allow both H323 trunks AND SIP trunks and that the SIP GW keycode only allows SIP.

Can anyone confirm? I want to try this to see if I can get some OCS2007/Exchange integration.

Regards
Clive

 

[cook1082]

They are two different keys one for SIP and one for h.323 not one for both.
BCM50 VOIP GW 1 TRUNK AUTH PRODUCT : VoIP Gateway 1 Trunk Authorization CodeTYPE : VoIP Gateway SW Authorization CodeCOMPATIBILITY : Nortel BCM 50 BCM50 VoIP Gateway - Trunk Authorization Code BCM50 VoIP Gateway (H.323): up to 12 VoIP trunks Supports the complete range of IP telephony capability offered byexisting BCM products VoIP Gateway is a VoIP trunk-side networking solution that enables voice applications to be handled over the data infrastructure The VoIP Gateway allows existing small multi-site Nortel system users to cost effectively enter into the VoIP environment while providingan opportunity for large multi-site companies with Nortel systemsto slowly migrate their voice network to IP The VoIP Gateway is ideal to IP-enable users businesscommunications system

 

[telcodog]

I think the confusion is with the keycode for H.323 trunks. If you have those, under VOIP Protocol in the H.323 setup, you can select H.323 or SIP. They work, but only BCM to BCM if you choose SIP.

With SIP Gateway keycodes, you have to use the SIP parameters to set things up to work. The H.323 stuff is irrelevant with these codes.

 

[ccarmock]

It seems the VoIP trunk keycode gives you both H323 AND SIP but the SIP keycode gives you just SIP.

Now only if Nortel would enable SIP over TCP it would be more useful!

 

[nooop]

What I have found with these codes are as follows. To network multiple BCM products, use VOIP trunks and you are good.

To connect BCM to a SIP system ie, sipxecs, or asterisk. Nortel has the SCS platform, so you could trunk BCM to SCS via SIP trunks.

If you are trying to buy SIP trunks from a ITSP provider using BCM SIP trunks, I don't think that will work. I hope I am wrong, but I can't get it to work. If you use a FX0 gateway, that works fine.

 

[ccarmock]

I think the issues around SIP are that Nortel have implemented SIP over UDP on the BCM platform, but many other devices/services expect SIP over TCP.

This seems to be an issue with Exchange 2007 UM integration.

There are some applications to convert out there but these run on LINUX it seems.

So far I haven't found anythign suitable that will run on Windows.

Ideally Nortel would introduce SIP over TCP as an option as is now in the Asterix soft PABX.

Regards
Clive