Пожалуйста, войдите здесь. Часто задаваемые вопросы О нас
Задайте Ваш вопрос

История изменений [назад]

нажмите, чтобы скрыть/показать версии 1
изначальная версия
редактировать

спросил 2015-12-03 17:51:34 +0400

wellus Gravatar wellus

FXS шлюзы теряют регистрацию порты

Установлен FreePBX (asterisk 11.20.0)

К нему подключены два восьми портовых FXS шлюза (eltex и yealink) и один восьми портовый fxo шлюз grandstream.

Настройки extensions у всех одинаковые, настройки транков на fxo у всех одинаковые.

Но через какое-то время по два порта на fxs шлюзах и один порт на fxo шлюзе - теряют регистрацию.

Причем:

  • это одни и те же порты.

  • на самих шлюзах статус этих портов - Зарегистрирован.

Если бы шлюзы были одного производителя - то грешил бы на них, но они все от разных.

Готов показать любые настройки, сразу выкладывать эти портянки не стал...

Может есть мысли хоть куда копать?

FXS шлюзы теряют регистрацию порты

Установлен FreePBX (asterisk 11.20.0)

К нему подключены два восьми портовых FXS шлюза (eltex и yealink) и один восьми портовый fxo шлюз grandstream.

Настройки extensions у всех одинаковые, настройки транков на fxo у всех одинаковые.

Но через какое-то время по два порта на fxs шлюзах и один порт на fxo шлюзе - теряют регистрацию.

Причем:

  • это одни и те же порты.

  • на самих шлюзах статус этих портов - Зарегистрирован.

Если бы шлюзы были одного производителя - то грешил бы на них, но они все от разных.

Готов показать любые настройки, сразу выкладывать эти портянки не стал...

Может есть мысли хоть куда копать?

Добавил дебаг:

<--- SIP read from UDP:192.168.0.12:5060 --->
REGISTER sip:192.168.0.150 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.12;rport;branch=z9hG4bKQFQ52vj7vgQDj
Max-Forwards: 70
From: <sip:108@192.168.0.150>;tag=36Z3ZXa7r98Uc
To: <sip:108@192.168.0.150>
Call-ID: 06d3df3f-9875-1200-7885-a8f94b092be0
CSeq: 27 REGISTER
Contact: <sip:108@192.168.0.12:5060>
Expires: 1800
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces, path
Authorization: Digest username="108", realm="asterisk", nonce="0ba7072e", algorithm=MD5, uri="sip:192.168.0.150", response="e3f97d001cb52638ef6c018e891f8351"
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Sending to 192.168.0.12:5060 (NAT)
Sending to 192.168.0.12:5060 (NAT)

<--- Transmitting (no NAT) to 192.168.0.12:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.12;branch=z9hG4bKQFQ52vj7vgQDj;received=192.168.0.12;rport=5060
From: <sip:108@192.168.0.150>;tag=36Z3ZXa7r98Uc
To: <sip:108@192.168.0.150>;tag=as689ecfb5
Call-ID: 06d3df3f-9875-1200-7885-a8f94b092be0
CSeq: 27 REGISTER
Server: FPBX-12.0.76.2(11.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="46a4e78a"
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '06d3df3f-9875-1200-7885-a8f94b092be0' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.0.12:5060 --->
REGISTER sip:192.168.0.150 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.12;rport;branch=z9hG4bKrrgy4Q3atSD0D
Max-Forwards: 70
From: <sip:108@192.168.0.150>;tag=36Z3ZXa7r98Uc
To: <sip:108@192.168.0.150>
Call-ID: 06d3df3f-9875-1200-7885-a8f94b092be0
CSeq: 28 REGISTER
Contact: <sip:108@192.168.0.12:5060>
Expires: 1800
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces, path
Authorization: Digest username="108", realm="asterisk", nonce="46a4e78a", algorithm=MD5, uri="sip:192.168.0.150", response="fa9efaa52eefcb66deac1cd33bf1d99e"
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Sending to 192.168.0.12:5060 (no NAT)
    -- Registered SIP '108' at 192.168.0.12:5060 <- ВОТ ОН ЗАРЕГИСТРИРОВАЛСЯ
Reliably Transmitting (no NAT) to 192.168.0.12:5060:
OPTIONS sip:108@192.168.0.12:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK7c4f56c1
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as4c005567
To: <sip:108@192.168.0.12:5060>
Contact: <sip:Unknown@192.168.0.150:5060>
Call-ID: 2dbb8050118c6ebb7b0b08f960284662@192.168.0.150:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-12.0.76.2(11.20.0)
Date: Thu, 03 Dec 2015 17:05:42 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


---

<--- Transmitting (no NAT) to 192.168.0.12:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.12;branch=z9hG4bKrrgy4Q3atSD0D;received=192.168.0.12;rport=5060
From: <sip:108@192.168.0.150>;tag=36Z3ZXa7r98Uc
To: <sip:108@192.168.0.150>;tag=as689ecfb5
Call-ID: 06d3df3f-9875-1200-7885-a8f94b092be0
CSeq: 28 REGISTER
Server: FPBX-12.0.76.2(11.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 1800
Contact: <sip:108@192.168.0.12:5060>;expires=1800
Date: Thu, 03 Dec 2015 17:05:42 GMT
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '3c165f462db98d9164d3c46772383934@192.168.0.150:5060' in 32000 ms (Method: NOTIFY)
Reliably Transmitting (no NAT) to 192.168.0.12:5060:
NOTIFY sip:108@192.168.0.12:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK75c94a99
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as79da1c57
To: <sip:108@192.168.0.12:5060>
Contact: <sip:Unknown@192.168.0.150:5060>
Call-ID: 3c165f462db98d9164d3c46772383934@192.168.0.150:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-12.0.76.2(11.20.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 88

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

---
Scheduling destruction of SIP dialog '06d3df3f-9875-1200-7885-a8f94b092be0' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.0.12:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK7c4f56c1
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as4c005567
To: <sip:108@192.168.0.12:5060>;tag=0g1QpNZgK0jKQ
Call-ID: 2dbb8050118c6ebb7b0b08f960284662@192.168.0.150:5060
CSeq: 102 OPTIONS
Contact: <sip:107@192.168.0.12:5060>
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces
Content-Type: application/sdp
Content-Length: 289

v=0
o=- 4627741027303652222 5980289334492692229 IN IP4 192.168.0.12
s=Session SDP
c=IN IP4 192.168.0.12
t=0 0
m=audio 0 RTP/AVP 8 0 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=inactive
a=ptime:20
a=silenceSupp:off - - - -
<------------->
--- (13 headers 13 lines) ---
[2015-12-03 20:05:42] NOTICE[1448]: chan_sip.c:23739 handle_response_peerpoke: Peer '108' is now Reachable. (7ms / 2000ms)
Really destroying SIP dialog '2dbb8050118c6ebb7b0b08f960284662@192.168.0.150:5060' Method: OPTIONS

<--- SIP read from UDP:192.168.0.12:5060 --->
SIP/2.0 481 Subscription Does Not Exist <- А ВОТ ПОЧЕМУ ПРИЛЕТЕЛО ВОТ ЭТО ПОНЯТЬ НЕ МОГУ
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK75c94a99
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as79da1c57
To: <sip:108@192.168.0.12:5060>;tag=1Stgrggmg985j
Call-ID: 3c165f462db98d9164d3c46772383934@192.168.0.150:5060
CSeq: 102 NOTIFY
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces
Content-Length: 0

<------------->

FXS шлюзы теряют регистрацию порты

Установлен FreePBX (asterisk 11.20.0)

К нему подключены два восьми портовых FXS шлюза (eltex и yealink) и один восьми портовый fxo шлюз grandstream.

Настройки extensions у всех одинаковые, настройки транков на fxo у всех одинаковые.

Но через какое-то время по два порта на fxs шлюзах и один порт на fxo шлюзе - теряют регистрацию.

Причем:

  • это одни и те же порты.

  • на самих шлюзах статус этих портов - Зарегистрирован.

Если бы шлюзы были одного производителя - то грешил бы на них, но они все от разных.

Готов показать любые настройки, сразу выкладывать эти портянки не стал...

Может есть мысли хоть куда копать?

Добавил дебаг:

<--- SIP read from UDP:192.168.0.12:5060 --->
REGISTER sip:192.168.0.150 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.12;rport;branch=z9hG4bKQFQ52vj7vgQDj
Max-Forwards: 70
From: <sip:108@192.168.0.150>;tag=36Z3ZXa7r98Uc
To: <sip:108@192.168.0.150>
Call-ID: 06d3df3f-9875-1200-7885-a8f94b092be0
CSeq: 27 REGISTER
Contact: <sip:108@192.168.0.12:5060>
Expires: 1800
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces, path
Authorization: Digest username="108", realm="asterisk", nonce="0ba7072e", algorithm=MD5, uri="sip:192.168.0.150", response="e3f97d001cb52638ef6c018e891f8351"
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Sending to 192.168.0.12:5060 (NAT)
Sending to 192.168.0.12:5060 (NAT)

<--- Transmitting (no NAT) to 192.168.0.12:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.12;branch=z9hG4bKQFQ52vj7vgQDj;received=192.168.0.12;rport=5060
From: <sip:108@192.168.0.150>;tag=36Z3ZXa7r98Uc
To: <sip:108@192.168.0.150>;tag=as689ecfb5
Call-ID: 06d3df3f-9875-1200-7885-a8f94b092be0
CSeq: 27 REGISTER
Server: FPBX-12.0.76.2(11.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="46a4e78a"
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '06d3df3f-9875-1200-7885-a8f94b092be0' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.0.12:5060 --->
REGISTER sip:192.168.0.150 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.12;rport;branch=z9hG4bKrrgy4Q3atSD0D
Max-Forwards: 70
From: <sip:108@192.168.0.150>;tag=36Z3ZXa7r98Uc
To: <sip:108@192.168.0.150>
Call-ID: 06d3df3f-9875-1200-7885-a8f94b092be0
CSeq: 28 REGISTER
Contact: <sip:108@192.168.0.12:5060>
Expires: 1800
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces, path
Authorization: Digest username="108", realm="asterisk", nonce="46a4e78a", algorithm=MD5, uri="sip:192.168.0.150", response="fa9efaa52eefcb66deac1cd33bf1d99e"
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Sending to 192.168.0.12:5060 (no NAT)
    -- Registered SIP '108' at 192.168.0.12:5060 <- ВОТ ОН ЗАРЕГИСТРИРОВАЛСЯ
Reliably Transmitting (no NAT) to 192.168.0.12:5060:
OPTIONS sip:108@192.168.0.12:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK7c4f56c1
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as4c005567
To: <sip:108@192.168.0.12:5060>
Contact: <sip:Unknown@192.168.0.150:5060>
Call-ID: 2dbb8050118c6ebb7b0b08f960284662@192.168.0.150:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-12.0.76.2(11.20.0)
Date: Thu, 03 Dec 2015 17:05:42 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


---

<--- Transmitting (no NAT) to 192.168.0.12:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.12;branch=z9hG4bKrrgy4Q3atSD0D;received=192.168.0.12;rport=5060
From: <sip:108@192.168.0.150>;tag=36Z3ZXa7r98Uc
To: <sip:108@192.168.0.150>;tag=as689ecfb5
Call-ID: 06d3df3f-9875-1200-7885-a8f94b092be0
CSeq: 28 REGISTER
Server: FPBX-12.0.76.2(11.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 1800
Contact: <sip:108@192.168.0.12:5060>;expires=1800
Date: Thu, 03 Dec 2015 17:05:42 GMT
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '3c165f462db98d9164d3c46772383934@192.168.0.150:5060' in 32000 ms (Method: NOTIFY)
Reliably Transmitting (no NAT) to 192.168.0.12:5060:
NOTIFY sip:108@192.168.0.12:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK75c94a99
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as79da1c57
To: <sip:108@192.168.0.12:5060>
Contact: <sip:Unknown@192.168.0.150:5060>
Call-ID: 3c165f462db98d9164d3c46772383934@192.168.0.150:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-12.0.76.2(11.20.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 88

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

---
Scheduling destruction of SIP dialog '06d3df3f-9875-1200-7885-a8f94b092be0' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.0.12:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK7c4f56c1
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as4c005567
To: <sip:108@192.168.0.12:5060>;tag=0g1QpNZgK0jKQ
Call-ID: 2dbb8050118c6ebb7b0b08f960284662@192.168.0.150:5060
CSeq: 102 OPTIONS
Contact: <sip:107@192.168.0.12:5060>
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces
Content-Type: application/sdp
Content-Length: 289

v=0
o=- 4627741027303652222 5980289334492692229 IN IP4 192.168.0.12
s=Session SDP
c=IN IP4 192.168.0.12
t=0 0
m=audio 0 RTP/AVP 8 0 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=inactive
a=ptime:20
a=silenceSupp:off - - - -
<------------->
--- (13 headers 13 lines) ---
[2015-12-03 20:05:42] NOTICE[1448]: chan_sip.c:23739 handle_response_peerpoke: Peer '108' is now Reachable. (7ms / 2000ms)
Really destroying SIP dialog '2dbb8050118c6ebb7b0b08f960284662@192.168.0.150:5060' Method: OPTIONS

<--- SIP read from UDP:192.168.0.12:5060 --->
SIP/2.0 481 Subscription Does Not Exist <- А ВОТ ПОЧЕМУ ПРИЛЕТЕЛО ВОТ ЭТО ПОНЯТЬ НЕ МОГУ
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK75c94a99
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as79da1c57
To: <sip:108@192.168.0.12:5060>;tag=1Stgrggmg985j
Call-ID: 3c165f462db98d9164d3c46772383934@192.168.0.150:5060
CSeq: 102 NOTIFY
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces
Content-Length: 0

<------------->

Добавил дебаг, после указания контроля методом OPTIONS на шлюзе.

<------------>
Scheduling destruction of SIP dialog '0ceb4fe938cb966a05a8afb36f8d815f@192.168.0.150:5060' in 32000 ms (Method: NOTIFY)
Reliably Transmitting (no NAT) to 192.168.0.12:5060:
NOTIFY sip:108@192.168.0.12:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK71070eb8
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as68842365
To: <sip:108@192.168.0.12:5060>
Contact: <sip:Unknown@192.168.0.150:5060>
Call-ID: 0ceb4fe938cb966a05a8afb36f8d815f@192.168.0.150:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-12.0.76.2(11.20.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 88

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

---
Scheduling destruction of SIP dialog 'b80cbe3f-987e-1200-8885-a8f94b092be0' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.0.12:5060 --->
SIP/2.0 481 Subscription Does Not Exist
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK71070eb8
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as68842365
To: <sip:108@192.168.0.12:5060>;tag=528SZpjv84j8F
Call-ID: 0ceb4fe938cb966a05a8afb36f8d815f@192.168.0.150:5060
CSeq: 102 NOTIFY
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces
Content-Length: 0

видно, что сервер шлет NOTIFY на шлюз и получает отказ... как отключить это?

FXS шлюзы теряют регистрацию порты

Установлен FreePBX (asterisk 11.20.0)

К нему подключены два восьми портовых FXS шлюза (eltex и yealink) и один восьми портовый fxo шлюз grandstream.

Настройки extensions у всех одинаковые, настройки транков на fxo у всех одинаковые.

Но через какое-то время по два порта на fxs шлюзах и один порт на fxo шлюзе - теряют регистрацию.

Причем:

  • это одни и те же порты.

  • на самих шлюзах статус этих портов - Зарегистрирован.

Если бы шлюзы были одного производителя - то грешил бы на них, но они все от разных.

Готов показать любые настройки, сразу выкладывать эти портянки не стал...

Может есть мысли хоть куда копать?

Добавил дебаг:

<--- SIP read from UDP:192.168.0.12:5060 --->
REGISTER sip:192.168.0.150 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.12;rport;branch=z9hG4bKQFQ52vj7vgQDj
Max-Forwards: 70
From: <sip:108@192.168.0.150>;tag=36Z3ZXa7r98Uc
To: <sip:108@192.168.0.150>
Call-ID: 06d3df3f-9875-1200-7885-a8f94b092be0
CSeq: 27 REGISTER
Contact: <sip:108@192.168.0.12:5060>
Expires: 1800
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces, path
Authorization: Digest username="108", realm="asterisk", nonce="0ba7072e", algorithm=MD5, uri="sip:192.168.0.150", response="e3f97d001cb52638ef6c018e891f8351"
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Sending to 192.168.0.12:5060 (NAT)
Sending to 192.168.0.12:5060 (NAT)

<--- Transmitting (no NAT) to 192.168.0.12:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.12;branch=z9hG4bKQFQ52vj7vgQDj;received=192.168.0.12;rport=5060
From: <sip:108@192.168.0.150>;tag=36Z3ZXa7r98Uc
To: <sip:108@192.168.0.150>;tag=as689ecfb5
Call-ID: 06d3df3f-9875-1200-7885-a8f94b092be0
CSeq: 27 REGISTER
Server: FPBX-12.0.76.2(11.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="46a4e78a"
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '06d3df3f-9875-1200-7885-a8f94b092be0' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.0.12:5060 --->
REGISTER sip:192.168.0.150 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.12;rport;branch=z9hG4bKrrgy4Q3atSD0D
Max-Forwards: 70
From: <sip:108@192.168.0.150>;tag=36Z3ZXa7r98Uc
To: <sip:108@192.168.0.150>
Call-ID: 06d3df3f-9875-1200-7885-a8f94b092be0
CSeq: 28 REGISTER
Contact: <sip:108@192.168.0.12:5060>
Expires: 1800
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces, path
Authorization: Digest username="108", realm="asterisk", nonce="46a4e78a", algorithm=MD5, uri="sip:192.168.0.150", response="fa9efaa52eefcb66deac1cd33bf1d99e"
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Sending to 192.168.0.12:5060 (no NAT)
    -- Registered SIP '108' at 192.168.0.12:5060 <- ВОТ ОН ЗАРЕГИСТРИРОВАЛСЯ
Reliably Transmitting (no NAT) to 192.168.0.12:5060:
OPTIONS sip:108@192.168.0.12:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK7c4f56c1
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as4c005567
To: <sip:108@192.168.0.12:5060>
Contact: <sip:Unknown@192.168.0.150:5060>
Call-ID: 2dbb8050118c6ebb7b0b08f960284662@192.168.0.150:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-12.0.76.2(11.20.0)
Date: Thu, 03 Dec 2015 17:05:42 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


---

<--- Transmitting (no NAT) to 192.168.0.12:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.12;branch=z9hG4bKrrgy4Q3atSD0D;received=192.168.0.12;rport=5060
From: <sip:108@192.168.0.150>;tag=36Z3ZXa7r98Uc
To: <sip:108@192.168.0.150>;tag=as689ecfb5
Call-ID: 06d3df3f-9875-1200-7885-a8f94b092be0
CSeq: 28 REGISTER
Server: FPBX-12.0.76.2(11.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 1800
Contact: <sip:108@192.168.0.12:5060>;expires=1800
Date: Thu, 03 Dec 2015 17:05:42 GMT
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '3c165f462db98d9164d3c46772383934@192.168.0.150:5060' in 32000 ms (Method: NOTIFY)
Reliably Transmitting (no NAT) to 192.168.0.12:5060:
NOTIFY sip:108@192.168.0.12:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK75c94a99
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as79da1c57
To: <sip:108@192.168.0.12:5060>
Contact: <sip:Unknown@192.168.0.150:5060>
Call-ID: 3c165f462db98d9164d3c46772383934@192.168.0.150:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-12.0.76.2(11.20.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 88

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

---
Scheduling destruction of SIP dialog '06d3df3f-9875-1200-7885-a8f94b092be0' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.0.12:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK7c4f56c1
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as4c005567
To: <sip:108@192.168.0.12:5060>;tag=0g1QpNZgK0jKQ
Call-ID: 2dbb8050118c6ebb7b0b08f960284662@192.168.0.150:5060
CSeq: 102 OPTIONS
Contact: <sip:107@192.168.0.12:5060>
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces
Content-Type: application/sdp
Content-Length: 289

v=0
o=- 4627741027303652222 5980289334492692229 IN IP4 192.168.0.12
s=Session SDP
c=IN IP4 192.168.0.12
t=0 0
m=audio 0 RTP/AVP 8 0 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=inactive
a=ptime:20
a=silenceSupp:off - - - -
<------------->
--- (13 headers 13 lines) ---
[2015-12-03 20:05:42] NOTICE[1448]: chan_sip.c:23739 handle_response_peerpoke: Peer '108' is now Reachable. (7ms / 2000ms)
Really destroying SIP dialog '2dbb8050118c6ebb7b0b08f960284662@192.168.0.150:5060' Method: OPTIONS

<--- SIP read from UDP:192.168.0.12:5060 --->
SIP/2.0 481 Subscription Does Not Exist <- А ВОТ ПОЧЕМУ ПРИЛЕТЕЛО ВОТ ЭТО ПОНЯТЬ НЕ МОГУ
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK75c94a99
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as79da1c57
To: <sip:108@192.168.0.12:5060>;tag=1Stgrggmg985j
Call-ID: 3c165f462db98d9164d3c46772383934@192.168.0.150:5060
CSeq: 102 NOTIFY
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces
Content-Length: 0

<------------->

Добавил дебаг, после указания контроля методом OPTIONS на шлюзе.

<------------>
Scheduling destruction of SIP dialog '0ceb4fe938cb966a05a8afb36f8d815f@192.168.0.150:5060' in 32000 ms (Method: NOTIFY)
Reliably Transmitting (no NAT) to 192.168.0.12:5060:
NOTIFY sip:108@192.168.0.12:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK71070eb8
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as68842365
To: <sip:108@192.168.0.12:5060>
Contact: <sip:Unknown@192.168.0.150:5060>
Call-ID: 0ceb4fe938cb966a05a8afb36f8d815f@192.168.0.150:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-12.0.76.2(11.20.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 88

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

---
Scheduling destruction of SIP dialog 'b80cbe3f-987e-1200-8885-a8f94b092be0' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.0.12:5060 --->
SIP/2.0 481 Subscription Does Not Exist
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK71070eb8
From: "Unknown" <sip:Unknown@192.168.0.150>;tag=as68842365
To: <sip:108@192.168.0.12:5060>;tag=528SZpjv84j8F
Call-ID: 0ceb4fe938cb966a05a8afb36f8d815f@192.168.0.150:5060
CSeq: 102 NOTIFY
User-Agent: TAU-8.IP/2.0.0 SN/VI33006252 sofia-sip/1.12.10
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, INFO
Supported: timer, 100rel, replaces
Content-Length: 0

видно, что сервер шлет NOTIFY на шлюз и получает отказ... как отключить это?

вот еще CORE SET DEBUG 9

[2015-12-04 09:14:25] DEBUG[1448]: chan_sip.c:3367 initialize_initreq: Initializing initreq for method OPTIONS - callid 740eb50851992c920d1eebc6405e18d2@192.168.0.150:5060
[2015-12-04 09:14:25] DEBUG[1448]: chan_sip.c:3724 __sip_xmit: Trying to put 'OPTIONS sip' onto UDP socket destined for 192.168.0.12:5060
[2015-12-04 09:14:25] DEBUG[1448]: chan_sip.c:9038 find_call: = Looking for  Call ID: 740eb50851992c920d1eebc6405e18d2@192.168.0.150:5060 (Checking To) --From tag as5fda32e2 --To-tag 0HvHH55XrXg2c  
[2015-12-04 09:14:25] DEBUG[1448]: chan_sip.c:4421 __sip_ack: Stopping retransmission on '740eb50851992c920d1eebc6405e18d2@192.168.0.150:5060' of Request 102: Match Found
[2015-12-04 09:14:25] DEBUG[1448]: chan_sip.c:6681 sip_destroy: Destroying SIP dialog 740eb50851992c920d1eebc6405e18d2@192.168.0.150:5060
[2015-12-04 09:14:26] DEBUG[1423]: devicestate.c:344 _ast_device_state: No provider found, checking channel drivers for SIP - 113
[2015-12-04 09:14:26] DEBUG[1423]: chan_sip.c:29923 sip_devicestate: Checking device state for peer 113
[2015-12-04 09:14:26] DEBUG[1423]: devicestate.c:476 do_state_change: Changing state for SIP/113 - state 5 (Unavailable)
[2015-12-04 09:14:26] DEBUG[1423]: devicestate.c:451 devstate_event: device 'SIP/113' state '5'
[2015-12-04 09:14:26] DEBUG[1461]: app_queue.c:1867 handle_statechange: Device 'SIP/113' changed to state '5' (Unavailable) but we don't care because they're not a member of any queue.
[2015-12-04 09:14:26] DEBUG[1425]: app_queue.c:1969 extension_state_cb: Extension '113@ext-local' changed to state '5' (Unavailable) but we don't care because they're not a member of any queue.
О проекте | Часто задаваемые вопросы | политика конфиденциальности | оставить отзыв

Проект компании "АТС Дизайн"
Asterisk® и Digium® являются зарегистрированными торговыми марками компании Digium, Inc., США.
IP АТС Asterisk распространяется под лицензией GNU GPL.