Bug 595133

Summary: Peers get often unreachable when using qualify=yes
Product: [Fedora] Fedora Reporter: invitu <contact>
Component: asteriskAssignee: Jeffrey C. Ollie <jeff>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 12CC: itamar, jeff
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-13 01:16:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description invitu 2010-05-23 14:29:51 UTC
Description of problem:
Peers lose registration when qualify=yes. The property qualify=yes is used when peers are behind a NAT network.

Version-Release number of selected component (if applicable):
1.6.1.18

How reproducible:
Always

Steps to Reproduce:
1.Set a peer with qualify=yes
2. Check sip logs and peers status with "sip show peers"
3. The peers get unreachable at the same time. SIP packets seem to be stucked somewhere between the server and the peers.
  
Actual results:
Peers get unreachable

Expected results:
Peers should keep their registration.

Additional info:
The issue is fixed in V. 1.6.1.20 : https://issues.asterisk.org/view.php?id=16936

Comment 1 invitu 2010-09-13 01:16:19 UTC
The issue was caused by a ISP DNS problem.