asterisk users - Aug 2008 - MWI working perfectly. Shouldn't it be broken??

I have a Sipura 962 endpoint on Asterisk 1.4 where the MWI works
perfectly, however my theory is that it should be broken. 

Obviously I'm wrong but "Sip show subscriptions" does not show the
endpoint subscribing to the MWI status on Asterisk, even though all of
the other endpoints on the system DO subscribe for their respective
mailboxes, including SNOM & Polycom endpoints.  

I'm confused.  Isn't MWI subscription the method by which the device is
setting its MWI?  I know that Asterisk 1.6 is moving toward an
event-driven model, but I'm running 1.4.21.1, so why is this working?  I
know that some smart cookie on this list will know the answer, but
unfortunately I am not said cookie. 

FYI, it's not an issue of the subscription not YET subscribing etc.  If
I were to restart the system and endpoints, all the subs slowly show up
one by one, but the 962 never does -- even after days, weeks, and
months.  Yet the MWI always works perfectly from the get-go. 

Thanks!

-Karl

On Aug 24, 2008, at 11:29 AM, Karl Fife wrote:
> FYI, it's not an issue of the subscription not YET subscribing etc.   
> If
> I were to restart the system and endpoints, all the subs slowly show  
> up
> one by one, but the 962 never does -- even after days, weeks, and
> months.  Yet the MWI always works perfectly from the get-go.

Asterisk will send the NOTIFY for MWI even if the device doesn't  
subscribe, unless you tell it not to.  This is necessary for some  
phones for MWI to work.  If you _don't_ want Asterisk to do this, you  
can set the "subscribemwi=yes" option in sip.conf.  This tells  
Asterisk to _only_ send MWI with an associated subscription.

--
Russell Bryant
Senior Software Engineer
Open Source Team Lead
Digium, Inc.

Russell Bryant schrieb:
> Philipp Kempgen wrote:
>> Is subscribemwi valid in peer context only or also in general?
>> sip.conf.sample is not clear about that.
> 
> Only within a peer definition.
Umm. I assume subscribemwi=no is the default if not specified which
is bad because RFC 3842 does not talk about implicit subscriptions.
Fixing a Realtime (MySQL) system to be standards compliant means
having to change the structure of the database (unless you had
a subscribemwi column "just in case").

-- 
   Philipp Kempgen
http://www.das-asterisk-buch.de  -  http://www.the-asterisk-book.com
Amooma GmbH - Bachstr. 126 - 56566 Neuwied  ->  http://www.amooma.de
Gesch?ftsf?hrer: Stefan Wintermeyer, Handelsregister: Neuwied B14998
--