Redemarrer poste YEALINK T41 ou T42

Added by Pascal LANGLOIS 9 months ago

Bonjour,

Comment peut on faire pour redemarrer un poste a distance par WAZO ?
Merci de votre aide


Replies (14)

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Etienne Lessard 9 months ago

S'il est déjà approvisionné par Wazo, tu peux cliquer sur le bouton synchronize de l'interface web, dans la page des terminaisons . Ca ne fait pas un reboot techniquement, ca fait juste demander au téléphone de mettre à jour sa config, et il va redémarrer au besoin (il est capable d'appliquer la plupart des modifications sans avoir a rebooter).

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Pascal LANGLOIS 9 months ago

Merci Etienne,

En fait je veux seulement rajouter ou modifier le label d une des 6 BLF du T41 et si je fais synchronize de l'interface web, dans la page des terminaisons comme tu me dis, la modif n est prise en compte si je fais un retour usine manuellemnt du T41,un reboot manuel simple du t41 ne change rien non plus, il faut un reboot usine manuel usine pour qu ela modification soit prise en compte.

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Etienne Lessard 9 months ago

En fait je veux seulement rajouter ou modifier le label d une des 6 BLF du T41 et si je fais synchronize de l'interface web, dans la page des terminaisons comme tu me dis, la modif n est prise en compte

Comment tu fais ta modification aux labels des touches de fonction ? Via un template custom ?

Ca me semble effectivement anormal que tu aies à faire un factory reset, à moins que tu configures manuellement certaines choses directement sur l'interface web du Yealink ou via l'interface du téléphone (PUI), ou qqch du genre.

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Pascal LANGLOIS 9 months ago

Non, je fais la modif de changement de nom dans UTILISTAEURS , onglet TOUCHES

Parc contre par erreur j ai initialisé en mode auto prov et je voudrais repasser en mode normal?

LABEL.PNG (20.6 KB)

AUTO PROV.PNG (4.21 KB)

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Sébastien Duthil 9 months ago

Pour réassocier le poste à un utilisateur, tu peux composer le code de provisioning sur le poste (le code apparait dans la liste des utilisateurs) ou dans le formulaire utilisateur associer la ligne à une terminaison, puis redémarrer le poste.

Tu pourrais nous donner les fichiers /var/log/xivo-confd.log et /var/log/xivo-provd.log après avoir changé une touche de fonction et synchronisé le poste? Tu peux nous indiquer l'heure des manipulations (ça nous aidera à trouver le bon endroit dans le fichier) ?

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Pascal LANGLOIS 8 months ago

Bonjour Sebastien,
Voici les logs

/var/log/xivo-confd.log

2017-01-10 10:11:08,417 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/wizard
2017-01-10 10:11:08,419 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/wizard 200
2017-01-10 10:11:08,462 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/devices
2017-01-10 10:11:08,467 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/devices 200
2017-01-10 10:11:08,472 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/users/3/lines
2017-01-10 10:11:08,476 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/users/3/lines 200
2017-01-10 10:11:08,478 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/lines/3
2017-01-10 10:11:08,502 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/lines/3 200
2017-01-10 10:11:08,503 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/lines/3/endpoints/sip
2017-01-10 10:11:08,522 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/lines/3/endpoints/sip 200
2017-01-10 10:11:08,523 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/endpoints/sip/3
2017-01-10 10:11:08,530 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/endpoints/sip/3 200
2017-01-10 10:11:08,532 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/lines/3/extensions
2017-01-10 10:11:08,554 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/lines/3/extensions 200
2017-01-10 10:11:08,555 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/extensions/35
2017-01-10 10:11:08,563 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/extensions/35 200
2017-01-10 10:11:08,565 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/lines/3/extensions
2017-01-10 10:11:08,584 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/lines/3/extensions 200
2017-01-10 10:11:08,585 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/extensions/35
2017-01-10 10:11:08,594 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/extensions/35 200
2017-01-10 10:11:08,595 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/extensions/35
2017-01-10 10:11:08,604 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/extensions/35 200
2017-01-10 10:11:08,608 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/users/3/voicemails
2017-01-10 10:11:08,613 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/users/3/voicemails 200
2017-01-10 10:11:08,614 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/voicemails/3
2017-01-10 10:11:08,621 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/voicemails/3 200
2017-01-10 10:11:08,623 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/users/3/funckeys
2017-01-10 10:11:08,632 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/users/3/funckeys 200
2017-01-10 10:11:08,640 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/cti_profiles
2017-01-10 10:11:08,643 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/cti_profiles 200
2017-01-10 10:11:08,672 [1297] (INFO) (xivo_confd.application): PUT http://127.0.0.1:9487/1.1/users/3/funckeys with data {"keys":{"1":{"label":"HENRY","blf":true,"destination":{"type":"user","user_id":4}},"2":{"label":"CHARLES","blf":true,"destination":{"type":"user","user_id":5}},"3":{"label":"HENRI","blf":true,"destination":{"type":"user","user_id":6}},"4":{"label":"SIMON","blf":true,"destination":{"type":"user","user_id":7}}}} 
2017-01-10 10:11:08,871 [1297] (INFO) (xivo_confd): (127.0.0.1) PUT http://127.0.0.1:9487/1.1/users/3/funckeys 204
2017-01-10 10:11:08,873 [1297] (INFO) (xivo_confd.application): PUT http://127.0.0.1:9487/1.1/lines/3 with data {"protocol":"sip","context":"interne-courrouge","registrar":"default","position":"1","caller_id_name":"Anaick STANDARD","id":"3"} 
2017-01-10 10:11:09,168 [1297] (INFO) (xivo_confd): (127.0.0.1) PUT http://127.0.0.1:9487/1.1/lines/3 204
2017-01-10 10:11:09,169 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/lines/3
2017-01-10 10:11:09,194 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/lines/3 200
2017-01-10 10:11:09,195 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/lines/3/endpoints/sip
2017-01-10 10:11:09,214 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/lines/3/endpoints/sip 200
2017-01-10 10:11:09,215 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/endpoints/sip/3
2017-01-10 10:11:09,223 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/endpoints/sip/3 200
2017-01-10 10:11:09,224 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/lines/3/extensions
2017-01-10 10:11:09,242 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/lines/3/extensions 200
2017-01-10 10:11:09,243 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/extensions/35
2017-01-10 10:11:09,251 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/extensions/35 200
2017-01-10 10:11:09,253 [1297] (INFO) (xivo_confd.application): PUT http://127.0.0.1:9487/1.1/extensions/35 with data {"exten":"100","context":"interne-courrouge","id":35} 
2017-01-10 10:11:09,297 [1297] (INFO) (xivo_confd): (127.0.0.1) PUT http://127.0.0.1:9487/1.1/extensions/35 204
2017-01-10 10:11:09,298 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/lines/3/devices
2017-01-10 10:11:09,315 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/lines/3/devices 200
2017-01-10 10:11:09,317 [1297] (INFO) (xivo_confd.application): PUT http://127.0.0.1:9487/1.1/voicemails/3 with data {"name":"VM-COURROUGE","number":"1","context":"interne-courrouge","timezone":"eu-fr","password":null,"email":null,"language":"fr_FR","pager":null,"max_messages":10,"ask_password":true,"attach_audio":true,"delete_messages":false,"options":[]} 
2017-01-10 10:11:09,327 [1297] (INFO) (urllib3.connectionpool): Starting new HTTP connection (1): localhost
2017-01-10 10:11:09,500 [1297] (INFO) (xivo_confd): (127.0.0.1) PUT http://127.0.0.1:9487/1.1/voicemails/3 204
2017-01-10 10:11:09,974 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/wizard
2017-01-10 10:11:09,976 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/wizard 200
2017-01-10 10:11:10,024 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/users?view=summary
2017-01-10 10:11:10,033 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/users?view=summary 200

---- apres avoir appuyé sur le bouton synchroniser ----

2017-01-10 10:11:22,037 [1297] (INFO) (urllib3.connectionpool): Starting new HTTPS connection (1): localhost
2017-01-10 10:11:42,190 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/wizard
2017-01-10 10:11:42,193 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/wizard 200
2017-01-10 10:11:42,250 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/devices?order=ip&direction=asc
2017-01-10 10:11:42,255 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/devices?order=ip&direction=asc 200
2017-01-10 10:11:47,692 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/wizard
2017-01-10 10:11:47,694 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/wizard 200
2017-01-10 10:11:47,728 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/devices/0af559006014418e876b25d24cd361dd
2017-01-10 10:11:47,732 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/devices/0af559006014418e876b25d24cd361dd 200
2017-01-10 10:11:47,805 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/wizard
2017-01-10 10:11:47,808 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/wizard 200
2017-01-10 10:11:47,909 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/wizard
2017-01-10 10:11:47,911 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/wizard 200
2017-01-10 10:11:47,942 [1297] (INFO) (xivo_confd.application): GET http://127.0.0.1:9487/1.1/devices?order=ip&direction=asc
2017-01-10 10:11:47,947 [1297] (INFO) (xivo_confd): (127.0.0.1) GET http://127.0.0.1:9487/1.1/devices?order=ip&direction=asc 200
2017-01-10 10:11:49,043 [1297] (INFO) (urllib3.connectionpool): Starting new HTTPS connection (1): localhost

Voici les /var/log/xivo-provd.log

2017-01-10 10:11:08,460 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:07 +0000] "GET /provd/cfg_mgr/configs?q64=eyJYX3R5cGUiOiJyZWdpc3RyYXIifQ==&sort=displayname&sort_ord=ASC HTTP/1.1" 200 203 "-" "-" 
2017-01-10 10:11:08,463 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:07 +0000] "GET /provd/dev_mgr/devices?sort=ip&sort_ord=ASC HTTP/1.1" 200 656 "-" "Python-urllib/2.7" 
2017-01-10 10:11:08,464 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:07 +0000] "GET /provd/cfg_mgr/configs/0af559006014418e876b25d24cd361dd HTTP/1.1" 200 1053 "-" "Python-urllib/2.7" 
2017-01-10 10:11:08,465 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:07 +0000] "GET /provd/cfg_mgr/configs/4f8be20d0f7c4249a4a08e3337178017 HTTP/1.1" 200 747 "-" "Python-urllib/2.7" 
2017-01-10 10:11:08,719 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:07 +0000] "GET /provd/dev_mgr/devices/0af559006014418e876b25d24cd361dd HTTP/1.1" 200 331 "-" "Python-urllib/2.7" 
2017-01-10 10:11:08,720 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:07 +0000] "GET /provd/cfg_mgr/configs/0af559006014418e876b25d24cd361dd HTTP/1.1" 200 1053 "-" "Python-urllib/2.7" 
2017-01-10 10:11:08,840 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:07 +0000] "GET /provd/cfg_mgr/configs?q=%7B%22X_type%22%3A+%22registrar%22%2C+%22id%22%3A+%22default%22%7D HTTP/1.1" 200 203 "-" "Python-urllib/2.7" 
2017-01-10 10:11:08,856 [1055] (INFO) (provd.app): Updating device 0af559006014418e876b25d24cd361dd
2017-01-10 10:11:08,857 [1055] (INFO) (provd.app): Not updating device 0af559006014418e876b25d24cd361dd: not changed
2017-01-10 10:11:08,857 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:07 +0000] "PUT /provd/dev_mgr/devices/0af559006014418e876b25d24cd361dd HTTP/1.1" 204 - "-" "Python-urllib/2.7" 
2017-01-10 10:11:08,858 [1055] (INFO) (provd.app): Updating config 0af559006014418e876b25d24cd361dd
2017-01-10 10:11:08,859 [1055] (INFO) (provd.app): Deconfiguring device 0af559006014418e876b25d24cd361dd with plugin xivo-yealink-v80
2017-01-10 10:11:08,859 [1055] (INFO) (provd.app): Configuring device 0af559006014418e876b25d24cd361dd with plugin xivo-yealink-v80
2017-01-10 10:11:08,859 [1055] (INFO) (provd.plugins): Using template T41P.tpl
2017-01-10 10:11:08,860 [1055] (INFO) (provd.plugins): Writing template to file "/var/lib/xivo-provd/plugins/xivo-yealink-v80/var/tftpboot/001565963783.cfg" 
2017-01-10 10:11:08,860 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:07 +0000] "PUT /provd/cfg_mgr/configs/0af559006014418e876b25d24cd361dd HTTP/1.1" 204 - "-" "Python-urllib/2.7" 
2017-01-10 10:11:08,967 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:07 +0000] "GET /provd/cfg_mgr/configs?q=%7B%22X_type%22%3A+%22registrar%22%7D HTTP/1.1" 200 203 "-" "Python-urllib/2.7" 
2017-01-10 10:11:08,985 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:08 +0000] "GET /provd/dev_mgr/devices/0af559006014418e876b25d24cd361dd HTTP/1.1" 200 331 "-" "Python-urllib/2.7" 
2017-01-10 10:11:08,987 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:08 +0000] "GET /provd/cfg_mgr/configs/0af559006014418e876b25d24cd361dd HTTP/1.1" 200 989 "-" "Python-urllib/2.7" 
2017-01-10 10:11:09,109 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:08 +0000] "GET /provd/cfg_mgr/configs?q=%7B%22X_type%22%3A+%22registrar%22%2C+%22id%22%3A+%22default%22%7D HTTP/1.1" 200 203 "-" "Python-urllib/2.7" 
2017-01-10 10:11:09,126 [1055] (INFO) (provd.app): Updating device 0af559006014418e876b25d24cd361dd
2017-01-10 10:11:09,158 [1055] (INFO) (provd.app): Not updating device 0af559006014418e876b25d24cd361dd: not changed
2017-01-10 10:11:09,159 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:08 +0000] "PUT /provd/dev_mgr/devices/0af559006014418e876b25d24cd361dd HTTP/1.1" 204 - "-" "Python-urllib/2.7" 
2017-01-10 10:11:09,160 [1055] (INFO) (provd.app): Updating config 0af559006014418e876b25d24cd361dd
2017-01-10 10:11:09,160 [1055] (INFO) (provd.app): config has not changed, ignoring update
2017-01-10 10:11:09,160 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:08 +0000] "PUT /provd/cfg_mgr/configs/0af559006014418e876b25d24cd361dd HTTP/1.1" 204 - "-" "Python-urllib/2.7" 

---- apres avoir appuyé sur le bouton synchroniser ----

017-01-10 10:11:47,736 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:46 +0000] "GET /provd/pg_mgr/plugins/xivo-yealink-v80/configure HTTP/1.1" 404 153 "-" "-" 
2017-01-10 10:11:47,736 [1055] (INFO) (provd.app): Synchronizing device 0af559006014418e876b25d24cd361dd
2017-01-10 10:11:47,737 [1055] (INFO) (provd.app): Synchronizing device 0af559006014418e876b25d24cd361dd with plugin xivo-yealink-v80
2017-01-10 10:11:47,737 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:46 +0000] "POST /provd/dev_mgr/synchronize HTTP/1.1" 201 - "-" "-" 
2017-01-10 10:11:47,840 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:46 +0000] "GET /provd/dev_mgr/synchronize/42 HTTP/1.1" 200 20 "-" "-" 
2017-01-10 10:11:47,841 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:46 +0000] "DELETE /provd/dev_mgr/synchronize/42 HTTP/1.1" 204 - "-" "-" 
2017-01-10 10:11:47,943 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:46 +0000] "GET /provd/dev_mgr/devices?sort=ip&sort_ord=ASC HTTP/1.1" 200 656 "-" "Python-urllib/2.7" 
2017-01-10 10:11:47,944 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:46 +0000] "GET /provd/cfg_mgr/configs/0af559006014418e876b25d24cd361dd HTTP/1.1" 200 989 "-" "Python-urllib/2.7" 
2017-01-10 10:11:47,945 [1055] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:09:11:46 +0000] "GET /provd/cfg_mgr/configs/4f8be20d0f7c4249a4a08e3337178017 HTTP/1.1" 200 747 "-" "Python-urllib/2.7" 

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Sébastien Duthil 8 months ago

OK, pas d'erreur en vue, mais on ne voit pas le téléphone demander son fichier de config après le clic sur "synchroniser"... Dans la console Asterisk, vois-tu des erreurs à ce moment-là?
Aussi, est-ce que ton téléphone est derrière un NAT, du point de vue du serveur Wazo?

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Pascal LANGLOIS 8 months ago

oui le phone est dernier un nat du point de vu wazo

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Etienne Lessard 8 months ago

Il y a quelques limitations connues avec le serveur d'approvisionnement et les téléphones derrière un NAT, bien que j'ai l'impression que ces limitations ne sont pas liés à ton problème:

Sinon, comme Sébastien a demandé, vois-tu des erreurs dans la console Asterisk au moment de la synchronisation (si c'est un message de retransmission, il va s'afficher seulement une 30aine de seconde plus tard) ?

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Christopher LEAL 8 months ago

Bonjour,

Je suis le collègue de Pascal

Effectivement on reçois un [Jan 10 19:15:55] WARNING1491: chan_sip.c:4071 retrans_pkt: Retransmission timeout reached on transmission b7e340bf622ab80e51f046c95e4d5baa for seqno 1 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions au bout de 30 sec,

Voici la trame SIP lorsque que l'on fait une demande de synchro :

[Jan 10 19:05:41] Scheduling destruction of SIP dialog '4d2872b34e698e8d07dcbcd461a0a06e@REMOTEIP:5060' in 32000 ms (Method: NOTIFY)
[Jan 10 19:05:41] Reliably Transmitting (NAT) to 90.62.22.40:1024:
[Jan 10 19:05:41] NOTIFY sip:5eobbx4f@192.168.1.12:5060 SIP/2.0
[Jan 10 19:05:41] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK5282e737;rport
[Jan 10 19:05:41] Max-Forwards: 70
[Jan 10 19:05:41] From: "wazo" <sip:wazo@REMOTEIP>;tag=as76db1d29
[Jan 10 19:05:41] To: <sip:5eobbx4f@192.168.1.12:5060>
[Jan 10 19:05:41] Contact: <sip:wazo@REMOTEIP:5060>
[Jan 10 19:05:41] Call-ID: 4d2872b34e698e8d07dcbcd461a0a06e@REMOTEIP:5060
[Jan 10 19:05:41] CSeq: 102 NOTIFY
[Jan 10 19:05:41] User-Agent: Wazo PBX
[Jan 10 19:05:41] Date: Tue, 10 Jan 2017 18:05:41 GMT
[Jan 10 19:05:41] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
[Jan 10 19:05:41] Supported: replaces, timer
[Jan 10 19:05:41] Subscription-State: terminated
[Jan 10 19:05:41] Event: check-sync
[Jan 10 19:05:41] Content-Length: 0
[Jan 10 19:05:41] 
[Jan 10 19:05:41] 
[Jan 10 19:05:41] ---
[Jan 10 19:05:41] 
[Jan 10 19:05:41] <--- SIP read from UDP:90.62.22.40:1024 --->
[Jan 10 19:05:41] SIP/2.0 200 OK
[Jan 10 19:05:41] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK5282e737;rport=5060
[Jan 10 19:05:41] From: "wazo" <sip:wazo@REMOTEIP>;tag=as76db1d29
[Jan 10 19:05:41] To: <sip:5eobbx4f@192.168.1.12:5060>;tag=2019916409
[Jan 10 19:05:41] Call-ID: 4d2872b34e698e8d07dcbcd461a0a06e@REMOTEIP:5060
[Jan 10 19:05:41] CSeq: 102 NOTIFY
[Jan 10 19:05:41] User-Agent: Yealink SIP-T41P 36.80.0.95
[Jan 10 19:05:41] Content-Length: 0
[Jan 10 19:05:41] 
[Jan 10 19:05:41] 
[Jan 10 19:05:41] <------------->
[Jan 10 19:05:41] --- (8 headers 0 lines) ---
[Jan 10 19:05:41] Really destroying SIP dialog '4d2872b34e698e8d07dcbcd461a0a06e@REMOTEIP:5060' Method: NOTIFY
[Jan 10 19:05:46] 
[Jan 10 19:05:46] <--- SIP read from UDP:90.62.22.40:5060 --->
[Jan 10 19:05:46] REGISTER sip:REMOTEIP SIP/2.0
[Jan 10 19:05:46] Via: SIP/2.0/UDP 192.168.1.11:5060;branch=z9hG4bK66f5d31b556aa2914d939018ccae1c05;rport
[Jan 10 19:05:46] From:  <sip:m9i1bnpw@REMOTEIP>;tag=3852329386
[Jan 10 19:05:46] To:  <sip:m9i1bnpw@REMOTEIP>
[Jan 10 19:05:46] Call-ID: 4101722640@192_168_1_16
[Jan 10 19:05:46] CSeq: 377 REGISTER
[Jan 10 19:05:46] Contact: <sip:m9i1bnpw@192.168.1.11:5060>
[Jan 10 19:05:46] Max-Forwards: 70
[Jan 10 19:05:46] User-Agent: A510 IP/42.207.00.000.000
[Jan 10 19:05:46] Expires: 180
[Jan 10 19:05:46] Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, SUBSCRIBE, NOTIFY, REFER
[Jan 10 19:05:46] Content-Length: 0
[Jan 10 19:05:46] 
[Jan 10 19:05:46] 
[Jan 10 19:05:46] <------------->
[Jan 10 19:05:46] --- (12 headers 0 lines) ---
[Jan 10 19:05:46] Sending to 90.62.22.40:5060 (no NAT)
[Jan 10 19:05:46] Sending to 90.62.22.40:5060 (no NAT)
[Jan 10 19:05:46] 
[Jan 10 19:05:46] <--- Transmitting (NAT) to 90.62.22.40:5060 --->
[Jan 10 19:05:46] SIP/2.0 401 Unauthorized
[Jan 10 19:05:46] Via: SIP/2.0/UDP 192.168.1.11:5060;branch=z9hG4bK66f5d31b556aa2914d939018ccae1c05;received=90.62.22.40;rport=5060
[Jan 10 19:05:46] From: <sip:m9i1bnpw@REMOTEIP>;tag=3852329386
[Jan 10 19:05:46] To: <sip:m9i1bnpw@REMOTEIP>;tag=as575fa198
[Jan 10 19:05:46] Call-ID: 4101722640@192_168_1_16
[Jan 10 19:05:46] CSeq: 377 REGISTER
[Jan 10 19:05:46] Server: Wazo PBX
[Jan 10 19:05:46] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
[Jan 10 19:05:46] Supported: replaces, timer
[Jan 10 19:05:46] WWW-Authenticate: Digest algorithm=MD5, realm="wazo", nonce="265e24fb" 
[Jan 10 19:05:46] Content-Length: 0
[Jan 10 19:05:46] 
[Jan 10 19:05:46] 
[Jan 10 19:05:46] <------------>
[Jan 10 19:05:46] Scheduling destruction of SIP dialog '4101722640@192_168_1_16' in 32000 ms (Method: REGISTER)
[Jan 10 19:05:46] 
[Jan 10 19:05:46] <--- SIP read from UDP:90.62.22.40:5060 --->
[Jan 10 19:05:46] REGISTER sip:REMOTEIP SIP/2.0
[Jan 10 19:05:46] Via: SIP/2.0/UDP 192.168.1.11:5060;branch=z9hG4bK2b05366c7eefd8e3c804afe9d6704327;rport
[Jan 10 19:05:46] From:  <sip:m9i1bnpw@REMOTEIP>;tag=3852329386
[Jan 10 19:05:46] To:  <sip:m9i1bnpw@REMOTEIP>
[Jan 10 19:05:46] Call-ID: 4101722640@192_168_1_16
[Jan 10 19:05:46] CSeq: 378 REGISTER
[Jan 10 19:05:46] Contact: <sip:m9i1bnpw@192.168.1.11:5060>
[Jan 10 19:05:46] Authorization: Digest username="m9i1bnpw", realm="wazo", algorithm=MD5, uri="sip:REMOTEIP", nonce="265e24fb", response="f90ad0db4d2f34b326ea3cb8a5ef6d2c" 
[Jan 10 19:05:46] Max-Forwards: 70
[Jan 10 19:05:46] User-Agent: A510 IP/42.207.00.000.000
[Jan 10 19:05:46] Expires: 180
[Jan 10 19:05:46] Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, SUBSCRIBE, NOTIFY, REFER
[Jan 10 19:05:46] Content-Length: 0
[Jan 10 19:05:46] 
[Jan 10 19:05:46] 
[Jan 10 19:05:46] <------------->
[Jan 10 19:05:46] --- (13 headers 0 lines) ---
[Jan 10 19:05:46] Sending to 90.62.22.40:5060 (NAT)
[Jan 10 19:05:46] Reliably Transmitting (NAT) to 90.62.22.40:5060:
[Jan 10 19:05:46] OPTIONS sip:m9i1bnpw@192.168.1.11:5060 SIP/2.0
[Jan 10 19:05:46] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK50c87c78;rport
[Jan 10 19:05:46] Max-Forwards: 70
[Jan 10 19:05:46] From: "wazo" <sip:wazo@REMOTEIP>;tag=as69e2e014
[Jan 10 19:05:46] To: <sip:m9i1bnpw@192.168.1.11:5060>
[Jan 10 19:05:46] Contact: <sip:wazo@REMOTEIP:5060>
[Jan 10 19:05:46] Call-ID: 4fb6f82b0628385d7fed384e55409b16@REMOTEIP:5060
[Jan 10 19:05:46] CSeq: 102 OPTIONS
[Jan 10 19:05:46] User-Agent: Wazo PBX
[Jan 10 19:05:46] Date: Tue, 10 Jan 2017 18:05:46 GMT
[Jan 10 19:05:46] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
[Jan 10 19:05:46] Supported: replaces, timer
[Jan 10 19:05:46] Content-Length: 0
[Jan 10 19:05:46] 
[Jan 10 19:05:46] 
[Jan 10 19:05:46] ---
[Jan 10 19:05:46] 
[Jan 10 19:05:46] <--- Transmitting (NAT) to 90.62.22.40:5060 --->
[Jan 10 19:05:46] SIP/2.0 200 OK
[Jan 10 19:05:46] Via: SIP/2.0/UDP 192.168.1.11:5060;branch=z9hG4bK2b05366c7eefd8e3c804afe9d6704327;received=90.62.22.40;rport=5060
[Jan 10 19:05:46] From: <sip:m9i1bnpw@REMOTEIP>;tag=3852329386
[Jan 10 19:05:46] To: <sip:m9i1bnpw@REMOTEIP>;tag=as575fa198
[Jan 10 19:05:46] Call-ID: 4101722640@192_168_1_16
[Jan 10 19:05:46] CSeq: 378 REGISTER
[Jan 10 19:05:46] Server: Wazo PBX
[Jan 10 19:05:46] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
[Jan 10 19:05:46] Supported: replaces, timer
[Jan 10 19:05:46] Expires: 180
[Jan 10 19:05:46] Contact: <sip:m9i1bnpw@192.168.1.11:5060>;expires=180
[Jan 10 19:05:46] Date: Tue, 10 Jan 2017 18:05:46 GMT
[Jan 10 19:05:46] Content-Length: 0
[Jan 10 19:05:46] 
[Jan 10 19:05:46] 
[Jan 10 19:05:46] <------------>
[Jan 10 19:05:46] Scheduling destruction of SIP dialog '4153565b74556d0f5dc87b6e473309a6@REMOTEIP:5060' in 32000 ms (Method: NOTIFY)
[Jan 10 19:05:46] Reliably Transmitting (NAT) to 90.62.22.40:5060:
[Jan 10 19:05:46] NOTIFY sip:m9i1bnpw@192.168.1.11:5060 SIP/2.0
[Jan 10 19:05:46] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK64290c1e;rport
[Jan 10 19:05:46] Max-Forwards: 70
[Jan 10 19:05:46] From: "wazo" <sip:wazo@REMOTEIP>;tag=as7d64fafc
[Jan 10 19:05:46] To: <sip:m9i1bnpw@192.168.1.11:5060>
[Jan 10 19:05:46] Contact: <sip:wazo@REMOTEIP:5060>
[Jan 10 19:05:46] Call-ID: 4153565b74556d0f5dc87b6e473309a6@REMOTEIP:5060
[Jan 10 19:05:46] CSeq: 102 NOTIFY
[Jan 10 19:05:46] User-Agent: Wazo PBX
[Jan 10 19:05:46] Event: message-summary
[Jan 10 19:05:46] Content-Type: application/simple-message-summary
[Jan 10 19:05:46] Content-Length: 90
[Jan 10 19:05:46] 
[Jan 10 19:05:46] Messages-Waiting: no
[Jan 10 19:05:46] Message-Account: sip:*98@REMOTEIP
[Jan 10 19:05:46] Voice-Message: 0/0 (0/0)
[Jan 10 19:05:46] 
[Jan 10 19:05:46] ---
[Jan 10 19:05:46] Scheduling destruction of SIP dialog '4101722640@192_168_1_16' in 32000 ms (Method: REGISTER)
[Jan 10 19:05:46] 
[Jan 10 19:05:46] <--- SIP read from UDP:90.62.22.40:5060 --->
[Jan 10 19:05:46] SIP/2.0 200 OK
[Jan 10 19:05:46] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK50c87c78;rport=5060
[Jan 10 19:05:46] From: "wazo" <sip:wazo@REMOTEIP>;tag=as69e2e014
[Jan 10 19:05:46] To: <sip:m9i1bnpw@192.168.1.11:5060>;tag=ar78d3d105
[Jan 10 19:05:46] Call-ID: 4fb6f82b0628385d7fed384e55409b16@REMOTEIP:5060
[Jan 10 19:05:46] CSeq: 102 OPTIONS
[Jan 10 19:05:46] Supported: replaces
[Jan 10 19:05:46] User-Agent: A510 IP/42.207.00.000.000
[Jan 10 19:05:46] Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, SUBSCRIBE, NOTIFY, REFER
[Jan 10 19:05:46] Accept: application/sdp,application/dtmf-relay,application/simple-message-summary,message/sipfrag
[Jan 10 19:05:46] Accept-Encoding: identity
[Jan 10 19:05:46] Accept-Language: en
[Jan 10 19:05:46] Content-Length: 0
[Jan 10 19:05:46] 
[Jan 10 19:05:46] 
[Jan 10 19:05:46] <------------->
[Jan 10 19:05:46] --- (13 headers 0 lines) ---
[Jan 10 19:05:46] Really destroying SIP dialog '4fb6f82b0628385d7fed384e55409b16@REMOTEIP:5060' Method: OPTIONS
[Jan 10 19:05:46] 
[Jan 10 19:05:46] <--- SIP read from UDP:90.62.22.40:5060 --->
[Jan 10 19:05:46] SIP/2.0 200 OK
[Jan 10 19:05:46] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK64290c1e;rport=5060
[Jan 10 19:05:46] From: "wazo" <sip:wazo@REMOTEIP>;tag=as7d64fafc
[Jan 10 19:05:46] To: <sip:m9i1bnpw@192.168.1.11:5060>;tag=ar6e75gagb
[Jan 10 19:05:46] Call-ID: 4153565b74556d0f5dc87b6e473309a6@REMOTEIP:5060
[Jan 10 19:05:46] CSeq: 102 NOTIFY
[Jan 10 19:05:46] User-Agent: A510 IP/42.207.00.000.000
[Jan 10 19:05:46] Content-Length: 0
[Jan 10 19:05:46] 
[Jan 10 19:05:46] 
[Jan 10 19:05:46] <------------->
[Jan 10 19:05:46] --- (8 headers 0 lines) ---
[Jan 10 19:05:46] Really destroying SIP dialog '4153565b74556d0f5dc87b6e473309a6@REMOTEIP:5060' Method: NOTIFY
[Jan 10 19:05:47] NOTICE[1491][C-0000000a]: chan_sip.c:26257 handle_request_invite: Failed to authenticate device 100<sip:100@REMOTEIP>;tag=fdb265cf
[Jan 10 19:05:47] 
[Jan 10 19:05:47] <--- SIP read from UDP:90.62.22.40:5060 --->
[Jan 10 19:05:47] REGISTER sip:REMOTEIP SIP/2.0
[Jan 10 19:05:47] Via: SIP/2.0/UDP 192.168.1.11:5060;branch=z9hG4bKfbc3c944c081ec23c4aba7c494128bc2;rport
[Jan 10 19:05:47] From:  <sip:zgxz6i7n@REMOTEIP>;tag=941870767
[Jan 10 19:05:47] To:  <sip:zgxz6i7n@REMOTEIP>
[Jan 10 19:05:47] Call-ID: 2914144240@192_168_1_16
[Jan 10 19:05:47] CSeq: 377 REGISTER
[Jan 10 19:05:47] Contact: <sip:zgxz6i7n@192.168.1.11:5060>
[Jan 10 19:05:47] Max-Forwards: 70
[Jan 10 19:05:47] User-Agent: A510 IP/42.207.00.000.000
[Jan 10 19:05:47] Expires: 180
[Jan 10 19:05:47] Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, SUBSCRIBE, NOTIFY, REFER
[Jan 10 19:05:47] Content-Length: 0
[Jan 10 19:05:47] 
[Jan 10 19:05:47] 
[Jan 10 19:05:47] <------------->
[Jan 10 19:05:47] --- (12 headers 0 lines) ---
[Jan 10 19:05:47] Sending to 90.62.22.40:5060 (no NAT)
[Jan 10 19:05:47] Sending to 90.62.22.40:5060 (no NAT)
[Jan 10 19:05:47] 
[Jan 10 19:05:47] <--- Transmitting (NAT) to 90.62.22.40:5060 --->
[Jan 10 19:05:47] SIP/2.0 401 Unauthorized
[Jan 10 19:05:47] Via: SIP/2.0/UDP 192.168.1.11:5060;branch=z9hG4bKfbc3c944c081ec23c4aba7c494128bc2;received=90.62.22.40;rport=5060
[Jan 10 19:05:47] From: <sip:zgxz6i7n@REMOTEIP>;tag=941870767
[Jan 10 19:05:47] To: <sip:zgxz6i7n@REMOTEIP>;tag=as38742cc0
[Jan 10 19:05:47] Call-ID: 2914144240@192_168_1_16
[Jan 10 19:05:47] CSeq: 377 REGISTER
[Jan 10 19:05:47] Server: Wazo PBX
[Jan 10 19:05:47] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
[Jan 10 19:05:47] Supported: replaces, timer
[Jan 10 19:05:47] WWW-Authenticate: Digest algorithm=MD5, realm="wazo", nonce="609bb9f3" 
[Jan 10 19:05:47] Content-Length: 0
[Jan 10 19:05:47] 
[Jan 10 19:05:47] 
[Jan 10 19:05:47] <------------>
[Jan 10 19:05:47] Scheduling destruction of SIP dialog '2914144240@192_168_1_16' in 32000 ms (Method: REGISTER)
[Jan 10 19:05:47] 
[Jan 10 19:05:47] <--- SIP read from UDP:90.62.22.40:5060 --->
[Jan 10 19:05:47] REGISTER sip:REMOTEIP SIP/2.0
[Jan 10 19:05:47] Via: SIP/2.0/UDP 192.168.1.11:5060;branch=z9hG4bKa8e20e541ca0d9756e8f89923d1c1a61;rport
[Jan 10 19:05:47] From:  <sip:zgxz6i7n@REMOTEIP>;tag=941870767
[Jan 10 19:05:47] To:  <sip:zgxz6i7n@REMOTEIP>
[Jan 10 19:05:47] Call-ID: 2914144240@192_168_1_16
[Jan 10 19:05:47] CSeq: 378 REGISTER
[Jan 10 19:05:47] Contact: <sip:zgxz6i7n@192.168.1.11:5060>
[Jan 10 19:05:47] Authorization: Digest username="zgxz6i7n", realm="wazo", algorithm=MD5, uri="sip:REMOTEIP", nonce="609bb9f3", response="3fea6bf2e71e4d901fd48100928dccc7" 
[Jan 10 19:05:47] Max-Forwards: 70
[Jan 10 19:05:47] User-Agent: A510 IP/42.207.00.000.000
[Jan 10 19:05:47] Expires: 180
[Jan 10 19:05:47] Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, SUBSCRIBE, NOTIFY, REFER
[Jan 10 19:05:47] Content-Length: 0
[Jan 10 19:05:47] 
[Jan 10 19:05:47] 
[Jan 10 19:05:47] <------------->
[Jan 10 19:05:47] --- (13 headers 0 lines) ---
[Jan 10 19:05:47] Sending to 90.62.22.40:5060 (NAT)
[Jan 10 19:05:47] Reliably Transmitting (NAT) to 90.62.22.40:5060:
[Jan 10 19:05:47] OPTIONS sip:zgxz6i7n@192.168.1.11:5060 SIP/2.0
[Jan 10 19:05:47] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK47d0b1a8;rport
[Jan 10 19:05:47] Max-Forwards: 70
[Jan 10 19:05:47] From: "wazo" <sip:wazo@REMOTEIP>;tag=as2d4f5f9d
[Jan 10 19:05:47] To: <sip:zgxz6i7n@192.168.1.11:5060>
[Jan 10 19:05:47] Contact: <sip:wazo@REMOTEIP:5060>
[Jan 10 19:05:47] Call-ID: 012a0eab3da375c44495e9dc1b4b6f21@REMOTEIP:5060
[Jan 10 19:05:47] CSeq: 102 OPTIONS
[Jan 10 19:05:47] User-Agent: Wazo PBX
[Jan 10 19:05:47] Date: Tue, 10 Jan 2017 18:05:47 GMT
[Jan 10 19:05:47] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
[Jan 10 19:05:47] Supported: replaces, timer
[Jan 10 19:05:47] Content-Length: 0
[Jan 10 19:05:47] 
[Jan 10 19:05:47] 
[Jan 10 19:05:47] ---
[Jan 10 19:05:47] 
[Jan 10 19:05:47] <--- Transmitting (NAT) to 90.62.22.40:5060 --->
[Jan 10 19:05:47] SIP/2.0 200 OK
[Jan 10 19:05:47] Via: SIP/2.0/UDP 192.168.1.11:5060;branch=z9hG4bKa8e20e541ca0d9756e8f89923d1c1a61;received=90.62.22.40;rport=5060
[Jan 10 19:05:47] From: <sip:zgxz6i7n@REMOTEIP>;tag=941870767
[Jan 10 19:05:47] To: <sip:zgxz6i7n@REMOTEIP>;tag=as38742cc0
[Jan 10 19:05:47] Call-ID: 2914144240@192_168_1_16
[Jan 10 19:05:47] CSeq: 378 REGISTER
[Jan 10 19:05:47] Server: Wazo PBX
[Jan 10 19:05:47] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
[Jan 10 19:05:47] Supported: replaces, timer
[Jan 10 19:05:47] Expires: 180
[Jan 10 19:05:47] Contact: <sip:zgxz6i7n@192.168.1.11:5060>;expires=180
[Jan 10 19:05:47] Date: Tue, 10 Jan 2017 18:05:47 GMT
[Jan 10 19:05:47] Content-Length: 0
[Jan 10 19:05:47] 
[Jan 10 19:05:47] 
[Jan 10 19:05:47] <------------>
[Jan 10 19:05:47] Scheduling destruction of SIP dialog '01c063c6718d88e4597bced8450530a0@REMOTEIP:5060' in 32000 ms (Method: NOTIFY)
[Jan 10 19:05:47] Reliably Transmitting (NAT) to 90.62.22.40:5060:
[Jan 10 19:05:47] NOTIFY sip:zgxz6i7n@192.168.1.11:5060 SIP/2.0
[Jan 10 19:05:47] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK11cce7e5;rport
[Jan 10 19:05:47] Max-Forwards: 70
[Jan 10 19:05:47] From: "wazo" <sip:wazo@REMOTEIP>;tag=as368c18ad
[Jan 10 19:05:47] To: <sip:zgxz6i7n@192.168.1.11:5060>
[Jan 10 19:05:47] Contact: <sip:wazo@REMOTEIP:5060>
[Jan 10 19:05:47] Call-ID: 01c063c6718d88e4597bced8450530a0@REMOTEIP:5060
[Jan 10 19:05:47] CSeq: 102 NOTIFY
[Jan 10 19:05:47] User-Agent: Wazo PBX
[Jan 10 19:05:47] Event: message-summary
[Jan 10 19:05:47] Content-Type: application/simple-message-summary
[Jan 10 19:05:47] Content-Length: 90
[Jan 10 19:05:47] 
[Jan 10 19:05:47] Messages-Waiting: no
[Jan 10 19:05:47] Message-Account: sip:*98@REMOTEIP
[Jan 10 19:05:47] Voice-Message: 0/0 (0/0)
[Jan 10 19:05:47] 
[Jan 10 19:05:47] ---
[Jan 10 19:05:47] Scheduling destruction of SIP dialog '2914144240@192_168_1_16' in 32000 ms (Method: REGISTER)
[Jan 10 19:05:47] 
[Jan 10 19:05:47] <--- SIP read from UDP:90.62.22.40:5060 --->
[Jan 10 19:05:47] SIP/2.0 200 OK
[Jan 10 19:05:47] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK47d0b1a8;rport=5060
[Jan 10 19:05:47] From: "wazo" <sip:wazo@REMOTEIP>;tag=as2d4f5f9d
[Jan 10 19:05:47] To: <sip:zgxz6i7n@192.168.1.11:5060>;tag=ar3e5g4g8e
[Jan 10 19:05:47] Call-ID: 012a0eab3da375c44495e9dc1b4b6f21@REMOTEIP:5060
[Jan 10 19:05:47] CSeq: 102 OPTIONS
[Jan 10 19:05:47] Supported: replaces
[Jan 10 19:05:47] User-Agent: A510 IP/42.207.00.000.000
[Jan 10 19:05:47] Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, SUBSCRIBE, NOTIFY, REFER
[Jan 10 19:05:47] Accept: application/sdp,application/dtmf-relay,application/simple-message-summary,message/sipfrag
[Jan 10 19:05:47] Accept-Encoding: identity
[Jan 10 19:05:47] Accept-Language: en
[Jan 10 19:05:47] Content-Length: 0
[Jan 10 19:05:47] 
[Jan 10 19:05:47] 
[Jan 10 19:05:47] <------------->
[Jan 10 19:05:47] --- (13 headers 0 lines) ---
[Jan 10 19:05:47] Really destroying SIP dialog '012a0eab3da375c44495e9dc1b4b6f21@REMOTEIP:5060' Method: OPTIONS
[Jan 10 19:05:47] 
[Jan 10 19:05:47] <--- SIP read from UDP:90.62.22.40:5060 --->
[Jan 10 19:05:47] SIP/2.0 200 OK
[Jan 10 19:05:47] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK11cce7e5;rport=5060
[Jan 10 19:05:47] From: "wazo" <sip:wazo@REMOTEIP>;tag=as368c18ad
[Jan 10 19:05:47] To: <sip:zgxz6i7n@192.168.1.11:5060>;tag=ar279b09ae
[Jan 10 19:05:47] Call-ID: 01c063c6718d88e4597bced8450530a0@REMOTEIP:5060
[Jan 10 19:05:47] CSeq: 102 NOTIFY
[Jan 10 19:05:47] User-Agent: A510 IP/42.207.00.000.000
[Jan 10 19:05:47] Content-Length: 0
[Jan 10 19:05:47] 
[Jan 10 19:05:47] 
[Jan 10 19:05:47] <------------->
[Jan 10 19:05:47] --- (8 headers 0 lines) ---
[Jan 10 19:05:47] Really destroying SIP dialog '01c063c6718d88e4597bced8450530a0@REMOTEIP:5060' Method: NOTIFY
[Jan 10 19:05:51] Reliably Transmitting (NAT) to 90.62.22.40:1024:
[Jan 10 19:05:51] OPTIONS sip:5eobbx4f@192.168.1.12:5060 SIP/2.0
[Jan 10 19:05:51] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK2ae43850;rport
[Jan 10 19:05:51] Max-Forwards: 70
[Jan 10 19:05:51] From: "wazo" <sip:wazo@REMOTEIP>;tag=as7e8304ab
[Jan 10 19:05:51] To: <sip:5eobbx4f@192.168.1.12:5060>
[Jan 10 19:05:51] Contact: <sip:wazo@REMOTEIP:5060>
[Jan 10 19:05:51] Call-ID: 422298a33aa89d980f2abc645e0c2302@REMOTEIP:5060
[Jan 10 19:05:51] CSeq: 102 OPTIONS
[Jan 10 19:05:51] User-Agent: Wazo PBX
[Jan 10 19:05:51] Date: Tue, 10 Jan 2017 18:05:51 GMT
[Jan 10 19:05:51] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
[Jan 10 19:05:51] Supported: replaces, timer
[Jan 10 19:05:51] Content-Length: 0
[Jan 10 19:05:51] 
[Jan 10 19:05:51] 
[Jan 10 19:05:51] ---
[Jan 10 19:05:51] 
[Jan 10 19:05:51] <--- SIP read from UDP:90.62.22.40:1024 --->
[Jan 10 19:05:51] SIP/2.0 200 OK
[Jan 10 19:05:51] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK2ae43850;rport=5060
[Jan 10 19:05:51] From: "wazo" <sip:wazo@REMOTEIP>;tag=as7e8304ab
[Jan 10 19:05:51] To: <sip:5eobbx4f@192.168.1.12:5060>;tag=2212842572
[Jan 10 19:05:51] Call-ID: 422298a33aa89d980f2abc645e0c2302@REMOTEIP:5060
[Jan 10 19:05:51] CSeq: 102 OPTIONS
[Jan 10 19:05:51] User-Agent: Yealink SIP-T41P 36.80.0.95
[Jan 10 19:05:51] Content-Length: 0
[Jan 10 19:05:51] 
[Jan 10 19:05:51] 
[Jan 10 19:05:51] <------------->
[Jan 10 19:05:51] --- (8 headers 0 lines) ---
[Jan 10 19:05:51] Really destroying SIP dialog '422298a33aa89d980f2abc645e0c2302@REMOTEIP:5060' Method: OPTIONS

ça ressemble bien à un problème de NAT.

Merci d'avance pour votre aide

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Etienne Lessard 8 months ago

Ah pourtant on voit bien le SIP NOTIFY "Event: check-sync" être envoyé au Yealink et qu'une réponse (200 OK) est ensuite recue (tout ça dans la même seconde):

[Jan 10 19:05:41] Scheduling destruction of SIP dialog '4d2872b34e698e8d07dcbcd461a0a06e@REMOTEIP:5060' in 32000 ms (Method: NOTIFY)
[Jan 10 19:05:41] Reliably Transmitting (NAT) to 90.62.22.40:1024:
[Jan 10 19:05:41] NOTIFY sip:5eobbx4f@192.168.1.12:5060 SIP/2.0
[Jan 10 19:05:41] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK5282e737;rport
[Jan 10 19:05:41] Max-Forwards: 70
[Jan 10 19:05:41] From: "wazo" <sip:wazo@REMOTEIP>;tag=as76db1d29
[Jan 10 19:05:41] To: <sip:5eobbx4f@192.168.1.12:5060>
[Jan 10 19:05:41] Contact: <sip:wazo@REMOTEIP:5060>
[Jan 10 19:05:41] Call-ID: 4d2872b34e698e8d07dcbcd461a0a06e@REMOTEIP:5060
[Jan 10 19:05:41] CSeq: 102 NOTIFY
[Jan 10 19:05:41] User-Agent: Wazo PBX
[Jan 10 19:05:41] Date: Tue, 10 Jan 2017 18:05:41 GMT
[Jan 10 19:05:41] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
[Jan 10 19:05:41] Supported: replaces, timer
[Jan 10 19:05:41] Subscription-State: terminated
[Jan 10 19:05:41] Event: check-sync
[Jan 10 19:05:41] Content-Length: 0
[Jan 10 19:05:41] 
[Jan 10 19:05:41] 
[Jan 10 19:05:41] ---
[Jan 10 19:05:41] 
[Jan 10 19:05:41] <--- SIP read from UDP:90.62.22.40:1024 --->
[Jan 10 19:05:41] SIP/2.0 200 OK
[Jan 10 19:05:41] Via: SIP/2.0/UDP REMOTEIP:5060;branch=z9hG4bK5282e737;rport=5060
[Jan 10 19:05:41] From: "wazo" <sip:wazo@REMOTEIP>;tag=as76db1d29
[Jan 10 19:05:41] To: <sip:5eobbx4f@192.168.1.12:5060>;tag=2019916409
[Jan 10 19:05:41] Call-ID: 4d2872b34e698e8d07dcbcd461a0a06e@REMOTEIP:5060
[Jan 10 19:05:41] CSeq: 102 NOTIFY
[Jan 10 19:05:41] User-Agent: Yealink SIP-T41P 36.80.0.95
[Jan 10 19:05:41] Content-Length: 0

À cette heure (Jan 10 19:05:41) et un peu après, est-ce que dans le log de xivo-provd (/var/log/xivo-provd.log), vous avez vu les requêtes HTTP faites par ce téléphone ?

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Christopher LEAL 8 months ago

Hello,

Dans /var/log/xivo-provd.log voici ce que j'ai :
A mon sens je ne vois pas de requêtes en provenance du téléphone.

2017-01-10 19:05:41,007 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:05:40 +0000] "GET /provd/dev_mgr/devices/0af559006014418e876b25d24cd361dd HTTP/1.1" 200 332 "-" "Python-urllib/2.7"
2017-01-10 19:05:41,008 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:05:40 +0000] "GET /provd/cfg_mgr/configs/0af559006014418e876b25d24cd361dd HTTP/1.1" 200 989 "-" "Python-urllib/2.7"
2017-01-10 19:05:41,011 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:05:40 +0000] "GET /provd/pg_mgr/plugins/xivo-yealink-v80/info HTTP/1.1" 200 1662 "-" "-"
2017-01-10 19:05:41,011 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:05:40 +0000] "GET /provd/pg_mgr/plugins/xivo-yealink-v80/install/installed HTTP/1.1" 200 164 "-" "-"
2017-01-10 19:05:41,012 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:05:40 +0000] "GET /provd/pg_mgr/plugins/xivo-yealink-v80/install/installable HTTP/1.1" 200 1057 "-" "-"
2017-01-10 19:05:41,013 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:05:40 +0000] "GET /provd/pg_mgr/plugins/xivo-yealink-v80/configure HTTP/1.1" 404 153 "-" "-"
2017-01-10 19:05:41,014 [944] (INFO) (provd.app): Synchronizing device 0af559006014418e876b25d24cd361dd
2017-01-10 19:05:41,014 [944] (INFO) (provd.app): Synchronizing device 0af559006014418e876b25d24cd361dd with plugin xivo-yealink-v80
2017-01-10 19:05:41,015 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:05:40 +0000] "POST /provd/dev_mgr/synchronize HTTP/1.1" 201 - "-" "-"
2017-01-10 19:05:41,118 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:05:40 +0000] "GET /provd/dev_mgr/synchronize/2 HTTP/1.1" 200 20 "-" "-"
2017-01-10 19:05:41,119 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:05:40 +0000] "DELETE /provd/dev_mgr/synchronize/2 HTTP/1.1" 204 - "-" "-"
2017-01-10 19:05:41,224 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:05:41 +0000] "GET /provd/dev_mgr/devices?sort=ip&sort_ord=ASC HTTP/1.1" 200 657 "-" "Python-urllib/2.7"
2017-01-10 19:05:41,225 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:05:41 +0000] "GET /provd/cfg_mgr/configs/4f8be20d0f7c4249a4a08e3337178017 HTTP/1.1" 200 747 "-" "Python-urllib/2.7"
2017-01-10 19:05:41,226 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:05:41 +0000] "GET /provd/cfg_mgr/configs/0af559006014418e876b25d24cd361dd HTTP/1.1" 200 989 "-" "Python-urllib/2.7"
2017-01-10 19:14:14,003 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:14:13 +0000] "GET /provd/dev_mgr/devices/0af559006014418e876b25d24cd361dd HTTP/1.1" 200 332 "-" "Python-urllib/2.7"
2017-01-10 19:14:14,004 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:14:13 +0000] "GET /provd/cfg_mgr/configs/0af559006014418e876b25d24cd361dd HTTP/1.1" 200 989 "-" "Python-urllib/2.7"
2017-01-10 19:14:14,007 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:14:13 +0000] "GET /provd/pg_mgr/plugins/xivo-yealink-v80/info HTTP/1.1" 200 1662 "-" "-"
2017-01-10 19:14:14,008 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:14:13 +0000] "GET /provd/pg_mgr/plugins/xivo-yealink-v80/install/installed HTTP/1.1" 200 164 "-" "-"
2017-01-10 19:14:14,008 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:14:13 +0000] "GET /provd/pg_mgr/plugins/xivo-yealink-v80/install/installable HTTP/1.1" 200 1057 "-" "-"
2017-01-10 19:14:14,009 [944] (INFO) (twisted): 127.0.0.1 - - [10/Jan/2017:18:14:13 +0000] "GET /provd/pg_mgr/plugins/xivo-yealink-v80/configure HTTP/1.1" 404 153 "-" "-"

Je ferais de nouveaux tests demain...

Bonne soirée et merci ;)

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Etienne Lessard 8 months ago

On ne voit effectivement pas les requêtes en provenance du téléphone.

De mon point de vue, les deux causes les plus probables sont:

RE: Redemarrer poste YEALINK T41 ou T42 - Added by Christopher LEAL 8 months ago

Bonjour Etienne,

Alors j'ai vérifié et effectivement une fois que le téléphone est provisionné il manque l'url de provisionning, actuellement nous utilisons le serveur RPS de yealink pour qu'au démarrage du téléphone la requête de provisionning soit redirigé vers le serveur WAZO.

Du coup j'ai rajouté l'url de provisionning à la main dans le Yealink ( je modifierais le template pour rajouter l'url de provisionning par la suite) et j'ai relancé une synchronisation mais j'ai le même phénomène, je vais renter la capture de trame pour voir ce que le téléphone envoi ou tente d'envoyé ou n'envoi pas ...

Cdlt

(1-14/14)