| Summary: | ASTERISK-11630: Registration with SIP-provider never succeeds | ||
| Reporter: | reinerotto (reinerotto) | Labels: | |
| Date Opened: | 2008-03-12 17:27:36 | Date Closed: | 2008-03-13 11:21:43 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Registration |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When asterisk is started immediately after boot, AND DNS not available at that time, registration with SIP-service provider does not succeed. Unfortunately, then an infinite loop is entered, trying to register again, failing again etc., even in case network and DNS are well up. Only a restart of asterisk solves the problem. Because of a bug in /etc/init.d/asterisk from SuSE exactly this can happen. Pls, refere to my previous report 12200 for details. Fixing 12200 will avoid this situation to occure, but there might be other scenarios, when registration never succeeds because of temporary DNS problem. It looks like, SIP-registration somehow does not "refresh completely" DNS-info, when retrying registration AND very first registration attempt already failed. | ||
| Comments: | By: Russell Bryant (russell) 2008-03-13 11:21:43 This is not something that we will fix for Asterisk 1.4. It requires adding dnsmgr support to chan_sip, which is an invasive enough thing that it can't be done for that release. I would suggest ensuring asterisk does not start until after your networking comes up ... | ||