[asterisk-bugs] [Asterisk 0012323]: Asterisk gives up on registration after receiving 408 Timeout response once
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Apr 1 09:15:34 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=12323
======================================================================
Reported By: voipdealer
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 12323
Category: Channels/chan_sip/Registration
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 03-28-2008 09:11 CDT
Last Modified: 04-01-2008 09:15 CDT
======================================================================
Summary: Asterisk gives up on registration after receiving
408 Timeout response once
Description:
I have noticed the following behavior:
- Asterisk registers fine to SIP provider for days
- SIP provider sends one 408 response due to some temporary issue on their
network
- Asterisk never attempts to register again, until it is restarted,
resulting in loss of inbound service
Ideally, a 408 should never happen. However, there are hundreds of
possible reasons a provider may send a 408 for a few seconds (systems are
failing over to backups, database is unavailable due to backup, whatever).
Asterisk should just reschedule registration as it does with all other 4xx
errors.
======================================================================
----------------------------------------------------------------------
voipdealer - 04-01-08 09:15
----------------------------------------------------------------------
Any chance of this bug fix making it in? To clarify, this is not due to a
client-side Asterisk configuration error that might cause other 4xx errors
(like a wrong username/password). This is due to a momentary glitch on the
remote side, which causes them to properly send a 408 Timeout, so the
client doesn't wait forever. However, that doesn't mean the client
shouldn't try again shortly.
I suspect this is not a more visible issue because most ITSPs are letting
Asterisk users connect to Asterisk servers, which, to my knowledge, never
send a 408 regardless of how long the database lookup takes. However, to
interop with other SIP gateways, Asterisk should be able to gracefully
process a timeout and just try again.
Issue History
Date Modified Username Field Change
======================================================================
04-01-08 09:15 voipdealer Note Added: 0084841
======================================================================
More information about the asterisk-bugs
mailing list