asterisk users - Jan 2005 - TA register to Asterisk and getting down after notify msg, why?

Hi, 

I have a terminal adaptor connected to Asterisk. I found that when it connect to
Asterisk v1.0.0,The TA send register msg, and get OK msg, but it get Notify msg
every 1 minute, The TA reply with "call does not exist" , usually 10
minutes later, The TA is down. But it work well with Asterisk v1.0-RC1, only
register and OK msg are sent and got, no Notify msg is sent to it. What's
worng with it ?

The following is the msg flow:
_________________________________________________
0 headers, 0 lines
Linux1*CLI>

Sip read:
REGISTER sip:10.144.166.220:5060 SIP/2.0
Via: SIP/2.0/UDP 10.144.169.136;branch=z9hG4bKc0bd6005d
To: 3000006666 <sip:3000006666@10.144.166.220:5060>
From: 3000006666 <sip:3000006666@10.144.166.220:5060>;tag=7abac26fdac761f
Call-ID: 3b4f38d8453c881116fdb6732d385ee4@10.144.169.136
CSeq: 1198861724 REGISTER
Contact: 3000006666 <sip:3000006666@10.144.169.136>
Allow: NOTIFY
Allow: REFER
Allow: OPTIONS
Allow: INVITE
Allow: ACK
Allow: CANCEL
Allow: BYE
Content-Length: 0
User-Agent: Brcm Callctrl/1.5.0.0 MxSF/v3.2.5.20


16 headers, 0 lines
Using latest request as basis request
Sending to 10.144.169.136 : 5060 (non-NAT)
Transmitting (no NAT):
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.144.169.136;branch=z9hG4bKc0bd6005d
From: 3000006666 <sip:3000006666@10.144.166.220:5060>;tag=7abac26fdac761f
To: 3000006666 <sip:3000006666@10.144.166.220:5060>;tag=as72ac2138
Call-ID: 3b4f38d8453c881116fdb6732d385ee4@10.144.169.136
CSeq: 1198861724 REGISTER
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Contact: <sip:3000006666@10.144.166.220>
Content-Length: 0


 to 10.144.169.136:5060
Transmitting (no NAT):
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.144.169.136;branch=z9hG4bKc0bd6005d
From: 3000006666 <sip:3000006666@10.144.166.220:5060>;tag=7abac26fdac761f
To: 3000006666 <sip:3000006666@10.144.166.220:5060>;tag=as72ac2138
Call-ID: 3b4f38d8453c881116fdb6732d385ee4@10.144.169.136
CSeq: 1198861724 REGISTER
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Expires: 120
Contact: <sip:3000006666@10.144.169.136>;expires=120
Date: Wed, 29 Dec 2004 05:54:15 GMT
Content-Length: 0


 to 10.144.169.136:5060
Scheduling destruction of call
'3b4f38d8453c881116fdb6732d385ee4@10.144.169.136'
 in 15000 ms
11 headers, 2 lines
Reliably Transmitting:
NOTIFY sip:3000006666@10.144.169.136 SIP/2.0
Via: SIP/2.0/UDP 10.144.166.220:5060;branch=z9hG4bK1777da90
From: "asterisk" <sip:asterisk@10.144.166.220>;tag=as471c4df7
To: <sip:3000006666@10.144.169.136>
Contact: <sip:asterisk@10.144.166.220>
Call-ID: 3c50df5e489466cc60d3177f7d479ef8@10.144.166.220
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 36

Messages-Waiting: no
oicemail: 0/0
 (no NAT) to 10.144.169.136:5060
Scheduling destruction of call
'3c50df5e489466cc60d3177f7d479ef8@10.144.166.220'
 in 15000 ms
Linux1*CLI>

Sip read:
SIP/2.0 481 Call Does Not Exist
Call-ID: 3c50df5e489466cc60d3177f7d479ef8@10.144.166.220
CSeq: 102 NOTIFY
From: "asterisk" <sip:asterisk@10.144.166.220>;tag=as471c4df7
To: <sip:3000006666@10.144.169.136>;tag=d9c50268ebc1858
Via: SIP/2.0/UDP 10.144.166.220:5060;branch=z9hG4bK1777da90
Content-Length: 0
Contact: <sip:3000006666@10.144.169.136>
User-Agent: Brcm Callctrl/1.5.0.0 MxSF/v3.2.5.20


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