Cisco, Yealink XML remote phone book synchronization

If you are planning to synchronize a large number of contacts, we recommend to configure Softphone.pro to obtain customer data from third-party system. This allows you to handle a lot more contacts and open a link to the Contact's page in your system from the incoming call window, which is not possible with XML contacts.

Softphone.Pro can synchronize with remote phone book. The remote phone book should be Cisco, Yealink XML file format located on shared network folder or HTTP/HTTPS web-server.

Configure Cisco, Yealink XML file synchronization

Download Cisco, Yealink XML remote phone book example

1. Open Settings - Contacts - XML File section:

2. Enter XML file display Name:

You can see that display name in a hint. The hint occurs when you place mouse cursor over a special "external contact" icon displayed near the contact. It can be helpful if you have multiple remote phone books.

3. Select appropriate XML file location (local\network shared folder or HTTP link) and enter file full path:

4. Enter reload timeout in minutes in Reload every, min. text input:

5. If you want to transfer calls to the persons you are going to synchronize, enable Transfer calls to this contact checkbox. All the persons from XML remote phone book will be displayed on Call transfer dialog window.

6. If your cloud or on-site PBX supports «Presence indication» feature and your XML file contains other PBX users, enable Enable presence indication checkbox. You also need to select an appropriate PBX SIP account. Read more on Presence indication (BLF).

If there are multiple phone numbers defined per contact, then Softphone.Pro uses the phone number with less digits for presence indication subscription.

Extended Cisco, Yealink XML file attributes

If your XML file stores both clients and coworkers' phone numbers you might want to enable or disable call transfer and/or contact presence indication (BLF) for particular contacts rather than the whole file. Use additional attributes described below to achieve that.

• UseForTransfer: can be 0 (do not show contact in the transfer list) or 1 (do not show contact in the transfer list). If missing transfer status depends on parameter chosen when configuring synchronization.
• EnableBLF: can be 0 (BLF is disabled for contact), 1 (BLF is enabled). If missing BLF usage status depends on parameter chosen when configuring synchronization.
• BlfSipAccount. Numerical order of SIP account (starts from 0 - the first SIP account, 1 - the second, etc. up to 31), used for BLF events subscription. If missing SIP account for BLF is the one that was picked when configuring synchronization.
• BlfSipUser. Contact's SIP username on the PBX. If missing the shortest number of contact is used.

Example of Cisco, Yealink XML record with additional parameters:

        <DirectoryEntry>
            <Name>Doctor Dolittle</Name>
            <Telephone type="ext">100</Telephone>
            <Telephone type="mobile">+19001234567</Telephone>
            <Telephone type="home">+19007654321</Telephone>
            <Telephone type="work">+19005555555</Telephone>
            <UseForTransfer>1</UseForTransfer>
            <EnableBlf>1</EnableBlf>
            <BlfSipAccount>0</BlfSipAccount>
            <BlfSipUser>user100</BlfSipUser>
        </DirectoryEntry>
        

See all articles