Atualizado em 27/07/2016 às 13:00hs (UTC-3)

yealink

Os telefones Yealink T21P_E2 estão com  problemas de firmware que impedem a realização de chamadas via Asterisk caso os mesmos estejam sendo provisionados. O fato ocorre nas versões <= 52.80.0.125 e só afeta as chamadas efetuadas (chamadas recebidas funcionam normalmente).

O problema acontece porque ao tentar discar, o telefone identifica-se como usuário “IP Phone”, e a autenticação falha.

[Jun 29 15:40:23] WARNING[16693][C-000026f0]: chan_sip.c:16393 check_auth: username mismatch, have <1421>, digest has <IP Phone>
[Jun 29 15:40:23] NOTICE[16693][C-000026f0]: chan_sip.c:25569 handle_request_invite: Failed to authenticate device “Usuario <1421>” <sip:1421@pbx.dominio.com.br:5060>;tag=2901932421

SIP debug:

Authorization: Digest username=”IP Phone”, realm=””, nonce=”1801b82b”, uri=”sip:1421@XXX.XXX.XXX.XXX:5060“, response=”7cbb8fb8cd55261a44868fbb50434069″, algorithm=MD5

Já abri chamado com a Yealink e o problema foi confirmado e deverá ser resolvido na próxima versão do firmware, que saíra até setembro.

EN version

Yealink phones model T21P_E2 has firmware bugs that doesn’t allow you to make calls via Asterisk if you are provisioning the phone. This bug affects the versions <= 52.80.0.125 and occurs just when you try to make a call (you can receive calls normally).

The problem occurs because when you try to make a call, the phone sends its user  name as  “IP Phone”, and authentication fails.

[Jun 29 15:40:23] WARNING[16693][C-000026f0]: chan_sip.c:16393 check_auth: username mismatch, have <1421>, digest has <IP Phone>
[Jun 29 15:40:23] NOTICE[16693][C-000026f0]: chan_sip.c:25569 handle_request_invite: Failed to authenticate device “Usuario <1421>” <sip:1421@pbx.dominio.com.br:5060>;tag=2901932421

SIP debug:

Authorization: Digest username=”IP Phone”, realm=””, nonce=”1801b82b”, uri=”sip:1421@XXX.XXX.XXX.XXX:5060“, response=”7cbb8fb8cd55261a44868fbb50434069″, algorithm=MD5

It should be resolved in the next firmware version, which will be released until September.

Yealink e-mail

* 【Support.usa】Problems provisioning Yealink T21P_E2 — new
> [Progress:
> Confirmed and Fixing]*
>
> *Directly reply to this email or click the link if you have an access
> account.*
> https://ticket.yealink.com/index.php/bug/26615
>
> ———————————————————————————————————————————————————————————————-
> *Comments*
> *Michael_Yealink * Reply Jun 03, 2016 04:57:20 +0800
>
> Marcelo
>
> thanks so much for your information
>
> i have submit this issue to our R&D , but as we are doing firmware
> control
> , and we will collect all bugs and release a firmware every three
> months ,
> so is it OK to add this issue to firmware control and release a fix
> firmware 3 months later ?

Agora só resta aguardar!!!

UPDATE 27/07/2016

O problema: o problema foi identificado. Ele ocorre somente quando a propriedade realm do arquivo sip.conf está vazia (realm=). Neste caso, o software assume que o valor de Register Name, usado no Digest Username  também está em branco (o valor default deste campo é IP Phone).

Se você não utiliza essa propriedade vazia não deve ter percebido o problema.

O suporte da Yealink me enviou um novo firmware que resolve o problema em questão. Você pode baixá-lo aqui enquanto ele não estiver amplamente disponível no link oficial.

EN version

The bug: the bug was identified. It occurs only when the realm parameter in sip.conf file is empty (realm=). In this case, the software assumes that the value of Register Name, used in Digest Username  is empty too (the default value of the parameter is IP Phone).

If you don’t set this parameter empty, you won’t notice the bug.

Yealink support team send me a new firmware that solves the problem. You can download it here before it is not available in Yealink support page.

[SOLVED] Yealink T21P_E2 com bugs no firmware (bugs in the Yealink T21P_E2 firmware)
Tags:             
Social Media Integration by Acurax Wordpress Developers
%d blogueiros gostam disto:
Visit Us On FacebookVisit Us On TwitterCheck Our FeedVisit Us On Linkedin