Status Xlite register tapi di sip show peers unracable

MUSTAFA_TAMBUNAN · June 22, 2015, 6:33am

Pak Anton,

Saya sedikit menemui kejanggalan pada saat register xlite ke server asterisk. di screen xlite berhasil register (Your username : 4071) tapi di sip show peer statusnya unracable. Ketika dilakukan call out bisa tapi call ke ex 4017 tidak bisa.Bisa di bantu trace penyebab issue ini?

Terlampir hasil tcpdump

[enter link description here][1]

http://202.52.48.81/tcpdump_backup.cap

Thanks

anton · June 22, 2015, 6:38am

Q: kenapa tidak bisa ditelepon ?
A: karena statusnya unreachable

Q: kenapa kalo unreachable call out bisa ?
A: by default memang bisa, asterisk tidak benar2 memeriksa status nya, namun paket nya, dalam paket nya terdapat data username dan password yang benar sehingga callout bisa

sip register dan sip invite bisa dibilang 2 kegiatan berbeda yang kadang2 tdk ada hubungannya, bisa karena banyak hal misalnya race condition (balapan antara waktu tunggu timeout dan waktu tunggu update)

cek paket nya dalam sip debug untuk tahu kenapa unreachable

anton

MUSTAFA_TAMBUNAN · June 22, 2015, 8:13am

Nah, justru yang bagian “cek paket nya dalam sip debug” saya kurang paham…haha…ada trink tuk new-bie?

Thanks

anton · June 22, 2015, 8:26am

Maksud saya sih bapak dapetin aja dulu sip debug log nya, nanti kita bahas sama2

Anton

MUSTAFA_TAMBUNAN · June 22, 2015, 8:43am

Pak Anton,

Bukankah hasil tcpdump yang saya lampirkan tidak cukup pak

command saya begini

tcpdump -i eth0 -s0 -vvv -c 500000 -w pcap1.cap

ada command line so dapat semua sip debugnya?

Thanks

anton · June 22, 2015, 10:01am

Malas periksa nya

Anton

MUSTAFA_TAMBUNAN · June 22, 2015, 10:18am

Ahh…bapak minta hasil sip debug, di file tcpdump sudah terlampir. skarang bapak bilang malas:D

OK deh kalau begitu…di close aja:)

Thanks

anton · June 22, 2015, 10:27am

ngambek pak ? jangan dong pak, karena situ salah pahami maksud saya

sip debug:

pastikan logger menulis full log

aktifkan sip debug

asterisk -rx "sip set debug ip x.x.x.x"

lakukan 1 kali test panggilan yang gagal
kirim log nya kesini

atau bisa juga dengan ngrep di server nya, lengkap nya disini:

http://antonraharja.com/2013/07/06/duh-kok-ga-konek-nih/

demikian asterisk sip debug yang dimaksud. saya malas baca cap.

anton

MASTERING_VOIP · June 24, 2015, 6:06am

Sorry Pak, baru ada waktu masuk ke server client

He, saya tidak ngambek loh pak:D

Berikut hasil sip set debugnya

ipbxdrc*CLI> sip set debug ip 10.22.205.81
SIP Debugging Enabled for IP: 10.22.205.81
Retransmitting #9 (NAT) to 10.22.205.81:29472:
NOTIFY sip:4071@10.22.205.81:29472;rinstance=ebc211a501829a14 SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK353e3dea;rport
Max-Forwards: 70
From: “asterisk” sip:asterisk@10.22.88.117;tag=as00fcf73d
To: sip:4071@10.22.205.81:29472;rinstance=ebc211a501829a14
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: 76f3a42f775458826177e65d6c300623@10.22.88.117:5060
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 92

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

Retransmitting #9 (NAT) to 10.22.205.81:29472:
NOTIFY sip:4071@10.22.205.81:29472 SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK4c370d3e;rport
Max-Forwards: 70
Route: sip:4071@10.22.205.81:29472
From: “asterisk” sip:asterisk@10.22.88.117;tag=as0f906b7f
To: sip:4071@10.22.205.81:29472;tag=4c13af3e
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: NTUxZTQ3YzFiNGU2YThmZjY1NTkxYWVjMjE5ODZjZGQ.
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 92

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

Retransmitting #10 (NAT) to 10.22.205.81:29472:
NOTIFY sip:4071@10.22.205.81:29472;rinstance=ebc211a501829a14 SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK353e3dea;rport
Max-Forwards: 70
From: “asterisk” sip:asterisk@10.22.88.117;tag=as00fcf73d
To: sip:4071@10.22.205.81:29472;rinstance=ebc211a501829a14
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: 76f3a42f775458826177e65d6c300623@10.22.88.117:5060
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 92

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

Retransmitting #10 (NAT) to 10.22.205.81:29472:
NOTIFY sip:4071@10.22.205.81:29472 SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK4c370d3e;rport
Max-Forwards: 70
Route: sip:4071@10.22.205.81:29472
From: “asterisk” sip:asterisk@10.22.88.117;tag=as0f906b7f
To: sip:4071@10.22.205.81:29472;tag=4c13af3e
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: NTUxZTQ3YzFiNGU2YThmZjY1NTkxYWVjMjE5ODZjZGQ.
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 92

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

Really destroying SIP dialog ‘NTUxZTQ3YzFiNGU2YThmZjY1NTkxYWVjMjE5ODZjZGQ.’ Method: SUBSCRIBE
Really destroying SIP dialog ‘ODRmZDRjNmQ0YWNiMmE4NDgwMGYxODZmYmE3YjcwM2Q.’ Method: REGISTER

<— SIP read from UDP:10.22.205.81:17862 —>
REGISTER sip:10.22.88.117 SIP/2.0
Via: SIP/2.0/UDP 10.22.205.81:17862;branch=z9hG4bK-d87543-fc2c6e5b5e3bbf79-1–d87543-;rport
Max-Forwards: 70
Contact: sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec
To: "4071"sip:4071@10.22.88.117
From: "4071"sip:4071@10.22.88.117;tag=89767a3f
Call-ID: MWEyMDBiZDFlYmFjOWFiNDJhYTJlMzE0OTRmNzZmNWM.
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
User-Agent: X-Lite release 1006e stamp 34025
Content-Length: 0

<------------->
— (12 headers 0 lines) —
Sending to 10.22.205.81:17862 (NAT)

<— Transmitting (NAT) to 10.22.205.81:17862 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.22.205.81:17862;branch=z9hG4bK-d87543-fc2c6e5b5e3bbf79-1–d87543-;received=10.22.205.81;rport=17862
From: "4071"sip:4071@10.22.88.117;tag=89767a3f
To: "4071"sip:4071@10.22.88.117;tag=as325895c1
Call-ID: MWEyMDBiZDFlYmFjOWFiNDJhYTJlMzE0OTRmNzZmNWM.
CSeq: 1 REGISTER
Server: Asterisk PBX 1.8.26.1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“10.22.88.117”, nonce="14639e55"
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘MWEyMDBiZDFlYmFjOWFiNDJhYTJlMzE0OTRmNzZmNWM.’ in 32000 ms (Method: REGISTER)

<— SIP read from UDP:10.22.205.81:17862 —>
REGISTER sip:10.22.88.117 SIP/2.0
Via: SIP/2.0/UDP 10.22.205.81:17862;branch=z9hG4bK-d87543-876ab251d520285a-1–d87543-;rport
Max-Forwards: 70
Contact: sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec
To: "4071"sip:4071@10.22.88.117
From: "4071"sip:4071@10.22.88.117;tag=89767a3f
Call-ID: MWEyMDBiZDFlYmFjOWFiNDJhYTJlMzE0OTRmNzZmNWM.
CSeq: 2 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
User-Agent: X-Lite release 1006e stamp 34025
Authorization: Digest username=“4071”,realm=“10.22.88.117”,nonce=“14639e55”,uri=“sip:10.22.88.117”,response=“db532af3066915f6ac7d0d6cb8e8a949”,algorithm=MD5
Content-Length: 0

<------------->
— (13 headers 0 lines) —
Sending to 10.22.205.81:17862 (NAT)
– Registered SIP ‘4071’ at 10.22.205.81:17862
Reliably Transmitting (NAT) to 10.22.205.81:17862:
OPTIONS sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK223090cb;rport
Max-Forwards: 70
From: “asterisk” sip:asterisk@10.22.88.117;tag=as0e7009ce
To: sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: 483e8c1c4663569849b62da044b5c157@10.22.88.117:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 1.8.26.1
Date: Wed, 24 Jun 2015 06:01:50 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

<— Transmitting (NAT) to 10.22.205.81:17862 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.22.205.81:17862;branch=z9hG4bK-d87543-876ab251d520285a-1–d87543-;received=10.22.205.81;rport=17862
From: "4071"sip:4071@10.22.88.117;tag=89767a3f
To: "4071"sip:4071@10.22.88.117;tag=as325895c1
Call-ID: MWEyMDBiZDFlYmFjOWFiNDJhYTJlMzE0OTRmNzZmNWM.
CSeq: 2 REGISTER
Server: Asterisk PBX 1.8.26.1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Expires: 3600
Contact: sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec;expires=3600
Date: Wed, 24 Jun 2015 06:01:50 GMT
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘6ea7c7c610eba4325638e33310bea6a8@10.22.88.117:5060’ in 32000 ms (Method: NOTIFY)
Reliably Transmitting (NAT) to 10.22.205.81:17862:
NOTIFY sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK263a0dea;rport
Max-Forwards: 70
From: “asterisk” sip:asterisk@10.22.88.117;tag=as1cb708e6
To: sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: 6ea7c7c610eba4325638e33310bea6a8@10.22.88.117:5060
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
ontent-Type: application/simple-message-summary
Content-Length: 92

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

Scheduling destruction of SIP dialog ‘MWEyMDBiZDFlYmFjOWFiNDJhYTJlMzE0OTRmNzZmNWM.’ in 32000 ms (Method: REGISTER)

<— SIP read from UDP:10.22.205.81:17862 —>
SUBSCRIBE sip:4071@10.22.88.117 SIP/2.0
Via: SIP/2.0/UDP 10.22.205.81:17862;branch=z9hG4bK-d87543-9159dc2eff46bf4d-1–d87543-;rport
Max-Forwards: 70
Contact: sip:4071@10.22.205.81:17862
To: "4071"sip:4071@10.22.88.117
From: "4071"sip:4071@10.22.88.117;tag=2d003a7a
Call-ID: MGQzNDhiNWFiMmU5YzU1ZDFiNGQzZWI5Y2Q0ZDhmNjI.
CSeq: 1 SUBSCRIBE
Expires: 300
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
User-Agent: X-Lite release 1006e stamp 34025
Event: message-summary
Content-Length: 0

<------------->
— (13 headers 0 lines) —
Creating new subscription
Sending to 10.22.205.81:17862 (NAT)
list_route: hop: sip:4071@10.22.205.81:17862
Found peer ‘4071’ for ‘4071’ from 10.22.205.81:17862

<— Transmitting (NAT) to 10.22.205.81:17862 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.22.205.81:17862;branch=z9hG4bK-d87543-9159dc2eff46bf4d-1–d87543-;received=10.22.205.81;rport=17862
From: "4071"sip:4071@10.22.88.117;tag=2d003a7a
To: "4071"sip:4071@10.22.88.117;tag=as2d7545fb
Call-ID: MGQzNDhiNWFiMmU5YzU1ZDFiNGQzZWI5Y2Q0ZDhmNjI.
CSeq: 1 SUBSCRIBE
Server: Asterisk PBX 1.8.26.1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“10.22.88.117”, nonce="207334b5"
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘MGQzNDhiNWFiMmU5YzU1ZDFiNGQzZWI5Y2Q0ZDhmNjI.’ in 32000 ms (Method: SUBSCRIBE)

<— SIP read from UDP:10.22.205.81:17862 —>
SUBSCRIBE sip:4071@10.22.88.117 SIP/2.0
Via: SIP/2.0/UDP 10.22.205.81:17862;branch=z9hG4bK-d87543-2540b5158b7cde74-1–d87543-;rport
Max-Forwards: 70
Contact: sip:4071@10.22.205.81:17862
To: "4071"sip:4071@10.22.88.117
From: “4071"sip:4071@10.22.88.117;tag=2d003a7a
Call-ID: MGQzNDhiNWFiMmU5YzU1ZDFiNGQzZWI5Y2Q0ZDhmNjI.
CSeq: 2 SUBSCRIBE
Expires: 300
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
User-Agent: X-Lite release 1006e stamp 34025
Authorization: Digest username=“4071”,realm=“10.22.88.117”,nonce=“207334b5”,uri="sip:4071@10.22.88.117”,response=“26efac924c56eff3d31f115a190e5ace”,algorithm=MD5
Event: message-summary
Content-Length: 0

<------------->
— (14 headers 0 lines) —
Creating new subscription
Sending to 10.22.205.81:17862 (NAT)
Found peer ‘4071’ for ‘4071’ from 10.22.205.81:17862
Scheduling destruction of SIP dialog ‘MGQzNDhiNWFiMmU5YzU1ZDFiNGQzZWI5Y2Q0ZDhmNjI.’ in 310000 ms (Method: SUBSCRIBE)

<— Transmitting (NAT) to 10.22.205.81:17862 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.22.205.81:17862;branch=z9hG4bK-d87543-2540b5158b7cde74-1–d87543-;received=10.22.205.81;rport=17862
From: "4071"sip:4071@10.22.88.117;tag=2d003a7a
To: "4071"sip:4071@10.22.88.117;tag=as2d7545fb
Call-ID: MGQzNDhiNWFiMmU5YzU1ZDFiNGQzZWI5Y2Q0ZDhmNjI.
CSeq: 2 SUBSCRIBE
Server: Asterisk PBX 1.8.26.1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Expires: 300
Contact: sip:4071@10.22.88.117:5060;expires=300
Content-Length: 0

<------------>
Reliably Transmitting (NAT) to 10.22.205.81:17862:
NOTIFY sip:4071@10.22.205.81:17862 SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK6f76a405;rport
Max-Forwards: 70
Route: sip:4071@10.22.205.81:17862
From: “asterisk” sip:asterisk@10.22.88.117;tag=as2d7545fb
To: sip:4071@10.22.205.81:17862;tag=2d003a7a
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: MGQzNDhiNWFiMmU5YzU1ZDFiNGQzZWI5Y2Q0ZDhmNjI.
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 92

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

Retransmitting #1 (NAT) to 10.22.205.81:17862:
NOTIFY sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK263a0dea;rport
Max-Forwards: 70
From: “asterisk” sip:asterisk@10.22.88.117;tag=as1cb708e6
To: sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: 6ea7c7c610eba4325638e33310bea6a8@10.22.88.117:5060
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 92

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

Retransmitting #1 (NAT) to 10.22.205.81:17862:
NOTIFY sip:4071@10.22.205.81:17862 SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK6f76a405;rport
Max-Forwards: 70
Route: sip:4071@10.22.205.81:17862
From: “asterisk” sip:asterisk@10.22.88.117;tag=as2d7545fb
To: sip:4071@10.22.205.81:17862;tag=2d003a7a
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: MGQzNDhiNWFiMmU5YzU1ZDFiNGQzZWI5Y2Q0ZDhmNjI.
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 92

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

Retransmitting #1 (NAT) to 10.22.205.81:17862:
OPTIONS sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK223090cb;rport
Max-Forwards: 70
From: “asterisk” sip:asterisk@10.22.88.117;tag=as0e7009ce
To: sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: 483e8c1c4663569849b62da044b5c157@10.22.88.117:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 1.8.26.1
Date: Wed, 24 Jun 2015 06:01:50 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

Retransmitting #2 (NAT) to 10.22.205.81:17862:
NOTIFY sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK263a0dea;rport
Max-Forwards: 70
From: “asterisk” sip:asterisk@10.22.88.117;tag=as1cb708e6
To: sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: 6ea7c7c610eba4325638e33310bea6a8@10.22.88.117:5060
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 92

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

Retransmitting #2 (NAT) to 10.22.205.81:17862:
NOTIFY sip:4071@10.22.205.81:17862 SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK6f76a405;rport
Max-Forwards: 70
Route: sip:4071@10.22.205.81:17862
From: “asterisk” sip:asterisk@10.22.88.117;tag=as2d7545fb
To: sip:4071@10.22.205.81:17862;tag=2d003a7a
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: MGQzNDhiNWFiMmU5YzU1ZDFiNGQzZWI5Y2Q0ZDhmNjI.
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 92

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

Retransmitting #2 (NAT) to 10.22.205.81:17862:
OPTIONS sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK223090cb;rport
Max-Forwards: 70
From: “asterisk” sip:asterisk@10.22.88.117;tag=as0e7009ce
To: sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: 483e8c1c4663569849b62da044b5c157@10.22.88.117:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 1.8.26.1
Date: Wed, 24 Jun 2015 06:01:50 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

Retransmitting #3 (NAT) to 10.22.205.81:17862:
OPTIONS sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK223090cb;rport
Max-Forwards: 70
From: “asterisk” sip:asterisk@10.22.88.117;tag=as0e7009ce
To: sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: 483e8c1c4663569849b62da044b5c157@10.22.88.117:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 1.8.26.1
Date: Wed, 24 Jun 2015 06:01:50 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

Retransmitting #3 (NAT) to 10.22.205.81:17862:
NOTIFY sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK263a0dea;rport
Max-Forwards: 70
From: “asterisk” sip:asterisk@10.22.88.117;tag=as1cb708e6
To: sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: 6ea7c7c610eba4325638e33310bea6a8@10.22.88.117:5060
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 92

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

Retransmitting #3 (NAT) to 10.22.205.81:17862:
NOTIFY sip:4071@10.22.205.81:17862 SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK6f76a405;rport
Max-Forwards: 70
Route: sip:4071@10.22.205.81:17862
From: “asterisk” sip:asterisk@10.22.88.117;tag=as2d7545fb
To: sip:4071@10.22.205.81:17862;tag=2d003a7a
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: MGQzNDhiNWFiMmU5YzU1ZDFiNGQzZWI5Y2Q0ZDhmNjI.
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 92

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

Retransmitting #4 (NAT) to 10.22.205.81:17862:
OPTIONS sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK223090cb;rport
Max-Forwards: 70
From: “asterisk” sip:asterisk@10.22.88.117;tag=as0e7009ce
To: sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: 483e8c1c4663569849b62da044b5c157@10.22.88.117:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 1.8.26.1
Date: Wed, 24 Jun 2015 06:01:50 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

Really destroying SIP dialog ‘483e8c1c4663569849b62da044b5c157@10.22.88.117:5060’ Method: OPTIONS
Retransmitting #4 (NAT) to 10.22.205.81:17862:
NOTIFY sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK263a0dea;rport
Max-Forwards: 70
From: “asterisk” sip:asterisk@10.22.88.117;tag=as1cb708e6
To: sip:4071@10.22.205.81:17862;rinstance=73e02d9583c569ec
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: 6ea7c7c610eba4325638e33310bea6a8@10.22.88.117:5060
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 92

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

Retransmitting #4 (NAT) to 10.22.205.81:17862:
NOTIFY sip:4071@10.22.205.81:17862 SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK6f76a405;rport
Max-Forwards: 70
Route: sip:4071@10.22.205.81:17862
From: “asterisk” sip:asterisk@10.22.88.117;tag=as2d7545fb
To: sip:4071@10.22.205.81:17862;tag=2d003a7a
Contact: sip:asterisk@10.22.88.117:5060
Call-ID: MGQzNDhiNWFiMmU5YzU1ZDFiNGQzZWI5Y2Q0ZDhmNjI.
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 92

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

Really destroying SIP dialog ‘76f3a42f775458826177e65d6c300623@10.22.88.117:5060’ Method: NOTIFY
ipbxdrcCLI> sip show peers
Name/username Host Dyn Forcerport ACL Port Status
4071/4071 10.22.205.81 D N A 17862 UNREACHABLE
trunk_sip/700 10.0.80.5 N 5060 OK (4 ms)
82 sip peers [Monitored: 1 online, 81 offline Unmonitored: 0 online, 0 offline]
ipbxdrcCLI>

Kira-kira dimana masalahnya Pak?

Thanks

anton · June 24, 2015, 6:11am

ini karena SIP NOTIFY tidak sampai, bisa karena banyak hal:

client tidak comply 100%
ada masalah network

coba set jangan di qualify, agar tidak dikirim notify oleh server. nanti hasilnya jadi unmonitored, tetapi asterisk akan tetap mencoba menerima call, dibanding saat statusnya unreachable.

anton

MASTERING_VOIP · June 24, 2015, 6:15am

Pak Anton,

Bisa di info di bagian mana yang menyatakan NOTIFY tidak sampe?

Apakah ini ?

Retransmitting #4 (NAT) to 10.22.205.81:17862:
NOTIFY sip:4071@10.22.205.81:17862 SIP/2.0
Via: SIP/2.0/UDP 10.22.88.117:5060;branch=z9hG4bK6f76a405;rport
Max-Forwards: 70
Route:
From: “asterisk” ;tag=as2d7545fb
To: ;tag=2d003a7a
Contact:
Call-ID: MGQzNDhiNWFiMmU5YzU1ZDFiNGQzZWI5Y2Q0ZDhmNjI.
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.26.1
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 92

Saya mau compare dengan yang normal untuk mengetahui message notify yang sebenarnya.

Thanks

anton · June 24, 2015, 6:18am

iya, seperti itu, itu sudah bbrp kali coba kirim ulang dan tidak sampai

jadi setelah sukses registrasi ngga berapa lama dia menjadi UNREACHABLE.

anton

MASTERING_VOIP · June 24, 2015, 8:13am

Pak Anton,

Thanks perjelasannya yang super!!!

Thanks