Bug 595133 - Peers get often unreachable when using qualify=yes
Peers get often unreachable when using qualify=yes
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: asterisk (Show other bugs)
12
All Linux
low Severity high
: ---
: ---
Assigned To: Jeffrey C. Ollie
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-23 10:29 EDT by invitu
Modified: 2010-09-12 21:16 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-09-12 21:16:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description invitu 2010-05-23 10:29:51 EDT
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-12 21:16:19 EDT
The issue was caused by a ISP DNS problem.

Note You need to log in before you can comment on or make changes to this bug.