[Asterisk-Users] Re: MWI problems on 9133i

Joe McConnaughey kenn10 at comcast.net
Mon Aug 22 15:17:38 MST 2005


Thank you Melissa.  I love the phone but the dial keypad is a little bouncy. 
I was hoping for a more solid feel like on the analog PT390's or my quality 
standard, the Nortel 9417CW.

Other than the MWI problem, I'd like more documentation on the configuration 
paramters.  I have found little online configuration documentation other 
than very basic stuff on the Sayson website.  I'd like to know about all the 
things that can be modified in the Aastra.cfg and <mac addr>.cfg files.  I 
stumbled on the dialplan command which solved my first big issue with the 
phone.  I'm sure there are other things I would like to have access to.  I 
want to know about shared call appearances, busy lamps, volume control 
parameters, etc., which are controlled by the config files.

Is there a document or additional config info you can send me?  These phones 
are going to knock the Polycoms and Grandstreams out of the water once the 
Asterisk and other open source communities understand their quality and 
flexibility.  I'd like to be on the cheering squad!

Joe McConnaughey

----- Original Message ----- 
From: "Melissa Lee" <melissa.lee at sayson.com>
To: <kenn10 at comcast.net>
Cc: "David Sayson" <frisketdog at hotmail.com>; 
<asterisk-users at lists.digium.com>
Sent: Monday, August 22, 2005 4:30 PM
Subject: RE: MWI problems on 9133i


Hi Joe:

Thank you for your feedback.

MWI problem on 9133i is a known bug and will be fixed in the August
release. The August release will be available to the public shortly.
Please check the www.sayson.com web site periodically.

Sincerely,

Melissa Lee


-----Original Message-----

Today's Topics:

    23. Aastra 9133i Phone and MWI (Joe McConnaughey)

Message: 23
Date: Mon, 22 Aug 2005 08:29:38 -0400
From: "Joe McConnaughey" <kenn10 at comcast.net>
Subject: [Asterisk-Users] Aastra 9133i Phone and MWI
To: <asterisk-users at lists.digium.com>
Message-ID: <000b01c5a715$29f12af0$6501a8c0 at JoesAthlon64>
Content-Type: text/plain; charset="iso-8859-1"

Hello -

I have just purchased an Aastra 9133i SIP phone for testing with
Asterisk. Its a little flakey but overall is a far superior phone to the
others in the $179 range.

I have an issue regarding the message waiting indicator.  The phone does
not seem to respond to the "NOTIFY" command from Asterisk.  Searching
archives seems to indicate that this was previously an issue on the 480i
telephone but that it got corrected.  I have downloaded the lastest
firmware (1.2.1) onto the phone but no go.  Below is an exerpt of the
SIP DEBUG from CLI.

I'd like feedback on whether this is an Aastra issue or an Asterisk
issue. Anyone have experience with these phones?  It appears that
Asterisk sends the message five times.  Perhaps it is awaiting a
response from the phone which never comes.  In any case, the MWI never
activates.

11 headers, 2 lines

Reliably Transmitting:

NOTIFY sip:2008 at 192.168.1.201 SIP/2.0

Via: SIP/2.0/UDP 192.168.1.251:5060;branch=z9hG4bK3b581d6c

From: "" <sip:@192.168.1.251>;tag=as77c9889f

To: <sip:2008 at 192.168.1.201>

Contact: <sip:192.168.1.251>

Call-ID: 4a4e5c1d173010e3027c5d226cac810b at 192.168.1.251

CSeq: 102 NOTIFY

User-Agent: Asterisk PBX

Event: message-summary

Content-Type: application/simple-message-summary

Content-Length: 43



Messages-Waiting: yes

Voice-Message: 1/0

 (no NAT) to 192.168.1.201:5060

Scheduling destruction of call
'4a4e5c1d173010e3027c5d226cac810b at 192.168.1.251' in 15000 ms

Retransmitting #1 (no NAT):

NOTIFY sip:2008 at 192.168.1.201 SIP/2.0

Via: SIP/2.0/UDP 192.168.1.251:5060;branch=z9hG4bK3b581d6c

From: "" <sip:@192.168.1.251>;tag=as77c9889f

To: <sip:2008 at 192.168.1.201>

Contact: <sip:192.168.1.251>

Call-ID: 4a4e5c1d173010e3027c5d226cac810b at 192.168.1.251

CSeq: 102 NOTIFY

User-Agent: Asterisk PBX

Event: message-summary

Content-Type: application/simple-message-summary

Content-Length: 43



Messages-Waiting: yes

Voice-Message: 1/0



<SNIP>



 to 192.168.1.201:5060

Retransmitting #5 (no NAT):

NOTIFY sip:2008 at 192.168.1.201 SIP/2.0

Via: SIP/2.0/UDP 192.168.1.251:5060;branch=z9hG4bK3b581d6c

From: "" <sip:@192.168.1.251>;tag=as77c9889f

To: <sip:2008 at 192.168.1.201>

Contact: <sip:192.168.1.251>

Call-ID: 4a4e5c1d173010e3027c5d226cac810b at 192.168.1.251

CSeq: 102 NOTIFY

User-Agent: Asterisk PBX

Event: message-summary

Content-Type: application/simple-message-summary

Content-Length: 43



Messages-Waiting: yes

Voice-Message: 1/0



 to 192.168.1.201:5060





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.
*****************************************************************************






More information about the asterisk-users mailing list