| Summary: | ASTERISK-20017: [patch] Multiple bugs in the handling of dynamic DUNDi peers | ||
| Reporter: | Peter Racz (pracz) | Labels: | patch |
| Date Opened: | 2012-06-18 06:35:47 | Date Closed: | |
| Priority: | Major | Regression? | |
| Status: | Open/New | Components: | PBX/pbx_dundi |
| Versions: | Frequency of Occurrence | Constant | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) dundi_dynamic_peers.patch | |
| Description: | The handling of dynamic DUNDi peers (peers that are configured with 'register=yes') has the following bugs: - Dynamic peers remain in the peer list after their registration has expired. Only their IP address and port number are cleared. - Reloading the dundi module does not remove expiration timers of dynamic peers. Therefore, the dynamic peer will expire before the peer re-registers again. - The dundi module keeps a list of dynamic peers in the Asterisk database with the key 'dundi/dpeers'. However, entries are not removed from the database and they remain forever in the database. The patch removes the entries when the registration expires and when the module is unloaded. The attached patch resolves these issues. | ||
| Comments: | By: Rusty Newton (rnewton) 2012-06-26 18:00:34.942-0500 Peter, thanks for the patch! Please edit the issue to reflect which version this patch is for, and please include a patch against trunk if the issue exists there. Additionally, pbx_dundi is an extended support component so it'll be up to community developers from here on out. Please find some others to post their test results with this patch if possible. Thanks! By: Peter Racz (pracz) 2012-06-28 04:23:39.348-0500 The patch is made against trunk, revision 369042. | ||