Yealink Forums

Full Version: t46g says "URL is empty"
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Found it. Love it. Now I just need to figure out the syntax in the provisioning file so I can deploy to all phones easily.

On the Directory tab, Setting node, add the Remote Phone Book (3CX, in my case) to the Dialing Source List. This lets me, on a phone at standby, dial 645 to see both the cell phone for Mike and the extension for Mike. Use the down arrow to select an entry, hit Send, and I'm off to the races.

Yealink support, some direction on this would have been appreciated. It's right there, I just had to figure it out. No mention in the admin guide that I saw.
that is so awesome. hadn't noticed the setting tab before.
Yealink,
Do you have any direction on how to include this setting in the provisioning file on a 3CX server. I asked 3CX tech support, and even though I have a valid paid support contract, they refuse to help with customizing templates.

Somehow I need the provisioning language to include the remote phone book as a contact source during dialing.
Hi engine411,

yes, you can configue this feature in auto-provisioning template.
1. Download the http://www.yealink.com/Upload/T4X/GA/Aut...ioning.zip which contains "common.cfg" and "super_search.xml" in XML Template Files floder.
2. Edit the super_search.xml, enable "remote_directory_search" as 1
-----------------------------------------------------------------------------------------
<root_super_search>
<item id_name="local_directory_search" display_name="Local Contacts" priority="1" enable="1" />
<item id_name="calllog_search" display_name="History" priority="2" enable="1" />
<item id_name="remote_directory_search" display_name="Remote Phonebook" priority="3" enable="1" />
<item id_name="ldap_search" display_name="LDAP" priority="4" enable="0" />
<item id_name="BroadSoft_directory_search" display_name="Network Directories" priority="5" enable="0" />
</root_super_search>
----------------------------------------------------------------------------------------------------
3. Then configure the "super_search.url = " in common.cfg,change common.cfg to y000000000028.cfg
4. Upload y000000000028.cfg and super_search.xml to the specific server
5. Then auto-provisioning

Hope it can help you.
(10-21-2013 11:24 AM)Yealink Support Wrote: [ -> ]3. Then configure the "super_search.url = " in common.cfg

And do what to this string? Or does this:
change common.cfg to y000000000028.cfg
belong with it? That parameter does not have "common.cfg".

(10-21-2013 11:24 AM)Yealink Support Wrote: [ -> ]change common.cfg to y000000000028.cfg
If not, does this mean to rename the file? It appears that way based on this:
(10-21-2013 11:24 AM)Yealink Support Wrote: [ -> ]4. Upload y000000000028.cfg and super_search.xml to the specific server
Hi engine411,

Sorry for the confusion.

1. yes, it means rename common.cfg as y000000000028.cfg
2. Fill the url of super_search.xml in the "super_search.url = "
For example:
super_search.url = http://10.2.5.236:8080/super_search.xml

You can get more details in auto-proviioning guide in page 116
http://www.yealink.com/Upload/T4X/GA/Yea...71_171.pdf
Pages: 1 2
Reference URL's