| Summary: | ASTERISK-17675: MWI not working for most ATAs | ||
| Reporter: | Ernie Dunbar (ernied) | Labels: | |
| Date Opened: | 2011-04-11 17:46:26 | Date Closed: | 2011-07-26 14:12:00 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | 1.6.2.17 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) mwiconfig.conf ( 1) sip_debug.txt | |
| Description: | After upgrading several (around 20 or so) customers to our new Asterisk server running version 1.6.2.17, most of them are complaining that their MWI no longer works. I've tested this with a variety for ATAs, and so far I can tell that these ATAs do not get a message waiting indicator: Thomson 780 and 784 Linksys SPA2102 Linksys PAP2 One ATA that I can verify *does* work, is an old Sipura SPA2002, which of course, is out of production. I've worked extensively on a Thomson 784 trying to get the MWI working, but to no avail. As far as I can tell (with the use of sip set debug peer on the Asterisk console), it doesn't even send the SIP NOTIFY message for the MWI. | ||
| Comments: | By: Elazar Broad (ebroad) 2011-04-12 15:22:13 Try setting 'subscribemwi=no' under the peer definition. By: Ernie Dunbar (ernied) 2011-04-12 15:35:05 I have. It still doesn't send out any SIP NOTIFY messages. Also, I've just verified that the 2002 doesn't work either - for whatever reason it just thinks that there is always voicemail, even when there is none. By: Ernie Dunbar (ernied) 2011-04-13 15:17:43 I've also just attached a snippet from sip.conf and voicemail.conf. By: Elazar Broad (ebroad) 2011-04-13 17:09:59 Are vmexten and mwi_from set? Additionally, I deleted your uploaded config as it contained the peers secret/password, in the future please redact such information before posting. elazar By: Ernie Dunbar (ernied) 2011-04-13 18:24:34 Yes, I've set those too without any results. By: Ernie Dunbar (ernied) 2011-04-15 12:16:55 Re-uploaded configuration with secret redacted. By: Leif Madsen (lmadsen) 2011-04-19 09:18:02 There is no configuration here. Additionally you'll need to supply the SIP trace from the Asterisk console per the bug guidelines. By: Ernie Dunbar (ernied) 2011-04-19 11:26:21 D'oh! Well, the configuration is uploaded now, and so is the SIP trace. I see from the SIP trace that the NOTIFY: Messages-Waiting message is getting sent, but why are none of the clients getting these messages? In this particular example, the ATA is connected directly to the internet (the Thomson 784 is an all-in-one router/DSL modem/ATA, and the ATA is not firewalled or NATed). Is the NOTIFY properly formatted? By: Leif Madsen (lmadsen) 2011-05-10 15:00:32 Well the NOTIFY might be a bit odd: Messages-Waiting: yes Message-Account: sip:default@<serverip> Voice-Message: 2/0 (0/0) why 'default' and not the account name? What revision does this happen at? If you can trace the specific revision that this regression was introduced in it will make it much easier to resolve. By: Ernie Dunbar (ernied) 2011-05-10 17:55:08 From configure.ac: AC_REVISION($Revision: 301220 $) By: Russell Bryant (russell) 2011-07-26 14:11:45.057-0500 Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions | ||