[SOLVED] Setting Up BLF keys on a Digium D65 phone

Asterisk Asterisk Endpoints
1

All,

We are making some good progress setting our new Digium D65 phones. What we would very much like to do is take advantage of using the 20 pages of BLF keys.

We have started pretty simple. The contacts.xml file has two groups in it. One for our receptionists and the second for one of our support groups. We would like for each group in the contacts.xml to have their own page on a D65 phone. Each group is essentially a queue that is setup in Asterisk.

It mostly works. If we are only using one page, and one group from the contacts.xml file, you see all the people in that group and we can monitor calls coming to and from a person in that group. Again, we are not wanting to do anything more complex right now such as use indicators, or setup in behaviors.

When we add the second page, it will display the primary user of the phone in position 0, and then display the next 3 BLF keys correctly, but will not display the 4th BLF on page 2. contacts.xml and the blf.items.xml are below. I highlighted the xml line that is used to put the 4th person in the group on page 2 of the D65.

Thanks as always.

<?xml version="1.0"?>
 <config>
  <smart_blf>
    <blf_items>
        <blf_item location="main" index="0" paging="1" contact_id="8901"/>
        <blf_item location="main" index="1" paging="1" contact_id="8900"/>
        <blf_item location="main" index="2" paging="1" contact_id="8927"/>
        <blf_item location="main" index="3" paging="1" contact_id="8980"/>
        <blf_item location="main" index="1" paging="2" contact_id="8708"/>
        <blf_item location="main" index="2" paging="2" contact_id="8942"/>
        <blf_item location="main" index="3" paging="2" contact_id="8965"/>
        **<blf_iten location="main" index="4" paging="2" contact_id="8977"/>**
     </blf_items>
   </smart_blf>
</config>

    <?xml version="1.0" encoding="UTF-8"?>
   <phonebooks>
      <contacts group_name="Milsoft Receptionists" editable="0" id="101">
        <contact
        server_uuid="Milasterisk4400"
        id="8901"
        prefix="Ms"
        first_name="Debra"
        second_name=""
        last_name="Levrets"
        contact_type="sip"
        organization="Milsoft"
        job_title="Receptionist"
        location="Abilene Texas"
    account_id="8901"
        subscribe_to="auto_hint_DebraLevrets"
    >
        <emails>
            <email address="xxxx@milsoft.com" label="Work" primary="1" />
        </emails>
        <actions>
            <action id="primary" dial="8901" label="Extension" name="Office"/>
        </actions>
    </contact>
    <contact
        server_uuid="Milasterisk4400"
        id="8900"
        prefix="Ms"
        first_name="Sharon"
        second_name=""
        last_name="Pillion"
        contact_type="sip"
        organization="Milsoft"
        job_title="Receptionist"
        location="Abilene Texas"
        account_id="8900"
    subscribe_to="auto_hint_SharonPillion"
        >
        <emails>
            <email address="xxxxx@milsoft.com" label="Work" primary="1" />
        </emails>
        <actions>
            <action id="primary" dial="8900" label="Extension" name="Office" />
        </actions>
    </contact>
    <contact
        server_uuid="Milasterisk4400"
        id="8927"
        prefix="Ms"
        first_name="Susan"
        second_name=""
        last_name="McWright"
        contact_type="sip"
        organization="Milsoft"
        job_title="Receptionist"
        location="Abilene Texas"
        subscribe_to="auto_hint_SusanMcWright"
    >
        <emails>
            <email address="xxxx@milsoft.com" label="Work" primary="1" />
        </emails>
        <actions>
            <action id="primary" dial="8927" label="Extension" name="Office" />
        </actions>
    </contact>
    <contact
        server_uuid="Milasterisk4400"
        id="8980"
        prefix="Ms"
        first_name="Sterling"
        second_name=""
        last_name="Skidgel"
        contact_type="sip"
        organization="Milsoft"
        job_title="Receptionist"
        location="Pensacola Florida"
    subscribe_to="auto_hint_SterlingSkidgel"
     >	
        <emails>
            <email address="xxxx@milsoft.com" label="Work" primary="1"/>
        </emails>
        <actions>
            <action id="primary" dial="8980" label="Extension" name="Office"/>
        </actions>
    </contact>
</contacts>
<contacts group_name="EA Support" editable="0" id="102">
     <contact
        server_uuid="Milasterisk4400"
        id="8708"
        prefix="Mr"
        first_name="Aaron"
        second_name=""
        last_name="Kirkes"
        contact_type="sip"
        organization="Milsoft EA Support"
        job_title="Customer Support"
        location="Abilene Texas"
        account_id="8708"
        subscribe_to="auto_hint_AaronKirkes"
        >
        <emails>
            <email address="xxxxx@milsoft.com" label="Work" primary="1" />
        </emails>
        <actions>
            <action id="primary" dial="8708" label="Extension" name="Office"/>
         </actions>
    </contact>   
    <contact
        server_uuid="Milasterisk4400"
        id="8942"
        prefix="Mr"
        first_name="Clay"
        second_name=""
        last_name="Schubert"
        contact_type="sip"
        organization="Milsoft EA Support"
        job_title="Customer Support"
        location="Abilene Texas"
        account_id="8942"
        subscribe_to="auto_hint_ClaySchubert"
        >
        <emails>
            <email address="xxxxx@milsoft.com" label="Work" primary="1" />
        </emails>
        <actions>
            <action id="primary" dial="8942" label="Extension" name="Office"/>
        </actions>
    </contact>
    <contact
        server_uuid="Milasterisk4400"
        id="8977"
        prefix="Mr"
        first_name="Greg"
        second_name=""
        last_name="Shirek"
        contact_type="sip"
        organization="Milsoft EA Support"
        job_title="Customer Support"
        location="Abilene Texas"
        account_id="8977"
        subscribe_to="auto_hint_GregShirek"
        >
        <emails>
            <email address="xxxxx@milsoft.com" label="Work" primary="1" />
        </emails>
        <actions>
            <action id="primary" dial="8977" label="Extension" name="Office"/>
        </actions>
    </contact> 
            <contact
        server_uuid="Milasterisk4400"
        id="8965"
        prefix="Ms"
        first_name="Hillary"
        second_name=""
        last_name="Proffit"
        contact_type="sip"
        organization="Milsoft EA Support"
        job_title="Customer Support"
        location="Abilene Texas"
        account_id="8965"
        subscribe_to="auto_hint_HillaryProffit"
        >
        <emails>
            <email address="xxxxx@milsoft.com" label="Work" primary="1" />
        </emails>
        <actions>
            <action id="primary" dial="8965" label="Extension" name="Office"/>
        </actions>
    </contact>
  </contacts>
 <contacts group_name="Family Members" editable="1" id="anythingyouwant">
 </contacts>
</phonebooks>
2

Howdy,

8901 is on index 0. That won’t work. Index 0 is consumed by your primary line on the phone. You should start at index=1. Subsequent pages will always show line keys on them.

Also, you’re not using the paging option correctly. See:

https://wiki.asterisk.org/wiki/display/DIGIUM/Smart+BLF

Where paging=1 (the default, and what happens if you don’t specify paging at all), the item will only be on the page that it should be on naturally. Where paging=0, the item will be on all pages.

Cheers

3

Thank you. I did add 8901 on index 0. I was experimenting on would it have any affect.

Paging is now set to what I believe to be correct based on the wiki. I did take paging out completely. New xml is below. The behavior after these changes is the same. Contact_ID 8977 does not show up at all. Everything else is on the correct page.The first 3 Contact_ID’s in the xml display correctly underneath position 0 which is the primary extension for the phone.

Contact_ID’s 8708, 8942, and 8965 display correctly on page 2. Again underneath index 0 which is the owner of the phone. Contact_ID 8977 does not display at all.

XML below.

<?xml version="1.0"?>
<config>
<smart_blf>
    <blf_items>
        <blf_item location="main" index="1" contact_id="8900"/>
        <blf_item location="main" index="2" contact_id="8927"/>
        <blf_item location="main" index="3" contact_id="8980"/>
        <blf_item location="main" index="1" contact_id="8708"/>
        <blf_item location="main" index="2" contact_id="8942"/>
        <blf_item location="main" index="3" contact_id="8965"/>
        <blf_iten location="main" index="4" contact_id="8977"/>
        <blf_iten location="main" index="1" contact_id="8959"/>
    </blf_items>
 </smart_blf>
</config>
4

I forgot to add, when you look at the contact list on the D65, everything is in order. All groups are there and the right members are in each group.

5

There’s a typo in there. You said “blf_iten” not “blf_item”

6

Howdy,

Also, if you’re trying to get 8977 to show on the second page, what you have won’t work. Because you have it on index 4 and because it’s the first item in index 4, it’ll show up on the first page.

If you want it to show up on the second page, specifically, and not the first, you’d need to insert a blank into the first index 4, e.g.:

<blf_item location="main" index="4" blank="1"/>

…and you’ll need that to appear before (top-down) the your 8977 item.

Cheers

7

I love your West Texas greeting. Living in Abilene, it is a very friendly and common greeting…

Sorry for the typo. I caught it of course after I posted…

This is starting to piece together nicely. I have building a rules chart of sorts as we learn how to make this work. We did the same with DPMA. All the subtle things that make it really work well.

Now the users do display properly. One rule that you state in the wiki is if start defining things with BLF, you are taking responsibility for how the BLF keys behave in every detail. The “blank” command is another example.

We are taking this slow as also suggested in your blog posts. Let’s get the basic functions we want to work first, in our case, the right people and queues on the individual pages on the D65. Once we have this laid out and tested, we will start adding behaviors and indications next.

Thanks again for the pointers…I know we are asking some very basic questions, but it is very helpful.

Best regards,

8

It’s uncommon in Alabama, but Huntsville’s rather uncommon, too.

re: typo, no worries. Over the weekend, having not read it carefully, I’d considered that the missing “blank” was suspect; glad it turned out to be simpler than that. :slight_smile: