[asterisk-bugs] [Asterisk 0018542]: [patch] OOH323 Outgoing Calls Fail with Asterisk 1.8.1.1
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Jan 18 16:03:25 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-18 16:03 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
======================================================================
----------------------------------------------------------------------
(0130644) may213 (manager) - 2011-01-18 16:03
https://issues.asterisk.org/view.php?id=18542#c130644
----------------------------------------------------------------------
Vladimir,
new patch attached, it must solve incoming call drop issue (removed start
of tcs procedure by called side if h245tunelling isn't active) and
disconnection delay issue.
incoming call drop issue found because your Avaya can't start tcs
procedure until call is answered, you had inconsistent results because
there was different dealys between setup and answer, calls worked fine if
tcs timer on asterisk wasn't expired. With new patch ooh323 channel will
wait start tcs procedure from Avaya. I'm not sure that it's best choice for
all cases and i think to implement config option about it.
Issue of 30 secs disconnection is related to simple mistake of codes,
there need to clear h.323 connection after h.245 sessions closed. Most of
H.323 endpoints clear connection regardless of call direction, but not your
avaya and asterisk didn't it also.
Unforunatelly previous patch isn't functional and you can not use him.
Issue History
Date Modified Username Field Change
======================================================================
2011-01-18 16:03 may213 Note Added: 0130644
======================================================================
More information about the asterisk-bugs
mailing list