+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: T4x Series (/forumdisplay.php?fid=31)
+--- Thread: Problem with XML Browser (/showthread.php?tid=625)
Pages: 1 2
Problem with XML Browser - NerdUno - 07-12-2013 09:41 PM
We've set up some sample XML applications to allow PBX in a Flash users to try out the T46G. Anyone can load this setup on their phone to test.
The problem is that the XML Browser in the phone doesn't return any results about 4 out of every 5 attempts. As the displayed server log documents, this is not a problem on the server side. It is receiving the requests and sending the appropriate response. But the T46G typically shows "Loading. Please wait..." FOREVER unless you cancel the request and resubmit it several more times.
Here's a link to the original forum post and the server log.
And here's the actual log showing 6 attempts, only 1 of which actually displayed on the phone:
![[Image: BO-hz1YCUAAQmiK.jpg:large]](https://pbs.twimg.com/media/BO-hz1YCUAAQmiK.jpg:large)
RE: Problem with XML Browser - NerdUno - 07-13-2013 01:37 AM
Just a heads up that one of our gurus has found a workaround that seems to resolve the problem. Apparently there is a timing issue when the phone is configured with DHCP. Once a static IP address is used with static DNS entries, the XML Browser works reliably 100% of the time. So this appears to be caused by a timing failure when the phone is configured for DHCP. We've only tested this with IPv4.
RE: Problem with XML Browser - Yealink Support - 07-15-2013 05:12 PM
Hi Nerd,
Here i tried your xml files with DHCP, but works well, so could you provide us PCAP trace/syslog/config.bin as i mentioned in the support email, so we can analyze?
Thanks.
RE: Problem with XML Browser - lekcomp - 03-03-2014 11:20 PM
This is still an ongoing issue with DHCP. I can confirm the same problem with the T38G. I have attempted to capture a .cap file but it shows no traffic to and from the phone when trying the xml. Also, attempting to log into the phone to produce the requested files fails. Could it be that the phone stops processing port 80? It usually works for me for about a day before it stops. A reboot always fixes it.
Edit: FW version: 38.70.0.126 shipped with phone. But the uk site shows 38.70.23.9. Is that newer? Is it valid for the US?
RE: Problem with XML Browser - Yealink Support - 03-04-2014 10:05 AM
Hi lekcomp,
Can you refer to XML browser user guide for more details?
Using XML Browser Feature on Yealink phones Rev_70.0
FW version: 38.70.0.126 is the neutual version of our T38G. Version 38.70.23.9 is a custom version of YUK. You can use any of them.
RE: Problem with XML Browser - lekcomp - 03-04-2014 10:23 PM
What is the Developer's Guide going to tell me? It's not a development issue. Pressing the button for the script brings up a "Note" that says "Loading, please wait..." and it eventually times out. Also, web access to the phones becomes unavailable. It's like there is no port 80 traffic being allowed on the phone. I was adding here that I have the same or similar issue with the T38G as NerdUno was having with his T46G phone. This is most definitely a firmware issue. Will there be future firmware updates to these phones? Or will you make them open source so we can try to fix them?
RE: Problem with XML Browser - Yealink Support - 03-05-2014 09:04 AM
Hi lekcomp， Please check wether your skype and other apps occupy port 80.
RE: Problem with XML Browser - lekcomp - 03-06-2014 03:37 AM
No Skype or anything like that. How would having Skype on my PC stop the phone from being able to reach the PBX? Or for any computer to be able to connect to the phone? Any why would it only affect the phone when it is DHCP and not static?
RE: Problem with XML Browser - Yealink Support - 03-06-2014 11:27 AM
Hi lekcomp,
Can you creat a teamviwer account that i can remote connect to your computer and debug?
Please send a PM to me.
RE: Problem with XML Browser - lekcomp - 03-07-2014 12:28 AM
Yes. I also wanted to update that in my case statically assigning the IP does not in fact fix the issue. I will PM you the info. Also, I am unable to ping the phone when the XML stops but it still responds to SIP and RTP. I am able to make/receive calls on it.