| Summary: | ASTERISK-12959: Dundi and DNS | ||
| Reporter: | K-H Hecker (kombjuder) | Labels: | |
| Date Opened: | 2008-10-24 11:25:40 | Date Closed: | 2008-12-15 10:17:52.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | PBX/pbx_dundi |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | If the ip of a dundi peer changes, dundi still uses the cached one. The solucion of issue 0013663 'reload pbx_dundi.so' do not work in 1.6.0.1. Only stop and start asterisk works. | ||
| Comments: | By: Russell Bryant (russell) 2008-10-24 11:26:58 Do you mean "module reload pbx_dundi.so" ? By: K-H Hecker (kombjuder) 2008-10-24 11:32:03 No, reload pbx_dundi.so A message "reloaded" an then a message that it is changed to "module reload pbx_dundi.so" I'll try tomorrow with "module reload pbx_dundi.so", than I'll have a peer with new ip. The same with "module reload pbx_dundi.so". Dundi do not use the new ip. By: Dmitry Andrianov (dimas) 2008-10-28 18:34:37 Actually, if Asterisk kept the hostname of the DUNDi peer and tried to resolve it sometimes (when?)it could be really useful. I also have some issues with DUNDi (13532) and now I start thinking that all my problems were caused by a scenario like: 1. Temporary loss of DNS service (because loss of connectivity between remote and central offices) 2. Restart of Asterisk (because of crash) 3. When Asterisk starts and can not resolve DUNDi peer IP, DUNDi does not work and it will not start working ever. Not sure how keeping the hostname and resolving it is consistent with other pieces of the system (sip/iax hostnames etc). By: Leif Madsen (lmadsen) 2008-12-12 11:33:28.000-0600 Assigned to russell for now to see if he can move this forward. Please reassign if necessary By: Digium Subversion (svnbot) 2008-12-15 10:17:51.000-0600 Repository: asterisk Revision: 164272 U trunk/pbx/pbx_dundi.c ------------------------------------------------------------------------ r164272 | russell | 2008-12-15 10:17:50 -0600 (Mon, 15 Dec 2008) | 8 lines When a reload is issued, always process the configuration for dundi.conf. The reason is that a reload can be used to refresh DNS lookups for defined peers. Even if the config file hasn't changed, we want to process it for that purpose. (closes issue ASTERISK-12959) Reported by: kombjuder ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=164272 | ||