Summary:	ASTERISK-12893: I get two MWI subscritions for a peer (phone)
Reporter:	ibercom (ibercom)	Labels:
Date Opened:	2009-01-07 17:24:48.000-0600	Date Closed:	2011-06-07 14:07:55
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/Subscriptions
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) sip.conf ( 1) sip_show_subscriptions.txt
Description:	When I reset a phone (working), it register and subscribe for MWI again then I get two different subscriptions for this peer. /* We only allow one subscription per peer */ isn't true. It could be related to bug 14133. I don't use realtime config.
Comments:	By: Joshua C. Colp (jcolp) 2009-01-21 18:06:11.000-0600 Please provide additional information with this including the configuration and sip show subscriptions. By: ibercom (ibercom) 2009-01-26 10:03:36.000-0600 In the sip show subscriptions file you can see the start. There is 299 active SIP subscriptions, when I reset 20001 phone's then I get 300 active SIP subscriptions. The phone (Thomsom ST2030) log an error twice in this moment and 30 minutes later. After I have 298 active SIP subscriptions and immediately 299 active SIP subscriptions and NO MORE ERROR. By: Joshua C. Colp (jcolp) 2009-02-10 12:36:03.000-0600 Are you using realtime peers for other devices too? I would really like to see this tested on a system running the latest 1.4 release (which does have an MWI subscription bugfix) without realtime at all. By: ibercom (ibercom) 2009-02-12 13:36:20.000-0600 I don't use realtime peers but I use voicemail storage with ODBC. I have some problem with DADHI, for that reason my system run asterisk 1.4.21.1, but I can patch the MWI subscription bugfix. Which is it ? By: Joshua C. Colp (jcolp) 2009-02-12 13:38:00.000-0600 What issue are you having with dahdi that makes it so you can't upgrade? By: ibercom (ibercom) 2009-02-18 07:25:26.000-0600 I upgrade to asterisk 1.4.23.1 and now I get the subscriptions correctly. I have only one subscription by phone. You can close the bug, thank you. By: Joshua C. Colp (jcolp) 2009-02-18 09:05:34.000-0600 Closed per reporter, issue has already been fixed.