[asterisk-users] Callmanager 3.3(5) and Asterisk with ooh323

[Dan Austin]

PJ Wrote:
> Did you apply correct "calling search space" on callmanager 
> gateway configuration page for incomming calls from asterisk
> to callmanager?  imho, oh323 is obsolete/unmaintained, I'm using
> original chan_h323 with callmanager 4.1 and it working fine 
> (including dtmf), ooh323 is probably perspektive and working also,
> but currently is not working dtmf between callmanager and asterisk
> (ooh323) see: http://bugs.digium.com/view.php?id=8191
> PJ
PJ is correct the the most likely cause of call failures from
Asterisk to CCM is an improper Calling Search Space on CCM.  It
could also be a case that the number format that Asterisk is
sending to CCM is not correct, if CCM expects four digit extensions
Asterisk should not send six digit extensions.

> Ward, Bill wrote:
> I started from scratch again. This time i went with oh323 instead 
> of ooh323.  I still get the same issue but this time it says call 
> refused by remote host.  It doesn't explain why though.  I can't 
> understand the CCM trace logs to see why it might be refusing the 
> connection.

On the DTMF issues with chan_ooh323, I've used the channel with
CCM 4.0, 4.1 and 5.0 with no issues.  At one point I tested all
of the DTMF methods ooH323 provides.  CCM definately works with
h245signal, and in the past has worked with q931keypad and 
h245alphanumeric.  Cisco's support of RFC2833 in CCM has not
been impressive.  It works OK as of CCM 5.0 with SIP, but still
not so solid with H323.

Dan