[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
Fri Jan 21 16:54:23 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-21 16:54 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
======================================================================
----------------------------------------------------------------------
(0130888) may213 (manager) - 2011-01-21 16:54
https://issues.asterisk.org/view.php?id=18542#c130888
----------------------------------------------------------------------
Vladimir,
Seems like to my previous suggestions about initiating side of tcs and msd
procedures was incorrect. I see in last log that tcs exchange procedure
simple don't start and i think it's reason of call termination after 16
mins.
RoundTrip request and replies are proccessed normal in this call, but
h.323 connection closed unexpectly from avaya side.
I think there is difference in tcs exchange procedure in H.323v2 (which
use your Avaya) and H.323v4 (which use ooh323) and we must work properly
with v2 endpoints. I'll read h.323v2 specs tomorrow and will try to see how
this proc work in opal/openh323 libraries.
Issue History
Date Modified Username Field Change
======================================================================
2011-01-21 16:54 may213 Note Added: 0130888
======================================================================
More information about the asterisk-bugs
mailing list