[Asterisk-Users] Problem with Avaya 4602 / SIP response 481

[Trevor G. Hammonds]

I have an Avaya 4602 IP phone that was previously working with Asterisk.  It
was being used elsewhere for several months, and I recently set it up again
to work with Asterisk.  Everything works fine for several minutes -- I am
able to receive and make calls as expected.  However, after a few minutes,
and every few minutes thereafter, I get the following message on the
console:

    -- Got SIP response 481 "Call Does Not Exist" back from 192.168.1.98

After this message, the phone no longer works properly -- if at all.  When
attempting to dial, the phone seems to ignore my dial plan, accepting no
more than five digits (I get the tone burst indicating that it is done
accepting digits), and it does not transmit anything to Asterisk.
Attempting to call the phone's extension results in a busy condition (SIP
response 486).  Soft resetting the phone restores it to working order for
several minutes.  

I have searched Google and the Wiki for answers to this problem, and see
that Brian Elton has experienced this exact situation.  However, I saw no
resolution posted to the list, and do not have Brian's contact information.


I suspect this may be related to the MWI indicator and the "mailbox="
statement in my sip.conf file, as the last time I was using this phone with
*, it was not set up to use voicemail. 

Any ideas or assistance will be greatly appreciated. 

		Sincerely,
		Trevor Hammonds


SIP Debug output:

Sip read:
SIP/2.0 481 Call Does Not Exist
Call-ID: 7fc1849a4132a3a74565eeed3c26d507 at 192.168.1.10
CSeq: 102 NOTIFY
From: "asterisk" <sip:asterisk at 192.168.1.10>;tag=as5860bf17
To: <sip:avaya4602 at 192.168.1.98>;tag=cad443b1cd74b1e
Via: SIP/2.0/UDP 192.168.1.10:5060;branch=z9hG4bK69c2e97b
Content-Length: 0
Contact: <sip:avaya4602 at 192.168.1.98>
User-Agent: Elite 1.0 Brcm Callctrl/1.5.1.0 MxSF/v3.2.6.26


9 headers, 0 lines
    -- Got SIP response 481 "Call Does Not Exist" back from 192.168.1.98
Destroying call '7fc1849a4132a3a74565eeed3c26d507 at 192.168.1.10'
Destroying call '3844dc0eeba9eb04adf132f539666c21 at 192.168.1.98'