[asterisk-bugs] [Asterisk 0018542]: OOH323 Outgoing Calls Fail with Asterisk 1.8.1.1
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Dec 29 00:31:16 UTC 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18542
======================================================================
Reported By: vmikhelson
Assigned To: may213
======================================================================
Project: Asterisk
Issue ID: 18542
Category: Addons/chan_ooh323
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Asterisk Version: 1.8.1.1
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-12-28 11:26 CST
Last Modified: 2010-12-28 18:31 CST
======================================================================
Summary: OOH323 Outgoing Calls Fail with Asterisk 1.8.1.1
Description:
1. Upgraded to Asterisk 1.8.1.1 from Asterisk 1.6.2.15.
2. All outgoing calls started to fail.
3. "ooh323 show" was not recognized as a valid command. Auto-complete
worked though.
4 Rebooted the system.
CLI:
pbx*CLI> ooh323 show peers
Name Accountcode ip:port Formats
avaya h3230101 172.17.135.2:1720 0x4 (ulaw)
FreePBX 2.8.0.4
AsteriskNOW 1.7
======================================================================
----------------------------------------------------------------------
(0130020) vmikhelson (reporter) - 2010-12-28 18:31
https://issues.asterisk.org/view.php?id=18542#c130020
----------------------------------------------------------------------
Hi may213,
A little bit more information.
Outgoing calls do not fail at 32 seconds, just incoming.
Call setup is different in regards to DTMF capabilities processing
compared to what happened in Asterisk 1.6.2.
I have "RFC2833" set in [general] and "h245alphanumeric" in [avaya]
sections of ooh323.conf.
Here is what we see for an outgoing call:
17:47:38:941 Enabled RTP/CISCO DTMF capability for (outgoing,
ooh323c_o_1)
17:47:38:941 Enabled RFC2833 DTMF capability for (outgoing, ooh323c_o_1)
17:47:38:941 Dtmf mode set to H.245(alphanumeric) for (outgoing,
ooh323c_o_1)
17:47:38:941 Dtmf mode set to H.245(signal) for (outgoing, ooh323c_o_1)
The same for incoming:
18:16:30:557 Enabled RTP/CISCO DTMF capability for (incoming, ooh323c_2)
18:16:30:557 Enabled RFC2833 DTMF capability for (incoming, ooh323c_2)
18:16:30:557 Dtmf mode set to H.245(alphanumeric) for (incoming,
ooh323c_2)
18:16:30:558 Dtmf mode set to H.245(signal) for (incoming, ooh323c_2)
It looks like incorrect processing of a peer specific "dtmfmode="
setting.
Thank you,
Vladimir
Issue History
Date Modified Username Field Change
======================================================================
2010-12-28 18:31 vmikhelson Note Added: 0130020
======================================================================
More information about the asterisk-bugs
mailing list