Телефон не регистрируется по OpenVPN

[Jugger1030]

И так, произошло чудо и телефон зарегистрировался. После того, как я сменил SIP на 5060 на * . Как и предполагал, решение оказалось простым до безобразия.. Всем огромное спасибо за ответы и помощь. Dedу персонально.. Только не пойму, почему при указании на клиенте порта 5160 он все равно долбит на 5060? еще думал, что все телефоны в локалке нужно будет перестраивать на 5060, но они так и остались зарегаными с портом 5160. Видимо мне нужно еще многое изучать, особенно про порты

Упс.. приходится перенастраивать, зареганы телефоны, но звонки не идут

[virus_net]

А все почему? Да потому, что так и не последовали моему совету и до сих пор не знаете tcpdump ключа -n

[Jugger1030]

мдее, рано я обрадовался. ZoIPer то регистрируется, а yealink настольный опять не хочет.. Станция посылает на него 401 а он не видит. Откуда там вообще взялось 5160, я вообще все перевел на 5060 и клиента и астериск

Код: выделить все

11:33:55.336565 IP 192.168.5.6.sip > icl.sangoma.local.sip: SIP: REGISTER sip:192.168.3.17:5060 SIP/2.0
Eh.H..@.?................4.oREGISTER sip:192.168.3.17:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK400873093
From: "test" <sip:4141@192.168.3.17:5060>;tag=1057327431
To: "test" <sip:4141@192.168.3.17:5060>
Call-ID: 0_876459970@192.168.5.6
CSeq: 1 REGISTER
Contact: <sip:4141@192.168.5.6:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T19P_E2 53.84.0.15
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0


11:33:55.336717 IP icl.sangoma.local.sip > 192.168.5.6.sip: SIP: SIP/2.0 401 Unauthorized
E`.&....@.R...............w.SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK400873093;received=192.168.5.6
From: "test" <sip:4141@192.168.3.17:5060>;tag=1057327431
To: "test" <sip:4141@192.168.3.17:5060>;tag=as51341b68
Call-ID: 0_876459970@192.168.5.6
CSeq: 1 REGISTER
Server: FPBX-14.0.13.4(13.22.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="2532f1ea"
Content-Length: 0


11:33:56.100290 IP icl.sangoma.local.sip > 192.168.5.6.5160: SIP: OPTIONS sip:4141@192.168.105.2:5160 SIP/2.0
E`.E....@.R............(.1F.OPTIONS sip:4141@192.168.105.2:5160 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.17:5060;branch=z9hG4bK3da5e65b
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.3.17>;tag=as24916c13
To: <sip:4141@192.168.105.2:5160>
Contact: <sip:Unknown@192.168.3.17:5060>
Call-ID: 2448ff534281798812ed206653195503@192.168.3.17:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.4(13.22.0)
Date: Wed, 14 Aug 2019 07:33:56 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


11:33:57.100457 IP icl.sangoma.local.sip > 192.168.5.6.5160: SIP: OPTIONS sip:4141@192.168.105.2:5160 SIP/2.0
E`.E.u..@.Pk...........(.1F.OPTIONS sip:4141@192.168.105.2:5160 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.17:5060;branch=z9hG4bK3da5e65b
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.3.17>;tag=as24916c13
To: <sip:4141@192.168.105.2:5160>
Contact: <sip:Unknown@192.168.3.17:5060>
Call-ID: 2448ff534281798812ed206653195503@192.168.3.17:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.4(13.22.0)
Date: Wed, 14 Aug 2019 07:33:56 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


11:33:58.099803 IP icl.sangoma.local.sip > 192.168.5.6.5160: SIP: OPTIONS sip:4141@192.168.105.2:5160 SIP/2.0
E`.E.G..@.L............(.1F.OPTIONS sip:4141@192.168.105.2:5160 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.17:5060;branch=z9hG4bK3da5e65b
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.3.17>;tag=as24916c13
To: <sip:4141@192.168.105.2:5160>
Contact: <sip:Unknown@192.168.3.17:5060>
Call-ID: 2448ff534281798812ed206653195503@192.168.3.17:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.4(13.22.0)
Date: Wed, 14 Aug 2019 07:33:56 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


11:33:59.099621 IP icl.sangoma.local.sip > 192.168.5.6.5160: SIP: OPTIONS sip:4141@192.168.105.2:5160 SIP/2.0
E`.E.;..@.J............(.1F.OPTIONS sip:4141@192.168.105.2:5160 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.17:5060;branch=z9hG4bK3da5e65b
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.3.17>;tag=as24916c13
To: <sip:4141@192.168.105.2:5160>
Contact: <sip:Unknown@192.168.3.17:5060>
Call-ID: 2448ff534281798812ed206653195503@192.168.3.17:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.4(13.22.0)
Date: Wed, 14 Aug 2019 07:33:56 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


11:33:59.366708 IP 192.168.5.6.sip > icl.sangoma.local.sip: SIP: REGISTER sip:192.168.3.17:5060 SIP/2.0
Eh.H..@.?................4.oREGISTER sip:192.168.3.17:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK400873093
From: "test" <sip:4141@192.168.3.17:5060>;tag=1057327431
To: "test" <sip:4141@192.168.3.17:5060>
Call-ID: 0_876459970@192.168.5.6
CSeq: 1 REGISTER
Contact: <sip:4141@192.168.5.6:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T19P_E2 53.84.0.15
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0


11:33:59.366834 IP icl.sangoma.local.sip > 192.168.5.6.sip: SIP: SIP/2.0 401 Unauthorized
E`.&.<..@.I...............w.SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK400873093;received=192.168.5.6
From: "test" <sip:4141@192.168.3.17:5060>;tag=1057327431
To: "test" <sip:4141@192.168.3.17:5060>;tag=as51341b68
Call-ID: 0_876459970@192.168.5.6
CSeq: 1 REGISTER
Server: FPBX-14.0.13.4(13.22.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="2532f1ea"
Content-Length: 0


11:34:00.100836 IP icl.sangoma.local.sip > 192.168.5.6.5160: SIP: OPTIONS sip:4141@192.168.105.2:5160 SIP/2.0
E`.E.w..@.Gi...........(.1F.OPTIONS sip:4141@192.168.105.2:5160 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.17:5060;branch=z9hG4bK3da5e65b
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.3.17>;tag=as24916c13
To: <sip:4141@192.168.105.2:5160>
Contact: <sip:Unknown@192.168.3.17:5060>
Call-ID: 2448ff534281798812ed206653195503@192.168.3.17:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.4(13.22.0)
Date: Wed, 14 Aug 2019 07:33:56 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


11:34:03.396007 IP 192.168.5.6.sip > icl.sangoma.local.sip: SIP: REGISTER sip:192.168.3.17:5060 SIP/2.0
Eh.H..@.?................4.oREGISTER sip:192.168.3.17:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK400873093
From: "test" <sip:4141@192.168.3.17:5060>;tag=1057327431
To: "test" <sip:4141@192.168.3.17:5060>
Call-ID: 0_876459970@192.168.5.6
CSeq: 1 REGISTER
Contact: <sip:4141@192.168.5.6:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T19P_E2 53.84.0.15
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0


11:34:03.396149 IP icl.sangoma.local.sip > 192.168.5.6.sip: SIP: SIP/2.0 401 Unauthorized
E`.&.9..@.F...............w.SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK400873093;received=192.168.5.6
From: "test" <sip:4141@192.168.3.17:5060>;tag=1057327431
To: "test" <sip:4141@192.168.3.17:5060>;tag=as51341b68
Call-ID: 0_876459970@192.168.5.6
CSeq: 1 REGISTER
Server: FPBX-14.0.13.4(13.22.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="2532f1ea"
Content-Length: 0


как и просил Ded, я опять воспроизвел ситуацию с первого поста темы))

[ded]

Удалите 4141 и заведите какой-то другой, типа 4143. Надеюсь у него будет стоять nat=no?

Диалог REGISTER проходит c порта 5060 на порт 5060, но дальше станция начинает бомбить телефон пакетами OPTIONS по порту 5160, что-то нехорошо она запомнила по вашим экспериментам.

В параметрах Имя регистрации и Имя пользователя указываем внутренний номер телефона (например, 26), который нужно настроить для этого телефонного аппарата.

В поле Пароль указываем пароль от SIP-аккаунта.

В параметрах Адрес SIP-сервера задаем адрес сервера Asterisk (например, 192.168.1.11).

Если телефоны будут находиться в одной локальной сети, то указываем внутренний адрес сервера Asterisk.

* Если телефоны будут находиться на удаленных объектах (за NAT), то указываем внешний адрес сервера Asterisk (никаких других настроек со стороны аппарата Yealink T19P E2 при работе за NAT не требуется).

Ждем кнопку Сохранить.
4. Проверяем связь с Asterisk

Проверить зарегистрировался ли телефон на сервере Asterisk очень просто. Для этого не нужно переходить на другую вкладку, достаточно посмотреть на первую строчку Статус регистрации. После сохранения настроек телефону требуется несколько секунд для регистрации, после этого появляется надпись Зарегистрировано.

https://asofts.ru/instrukcii/instrukciy ... 9p-e2.html

[Jugger1030]

удалил, завел другой номер, все тоже самое, за исключением того, что теперь не используется 5160

Код: выделить все

12:26:27.280384 IP 192.168.5.6.sip > icl.sangoma.local.sip: SIP: REGISTER sip:192.168.3.17:5060 SIP/2.0
Eh.R..@.?................>2'REGISTER sip:192.168.3.17:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK4041631440
From: "........" <sip:4170@192.168.3.17:5060>;tag=1970937568
To: "........" <sip:4170@192.168.3.17:5060>
Call-ID: 0_1865556458@192.168.5.6
CSeq: 1 REGISTER
Contact: <sip:4170@192.168.5.6:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T19P_E2 53.84.0.15
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0


12:26:27.280508 IP icl.sangoma.local.sip > 192.168.5.6.sip: SIP: SIP/2.0 401 Unauthorized
E`.0....@...................SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK4041631440;received=192.168.5.6
From: "........" <sip:4170@192.168.3.17:5060>;tag=1970937568
To: "........" <sip:4170@192.168.3.17:5060>;tag=as09ebed0c
Call-ID: 0_1865556458@192.168.5.6
CSeq: 1 REGISTER
Server: FPBX-14.0.13.4(13.22.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="6c05a479"
Content-Length: 0


12:26:31.310109 IP 192.168.5.6.sip > icl.sangoma.local.sip: SIP: REGISTER sip:192.168.3.17:5060 SIP/2.0
Eh.R..@.?................>2'REGISTER sip:192.168.3.17:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK4041631440
From: "........" <sip:4170@192.168.3.17:5060>;tag=1970937568
To: "........" <sip:4170@192.168.3.17:5060>
Call-ID: 0_1865556458@192.168.5.6
CSeq: 1 REGISTER
Contact: <sip:4170@192.168.5.6:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T19P_E2 53.84.0.15
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0


12:26:31.310228 IP icl.sangoma.local.sip > 192.168.5.6.sip: SIP: SIP/2.0 401 Unauthorized
E`.0
...@...................SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK4041631440;received=192.168.5.6
From: "........" <sip:4170@192.168.3.17:5060>;tag=1970937568
To: "........" <sip:4170@192.168.3.17:5060>;tag=as09ebed0c
Call-ID: 0_1865556458@192.168.5.6
CSeq: 1 REGISTER
Server: FPBX-14.0.13.4(13.22.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="6c05a479"
Content-Length: 0


12:26:35.339783 IP 192.168.5.6.sip > icl.sangoma.local.sip: SIP: REGISTER sip:192.168.3.17:5060 SIP/2.0
Eh.R..@.?................>2'REGISTER sip:192.168.3.17:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK4041631440
From: "........" <sip:4170@192.168.3.17:5060>;tag=1970937568
To: "........" <sip:4170@192.168.3.17:5060>
Call-ID: 0_1865556458@192.168.5.6
CSeq: 1 REGISTER
Contact: <sip:4170@192.168.5.6:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T19P_E2 53.84.0.15
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0


12:26:35.339911 IP icl.sangoma.local.sip > 192.168.5.6.sip: SIP: SIP/2.0 401 Unauthorized
E`.0.p..@...................SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK4041631440;received=192.168.5.6
From: "........" <sip:4170@192.168.3.17:5060>;tag=1970937568
To: "........" <sip:4170@192.168.3.17:5060>;tag=as09ebed0c
Call-ID: 0_1865556458@192.168.5.6
CSeq: 1 REGISTER
Server: FPBX-14.0.13.4(13.22.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="6c05a479"
Content-Length: 0


12:26:39.370408 IP 192.168.5.6.sip > icl.sangoma.local.sip: SIP: REGISTER sip:192.168.3.17:5060 SIP/2.0
Eh.R..@.?................>2'REGISTER sip:192.168.3.17:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK4041631440
From: "........" <sip:4170@192.168.3.17:5060>;tag=1970937568
To: "........" <sip:4170@192.168.3.17:5060>
Call-ID: 0_1865556458@192.168.5.6
CSeq: 1 REGISTER
Contact: <sip:4170@192.168.5.6:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T19P_E2 53.84.0.15
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0


12:26:39.370537 IP icl.sangoma.local.sip > 192.168.5.6.sip: SIP: SIP/2.0 401 Unauthorized
E`.0....@...................SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK4041631440;received=192.168.5.6
From: "........" <sip:4170@192.168.3.17:5060>;tag=1970937568
To: "........" <sip:4170@192.168.3.17:5060>;tag=as09ebed0c
Call-ID: 0_1865556458@192.168.5.6
CSeq: 1 REGISTER
Server: FPBX-14.0.13.4(13.22.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="6c05a479"


[ded]

всё то же, до телефона не доходит ответ

Код: выделить все

IP icl.sangoma.local.sip > 192.168.5.6.sip: SIP: SIP/2.0 401 Unauthorized

после которого он должен был послать REGISTER с WWW Auth Digest + realm + nonce

А что у него на вкладке Сеть?
Можно посмотреть этот же процесс когда он в локальной подсети 192.168.3.0/24 - как проходит?
Можно посмотреть этот же процесс регистрации софтфона Zoiper из подсети 192.168.5.0/24

Прошивка кривая?

[Jugger1030]

ZoiPer:

Код: выделить все

12:50:15.802285 IP 192.168.5.6.sip > icl.sangoma.local.sip: SIP: REGISTER sip:192.168.3.17;transport=UDP SIP/2.0
E..b..@.?..#.............N..REGISTER sip:192.168.3.17;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK-524287-1---ed4b3eb4a172089f;rport
Max-Forwards: 70
Contact: <sip:4170@192.168.5.6:5060;rinstance=2e8aae3565cf7d9c;transport=UDP>
To: "4141"<sip:4170@192.168.3.17;transport=UDP>
From: "4141"<sip:4170@192.168.3.17;transport=UDP>;tag=501b182a
Call-ID: 5mWvLEyYft8y3A1TdICqlA..
CSeq: 1 REGISTER
Expires: 60
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
User-Agent: Zoiper rv2.9.15-mod
Allow-Events: presence, kpml, talk
Content-Length: 0


12:50:15.802484 IP icl.sangoma.local.sip > 192.168.5.6.sip: SIP: SIP/2.0 401 Unauthorized
E`.S....@..R.............?..SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK-524287-1---ed4b3eb4a172089f;received=192.168.5.6;rport=5060
From: "4141"<sip:4170@192.168.3.17;transport=UDP>;tag=501b182a
To: "4141"<sip:4170@192.168.3.17;transport=UDP>;tag=as32b9415f
Call-ID: 5mWvLEyYft8y3A1TdICqlA..
CSeq: 1 REGISTER
Server: FPBX-14.0.13.4(13.22.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="427badc3"
Content-Length: 0


12:50:15.869581 IP 192.168.5.6.sip > icl.sangoma.local.sip: SIP: REGISTER sip:192.168.3.17;transport=UDP SIP/2.0
E..b..@.?..#.............N..REGISTER sip:192.168.3.17;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK-524287-1---ed4b3eb4a172089f;rport
Max-Forwards: 70
Contact: <sip:4170@192.168.5.6:5060;rinstance=2e8aae3565cf7d9c;transport=UDP>
To: "4141"<sip:4170@192.168.3.17;transport=UDP>
From: "4141"<sip:4170@192.168.3.17;transport=UDP>;tag=501b182a
Call-ID: 5mWvLEyYft8y3A1TdICqlA..
CSeq: 1 REGISTER
Expires: 60
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
User-Agent: Zoiper rv2.9.15-mod
Allow-Events: presence, kpml, talk
Content-Length: 0


12:50:15.869713 IP icl.sangoma.local.sip > 192.168.5.6.sip: SIP: SIP/2.0 401 Unauthorized
E`.S....@................?..SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK-524287-1---ed4b3eb4a172089f;received=192.168.5.6;rport=5060
From: "4141"<sip:4170@192.168.3.17;transport=UDP>;tag=501b182a
To: "4141"<sip:4170@192.168.3.17;transport=UDP>;tag=as32b9415f
Call-ID: 5mWvLEyYft8y3A1TdICqlA..
CSeq: 1 REGISTER
Server: FPBX-14.0.13.4(13.22.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="427badc3"
Content-Length: 0


12:50:16.059756 IP 192.168.5.6.sip > icl.sangoma.local.sip: SIP: REGISTER sip:192.168.3.17;transport=UDP SIP/2.0
E..
..@.?..{................REGISTER sip:192.168.3.17;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK-524287-1---d485548acc913271;rport
Max-Forwards: 70
Contact: <sip:4170@192.168.5.6:5060;rinstance=2e8aae3565cf7d9c;transport=UDP>
To: "4141"<sip:4170@192.168.3.17;transport=UDP>
From: "4141"<sip:4170@192.168.3.17;transport=UDP>;tag=501b182a
Call-ID: 5mWvLEyYft8y3A1TdICqlA..
CSeq: 2 REGISTER
Expires: 60
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
User-Agent: Zoiper rv2.9.15-mod
Authorization: Digest username="4170",realm="asterisk",nonce="427badc3",uri="sip:192.168.3.17;transport=UDP",response="5d0afb1b64500157aca0ba27156c49ed",algorithm=MD5
Allow-Events: presence, kpml, talk
Content-Length: 0


12:50:16.060333 IP icl.sangoma.local.sip > 192.168.5.6.sip: SIP: OPTIONS sip:4170@192.168.5.6:5060;rinstance=2e8aae3565cf7d9c;transport=UDP SIP/2.0
E`......@..u.............._.OPTIONS sip:4170@192.168.5.6:5060;rinstance=2e8aae3565cf7d9c;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.3.17:5060;branch=z9hG4bK098d451f
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.3.17>;tag=as5b592237
To: <sip:4170@192.168.5.6:5060;rinstance=2e8aae3565cf7d9c;transport=UDP>
Contact: <sip:Unknown@192.168.3.17:5060>
Call-ID: 3a63cc154d45641862bdda8743ddfec9@192.168.3.17:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.4(13.22.0)
Date: Wed, 14 Aug 2019 08:50:16 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


12:50:16.060437 IP icl.sangoma.local.sip > 192.168.5.6.sip: SIP: SIP/2.0 200 OK
E`......@..~.............u..SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.5.6:5060;branch=z9hG4bK-524287-1---d485548acc913271;received=192.168.5.6;rport=5060
From: "4141"<sip:4170@192.168.3.17;transport=UDP>;tag=501b182a
To: "4141"<sip:4170@192.168.3.17;transport=UDP>;tag=as32b9415f
Call-ID: 5mWvLEyYft8y3A1TdICqlA..
CSeq: 2 REGISTER
Server: FPBX-14.0.13.4(13.22.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 60
Contact: <sip:4170@192.168.5.6:5060;rinstance=2e8aae3565cf7d9c;transport=UDP>;expires=60
Date: Wed, 14 Aug 2019 08:50:16 GMT
Content-Length: 0


12:50:16.060644 IP icl.sangoma.local.sip > 192.168.5.6.sip: SIP: NOTIFY sip:4170@192.168.5.6:5060;rinstance=2e8aae3565cf7d9c;transport=UDP SIP/2.0
E`......@..p...............3NOTIFY sip:4170@192.168.5.6:5060;rinstance=2e8aae3565cf7d9c;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.3.17:5060;branch=z9hG4bK2b543a4f
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.3.17>;tag=as27e60969
To: <sip:4170@192.168.5.6:5060;rinstance=2e8aae3565cf7d9c;transport=UDP>
Contact: <sip:Unknown@192.168.3.17:5060>
Call-ID: 6e81539306af41e9326bb9f446504a8b@192.168.3.17:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-14.0.13.4(13.22.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 87

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

12:50:16.229782 IP 192.168.5.6.sip > icl.sangoma.local.sip: SIP: SIP/2.0 200 OK
E.....@.?..................bSIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.3.17:5060;branch=z9hG4bK098d451f
Contact: <sip:192.168.5.6:5060>
To: <sip:4170@192.168.5.6:5060;rinstance=2e8aae3565cf7d9c;transport=UDP>;tag=b964393e
From: "Unknown" <sip:Unknown@192.168.3.17>;tag=as5b592237
Call-ID: 3a63cc154d45641862bdda8743ddfec9@192.168.3.17:5060
CSeq: 102 OPTIONS
Accept: application/sdp, application/sdp
Accept-Language: en
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, outbound, path, X-cisco-serviceuri
User-Agent: Zoiper rv2.9.15-mod
Allow-Events: presence, kpml, talk
Content-Length: 0


12:50:16.249429 IP 192.168.5.6.sip > icl.sangoma.local.sip: SIP: SIP/2.0 200 OK
E.....@.?..................2SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.3.17:5060;branch=z9hG4bK2b543a4f
Contact: <sip:192.168.5.6:5060>
To: <sip:4170@192.168.5.6:5060;rinstance=2e8aae3565cf7d9c;transport=UDP>;tag=027cd470
From: "Unknown" <sip:Unknown@192.168.3.17>;tag=as27e60969
Call-ID: 6e81539306af41e9326bb9f446504a8b@192.168.3.17:5060
CSeq: 102 NOTIFY
User-Agent: Zoiper rv2.9.15-mod
Content-Length: 0


вот по локалке:

Код: выделить все

13:10:32.744150 IP 192.168.105.2.sip > icl.sangoma.local.sip: SIP: REGISTER sip:192.168.3.17:5060 SIP/2.0
Eh.W..@.?.K...i..........C.sREGISTER sip:192.168.3.17:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.105.2:5060;branch=z9hG4bK1853050567
From: "........" <sip:4170@192.168.3.17:5060>;tag=115329708
To: "........" <sip:4170@192.168.3.17:5060>
Call-ID: 0_3808308965@192.168.105.2
CSeq: 1 REGISTER
Contact: <sip:4170@192.168.105.2:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T19P_E2 53.84.0.15
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0


13:10:32.744346 IP icl.sangoma.local.sip > 192.168.105.2.sip: SIP: SIP/2.0 401 Unauthorized
E`.5B...@.H.......i......!..SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.105.2:5060;branch=z9hG4bK1853050567;received=192.168.105.2
From: "........" <sip:4170@192.168.3.17:5060>;tag=115329708
To: "........" <sip:4170@192.168.3.17:5060>;tag=as12e445f7
Call-ID: 0_3808308965@192.168.105.2
CSeq: 1 REGISTER
Server: FPBX-14.0.13.4(13.22.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="1ba65505"
Content-Length: 0


13:10:32.756106 IP 192.168.105.2.sip > icl.sangoma.local.sip: SIP: REGISTER sip:192.168.3.17:5060 SIP/2.0
Eh....@.?.K&..i............UREGISTER sip:192.168.3.17:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.105.2:5060;branch=z9hG4bK1239507359
From: "........" <sip:4170@192.168.3.17:5060>;tag=115329708
To: "........" <sip:4170@192.168.3.17:5060>
Call-ID: 0_3808308965@192.168.105.2
CSeq: 2 REGISTER
Contact: <sip:4170@192.168.105.2:5060>
Authorization: Digest username="4170", realm="asterisk", nonce="1ba65505", uri="sip:192.168.3.17:5060", response="782f9949f5ebf8f8bbd6e604624e679b", algorithm=MD5
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T19P_E2 53.84.0.15
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0


13:10:32.756641 IP icl.sangoma.local.sip > 192.168.105.2.sip: SIP: OPTIONS sip:4170@192.168.105.2:5060 SIP/2.0
E`.MB...@.H.......i......9.{OPTIONS sip:4170@192.168.105.2:5060 SIP/2.0
Via: SIP/2.0/UDP 31.173.187.189:5060;branch=z9hG4bK05faed57
Max-Forwards: 70
From: "Unknown" <sip:Unknown@31.173.187.189>;tag=as61afb5e5
To: <sip:4170@192.168.105.2:5060>
Contact: <sip:Unknown@31.173.187.189:5060>
Call-ID: 5217d75911990ab2107781b27e292532@31.173.187.189:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.4(13.22.0)
Date: Wed, 14 Aug 2019 09:10:32 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


13:10:32.756763 IP icl.sangoma.local.sip > 192.168.105.2.sip: SIP: SIP/2.0 200 OK
E`.HB...@.H.......i......49.SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.105.2:5060;branch=z9hG4bK1239507359;received=192.168.105.2
From: "........" <sip:4170@192.168.3.17:5060>;tag=115329708
To: "........" <sip:4170@192.168.3.17:5060>;tag=as12e445f7
Call-ID: 0_3808308965@192.168.105.2
CSeq: 2 REGISTER
Server: FPBX-14.0.13.4(13.22.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 3600
Contact: <sip:4170@192.168.105.2:5060>;expires=3600
Date: Wed, 14 Aug 2019 09:10:32 GMT
Content-Length: 0


13:10:32.756934 IP icl.sangoma.local.sip > 192.168.105.2.sip: SIP: NOTIFY sip:4170@192.168.105.2:5060 SIP/2.0
E`.RB...@.H.......i......>..NOTIFY sip:4170@192.168.105.2:5060 SIP/2.0
Via: SIP/2.0/UDP 31.173.187.189:5060;branch=z9hG4bK796fc99e
Max-Forwards: 70
From: "Unknown" <sip:Unknown@31.173.187.189>;tag=as432614fc
To: <sip:4170@192.168.105.2:5060>
Contact: <sip:Unknown@31.173.187.189:5060>
Call-ID: 6c367abf1f0e8b4c76d98413549956d2@31.173.187.189:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-14.0.13.4(13.22.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 89

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

13:10:32.777200 IP 192.168.105.2.sip > icl.sangoma.local.sip: SIP: SIP/2.0 200 OK
Eh.l..@.>.M...i..........XqMSIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.3.17:5060;branch=z9hG4bK05faed57
From: "Unknown" <sip:Unknown@192.168.3.17:5060>;tag=as61afb5e5
To: <sip:4170@192.168.105.2:5060>;tag=2342449824
Call-ID: 5217d75911990ab2107781b27e292532@31.173.187.189:5060
CSeq: 102 OPTIONS
User-Agent: Yealink SIP-T19P_E2 53.84.0.15
Content-Length: 0


13:10:32.798049 IP 192.168.105.2.sip > icl.sangoma.local.sip: SIP: SIP/2.0 200 OK
Eh.k..@.>.M...i..........W..SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.3.17:5060;branch=z9hG4bK796fc99e
From: "Unknown" <sip:Unknown@192.168.3.17:5060>;tag=as432614fc
To: <sip:4170@192.168.105.2:5060>;tag=1887240658
Call-ID: 6c367abf1f0e8b4c76d98413549956d2@31.173.187.189:5060
CSeq: 102 NOTIFY
User-Agent: Yealink SIP-T19P_E2 53.84.0.15
Content-Length: 0


[Jugger1030]

Прошивка кривая?

прошивка с офсайта, есть еще аппарат грандстрим, такая же картина

[Jugger1030]

А что у него на вкладке Сеть?

[ded]

1) А расскажите мне, как это может быть: с адреса 192.168.5.6 регистрировался аппаратный Yealink T19
и с того же адреса вы умудряетесь зарегистрировать софтфон Zoiper? Но Zoiper не может быть на аппаратном телефоне, как минимум должен быть на другом устройстве - смартфоне или компьютере.
??

2) Сетевые настройки предполагалось увидеть когда Yealink T19 в туннеле OpenVPN.