Yealink Forums

Full Version: Yealink XML browser issues
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I upgraded to 28.73.0.51, and I'm having trouble getting all of my xml scripts to run. I was curious if there was a change in the format at all? I now get a "Loading Error" on my T46

Here was the source output, from my browser:

PHP Code:
<YealinkIPPhoneDirectory
style
="radio"
Beep="no"
defaultIndex="1"
>
<
Title wrap="yes">HELD CALLS</Title>
<
MenuItem>
<
Prompt>244</Prompt>
<
URI>555244</URI>
</
MenuItem>
<
MenuItem>
<
Prompt>217</Prompt>
<
URI>555217</URI>
</
MenuItem>
<
SoftKey index="1">
<
Label>Pickup</Label>
<
URI>SoftKey:Dial</URI>
</
SoftKey>
<
SoftKey index="4">
<
Label>Exit</Label>
<
URI>SoftKey:Exit</URI>
</
SoftKey>
</
YealinkIPPhoneDirectory

Everything looks like it always did, but its not loading on the phones...
I used a default Yealink template (from the guide), and I'm still not able to retrieve things in the xml browser. Using chrome, the output from the webserver looks like this:

PHP Code:
<?xml version="1.0" encoding="ISO-8859-1"?>
<YealinkIPPhoneDirectory
defaultIndex="1"
next="http://10.3.5.198/ImageMenu.xml"
previous="http://10.3.5.198/ImageScreen.xml"
cancelAction="http://10.3.5.198/TextScreen.xml"
Timeout="15"
LockIn="no">
<Title>My Directory</Title>
<MenuItem>
<Prompt>Joy</Prompt>
<URI>10.2.11.163</URI>
</MenuItem>
<MenuItem>
<Prompt>John Doe</Prompt>
<URI>1003</URI>
</MenuItem>
</YealinkIPPhoneDirectory> 

I have a feeling the XML browser might not be working at all...
Hi Nick,

I just test in 28.73.0.51, the directory.xml works.
I attach the XML file. Please see whether it works in your side.

Regards,
James
(05-09-2015 05:05 AM)Yealink_James Wrote: [ -> ]Hi Nick,

I just test in 28.73.0.51, the directory.xml works.
I attach the XML file. Please see whether it works in your side.

Regards,
James

Initially this did not work for me either.

However, it seems that restarting the phones has fixed the issue (for now). I should have tried that first. Hopefully it was just an issue after being upgraded, and won't happen again..
Reference URL's