[asterisk-bugs] [Asterisk 0018542]: [patch] OOH323 Outgoing Calls Fail with Asterisk 1.8.1.1
Asterisk Bug Tracker
noreply at bugs.digium.com
Sun Jan 16 18:31:58 CST 2011
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: acknowledged
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: 2011-01-16 18:31 CST
======================================================================
Summary: [patch] 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
======================================================================
----------------------------------------------------------------------
(0130537) vmikhelson (reporter) - 2011-01-16 18:31
https://issues.asterisk.org/view.php?id=18542#c130537
----------------------------------------------------------------------
May213,
Set h245tunneling=no, reloaded ooh323.
Outgoing call was still working fine.
Incoming call did not drop at 30 seconds which was good. Unfortunately
after the call was hung by Avaya Asterisk kept the channel up for about 30
seconds. I will be able to test DTMF for incoming calls tomorrow, I will
update the case then.
Also I experienced the same log "poisoning" with SIP messages as I did
when I disabled h245tunneling last time in our troubleshooting. The log is
attached with the sensitive information masked.
Thank you,
Vladimir
Issue History
Date Modified Username Field Change
======================================================================
2011-01-16 18:31 vmikhelson Note Added: 0130537
======================================================================
More information about the asterisk-bugs
mailing list