[Asterisk-Users] Re: Asterisk and MWI

[Joe McConnaughey]

MessageMelissa -

I added the "fromuser=AnyName" to my sip.conf file stations and that, in fact, corrected the problem.  The MWI now works flawlessly.

I would recommend that Aastra/Sayson pursue this with the Asterisk team so that it is listed as a known issue or to have Asterisk patched to fix it.  I will submit a bug on it as well.  I'm copying the Users Mailing List on this.

For your records, I'm running Asterisk HEAD as of 08/22/2005.  This is the very latest version of Asterisk from the CVS repository.

Please thank everyone for their hard work and fact finding.  I think you have tremendous customer support!  It only took a couple of days to track and correct this issue.  I'm extremely pleased with your phones and your support!

Joe McConnaughey
  ----- Original Message ----- 
  From: Melissa Lee 
  To: kenn10 at comcast.net 
  Sent: Wednesday, August 24, 2005 4:05 PM
  Subject: FW: Asterisk and MWI 


  Joe

  Following is the findings from our expert. Please let me know which version of Asterisk that you are using and please also forward your extension.conf to me so that we can compare the files that work in our test lab. Thanks. Melissa. 


  Currently there are two known issues (both resolved) that have led customers to complain that MWI isn't working with 1.2.x





  The first problem is most likely reported as MWI worked in 1.0.0.78 but doesn't work with 1.2.x.  This is because there was a bug in Asterisk versions prior to 1.0.4 that meant it wasn't compliant to RFC3842.  One of the issues also stopped the message count working in 1.0.0.78, but at least the LED came on.   The solution is to upgrade Asterisk to version 1.0.4 or later, the latest is 1.0.9



  The second problem is characterised by the phone not responding to MWI messages from Asterisk (I think 1.0.0.78 exhibits the same problem).  This is caused by an illegal "From" header in the NOTIFY message from Asterisk:



  NOTIFY sip:1041 at 192.168.0.160 SIP/2.0
  Via: SIP/2.0/UDP 192.168.0.101:5060;branch=z9hG4bK5a616fef;rport
  From: "asterisk" <sip:@192.168.0.101>;tag=as09997aed
  To: <sip:1041 at 192.168.0.160>
  Contact: <sip:@192.168.0.101>
  Call-ID: 07bfcea213fa8c9c13554849713e0f93 at 192.168.0.101
  CSeq: 102 NOTIFY
  User-Agent: Asterisk PBX
  Event: message-summary
  Content-Type: application/simple-message-summary
  Content-Length: 43



  Messages-Waiting: yes
  Voice-Message: 3/0





  I don't know if this is an Asterisk bug or configuration problem, so if someone comes across this issue can they gather the voicemail.conf, sip.conf and extension.conf files from the asterisk server and version that is running.  In the meantime, Mani found a workaround for this:-



  We have to tell our customers to add following line



  fromuser=AnyName



  to each user setting in the sip.conf on their asterisk server.



  Sayson Technologies Ltd.
  210 - 1910 Quebec St
  Vancouver, BC  V5T4K1
  Canada
  Phone: 604.730.1842
  Fax: 604.732.8726


------------------------------------------------------------------------------

  This email and any files transmitted with it are confidential material. They are intended solely for the use of the designated individual or entity to whom they are addressed. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, distribution or copying of this communication is strictly prohibited and may be unlawful.

  If you have received this email in error please notify info at sayson.com and permanently delete the e-mail and files.


------------------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050824/fce83c95/attachment.htm