Unreachable

bruestle · December 16, 2012, 6:44am

I’ve just moved my Asterisk/FreePBX server out into the cloud and am having trouble getting my Yealink phones to work. They can call out, but can;t be called. My Bria softphones are working fine.

I suspect, even though the phone think they are registered, that they aren’t. When I enable one of my softphones, I get the messages:

[2012-12-16 01:38:11] VERBOSE[2472] chan_sip.c: – Registered SIP ‘303’ at 192.0.0.89:54288
[2012-12-16 01:38:11] VERBOSE[2472] chan_sip.c: – Unregistered SIP ‘303’
[2012-12-16 01:38:11] VERBOSE[2472] chan_sip.c: – Registered SIP ‘303’ at 71.245.122.112:54288

…and the phone works just fine. When I enable one of the Yealink phones, I get:

[2012-12-16 01:39:51] VERBOSE[2472] chan_sip.c: – Registered SIP ‘302’ at 192.0.0.20:5062
[2012-12-16 01:39:55] NOTICE[2472] chan_sip.c: Peer ‘302’ is now UNREACHABLE! Last qualify: 0

So why would my Yealink be unreachable? COuld it have something to do with the very diffreent port numbers? I have the Yealink’s SIP port set to 5060. Why is 5063 showing up?

Any advice would be appreciated.

John

david55 · December 16, 2012, 10:07am

I would worry about the rapid change n registration between two different sub-networks, even if the phone is working.

To see what is going on with the second phne, you need to provide a SIP protocol trace (sip set debug on).

Don’t expect good audio quality when running VoIP on a virtual machine that you don’t control.

bruestle · December 18, 2012, 6:13am

Thanks for the advice. I turned on the sip debugging and got a whole bunch recorded, with the culminating in the line “Peer ‘302’ is now UNREACHABLE!”. This is only happening on the hardware phones (Yealink). The Bria softphones connect without issue. Any advice would be appreciated.

John

<------------>
[2012-12-18 01:06:19] VERBOSE[2472] chan_sip.c: Scheduling destruction of SIP dialog ‘4861c687-03a14ec7-a031a04@216.115.69.131’ in 32000 ms (Method: OPTIONS)
[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c:
<— SIP read from UDP:71.245.122.112:5062 —>
REGISTER sip:199.38.181.198 SIP/2.0
Via: SIP/2.0/UDP 192.0.0.20:5062;branch=z9hG4bK2061998131
From: “302” sip:302@199.38.181.198;tag=1829820468
To: “302” sip:302@199.38.181.198
Call-ID: 66434160@192.0.0.20
CSeq: 1 REGISTER
Contact: sip:302@192.0.0.20:5062
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.61.0.83
Expires: 3600
Content-Length: 0

<------------->
[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c: — (12 headers 0 lines) —
[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c: Sending to 71.245.122.112:5062 (NAT)
[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c:
<— Transmitting (no NAT) to 71.245.122.112:5062 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.0.0.20:5062;branch=z9hG4bK2061998131;received=71.245.122.112
From: “302” sip:302@199.38.181.198;tag=1829820468
To: “302” sip:302@199.38.181.198;tag=as63105f2d
Call-ID: 66434160@192.0.0.20
CSeq: 1 REGISTER
Server: FPBX-2.10.1(1.8.16.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce="0fdd8218"
Content-Length: 0

<------------>
[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c: Scheduling destruction of SIP dialog ‘66434160@192.0.0.20’ in 32000 ms (Method: REGISTER)
[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c:
<— SIP read from UDP:71.245.122.112:5062 —>
REGISTER sip:199.38.181.198 SIP/2.0
Via: SIP/2.0/UDP 192.0.0.20:5062;branch=z9hG4bK1421300169
From: “302” sip:302@199.38.181.198;tag=1829820468
To: “302” sip:302@199.38.181.198
Call-ID: 66434160@192.0.0.20
CSeq: 2 REGISTER
Contact: sip:302@192.0.0.20:5062
Authorization: Digest username=“302”, realm=“asterisk”, nonce=“0fdd8218”, uri=“sip:199.38.181.198”, response=“ad8208ba90bb3794903a3c2e3c5cf7a1”, algorithm=MD5
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.61.0.83
Expires: 3600
Content-Length: 0

<------------->
[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c: — (13 headers 0 lines) —
[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c: Sending to 71.245.122.112:5062 (no NAT)
[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c: – Registered SIP ‘302’ at 192.0.0.20:5062
[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c: Reliably Transmitting (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK22f5351a
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as77a03cce
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 463382ca0c19ba664c235c815c88c297@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:20 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c:
<— Transmitting (no NAT) to 71.245.122.112:5062 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.0.0.20:5062;branch=z9hG4bK1421300169;received=71.245.122.112
From: “302” sip:302@199.38.181.198;tag=1829820468
To: “302” sip:302@199.38.181.198;tag=as63105f2d
Call-ID: 66434160@192.0.0.20
CSeq: 2 REGISTER
Server: FPBX-2.10.1(1.8.16.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Expires: 3600
Contact: sip:302@192.0.0.20:5062;expires=3600
Date: Tue, 18 Dec 2012 06:06:20 GMT
Content-Length: 0

<------------>
[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c: Scheduling destruction of SIP dialog ‘0c0305e575fbcca03d27291c08beb235@199.38.181.198:5060’ in 32000 ms (Method: NOTIFY)
[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c: Reliably Transmitting (no NAT) to 192.0.0.20:5062:
NOTIFY sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK602a5e85
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as7641e983
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 0c0305e575fbcca03d27291c08beb235@199.38.181.198:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-2.10.1(1.8.16.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 89

Messages-Waiting: no
Message-Account: sip:*97@199.38.181.198
Voice-Message: 0/0 (0/0)

[2012-12-18 01:06:20] VERBOSE[2472] chan_sip.c: Scheduling destruction of SIP dialog ‘66434160@192.0.0.20’ in 32000 ms (Method: REGISTER)
[2012-12-18 01:06:21] VERBOSE[2472] chan_sip.c: Retransmitting #1 (no NAT) to 192.0.0.20:5062:
NOTIFY sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK602a5e85
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as7641e983
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 0c0305e575fbcca03d27291c08beb235@199.38.181.198:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-2.10.1(1.8.16.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 89

Messages-Waiting: no
Message-Account: sip:*97@199.38.181.198
Voice-Message: 0/0 (0/0)

[2012-12-18 01:06:21] VERBOSE[2472] chan_sip.c: Retransmitting #1 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK22f5351a
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as77a03cce
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 463382ca0c19ba664c235c815c88c297@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:20 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:22] VERBOSE[2472] chan_sip.c: Retransmitting #2 (no NAT) to 192.0.0.20:5062:
NOTIFY sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK602a5e85
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as7641e983
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 0c0305e575fbcca03d27291c08beb235@199.38.181.198:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-2.10.1(1.8.16.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 89

Messages-Waiting: no
Message-Account: sip:*97@199.38.181.198
Voice-Message: 0/0 (0/0)

[2012-12-18 01:06:22] VERBOSE[2472] chan_sip.c: Retransmitting #2 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK22f5351a
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as77a03cce
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 463382ca0c19ba664c235c815c88c297@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:20 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:23] VERBOSE[2472] chan_sip.c: Retransmitting #3 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK22f5351a
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as77a03cce
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 463382ca0c19ba664c235c815c88c297@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:20 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:23] VERBOSE[2472] chan_sip.c: Really destroying SIP dialog ‘757548984@192.0.0.20’ Method: REGISTER
[2012-12-18 01:06:24] VERBOSE[2472] chan_sip.c: Retransmitting #3 (no NAT) to 192.0.0.20:5062:
NOTIFY sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK602a5e85
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as7641e983
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 0c0305e575fbcca03d27291c08beb235@199.38.181.198:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-2.10.1(1.8.16.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 89

Messages-Waiting: no
Message-Account: sip:*97@199.38.181.198
Voice-Message: 0/0 (0/0)

[2012-12-18 01:06:24] VERBOSE[2472] chan_sip.c: Retransmitting #4 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK22f5351a
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as77a03cce
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 463382ca0c19ba664c235c815c88c297@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:20 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:24] NOTICE[2472] chan_sip.c: Peer ‘302’ is now UNREACHABLE! Last qualify: 0
[2012-12-18 01:06:24] VERBOSE[2472] chan_sip.c: Really destroying SIP dialog ‘463382ca0c19ba664c235c815c88c297@199.38.181.198:5060’ Method: OPTIONS
[2012-12-18 01:06:28] VERBOSE[2472] chan_sip.c: Retransmitting #4 (no NAT) to 192.0.0.20:5062:
NOTIFY sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK602a5e85
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as7641e983
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 0c0305e575fbcca03d27291c08beb235@199.38.181.198:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-2.10.1(1.8.16.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 89

Messages-Waiting: no
Message-Account: sip:*97@199.38.181.198
Voice-Message: 0/0 (0/0)

[2012-12-18 01:06:29] VERBOSE[2472] chan_sip.c: Really destroying SIP dialog ‘074200785b20aa3d5188372056ec777f@199.38.181.198’ Method: REGISTER
[2012-12-18 01:06:32] VERBOSE[2472] chan_sip.c: Retransmitting #5 (no NAT) to 192.0.0.20:5062:
NOTIFY sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK602a5e85
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as7641e983
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 0c0305e575fbcca03d27291c08beb235@199.38.181.198:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-2.10.1(1.8.16.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 89

Messages-Waiting: no
Message-Account: sip:*97@199.38.181.198
Voice-Message: 0/0 (0/0)

[2012-12-18 01:06:33] VERBOSE[2472] chan_sip.c:
<— SIP read from UDP:216.115.69.144:5060 —>
OPTIONS sip:199.38.181.198:5060 SIP/2.0
Max-Forwards: 10
Record-Route: sip:216.115.69.144;lr
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK3a61.1a3bb2c5526763a3723117e7bf90c0c8.0
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Route: sip:216.115.69.144;lr;received="sip:199.38.181.198:5060"
From: sip:ping@invalid;tag=2303e039
To: sip:199.38.181.198:5060
Call-ID: 67955571-9bfc5fa9-a5550b4@70.167.153.136
CSeq: 1 OPTIONS
Content-Length: 0

<------------->
[2012-12-18 01:06:33] VERBOSE[2472] chan_sip.c: — (11 headers 0 lines) —
[2012-12-18 01:06:33] VERBOSE[2472] chan_sip.c: Looking for s in from-sip-external (domain 199.38.181.198)
[2012-12-18 01:06:33] VERBOSE[2472] chan_sip.c:
<— Transmitting (NAT) to 216.115.69.144:5060 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK3a61.1a3bb2c5526763a3723117e7bf90c0c8.0;received=216.115.69.144;rport=5060
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Record-Route: sip:216.115.69.144;lr
From: sip:ping@invalid;tag=2303e039
To: sip:199.38.181.198:5060;tag=as58e82f4b
Call-ID: 67955571-9bfc5fa9-a5550b4@70.167.153.136
CSeq: 1 OPTIONS
Server: FPBX-2.10.1(1.8.16.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: sip:199.38.181.198:5060
Accept: application/sdp
Content-Length: 0

<------------>
[2012-12-18 01:06:33] VERBOSE[2472] chan_sip.c: Scheduling destruction of SIP dialog ‘67955571-9bfc5fa9-a5550b4@70.167.153.136’ in 32000 ms (Method: OPTIONS)
[2012-12-18 01:06:34] VERBOSE[2472] chan_sip.c: Reliably Transmitting (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK2a7a2058
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as095215e3
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 08063325241acfcc4980cc643135e9d2@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:35] VERBOSE[2472] chan_sip.c: Retransmitting #1 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK2a7a2058
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as095215e3
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 08063325241acfcc4980cc643135e9d2@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:36] VERBOSE[2472] chan_sip.c: Retransmitting #6 (no NAT) to 192.0.0.20:5062:
NOTIFY sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK602a5e85
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as7641e983
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 0c0305e575fbcca03d27291c08beb235@199.38.181.198:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-2.10.1(1.8.16.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 89

Messages-Waiting: no
Message-Account: sip:*97@199.38.181.198
Voice-Message: 0/0 (0/0)

[2012-12-18 01:06:36] VERBOSE[2472] chan_sip.c: Retransmitting #2 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK2a7a2058
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as095215e3
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 08063325241acfcc4980cc643135e9d2@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:37] VERBOSE[2472] chan_sip.c: Retransmitting #3 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK2a7a2058
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as095215e3
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 08063325241acfcc4980cc643135e9d2@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:38] VERBOSE[2472] chan_sip.c: Retransmitting #4 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK2a7a2058
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as095215e3
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 08063325241acfcc4980cc643135e9d2@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:38] VERBOSE[2472] chan_sip.c: Really destroying SIP dialog ‘08063325241acfcc4980cc643135e9d2@199.38.181.198:5060’ Method: OPTIONS
[2012-12-18 01:06:40] VERBOSE[2472] chan_sip.c: Retransmitting #7 (no NAT) to 192.0.0.20:5062:
NOTIFY sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK602a5e85
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as7641e983
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 0c0305e575fbcca03d27291c08beb235@199.38.181.198:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-2.10.1(1.8.16.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 89

Messages-Waiting: no
Message-Account: sip:*97@199.38.181.198
Voice-Message: 0/0 (0/0)

[2012-12-18 01:06:44] VERBOSE[2472] chan_sip.c: Retransmitting #8 (no NAT) to 192.0.0.20:5062:
NOTIFY sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK602a5e85
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as7641e983
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 0c0305e575fbcca03d27291c08beb235@199.38.181.198:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-2.10.1(1.8.16.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 89

Messages-Waiting: no
Message-Account: sip:*97@199.38.181.198
Voice-Message: 0/0 (0/0)

[2012-12-18 01:06:48] VERBOSE[2472] chan_sip.c: Retransmitting #9 (no NAT) to 192.0.0.20:5062:
NOTIFY sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK602a5e85
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as7641e983
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 0c0305e575fbcca03d27291c08beb235@199.38.181.198:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-2.10.1(1.8.16.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 89

Messages-Waiting: no
Message-Account: sip:*97@199.38.181.198
Voice-Message: 0/0 (0/0)

[2012-12-18 01:06:48] VERBOSE[2472] chan_sip.c: Reliably Transmitting (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK2c344b88
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as582c3675
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 5b9f7ede655d969953282cbf3db29804@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:48 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:49] VERBOSE[2472] chan_sip.c: Retransmitting #1 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK2c344b88
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as582c3675
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 5b9f7ede655d969953282cbf3db29804@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:48 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:50] VERBOSE[2472] chan_sip.c: Retransmitting #2 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK2c344b88
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as582c3675
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 5b9f7ede655d969953282cbf3db29804@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:48 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:50] VERBOSE[2472] chan_sip.c:
<— SIP read from UDP:71.245.122.112:5062 —>

<------------->
[2012-12-18 01:06:51] VERBOSE[2472] chan_sip.c: Really destroying SIP dialog ‘4861c687-03a14ec7-a031a04@216.115.69.131’ Method: OPTIONS
[2012-12-18 01:06:51] VERBOSE[2472] chan_sip.c: Retransmitting #3 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK2c344b88
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as582c3675
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 5b9f7ede655d969953282cbf3db29804@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:48 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:52] VERBOSE[2472] chan_sip.c: Retransmitting #10 (no NAT) to 192.0.0.20:5062:
NOTIFY sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK602a5e85
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as7641e983
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 0c0305e575fbcca03d27291c08beb235@199.38.181.198:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-2.10.1(1.8.16.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 89

Messages-Waiting: no
Message-Account: sip:*97@199.38.181.198
Voice-Message: 0/0 (0/0)

[2012-12-18 01:06:52] VERBOSE[2472] chan_sip.c: Retransmitting #4 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK2c344b88
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as582c3675
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 5b9f7ede655d969953282cbf3db29804@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:06:48 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:06:52] VERBOSE[2472] chan_sip.c: Really destroying SIP dialog ‘5b9f7ede655d969953282cbf3db29804@199.38.181.198:5060’ Method: OPTIONS
[2012-12-18 01:06:52] VERBOSE[2472] chan_sip.c: Really destroying SIP dialog ‘66434160@192.0.0.20’ Method: REGISTER
[2012-12-18 01:06:52] WARNING[2472] chan_sip.c: Retransmission timeout reached on transmission 0c0305e575fbcca03d27291c08beb235@199.38.181.198:5060 for seqno 102 (Non-critical Request) – See wiki.asterisk.org/wiki/display/ … nsmissions
Packet timed out after 32000ms with no response
[2012-12-18 01:07:02] VERBOSE[2472] chan_sip.c: Reliably Transmitting (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK2dec6148
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as300478ea
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 523f1c1628999af80f3f218d283b0a59@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:07:02 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:07:03] VERBOSE[2472] chan_sip.c: Retransmitting #1 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK2dec6148
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as300478ea
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 523f1c1628999af80f3f218d283b0a59@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:07:02 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

[2012-12-18 01:07:04] VERBOSE[2472] chan_sip.c: Retransmitting #2 (no NAT) to 192.0.0.20:5062:
OPTIONS sip:302@192.0.0.20:5062 SIP/2.0
Via: SIP/2.0/UDP 199.38.181.198:5060;branch=z9hG4bK2dec6148
Max-Forwards: 70
From: “Unknown” sip:Unknown@199.38.181.198;tag=as300478ea
To: sip:302@192.0.0.20:5062
Contact: sip:Unknown@199.38.181.198:5060
Call-ID: 523f1c1628999af80f3f218d283b0a59@199.38.181.198:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.10.1(1.8.16.0)
Date: Tue, 18 Dec 2012 06:07:02 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

david55 · December 18, 2012, 8:05am

Something is broken in 192.0.0.20’s handling of the OPTION packets, used to implement qualify. It should respond, even if only to reject the request. Asterisk doesn’t require an OK to consider the link up; it just requires a response.

If this just affects OPTIONS, you should disable qualify for that peer. However, if it means that packets are being lost inbound or outbound, you need ot investigate your network, particularly looking for SIP aware proxies.

dejanst · December 18, 2012, 10:27am

If I understand correctly, the Asterisk server is on public IP address and the hardware phone is behind a NAT router. Is that correct or not?

If that is correct, than you have improperly set local network. 192.0.0.20 is a public IP address, not a private one. And I have a hunch that the LAN network of your NAT router is set to 192.0.0.0/24.

If my assumptions are correct, your problem might be solved with one of those propositions:

use STUN server on your hardphone
use nat=yes in the sip.conf settings

bruestle · December 22, 2012, 5:19am

Thanks everybody for your help. I did resolve the problem by changing the Asterisk extension setting “NAT” to “Yes”. My Yealink phones are now working. It is curious that the Bria softphone didn’t need the setting, but I’m guessing it is a little more sophisticated about find usable ports.

John

david55 · December 22, 2012, 11:17am

nat= should only be needed when Asterisk is outside a broken NAT environment. Looks like one phone had a better NAT implementation.

Note that nat=yes no longer works in the latest Asterisk. You must specify the particular NAT work rounds needed in place of the “yes”.