Connecting BCM50 and Avaya IPO 500 Licensing Question

[bbaits25]

I have a quick question about connecting (creating h.323 trunk connections) a BCM50 and Avaya IPO 500 so we can make internal calls etc.

The BCM50 is a release 6.0 which I just upgraded, for licensing do I need a VOIP Gateway license for the trunk connection to the Avaya IPO 500


For The Avaya IPO 500 release 8.1 (69), Do I need a Avaya IPO 500 Voice Networking Channels for the h.323 trunk to the BCM50?

Thanks.

 

[amriddle01]

Aren't these best linked via SIP? SIP licences are cheaper and you'll get the same integration (calls, name and number)

 

[montyzummer]

for the ipo yes ....for the bcm i do believe google and the knowledge base has a very comprehensive interoperability section

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[bbaits25]

Yes I did see the interoperability article from Avaya, but it is possible to do h.323 trunk with the licenses above?

Avaya IPO - Voice Networking Channels

BCm50 - VOIP Gateway


Why is it best linked with SIP compared to h.323?

 

[bbaits25]

I have 9608 phones which are h.323 extensions and the BCM50 are nortel T7316e as well.

 

[montyzummer]

OK im no designer of communication potocols but i do know that a supported method that is easy to trouble shoot due to easy to read messaging outputs and a new technology that is a pleasure to work with and maintain is going to be my choice over something that was designed (i think in the late 80`S), im sure others have much more articulate answers but im in a kind of call it as i see it mood .. no offense intended you understand

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[bbaits25]

I gotcha. I guess when I Implemented a few other Avaya IPO's at a couple branch locations I setup h.323 trunks and haven't had a problem. I was just making sure that it was possible to do the same for BCM50 and Avaya IPO trunk connect.

 

[montyzummer]

apologies , mr riddle has me corrected , you will need sip trunk licenses for my suggestion ( too many wines on my part) however my comments stand and as amriddle points out cheaper and the advantages going forward will benefit you beyond you just price ... invest in the future not the past

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[bbaits25]

Ok thanks for the suggestion guys. I need a few glasses of wine myself.

 

[bbaits25]

So all in all

- use SIP because its a progressing protocol compared to h.323
- cheaper in price based on licensing for BCM50 and Avaya IPO


I was looking at this article,

http://www.packetizer.com/ipmc/h323_vs_sip/

 

[amriddle01]

Amazing how that article "bigs up" the H323 protocol, the same protocol they are using while trying to peddle their "Advanced Multimedia System". I bet all those SIP providers out there are shitting themselves now

 

[bbaits25]

ha yea. I guess in my stance im going to stick with the h.323 for now since I already have the licensing for it. I assume its not going away for a while right? lol

 

[montyzummer]

H.323 was actually designed for video conferencing , so if you want to trouble shoot the messaging with wireshark good luck ..... look sip works when implemented correctly , its piss easy to trouble shoot and works like a dream .... if you want to work on a q931 type protocol (hey tried and tested carry on old chap) but ...... hey you know what i was about to start going on about major clients etc ect .. you make you own mind up ... this forum is full of experienced techs we dont get commission for selling trunks we are trying to provide , informed experienced ...blood sweat and tears advice .... i truly wish you luck in all your en devours.

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[chrisag]

Use sip for this.
But I also tested it with h323 and it works.