TAU-32M.IP ошибки аутентификации
Добавлено: 27 мар 2014 22:24
Имеется всё та же ТАУ 32 с модулем 8 FXO, прошивка последняя на сегодня. Порты FXO имеют номера 1824...1831, зарегистрированы на астериск 11.6
Как то проверяя новые фичи заметил, что при входящем звонке из PSTN на 1829, где прописан хотлайн 1836, не проходит аутентификация. Естественно входящему абоненту "занято". Стал разбираться, записал дамп ( вышлю по запросу).Оказалось, что 1829 не аутентифицируется, астериск ругается на дайджест: (192.168.18.220- астериск, 192.168.18.230- тау)
=============================================
[2014-03-27 18:22:23] WARNING[1842][C-0000029c] chan_sip.c: username mismatch, have <1824>, digest has <1829>
[2014-03-27 18:22:23] NOTICE[1842][C-0000029c] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=eaDc0e7ZNB3vD
[2014-03-27 18:23:02] VERBOSE[1766] asterisk.c: -- Remote UNIX connection
[2014-03-27 18:23:44] WARNING[1842][C-0000029d] chan_sip.c: username mismatch, have <1825>, digest has <1829>
[2014-03-27 18:23:44] NOTICE[1842][C-0000029d] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=gvZX3486FXF2m
=============================================
В принципе случаи единичные, можно и не заметить. Однако это не так!Вот лог за сегодня:
=============================================
[2014-03-27 09:18:46] NOTICE[1842][C-00000161] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=py2ry3gBrc3mm
[2014-03-27 09:24:26] NOTICE[1842][C-00000163] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=aKv8101Hyy0ac
[2014-03-27 09:24:51] NOTICE[1842][C-00000164] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=c5et5p3rrgDgK
[2014-03-27 09:25:17] NOTICE[1842][C-00000165] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=De8j7HmvNS32e
[2014-03-27 09:26:50] NOTICE[1842][C-00000166] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=g9KXc366cm6tH
[2014-03-27 09:28:18] NOTICE[1842][C-00000167] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=HjDpeyQaaXvDD
[2014-03-27 09:28:50] NOTICE[1842][C-00000169] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=K4Z7HmSH4e9jm
[2014-03-27 09:30:24] NOTICE[1842][C-0000016a] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=mDS0KFaN1QZ5F
[2014-03-27 09:30:51] NOTICE[1842][C-0000016b] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=NpjSNaUry0NrB
[2014-03-27 09:31:06] NOTICE[1842][C-0000016c] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=pZBjQ5BvU9BBQ
[2014-03-27 09:31:34] NOTICE[1842][C-0000016d] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=Q84aS0vZrj2Xj
[2014-03-27 09:31:50] NOTICE[1842][C-0000016e] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=rHy3tUD3NUrge
[2014-03-27 09:36:16] NOTICE[1842][C-0000016f] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=t3gNyHFagD5NN
[2014-03-27 09:36:50] NOTICE[1842][C-00000170] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=Ucae0c0DDpU8g
[2014-03-27 09:38:13] NOTICE[1842][C-00000171] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=vN3617gHaZHUc
[2014-03-27 10:40:56] NOTICE[1842][C-0000019c] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=83428FHXe4e8c
[2014-03-27 10:41:25] NOTICE[1842][C-0000019d] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=apQmc6j48NUDm
[2014-03-27 10:42:45] NOTICE[1842][C-0000019f] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=c895FvmB377jB
[2014-03-27 10:43:08] NOTICE[1842][C-000001a0] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=DH3yHQ5e0gy5p
[2014-03-27 10:43:31] NOTICE[1842][C-000001a1] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=etvQKjpjXSmrj
[2014-03-27 10:43:54] NOTICE[1842][C-000001a3] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=gcF9p8QSQB1XS
[2014-03-27 10:44:22] NOTICE[1842][C-000001a4] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=HN81r38vmmQgN
[2014-03-27 10:44:57] NOTICE[1842][C-000001a5] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=jy1ttyS0HXD3g
[2014-03-27 10:45:23] NOTICE[1842][C-000001a6] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=K7tKvSa4e63Nc
[2014-03-27 10:47:20] NOTICE[1842][C-000001a7] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=NSD5ZFcB9QgUK
[2014-03-27 10:47:50] NOTICE[1842][C-000001a8] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=p26X1aXe606DF
[2014-03-27 10:48:17] NOTICE[1842][C-000001a9] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=QB0p35Dj39v0a
[2014-03-27 10:48:43] NOTICE[1842][C-000001aa] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=rmSF50yN0jKKp
[2014-03-27 10:49:08] NOTICE[1842][C-000001ab] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=SXj86UFSXU95H
[2014-03-27 10:49:34] NOTICE[1842][C-000001ac] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=t6B18p0vt4ZrD
[2014-03-27 10:55:41] NOTICE[1842][C-000001af] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=0v3NKS5H9S58j
[2014-03-27 18:22:23] NOTICE[1842][C-0000029c] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=eaDc0e7ZNB3vD
[2014-03-27 18:23:44] NOTICE[1842][C-0000029d] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=gvZX3486FXF2m
[2014-03-27 18:28:06] NOTICE[1842][C-0000029f] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=jejF7taeaFv7B
======================================================
Схожая проблема была с длинком DVG6004, там тоже отваливалась регистрация, но посерьезнее. Помогала перезагрузка астериск, но на некоторое время. Выставление параметра pedantic=no решило проблему на длинке. А в нашем случае-нет, опция уже стоит.
Перегрузка астериска я думаю и в нашем случае на время решит проблему, но это не выход.
Как мне объяснили коллеги, астериск ведет историю сгенерированных дайджестов и проверяет, был ли он уже сгенерирован. RFC недостаточно ясно говорит о времени устаревания, отсюда и конфликт.Как то так.
Итак,коллеги, что делать? Специально пока не буду ребутить шлюз, жду реакции
Как то проверяя новые фичи заметил, что при входящем звонке из PSTN на 1829, где прописан хотлайн 1836, не проходит аутентификация. Естественно входящему абоненту "занято". Стал разбираться, записал дамп ( вышлю по запросу).Оказалось, что 1829 не аутентифицируется, астериск ругается на дайджест: (192.168.18.220- астериск, 192.168.18.230- тау)
=============================================
[2014-03-27 18:22:23] WARNING[1842][C-0000029c] chan_sip.c: username mismatch, have <1824>, digest has <1829>
[2014-03-27 18:22:23] NOTICE[1842][C-0000029c] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=eaDc0e7ZNB3vD
[2014-03-27 18:23:02] VERBOSE[1766] asterisk.c: -- Remote UNIX connection
[2014-03-27 18:23:44] WARNING[1842][C-0000029d] chan_sip.c: username mismatch, have <1825>, digest has <1829>
[2014-03-27 18:23:44] NOTICE[1842][C-0000029d] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=gvZX3486FXF2m
=============================================
В принципе случаи единичные, можно и не заметить. Однако это не так!Вот лог за сегодня:
=============================================
[2014-03-27 09:18:46] NOTICE[1842][C-00000161] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=py2ry3gBrc3mm
[2014-03-27 09:24:26] NOTICE[1842][C-00000163] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=aKv8101Hyy0ac
[2014-03-27 09:24:51] NOTICE[1842][C-00000164] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=c5et5p3rrgDgK
[2014-03-27 09:25:17] NOTICE[1842][C-00000165] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=De8j7HmvNS32e
[2014-03-27 09:26:50] NOTICE[1842][C-00000166] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=g9KXc366cm6tH
[2014-03-27 09:28:18] NOTICE[1842][C-00000167] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=HjDpeyQaaXvDD
[2014-03-27 09:28:50] NOTICE[1842][C-00000169] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=K4Z7HmSH4e9jm
[2014-03-27 09:30:24] NOTICE[1842][C-0000016a] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=mDS0KFaN1QZ5F
[2014-03-27 09:30:51] NOTICE[1842][C-0000016b] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=NpjSNaUry0NrB
[2014-03-27 09:31:06] NOTICE[1842][C-0000016c] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=pZBjQ5BvU9BBQ
[2014-03-27 09:31:34] NOTICE[1842][C-0000016d] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=Q84aS0vZrj2Xj
[2014-03-27 09:31:50] NOTICE[1842][C-0000016e] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=rHy3tUD3NUrge
[2014-03-27 09:36:16] NOTICE[1842][C-0000016f] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=t3gNyHFagD5NN
[2014-03-27 09:36:50] NOTICE[1842][C-00000170] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=Ucae0c0DDpU8g
[2014-03-27 09:38:13] NOTICE[1842][C-00000171] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=vN3617gHaZHUc
[2014-03-27 10:40:56] NOTICE[1842][C-0000019c] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=83428FHXe4e8c
[2014-03-27 10:41:25] NOTICE[1842][C-0000019d] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=apQmc6j48NUDm
[2014-03-27 10:42:45] NOTICE[1842][C-0000019f] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=c895FvmB377jB
[2014-03-27 10:43:08] NOTICE[1842][C-000001a0] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=DH3yHQ5e0gy5p
[2014-03-27 10:43:31] NOTICE[1842][C-000001a1] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=etvQKjpjXSmrj
[2014-03-27 10:43:54] NOTICE[1842][C-000001a3] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=gcF9p8QSQB1XS
[2014-03-27 10:44:22] NOTICE[1842][C-000001a4] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=HN81r38vmmQgN
[2014-03-27 10:44:57] NOTICE[1842][C-000001a5] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=jy1ttyS0HXD3g
[2014-03-27 10:45:23] NOTICE[1842][C-000001a6] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=K7tKvSa4e63Nc
[2014-03-27 10:47:20] NOTICE[1842][C-000001a7] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=NSD5ZFcB9QgUK
[2014-03-27 10:47:50] NOTICE[1842][C-000001a8] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=p26X1aXe606DF
[2014-03-27 10:48:17] NOTICE[1842][C-000001a9] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=QB0p35Dj39v0a
[2014-03-27 10:48:43] NOTICE[1842][C-000001aa] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=rmSF50yN0jKKp
[2014-03-27 10:49:08] NOTICE[1842][C-000001ab] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=SXj86UFSXU95H
[2014-03-27 10:49:34] NOTICE[1842][C-000001ac] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=t6B18p0vt4ZrD
[2014-03-27 10:55:41] NOTICE[1842][C-000001af] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=0v3NKS5H9S58j
[2014-03-27 18:22:23] NOTICE[1842][C-0000029c] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=eaDc0e7ZNB3vD
[2014-03-27 18:23:44] NOTICE[1842][C-0000029d] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=gvZX3486FXF2m
[2014-03-27 18:28:06] NOTICE[1842][C-0000029f] chan_sip.c: Failed to authenticate device <sip:192.168.18.220>;tag=jejF7taeaFv7B
======================================================
Схожая проблема была с длинком DVG6004, там тоже отваливалась регистрация, но посерьезнее. Помогала перезагрузка астериск, но на некоторое время. Выставление параметра pedantic=no решило проблему на длинке. А в нашем случае-нет, опция уже стоит.
Перегрузка астериска я думаю и в нашем случае на время решит проблему, но это не выход.
Как мне объяснили коллеги, астериск ведет историю сгенерированных дайджестов и проверяет, был ли он уже сгенерирован. RFC недостаточно ясно говорит о времени устаревания, отсюда и конфликт.Как то так.
Итак,коллеги, что делать? Специально пока не буду ребутить шлюз, жду реакции