[Home]

Summary:ASTERISK-08846: MWI on Avaya phones does not work
Reporter:shmattie (shmattie)Labels:
Date Opened:2007-02-19 16:40:58.000-0600Date Closed:2007-05-30 02:42:54
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/Subscriptions
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:The message waiting indicator does not work on Avaya phones.  A sip debug shows the error is "Invalid Subscription-State."

I have tested with SVN-trunk-r54575 and included a sip debug.  Let me know if you need any more information.

****** ADDITIONAL INFORMATION ******

Reliably Transmitting (no NAT) to 10.0.2.237:5060:
NOTIFY sip:500@10.0.2.237:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.32:5060;branch=z9hG4bK1a68d459;rport
Max-Forwards: 70
From: "asterisk" <sip:asterisk@10.0.0.32>;tag=as05f0d373
To: <sip:500@10.0.2.237:5060>
Contact: <sip:asterisk@10.0.0.32>
Call-ID: 4deaa29f76b10889225b67cc02d219c4@10.0.0.32
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX SVN-trunk-r54575
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 90

Messages-Waiting: yes
Message-Account: sip:asterisk@10.0.0.32
Voice-Message: 3/0 (0/0)

---
hqtcat01*CLI>
<--- SIP read from 10.0.2.237:5060 --->
SIP/2.0 400 Invalid Subscription-State
Call-ID: 4deaa29f76b10889225b67cc02d219c4@10.0.0.32
CSeq: 102 NOTIFY
From: "asterisk" <sip:asterisk@10.0.0.32>;tag=as05f0d373
To: <sip:500@10.0.2.237:5060>;tag=a96c3fda9354b47
Via: SIP/2.0/UDP 10.0.0.32:5060;branch=z9hG4bK1a68d459;rport
Content-Length: 0
User-Agent: Avaya SIP R2.2 Endpoint Brcm Callctrl/1.5.1.0 MxSF/v3.2.6.26


<------------->
--- (8 headers 0 lines) ---
   -- Got SIP response 400 "Invalid Subscription-State" back from 10.0.2.237
Comments:By: Olle Johansson (oej) 2007-02-20 00:43:04.000-0600

have you tried enabling MWI subscriptions in asterisk? Check sip.conf.sample for advice.
By: shmattie (shmattie) 2007-02-20 09:12:35.000-0600

I am not clear on what you mean by MWI subscriptions.  allowsubscribe=yes and  the endpoint has a mailbox= line.

Are either of those what you are talking about?
By: Serge Vecher (serge-v) 2007-02-20 10:50:05.000-0600

allowsubscribe is for "call-state" notification, not MWI, afaik.

subscribemwi is what you are looking for, I think.
By: Serge Vecher (serge-v) 2007-03-06 09:57:10.000-0600

what's the status?
By: shmattie (shmattie) 2007-03-09 09:15:15.000-0600

I tried subscribemwi but the message waiting light still does not work.  I don't see attempts by the phone to determine the mwi status in a sip debug.  That makes me think it is an issue with the phone however there are no additional settings for voicemail in the phone's config.

Is it possible that Asterisk needs to send the phone information about MWI in a different format or standard?
By: Olle Johansson (oej) 2007-03-13 04:35:25

As required by the bug guidelines, add a SIP debug. Otherwise, everything we say will be qualified guesses and of no use.
By: Serge Vecher (serge-v) 2007-03-26 12:58:07

1) Prepare test environment (reduce the amount of unrelated traffic on the server);
2) Make sure your logger.conf has the following line:
  console => notice,warning,error,debug
3) restart Asterisk with the following command:
  'asterisk -Tvvvvvdddddngc | tee /tmp/verbosedebug.txt'
4) Enable SIP transaction logging with the following CLI commands (1.4/trunk commands in parenthesis):
set debug 4 (core set debug 4)
set verbose 4 (core set verbose 4)
sip debug (sip set debug)
5) Reproduce the problem
6) Trim startup information and attach verbosedebug.txt to the issue.
By: shmattie (shmattie) 2007-04-23 10:56:34

Avaya released an update for the SIP firmware.  Using that firmware with the latest Asterisk SVN trunk has been stable for a few days.  However, that was only done with limited testing.  Using the latest firmware with Asterisk 1.4.2 is causing the phones to freeze after a few days of use.  I plan on spending more time this week gathering the requested logs and doing more testing on the SVN trunk.
By: Olle Johansson (oej) 2007-04-27 09:12:18

But the MWI issue is gone? Right? Is it time to close this bug report?
By: shmattie (shmattie) 2007-05-01 12:57:32

This bug can be closed.  Using the latest Avaya SIP firmware with the latest Asterisk trunk the phone's MWI is working fine.

It is my understanding that 1.4 is only getting maintenance fixes and that I should not expect to get this phone's MWI working with 1.4.  I believe the fixes in the trunk will go into 1.6.  Do you have any rough estimations when 1.6 will be released?
By: Olle Johansson (oej) 2007-05-30 02:42:04

1.6 will propably be released at the end of the year, but there's no final plans for that made yet.
And for released versions, we only implement bug fixes.
By: Olle Johansson (oej) 2007-05-30 02:42:53

If you find out what freezes the phones, please open another bug report.

Thanks.