[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
Mon Jan 24 17:53:10 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-24 17:53 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
======================================================================
----------------------------------------------------------------------
(0130971) vmikhelson (reporter) - 2011-01-24 17:53
https://issues.asterisk.org/view.php?id=18542#c130971
----------------------------------------------------------------------
May213,
Here is a snapshot of a firewall traffic monitor on the Asterisk end.
Interestingly the first TCP connection which looks like a control
connection to me does not send back any traffic. It initially sent 750
bytes. Then it periodically receive packets but does not reply. The
increment is around 53 bytes.
# Source IP Source Port Destination IP Destination Port Protocol
Src Interface Dst Interface Tx Bytes Rx Bytes
1 172.17.135.2 4488 172.17.137.11 1720 TCP OPT LAN 750 2513
2 172.17.135.2 51081 172.17.137.11 12113 UDP OPT LAN 9288 7728
3 172.17.135.2 51080 172.17.137.11 12112 UDP OPT LAN 4239200 207800
4 172.17.135.2 4489 172.17.137.11 12037 TCP OPT LAN 9687 3893
Here is the snapshot in 12.5 minutes:
# Source IP Source Port Destination IP Destination Port Protocol
Src Interface Dst Interface Tx Bytes Rx Bytes
1 172.17.135.2 4488 172.17.137.11 1720 TCP OPT LAN 750 2972
2 172.17.135.2 51081 172.17.137.11 12113 UDP OPT LAN 16416 13616
3 172.17.135.2 51080 172.17.137.11 12112 UDP OPT LAN 7405600 716400
4 172.17.135.2 4489 172.17.137.11 12037 TCP OPT LAN 16164 6290
Here is a final snapshot at 16 minutes when the call was dropped:
# Source IP Source Port Destination IP Destination Port Protocol Src
Interface Dst Interface Tx Bytes Rx Bytes
1 172.17.135.2 4488 172.17.137.11 1720 TCP OPT LAN 750 3125
2 172.17.135.2 51081 172.17.137.11 12113 UDP OPT LAN 21060 17664
3 172.17.135.2 51080 172.17.137.11 12112 UDP OPT LAN 2400 0
As you see the non-responsive TCP connection did not drop but another TCP
connection was dropped and one of the UDP connections was reset.
This test pretty much rules out a TCP timeout as a cause of the
disconnect.
Some H323 control signaling is left not answered by Asterisk.
Thank you,
Vladimir
Issue History
Date Modified Username Field Change
======================================================================
2011-01-24 17:53 vmikhelson Note Added: 0130971
======================================================================
More information about the asterisk-bugs
mailing list