[Asterisk-Users] MWI indicator on SNOM200 doesn't disappear

[Geert Nijpels]

Ian White wrote:

>
> On Apr 22, 2004, at 23:48, Olle E. Johansson wrote:
>
>> Geert Nijpels wrote:
>>
>>> Ian White wrote:
>>>
>>>>
>>>> On recent releases of the snom200 firmware, the MWI indicator will 
>>>> turn on, but won't turn off when the message has been checked. It 
>>>> works on firmware 2.03o, but not in 2.04g or newer. I filed a bug 
>>>> report with snom, but they're claiming it is an asterisk issue and 
>>>> that it should have been resolved. They suggested that I ask on the 
>>>> list.
>>>>
>>>> "Anyway, Asterisk had a bug where it didn't send the NOTIFY 
>>>> correctly to
>>>> turn off the MWI.  The message doesn't contain the line so the phone
>>>> doesn't know which line to apply the messages to.
>>>>
>>>> Basically the NOTIFY message should contain something like the
>>>> following:
>>>> NOTIFY sip:dephone at 209.232.233.232;line=34n34jed SIP/2.0
>>>>
>>>> There was a bugfix for this in Asterisk for this problem, do you have
>>>> that applied?"
>>>>
>>>> I am running the current CVS version, and don't see anything in the 
>>>> code that looks like this has been touched, and I haven't seen 
>>>> reference to it on this list. They are right in that the line 
>>>> information isn't being sent, looking at the SIP debugs on both 
>>>> ends. Anybody have ideas?
>>>>
>>>> Ian
>>>>
>>> This is a problem I have been digging into a bit. In my case 
>>> asterisk did not send out the NOTIFY with the header Content-Type: 
>>> "application/simple-message-summary", but with "Content-Type: 
>>> text/plain", so the NOTIFY is treated as a txt message. In result, 
>>> when I pressed the MWI button, I saw the text from asterisk stating 
>>> the amount of messages I have. I changed it to work, and now 
>>> asterisk calls the extension the message is sent from 
>>> (asterisk at sip-server). After calling this the MWI indication 
>>> disappears, I'm not sure if it also disappears after calling from 
>>> another phone.
>>> I'm using chan_sip2 and I changed some stuff, so I'm not sure if 
>>> this is also a problem with standard chan_sip (the txt vs vm issue).
>>
>>
>> Chan_sip2 handles Contact: differently than chan_sip and works better 
>> with Snom phones.
>> It's actually where the whole chan_sip2 project started... :-)
>
>
> Any idea what sort of time frame before chan_sip2 becomes usable in a 
> production environment, or at least becomes part of the CVS tree? I 
> see your note saying that you are using it in production.

I'm using it with some changes with -stable. It's developed by oej for 
-devel. Works great with my SNOM's and Cisco 9760.

You can get chan_sip2 through the bugtracker:
http://bugs.digium.com/bug_view_page.php?bug_id=0000759

I can also send you my -stable version, but you can backport it with 
some minor trouble yourself.

Geert