After reading plenty of good reviews about these phones i bought a few (six) to use with a new setup.
I am using the lastest Distro on asterisk 11. I have installed and licensed the DPMA and got it working (appart from the mDNS, no idea why). I have also upgraded the asterisk module to 1.7. I have upgraded each phone also to the latest firmware.
I need to be able to:
Call Flow:
Change one of the BLF’s on the phone to show RED or GREEN for the call flow toggle (hint *280) i have created a phonebook entry and so far i have made it show GREEN for “ON” (red on all other phone makes) and OFF for “GREEN” (green on all other phone makes).
I understand i may need to use a Smart BLF. However i’m stumpped as to where to configure this. I have been through the below however it fails to tell me where the location of the XML config should go. Unless i’ve missed it.
Bare in mind that I have been using YeaLink and Cisco SPA942 and SPA504Gs in the past and have had them configured through the OSS endpoint manager for a number of years. never before have i had so mush hassle with customising phones!
Hope someone can shed some light?
Thanks.
Have you updated the D70’s to the latest firmware?
The problem i found was the FreePBX module for the digium phones is pretty limited, there’s still some work to be done.
I have “hacked” the module on my system to make it do what I need it to do but I wouldn’t want to make my hack public as it’s a little messy. I can however send you the updated files if you wish to try them out.
You could however post your myblfitems.xml so that we can see if that’s all good
The GUI will overwrite the res_digium_ con figs! that is what it is supposed to do. Do you have the Digum module in easy mode. I think you need advanced mode to make the changes.
I’ve been tinkering about with it and yes it certainly does overwrite the res_digium files.
It’s not in easy mode, however I still find anywhere in the GUI that gives these advanced configuration options, such as BLF_ITEMS xml input.
Some progress, I have edited the module php files to luxe the blf_items into the SQL, this in turn is processing the info into the res files and then into the astrisk config.
If anyone is interested in these files let me know and I will make them public
Next I need to sort out the blf XML to do as I need it. Results will be posted here
The add-on doesn’t currently deal with the new things provided via Smart BLF. We’re working on that.
There’s no way to change the “Digium Asterisk” text there in the corner at present. We’ve a feature request on file to allow customization of that, but it’s not possible in any current firmware.
Hi Malcolm, Thanks for the update, It would be excelent to see Smart BLF in the module. I have made some changes to the modules source code to try and get Smart BLF working. So far i have:
localhost*CLI> digium_phones show phone 1030
Name: 1030
Group Pin:
Pin:
MAC:
Active Ringtone: Office
Timezone: Europe/London
NTP Resync: default
Web UI enabled: Yes
BLF on unused Line keys: No
Recording enabled: Yes
Use Local Contact Storage: Yes
Parking Extension: 70
D40 Logo File: None
D50 Logo File: user_image_3.png
D70 Logo File: None
Login Password:
Accept Local Calls From: host
Electronic Hook Switch: None
Name Format: first_last
Preferences Locked: No
Parking Transfer Type: Blind
ConfigFile: AUTO_GENERATED
Line: 1030
Contacts Display Items: None
Contact: contacts-1.xml
BLF Items: myblfitems.xml
Contacts Max Subscriptions: default
LCD Brightness: 9
LCD Contrast:
What’s your blf_contact_group for your type=phone configuration in the _devices.conf file? Is it “Main List”? Also, I’m not, offhand, sure about spaces in that; they’re probably fine, but shrug.
Your contacts node doesn’t define an “id;” it should have one.
has_voicemail, can_intercom, and can_monitor are deprecated. They’re not part of 1.4, per-se. We’ll still do the right stuff under the hood to support them, but they shouldn’t be used anymore. (not entirely your fault, we’re probably setting them right now in our addon, and they’re not actually usable anyway because the addon doesn’t inject dialplan into the dial macro to handle them…which we know about)
Contacts are wildly different in phone firmware 1.4. Stuff is as backwards-compatible as possible, but you’ve got numbers defined, and in your BLF Items file you’re referencing actions that don’t exist in your Contacts files.
Thanks for looking over the config. I’ve just done the following to my configs:
(lifted from the wiki and adjusted slightly) It’s at a minimum to try and get this to work.
End Result: BLF key still unlit and does nothing. I could do with finding out if the myblfitems.xml is being processed by the D50. On the freepbx module the file is located with the contacts-1.xml and that is being received by the phone (I have made changes to the file and these are present on the phone after a reconfig). permissions also match.
BLF Items files aren’t retrieved from the file_directory (set to /etc/asterisk/digium_phones for the add-on), BLF Items file are only retrieved from the file_url_prefix.
I’d put the files in there too, however should it be accessible through a browser? as i get a forbidden error.
So i changed the address to go to an external address that i know is accessible:
It should be accessibly through a browser, because the phone’s actually going to cURL them in. More importantly, it should be accessible from the phone. The phone uses a URL-base defined by the file_url_prefix option as specified for a network definition that’s applied to the phone. Depending on the network the phone’s on, based upon what it discovers when it boots and gets an IP address, it’ll use that network and thus that prefix when it makes its request.
I’ve downloaded your blf items file and looked at it, and tested it, and you are the unfortunate victim of bad documentation on my part. I’ve updated the wiki. The gist is that using the blank option in combination with the contact_id option for a blf_item is bad. So, where you’ve got:
What you really want is:
A couple of points only tangentially related to your goal, your BLF Items sheet is listed as a .php file. You might want that as .xml since it’s not actually a php file (and we wouldn’t want anyone reading this whose web server does weird things to php files on their way to clients to fall prey), and you’ve got the webui turned on. If you’re configuring a phone via DPMA, XML or Switchvox, you should never touch anything in the phone’s webui, or badness can happen (this is more of a warning for any readers, like the first point).
I have altered the functions.inc.php to adjust the phone config to put the new address in the network section. I have installed a distro from scratch and I still get the unauthorised error. This maybe a bug as i also had problems updating the firmware through the GUI. I had to upgrade through the phone GUI.
The system is at work, I will have a go with the altered blf XML file in the morning and will post results.
I have removed the blank=“0” and hey presto it worked. This SmartBLF feature is a powerful feature. As you say it is important to note that the PHP was used purely for diagnosis and not to be recommended for production use.
There is definitely a bug within the FreePBX Module as the http://<IP_ADDRESS/admin/modules/digium_phones/firmware_package/
gives a 403 error when accessed. I put the working XML back there and it wouldn’t have any of it.
I also had to create a contacts-1.xml file manually and store that in it’s usual home:
/etc/asterisk/digium_phones/
After every reload in asterisk I over wrote this file with my own custom one (again just a hack).
There are a few other changes I had to make to the files so that the module produces the phone config file with the required settings like the blf_items= etc.
Note: I’m using 2.11.0.5 and the phones must have the 1.4 firmware installed.
The wiki is your bible, hopefully someone out there will benefit from this thread. with abit more work on the GUI these phones will be a game changer IMHO.
An idea for a feature, on the ring=“1” it would be nice to be able to ring the local phone for a determined time. So when “beep” is set for example it just beeps once and not over and over again.
I have removed the blank=“0” and hey presto it worked. This SmartBLF feature is a powerful feature. As you say it is important to note that the PHP was used purely for diagnosis and not to be recommended for production use.
There is definitely a bug within the FreePBX Module as the http://<IP_ADDRESS/admin/modules/digium_phones/firmware_package/
gives a 403 error when accessed. I put the working XML back there and it wouldn’t have any of it.
I had to change (hack) line 3310 (or there abouts) to:
$n[‘settings’][‘file_url_prefix’] = “”;
I also had to create a contacts-1.xml file manually and store that in it’s usual home:
/etc/asterisk/digium_phones/
After every reload in asterisk I over wrote this file with my own custom one (again just a hack).
There are a few other changes I had to make to the files so that the module produces the phone config file with the required settings like the blf_items= etc.
Note: I’m using 2.11.0.5 and the phones must have the 1.4 firmware installed.
The wiki is your bible, hopefully someone out there will benefit from this thread. with abit more work on the GUI these phones will be a game changer IMHO.
An idea for a feature, on the ring=“1” it would be nice to be able to ring the local phone for a determined time. So when “beep” is set for example it just beeps once and not over and over again.