hello Dan,
seems that ooh323 incorrectly handles dtmfmode settings from peer
definition, because:
when I put "dtmfmode=h245signal" in [general] section it works, but when
I put this only to peer definition (i.e. in [general] is default mode
rfc2833) it doesn't work!
also, when I put h245signal in [general] and in peer definition I have
rfc2833, it work also!
seems, that ooh323 completely ignores dtmfmode, when this is set in peer
definition (but in "ooh323 show peer ccm", from my example, is displayed
what I set)...
Dan, please can you confirm this, after that I update bug report:
http://bugs.digium.com/view.php?id=8191
PJ
my working config (dtmfmode=rfc2833 in peer definition has no efect at all)
[general]
disallow=all
allow=alaw,g729
dtmfmode=h245signal
[ccm]
type=friend
ip=192.168.40.7
port=1720
dtmfmode=rfc2833
Dan Austin wrote:
PJ Wrote:
Dan, can you supply your ooh323.conf for me? I would like resolve my
issue with not recognizing dtmf by ooh323 from callmanager
my ooh323 is quite simple, also on callmanager config page for gateway
to asterisk is nothing special, no faststart, no mtp; ccm v4.1.3sr3a
There's nothing secret about it, but I think I can skip that if the
settings below are what you are using-
[general]
disallow=all
allow=alaw
;faststart=no
;h245tunneling=no
[ccm]
type=peer
ip=192.168.40.7
port=1720
;dtmfmode=rfc2833
;dtmfmode=h245signal
;h245tunneling=no
;faststart=no
I tend to use type=friend since I want calls in both directions.
>From the list above, you have not set the dtmfmode in [general],
which is where I set it, or in the peer. The sample ooh323.conf
shows that the default is RFC2833, which does not work with CCM.
Either uncomment ;dtmfmode=h245signal in the peer, or uncomment it
and move it to [general].
Dan Austin wrote:
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
_______________________________________________
--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