Registration failure - Stale nonce message

I have searched the forums for this, and see “it is a warning and can be ignored”, but we are still getting registration failures every other minute (our registration is currently set at 60 seconds).
As I understand it, it is expected to have the first response to a register request reply as Unauthorized, because there isn’t a nonce in the conversation yet, but the second one should be valid (200 OK). For every other cycle of Register, Unauthorized, Register, OK, the phone goes Not Responding and asterisk gives the message:
"Correct auth, but based on stale nonce received from '“Test User” sip:test1@10.10.10.15"
From what I see, it was the last nonce that was issued, how could it be stale?

Another question along the same lines: Is there a better way to keep the firewall UDP port open than to register every 60 seconds. Most firewalls that we need to traverse have a 60 - 90 second window. A keep alive (I don’t think qualify does this) would probably serve the same purpose.

Thanks,

Mike

==== SIP DEBUG ====

[size=85]<— SIP read from UDP:75.75.75.75:15573 —>
REGISTER sip:10.10.10.15 SIP/2.0
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-fkyeo5zwy52o;rport
From: “Test User” sip:test1@10.10.10.15;tag=4434xh8euy
To: “Test User” sip:test1@10.10.10.15
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4174 REGISTER
Max-Forwards: 70
Contact: sip:test1@192.168.86.18:2048;flow-id=1;q=1.0;+sip.instance="urn:uuid:c32992b8-83b2-427e-a9d6-b2b554e5a1eb"
User-Agent: snom300/7.1.33
Supported: gruu
Allow-Events: dialog
X-Real-IP: 192.168.86.18
Expires: 20
Content-Length: 0

<------------->
— (14 headers 0 lines) —
Sending to 75.75.75.75:15573 (NAT)

<— Transmitting (NAT) to 75.75.75.75:15573 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-fkyeo5zwy52o;received=75.75.75.75;rport=15573
From: “Test User” sip:test1@10.10.10.15;tag=4434xh8euy
To: “Test User” sip:test1@10.10.10.15;tag=as7ce5886a
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4174 REGISTER
Server: Asterisk PBX 11.0.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce="56d05fc8"
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘3c267026aebe-4bct4hjljgvb’ in 32000 ms (Method: REGISTER)

<— SIP read from UDP:75.75.75.75:15573 —>
REGISTER sip:10.10.10.15 SIP/2.0
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-dyorse6dcklh;rport
From: “Test User” sip:test1@10.10.10.15;tag=4434xh8euy
To: “Test User” sip:test1@10.10.10.15
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4175 REGISTER
Max-Forwards: 70
Contact: sip:test1@192.168.86.18:2048;flow-id=1;q=1.0;+sip.instance="urn:uuid:c32992b8-83b2-427e-a9d6-b2b554e5a1eb"
User-Agent: snom300/7.1.33
Supported: gruu
Allow-Events: dialog
X-Real-IP: 192.168.86.18
Authorization: Digest username=“test1”,realm=“asterisk”,nonce=“56d05fc8”,uri=“sip:10.10.10.15”,response=“dac0b85287c03ae5142232da95a381ca”,algorithm=MD5
Expires: 20
Content-Length: 0

<------------->
— (15 headers 0 lines) —
Sending to 75.75.75.75:15573 (NAT)
[Dec 11 12:59:27] NOTICE[7738]: chan_sip.c:15973 check_auth: Correct auth, but based on stale nonce received from ‘“Test User” sip:test1@10.10.10.15;tag=4434xh8euy’

<— Transmitting (NAT) to 75.75.75.75:15573 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-dyorse6dcklh;received=75.75.75.75;rport=15573
From: “Test User” sip:test1@10.10.10.15;tag=4434xh8euy
To: “Test User” sip:test1@10.10.10.15;tag=as347348c6
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4175 REGISTER
Server: Asterisk PBX 11.0.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce=“066e9b4a”, stale=true
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘3c267026aebe-4bct4hjljgvb’ in 32000 ms (Method: REGISTER)
Reliably Transmitting (NAT) to 75.75.75.75:15573:
OPTIONS sip:test1@192.168.86.18:2048 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.15:5060;branch=z9hG4bK1810e2a8;rport
Max-Forwards: 70
From: “asterisk” sip:test1@10.10.10.15;tag=as65da96e1
To: sip:test1@192.168.86.18:2048
Contact: sip:test1@10.10.10.15:5060
Call-ID: 0d2f715a75e382c66d3099ac59a78cdd@10.10.10.15:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 11.0.0
Date: Tue, 11 Dec 2012 17:59:57 GMT
Session-Expires: 7200
Min-SE: 90
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


<— SIP read from UDP:75.75.75.75:15573 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.10.15:5060;branch=z9hG4bK1810e2a8;rport=5060
From: “asterisk” sip:test1@10.10.10.15;tag=as65da96e1
To: sip:test1@192.168.86.18:2048
Call-ID: 0d2f715a75e382c66d3099ac59a78cdd@10.10.10.15:5060
CSeq: 102 OPTIONS
Contact: sip:test1@192.168.86.18:2048;flow-id=1
User-Agent: snom300/7.1.33
Accept-Language: en
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
Allow-Events: talk, hold, refer, call-info
Supported: timer, 100rel, replaces, from-change
Content-Length: 0

<------------->
— (14 headers 0 lines) —
Really destroying SIP dialog ‘0d2f715a75e382c66d3099ac59a78cdd@10.10.10.15:5060’ Method: OPTIONS
Really destroying SIP dialog ‘3c267026aebe-4bct4hjljgvb’ Method: REGISTER
Really destroying SIP dialog ‘3c267026aebe-4bct4hjljgvb’ Method: REGISTER
<— SIP read from UDP:75.75.75.75:15573 —>
REGISTER sip:10.10.10.15 SIP/2.0
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-53n2coj811xs;rport
From: “Test User” sip:test1@10.10.10.15;tag=trhgxja9ri
To: “Test User” sip:test1@10.10.10.15
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4177 REGISTER
Max-Forwards: 70
Contact: sip:test1@192.168.86.18:2048;flow-id=1;q=1.0;+sip.instance="urn:uuid:c32992b8-83b2-427e-a9d6-b2b554e5a1eb"
User-Agent: snom300/7.1.33
Supported: gruu
Allow-Events: dialog
X-Real-IP: 192.168.86.18
Expires: 20
Content-Length: 0

<------------->
— (14 headers 0 lines) —
Sending to 75.75.75.75:15573 (NAT)

<— Transmitting (NAT) to 75.75.75.75:15573 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-53n2coj811xs;received=75.75.75.75;rport=15573
From: “Test User” sip:test1@10.10.10.15;tag=trhgxja9ri
To: “Test User” sip:test1@10.10.10.15;tag=as3cd96c71
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4177 REGISTER
Server: Asterisk PBX 11.0.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce="4ac4b3a9"
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘3c267026aebe-4bct4hjljgvb’ in 32000 ms (Method: REGISTER)

<— SIP read from UDP:75.75.75.75:15573 —>
REGISTER sip:10.10.10.15 SIP/2.0
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-1d4ipmns99oh;rport
From: “Test User” sip:test1@10.10.10.15;tag=trhgxja9ri
To: “Test User” sip:test1@10.10.10.15
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4178 REGISTER
Max-Forwards: 70
Contact: sip:test1@192.168.86.18:2048;flow-id=1;q=1.0;+sip.instance="urn:uuid:c32992b8-83b2-427e-a9d6-b2b554e5a1eb"
User-Agent: snom300/7.1.33
Supported: gruu
Allow-Events: dialog
X-Real-IP: 192.168.86.18
Authorization: Digest username=“test1”,realm=“asterisk”,nonce=“4ac4b3a9”,uri=“sip:10.10.10.15”,response=“424cb22ce5169bad02c1ed72b6da8214”,algorithm=MD5
Expires: 20
Content-Length: 0

<------------->
— (15 headers 0 lines) —
Sending to 75.75.75.75:15573 (NAT)
– Registered SIP ‘test1’ at 75.75.75.75:15573
Reliably Transmitting (NAT) to 75.75.75.75:15573:
OPTIONS sip:test1@192.168.86.18:2048 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.15:5060;branch=z9hG4bK0372ec5a;rport
Max-Forwards: 70
From: “asterisk” sip:test1@10.10.10.15;tag=as67a38c52
To: sip:test1@192.168.86.18:2048
Contact: sip:test1@10.10.10.15:5060
Call-ID: 10fd80a95edc90d049eceb896501576a@10.10.10.15:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 11.0.0
Date: Tue, 11 Dec 2012 18:00:27 GMT
Session-Expires: 7200
Min-SE: 90
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


<— Transmitting (NAT) to 75.75.75.75:15573 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-1d4ipmns99oh;received=75.75.75.75;rport=15573
From: “Test User” sip:test1@10.10.10.15;tag=trhgxja9ri
To: “Test User” sip:test1@10.10.10.15;tag=as3cd96c71
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4178 REGISTER
Server: Asterisk PBX 11.0.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Expires: 60
Contact: sip:test1@192.168.86.18:2048;expires=60
Date: Tue, 11 Dec 2012 18:00:27 GMT
Content-Length: 0

<------------>
Reliably Transmitting (NAT) to 75.75.75.75:15573:
NOTIFY sip:test1@192.168.86.18:2048 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.15:5060;branch=z9hG4bK6b2cdbcb
Max-Forwards: 70
Route: sip:test1@192.168.86.18:2048
From: “asterisk” sip:asterisk@10.10.10.15;tag=as2b5ec0a2
To: sip:test1@192.168.86.18:2048;tag=9ghy78vxlj
Contact: sip:asterisk@10.10.10.15:5060
Call-ID: 3c2677650cab-6j60q1pclvem
CSeq: 960 NOTIFY
User-Agent: Asterisk PBX 11.0.0
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 93

Messages-Waiting: no
Message-Account: sip:asterisk@10.10.10.15
Voice-Message: 0/0 (0/0)


Scheduling destruction of SIP dialog ‘3c267026aebe-4bct4hjljgvb’ in 32000 ms (Method: REGISTER)

<— SIP read from UDP:75.75.75.75:15573 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.10.15:5060;branch=z9hG4bK0372ec5a;rport=5060
From: “asterisk” sip:test1@10.10.10.15;tag=as67a38c52
To: sip:test1@192.168.86.18:2048
Call-ID: 10fd80a95edc90d049eceb896501576a@10.10.10.15:5060
CSeq: 102 OPTIONS
Contact: sip:test1@192.168.86.18:2048;flow-id=1
User-Agent: snom300/7.1.33
Accept-Language: en
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
Allow-Events: talk, hold, refer, call-info
Supported: timer, 100rel, replaces, from-change
Content-Length: 0

<------------->
— (14 headers 0 lines) —
Really destroying SIP dialog ‘10fd80a95edc90d049eceb896501576a@10.10.10.15:5060’ Method: OPTIONS

<— SIP read from UDP:75.75.75.75:15573 —>
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 10.10.10.15:5060;branch=z9hG4bK6b2cdbcb
From: “asterisk” sip:asterisk@10.10.10.15;tag=as2b5ec0a2
To: sip:test1@192.168.86.18:2048;tag=9ghy78vxlj
Call-ID: 3c2677650cab-6j60q1pclvem
CSeq: 960 NOTIFY
Content-Length: 0

<------------->
— (7 headers 0 lines) —
<— SIP read from UDP:75.75.75.75:15573 —>
REGISTER sip:10.10.10.15 SIP/2.0
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-1evbktoiepw2;rport
From: “Test User” sip:test1@10.10.10.15;tag=htiy6i0wgn
To: “Test User” sip:test1@10.10.10.15
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4179 REGISTER
Max-Forwards: 70
Contact: sip:test1@192.168.86.18:2048;flow-id=1;q=1.0;+sip.instance="urn:uuid:c32992b8-83b2-427e-a9d6-b2b554e5a1eb"
User-Agent: snom300/7.1.33
Supported: gruu
Allow-Events: dialog
X-Real-IP: 192.168.86.18
Expires: 20
Content-Length: 0

<------------->
— (14 headers 0 lines) —
Sending to 75.75.75.75:15573 (NAT)

<— Transmitting (NAT) to 75.75.75.75:15573 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-1evbktoiepw2;received=75.75.75.75;rport=15573
From: “Test User” sip:test1@10.10.10.15;tag=htiy6i0wgn
To: “Test User” sip:test1@10.10.10.15;tag=as7a623395
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4179 REGISTER
Server: Asterisk PBX 11.0.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce="72fb4347"
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘3c267026aebe-4bct4hjljgvb’ in 32000 ms (Method: REGISTER)

<— SIP read from UDP:75.75.75.75:15573 —>
REGISTER sip:10.10.10.15 SIP/2.0
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-hdrqpbc4678j;rport
From: “Test User” sip:test1@10.10.10.15;tag=htiy6i0wgn
To: “Test User” sip:test1@10.10.10.15
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4180 REGISTER
Max-Forwards: 70
Contact: sip:test1@192.168.86.18:2048;flow-id=1;q=1.0;+sip.instance="urn:uuid:c32992b8-83b2-427e-a9d6-b2b554e5a1eb"
User-Agent: snom300/7.1.33
Supported: gruu
Allow-Events: dialog
X-Real-IP: 192.168.86.18
Authorization: Digest username=“test1”,realm=“asterisk”,nonce=“72fb4347”,uri=“sip:10.10.10.15”,response=“88b54b4cd3190d473bb5c936fd8dea13”,algorithm=MD5
Expires: 20
Content-Length: 0

<------------->
— (15 headers 0 lines) —
Sending to 75.75.75.75:15573 (NAT)
[Dec 11 13:00:57] NOTICE[7738]: chan_sip.c:15973 check_auth: Correct auth, but based on stale nonce received from ‘“Test User” sip:test1@10.10.10.15;tag=htiy6i0wgn’

<— Transmitting (NAT) to 75.75.75.75:15573 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-hdrqpbc4678j;received=75.75.75.75;rport=15573
From: “Test User” sip:test1@10.10.10.15;tag=htiy6i0wgn
To: “Test User” sip:test1@10.10.10.15;tag=as3cd96c71
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4180 REGISTER
Server: Asterisk PBX 11.0.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce=“14e45b89”, stale=true
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘3c267026aebe-4bct4hjljgvb’ in 32000 ms (Method: REGISTER)


<— SIP read from UDP:75.75.75.75:15573 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.10.15:5060;branch=z9hG4bK108f642d;rport=5060
From: “asterisk” sip:test1@10.10.10.15;tag=as3c3cbb8f
To: sip:test1@192.168.86.18:2048
Call-ID: 75398baf48d62bad3196344c0cb187e5@10.10.10.15:5060
CSeq: 102 OPTIONS
Contact: sip:test1@192.168.86.18:2048;flow-id=1
User-Agent: snom300/7.1.33
Accept-Language: en
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
Allow-Events: talk, hold, refer, call-info
Supported: timer, 100rel, replaces, from-change
Content-Length: 0

<------------->
— (14 headers 0 lines) —
Really destroying SIP dialog ‘75398baf48d62bad3196344c0cb187e5@10.10.10.15:5060’ Method: OPTIONS
Really destroying SIP dialog ‘3c267026aebe-4bct4hjljgvb’ Method: REGISTER
Really destroying SIP dialog ‘3c267026aebe-4bct4hjljgvb’ Method: REGISTER

<— SIP read from UDP:75.75.75.75:15573 —>
REGISTER sip:10.10.10.15 SIP/2.0
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-w03wlqy47vvh;rport
From: “Test User” sip:test1@10.10.10.15;tag=6ygqsrb1pd
To: “Test User” sip:test1@10.10.10.15
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4182 REGISTER
Max-Forwards: 70
Contact: sip:test1@192.168.86.18:2048;flow-id=1;q=1.0;+sip.instance="urn:uuid:c32992b8-83b2-427e-a9d6-b2b554e5a1eb"
User-Agent: snom300/7.1.33
Supported: gruu
Allow-Events: dialog
X-Real-IP: 192.168.86.18
Expires: 20
Content-Length: 0

<------------->
— (14 headers 0 lines) —
Sending to 75.75.75.75:15573 (NAT)

<— Transmitting (NAT) to 75.75.75.75:15573 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-w03wlqy47vvh;received=75.75.75.75;rport=15573
From: “Test User” sip:test1@10.10.10.15;tag=6ygqsrb1pd
To: “Test User” sip:test1@10.10.10.15;tag=as58bdc3a5
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4182 REGISTER
Server: Asterisk PBX 11.0.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce="75eb6e28"
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘3c267026aebe-4bct4hjljgvb’ in 32000 ms (Method: REGISTER)

<— SIP read from UDP:75.75.75.75:15573 —>
REGISTER sip:10.10.10.15 SIP/2.0
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-nexg7ucsxsxn;rport
From: “Test User” sip:test1@10.10.10.15;tag=6ygqsrb1pd
To: “Test User” sip:test1@10.10.10.15
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4183 REGISTER
Max-Forwards: 70
Contact: sip:test1@192.168.86.18:2048;flow-id=1;q=1.0;+sip.instance="urn:uuid:c32992b8-83b2-427e-a9d6-b2b554e5a1eb"
User-Agent: snom300/7.1.33
Supported: gruu
Allow-Events: dialog
X-Real-IP: 192.168.86.18
Authorization: Digest username=“test1”,realm=“asterisk”,nonce=“75eb6e28”,uri=“sip:10.10.10.15”,response=“75e8f83628e6f64e45e00f68dba35c46”,algorithm=MD5
Expires: 20
Content-Length: 0

<------------->
— (15 headers 0 lines) —
Sending to 75.75.75.75:15573 (NAT)
– Registered SIP ‘test1’ at 75.75.75.75:15573
Reliably Transmitting (NAT) to 75.75.75.75:15573:
OPTIONS sip:test1@192.168.86.18:2048 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.15:5060;branch=z9hG4bK0436e586;rport
Max-Forwards: 70
From: “asterisk” sip:test1@10.10.10.15;tag=as14a54148
To: sip:test1@192.168.86.18:2048
Contact: sip:test1@10.10.10.15:5060
Call-ID: 0f36353336eb03ba05e9df844e064381@10.10.10.15:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 11.0.0
Date: Tue, 11 Dec 2012 18:01:58 GMT
Session-Expires: 7200
Min-SE: 90
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


<— Transmitting (NAT) to 75.75.75.75:15573 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.86.18:2048;branch=z9hG4bK-nexg7ucsxsxn;received=75.75.75.75;rport=15573
From: “Test User” sip:test1@10.10.10.15;tag=6ygqsrb1pd
To: “Test User” sip:test1@10.10.10.15;tag=as58bdc3a5
Call-ID: 3c267026aebe-4bct4hjljgvb
CSeq: 4183 REGISTER
Server: Asterisk PBX 11.0.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Expires: 60
Contact: sip:test1@192.168.86.18:2048;expires=60
Date: Tue, 11 Dec 2012 18:01:58 GMT
Content-Length: 0

<------------>
Reliably Transmitting (NAT) to 75.75.75.75:15573:
NOTIFY sip:test1@192.168.86.18:2048 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.15:5060;branch=z9hG4bK6b2cdbcb
Max-Forwards: 70
Route: sip:test1@192.168.86.18:2048
From: “asterisk” sip:asterisk@10.10.10.15;tag=as2b5ec0a2
To: sip:test1@192.168.86.18:2048;tag=9ghy78vxlj
Contact: sip:asterisk@10.10.10.15:5060
Call-ID: 3c2677650cab-6j60q1pclvem
CSeq: 961 NOTIFY
User-Agent: Asterisk PBX 11.0.0
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 93

Messages-Waiting: no
Message-Account: sip:asterisk@10.10.10.15
Voice-Message: 0/0 (0/0)


Scheduling destruction of SIP dialog ‘3c267026aebe-4bct4hjljgvb’ in 32000 ms (Method: REGISTER)[/size]

It appears that the problem was that Asterisk 11 wasn’t compatible with the older firmware for the SNOM 300 phones we were using. After upgrading from 7.1.3 to 7.3.30, the problem was resolved. Version 8.X.X also seem to work fine.