(11-07-2019 11:41 AM)Garry_Yealink Wrote: Dear Customer,
Good day. This is Garry from Yealink Technical Support Team.
We have created a Ticket for your question and you can go to the Ticket and provide the materials we need. When you reply in Ticket, make sure you enter your email address.
https://ticket.yealink.com/page/question...l?id=96392
1) Since you are using an early 80 firmware version of T58, it may be that the version is too long. You open the following link to download the latest firmware version of T58 (58.84.0.15) and start from there. See if the SpeedDial function working properly?
http://support.yealink.com/documentFront...mentId=268
2) DNS server failure can also cause this problem, you can try to check DNS server.
3) if your problem is not solved by the above two methods, We can ask you to provide diagnostic files (PCAP trace, level-6 log file and config.bin) for our analysis?
Here are the steps to get the diagnostic files(PCAP trace, level-6 log file and config.bin),
1) Go to the web UI of T58 -> Settings -> Configuration page
2) Drop down the page and you will see “Syslog Level “.( Set it to 6)
3) Drop down the page and you will see “Export All Diagnostic Files “ option.
4) Press Start. Then start to reproduce the problem.
5) To reproduce the issue: Look up the contact in Directory: 111@172.17.0.11, then call out, and hang up after the call is established successfully. Then, use the SpeedDial function you set for Key 37 to quickly broadcast a call to 111@172.17.0.11 ,you can finish the test., until you receive the prompt "invite request no response" .
6) After finishing test, press “Stop” and then “Export”. Please export it immediately after testing, just in case the messages been overwritten.
Then send us the exported file. We will locate your question based on the information you provide.
I am looking forward to your reply.
Best Regards
Garry
Hi Garry,
Thanks a lot for reply.
1.-) Updated firmware to latest rom on a couple of devices for testing with no issues. Devices are on ext 109 and 111 at ip's 172.17.0.9 and 172.17.0.11
2.-) DNS are public google ones received by network appliance on voice vlan 2 at 172.17.0.0/24.
3.-) Testing new rom, but after upgrade I receive a call failed on same phones
Doing diag files and little test to provide you with the material
I'll update threat when material are posted to ticket to let you know they're uploaded.
Ed
