[asterisk-bugs] [Asterisk 0018542]: [patch] OOH323 Incoming and Outgoing Calls Fail Avaya with Asterisk 1.8.1.1
Asterisk Bug Tracker
noreply at bugs.digium.com
Sat Jan 29 17:23:59 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: SVN
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-29 17:23 CST
======================================================================
Summary: [patch] OOH323 Incoming and Outgoing Calls Fail
Avaya 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
======================================================================
----------------------------------------------------------------------
(0131229) vmikhelson (reporter) - 2011-01-29 17:23
https://issues.asterisk.org/view.php?id=18542#c131229
----------------------------------------------------------------------
May213,
We are facing two (2) separate issues.
1. SonicWall end-point dropping H.323 traffic as not H.323 compliant. All
other devices but Asterisk work fine with the enforcement activated.
Asterisk version 1.6.2.15 worked fine as well. The implementation coming
with 1.8.x does not pass the test, and the traffic is dropped as a result.
2. "Default TCP Connection Timeout" is a global SonicWall setting
applicable to all connections, it is not specific to Avaya. I can force it
to 10, 15 minutes, etc. That will mean that the call will be dropped at
that time. On top of that it is insecure.
The bottom line there is some H.323 in-compliance and there are no keep
alive messages to keep the established TCP connection on. It would be nice
to fix both, but keep-alive for a lengthy TCP connection is a must.
Thank you,
Vladimir
Issue History
Date Modified Username Field Change
======================================================================
2011-01-29 17:23 vmikhelson Note Added: 0131229
======================================================================
More information about the asterisk-bugs
mailing list