push "Local Directory" to Yealink handsets from FreePBX

360col

On the yealink handsets there is the "Local" phone directory which users can add numbers themselves. However if the phone get factory rested / auto provisioned. It gets blown away.

Is it possible to push this out from FreePBX? Basically we want the user to give us a list of names & numbers and we can add for them. That will keep reloaded if the phone needs to be factory reset etc (when trouble shooting etc).

I'm referring to the individual handsets Local Directory and not the shared one. I know that you can manually export it as an XML then re import it after reseting the phone. Can this be automated.

This is part of if any issue config gets blown away and re-provioned from FreePBX to a known state.

Thanks.

360col

I'm guessing no one has done this before.

scottalanmiller

Not me

1337

@360col said in push "Local Directory" to Yealink handsets from FreePBX:

On the yealink handsets there is the "Local" phone directory which users can add numbers themselves. However if the phone get factory rested / auto provisioned. It gets blown away.

Is it possible to push this out from FreePBX? Basically we want the user to give us a list of names & numbers and we can add for them. That will keep reloaded if the phone needs to be factory reset etc (when trouble shooting etc).

I'm referring to the individual handsets Local Directory and not the shared one. I know that you can manually export it as an XML then re import it after reseting the phone. Can this be automated.

This is part of if any issue config gets blown away and re-provioned from FreePBX to a known state.

Thanks.

First off, I'm not a freepbx user, we use 3cx.

But I know that you can have more than one remote phonebook in the phone. I suggest skipping the local directory and setting up a second remote phonebook that points somewhere unique for each user. Set it up in the provisioning templates in freepbx.

So it points to something like http://your_server/unique_user/phonebook.xml

It should reside on a http server and it's just an xml file. It's very simple. You could edit it manually and have apache serve it.

Or if you want to go all out you can have a small web application that allows users to edit their phonebook themselves. Or sync it to something else.

JaredBusch

@360col said in push "Local Directory" to Yealink handsets from FreePBX:

I'm guessing no one has done this before.

Yes, I have stuff for this. I’m not readily available to help you right now.

Look at these
https://github.com/sorvani/freepbx-helper-scripts

360col

Thanks @Pete-S and @JaredBusch I'll have a look into both.

JaredBusch

@360col said in push "Local Directory" to Yealink handsets from FreePBX:

On the yealink handsets there is the "Local" phone directory which users can add numbers themselves. However if the phone get factory rested / auto provisioned. It gets blown away.

Is it possible to push this out from FreePBX? Basically we want the user to give us a list of names & numbers and we can add for them. That will keep reloaded if the phone needs to be factory reset etc (when trouble shooting etc).

I'm referring to the individual handsets Local Directory and not the shared one. I know that you can manually export it as an XML then re import it after reseting the phone. Can this be automated.

This is part of if any issue config gets blown away and re-provioned from FreePBX to a known state.

Thanks.

Ok, I read this more carefully, so no, my scripts linked above are not what you want.

But, yes you can do what you want. There is a setting that you can include in the config file for each phone to have it pull in a local address book.

You want this setting: local_contact.data.url

The file must in this format

<?xml version="1.0" encoding="utf-8"?>
<root_group>
	<group display_name="All Contacts" />
	<group display_name="Blacklist" />
</root_group>
<root_contact>
	<contact display_name="Jared" office_number="6365551212" mobile_number="3145551212" other_number="" line="0" ring="Auto" group_id_name="All Contacts" />
</root_contact>

360col

@JaredBusch said in push "Local Directory" to Yealink handsets from FreePBX:

There is a setting that you can include in the config file for each phone to have it pull in a local address book.
You want this setting: local_contact.data.url

Thanks. That sounds much easier.

1337

@360col said in push "Local Directory" to Yealink handsets from FreePBX:

@JaredBusch said in push "Local Directory" to Yealink handsets from FreePBX:

There is a setting that you can include in the config file for each phone to have it pull in a local address book.
You want this setting: local_contact.data.url

Thanks. That sounds much easier.

Sorry, but it's almost exactly the same as what I said above. Except that it will show up as the local directory instead of as a second remote directory.

In both cases you change the provisioning templates so that each phone gets a unique link to a xml file with the phone records. The xml file can be hosted on ftp, tftp, http or https server. It can be the provisioning server itself or something else - whatever the url points to.

To use a second remote directory it is: remote_phonebook.data.2.url
To use local directory it was: local_contact.data.url
There are some differences in the xml file itself.

I think that if you use the local directory you have to reprovision the phone to update the directory. If you use remote directory you can press update directory on the phone and it will go get the new updated directory. At least that is the case with the T41 I have in front of me right now.

360col

@Pete-S said in push "Local Directory" to Yealink handsets from FreePBX:

If you use remote directory you can press update directory on the phone and it will go get the new updated directory.

That bit sounds good. I'm parking this feature for the moment.

scottalanmiller

@360col Parking is a completely different feature.

LOLOLOLOL

JaredBusch

@scottalanmiller said in push "Local Directory" to Yealink handsets from FreePBX:

@360col Parking is a completely different feature.

LOLOLOLOL

Totally downvoted for the horrible pun.