Summary: | ASTERISK-17661: [patch] Remove a jabber account | ||
Reporter: | Nuno Borges (nerbos) | Labels: | |
Date Opened: | 2011-04-08 08:55:48 | Date Closed: | 2013-01-03 15:25:36.000-0600 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Resources/res_jabber Resources/res_xmpp |
Versions: | 1.8.3 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Attachments: | ( 0) 19085.patch | |
Description: | Greetings, Imagine that i want to remove a jabber account from my configuration. I go to the configuration file and clean up the account configuration, then i issue a "core reload" in asterisk CL. When checking connections the removed client no longer appears, that's correct. The problem is the client is still connected and i am still receiving packages from it (checked by AMI), when issuing a reload we should re-check which clients/components are no longer in the configuration file and destroy from jabber structure. Brest regards. | ||
Comments: | By: Leif Madsen (lmadsen) 2011-04-13 09:25:14 That is certainly a great idea, however we cannot accept features requests on the issue tracker without any submitted code. If you are able to provide this functionality then please do re-open this issue. Thanks! PS: For now, a work around may be to do a 'module unload res_jabber.so' and then 'module load res_jabber.so' to reinitialize the configuration. By: Nuno Borges (nerbos) 2011-04-14 08:52:48 Patch provided for ISSUE: 19085 By: Nuno Borges (nerbos) 2011-04-14 08:55:14 Greetings, I consider this a problem and not an improvement :). Either way patch provided. Best regards. By: Leif Madsen (lmadsen) 2011-04-14 09:04:38 Awesome! Open source works again! :) (I knew this wouldn't get bumped up to any sort of priority without a patch, so thanks!) |