I have exactly oposite experience:
I'm using in two sites one with callmanager (v4), one with gnugk
gatekeeper and ci$co h323 gateways
with ooh323 - caller id name is not go through, when calling from
asterisk to callmanager, sending dtmf from callmanger to asterisk isn't
funtional
with oh323 - caller id isn't working, dtmf OK, but problems with oh323
registering to two gatekeepers, also seems, that oh323 isn't good
maintained, look at bugtracker and last release date :-(
original h.323 is working prety good for me on site with callmanager and
on site with dual gatekeepers (except pickup via this channel, as I
wrote at beginning, but maybe this be implemented soon ;-)
PJ
Dan Austin wrote:
Better is subjective in this case. There's no doubt that chan_ooh323
has some warts. On the other hand it has NO external library
requirements,
and works out of the box with Cisco's Call Manager.
One could argue that Call Manager is crap. Fine, that doesn't change
the fact some of us are stuck with it.
Chan_h323 did not work with CCM, and a query/bug report was dismissed,
basically stating that Cisco was F'd up and the channel would not be
updated to work with it unless funded. (fair, but not helpful)
Chan_oh323 worked with CCM, but suffered from the external library
requirements.
Chan_ooh323 just worked. The code is, to a infrequent programmer,
easy to read, extend and fix bugs.
So for me chan_ooh323 is a 'better' H.323 channel driver.
Dan
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
