[asterisk-bugs] [JIRA] (ASTERISK-20925) 'sip reload' does not properly flush MWI outbound subscriptions defined in sip.conf

[Rusty Newton (JIRA)]

Rusty Newton created ASTERISK-20925:
---------------------------------------

             Summary: 'sip reload' does not properly flush MWI outbound subscriptions defined in sip.conf
                 Key: ASTERISK-20925
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20925
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Channels/chan_sip/Subscriptions
    Affects Versions: 11.1.0, 11.1.1
         Environment: Centos 6.3 / 2.6.32-279.19.1.el6.i686 #1 SMP Wed Dec 19 04:30:58 UTC 2012 i686 i686 i386 GNU/Linux
            Reporter: kris2k
            Assignee: Rusty Newton
            Severity: Minor


Using the following MWI registration pattern in sip.conf
mwi => 120:passwordA:120 at 192.168.1.2/120
mwi => 121:passwordB:121 at 192.168.1.2/121
mwi => 122:passwordC:122 at 192.168.1.2/122

Then referred by my sip "friends" with the mailbox argument:
mailbox=120 at SIP_Remote, etc..

1. Upon asterisk startup
"sip show mwi" will list valid MWI registrations for 120,121,122

2. Following a "sip reload"
"sip show mwi" will list valid MWI registrations for 120,121,122,120,121,122

3. Following another "sip reload" (even tried with module reload chan_sip.so)
"sip show mwi" will list valid MWI registrations for 120,121,122,120,121,122,120,121,122

This suggest that the reload routine, is not destroying existing MWI subscriptions, and at every reload, new MWI subscriptions are added.

I thought this may have just been a question of expiration of the older subscriptions, but after waiting significantly beyond the subscription refresh interval, the redundant MWI registrations still persisted.

This is causing the target PBX to complain about bad auth for certain MWI subscriptions.

Performing a "module unload chan_sip.so" then "module load chan_sip.so" puts the MWI subscriptions back into normal operation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira