Summary:ASTERISK-06489: MWI for IAX2 phones incorrect
Reporter:Rens Dijkshoorn (rens)Labels:
Date Opened:2006-03-06 17:26:13.000-0600Date Closed:2008-01-15 17:28:38.000-0600
Versions:Frequency of
Description:When using an Yuxin ST-102 phone with IAX2 firmware version 1.4.9 or 1.5.0, if there is one
message waiting the display indicates 255. Checking with IAX2 debug shows that the message
count send is 65535. If there are no messages waiting, message count = 0


Debug info

Tx-Frame Retry[000] -- OSeqno: 001 ISeqno: 002 Type: IAX     Subclass: REGACK
  Timestamp: 00061ms  SCall: 00007  DCall: 25930 [xxx.xxx.xxx.xxx:1026]
  USERNAME        : 2006
  DATE TIME       : 2006-03-06  23:00:38
  REFRESH         : 60
  APPARENT ADDRES : IPV4 xxx.xxx.xxx.xxx:1026  
  MESSAGE COUNT   : 65535
  CALLING NAME    : Rens Thuis
Comments:By: Rens Dijkshoorn (rens) 2006-03-12 15:34:45.000-0600

Adding "mailboxdetail=yes" to iax.conf changed the behavior to the correct MWI count

By: Russell Bryant (russell) 2006-03-14 11:22:07.000-0600

The attached patch should make the phone just display "1" anytime there is any number of messages.  However, I'm going to have to ask around to make sure this will still work for the IAXy and also find out why it was this way in the first place.

By: Russell Bryant (russell) 2006-03-14 11:51:59.000-0600

The issue here is that we currently have two ways to represent MWI information in the same information element.  The original way, (mailboxdetail=no), sets both bytes of the information element all to 1's to indicate that there is some non-zero number of messages waiting.

The second method (mailboxdetail=yes) sets one byte to the number of new messages and the other to the number of old messages.

I think at this point we should remove the original method and the mailboxdetail option.  We should always send MWI information in detail.  That way, the endpoint can decide how to interpret the information.  They can either take it as zero/non-zero or use the values for the actual number waiting.

I feel that we are gaining no benefit by keeping this option around.

By: Russell Bryant (russell) 2006-03-14 11:57:37.000-0600

Also, it is worthwhile to note what the most up to date version of the draft for the IAX2 spec has to say about this:


It is already assuming that messagedetail is always in use.

By: Russell Bryant (russell) 2006-03-14 12:06:19.000-0600

I decided to completely remove the "mailboxdetail" option in the trunk and to always use this behavior.  This change was made in revision 12923.

By: Digium Subversion (svnbot) 2008-01-15 17:28:38.000-0600

Repository: asterisk
Revision: 12923

U   trunk/channels/chan_iax2.c
U   trunk/configs/iax.conf.sample

r12923 | russell | 2008-01-15 17:28:38 -0600 (Tue, 15 Jan 2008) | 2 lines

deprecate the mailboxdetail option and always use its behavior, instead (issue ASTERISK-6489)