Prevent prefetching of remote phonebook

[Travis_Yealink]

(01-17-2017 11:35 AM)dmark Wrote:  Hello Travis,

thank you for your answer. I sent you the requested video and additionally
- the Apache access.log when opening the remote phonebook. You can see a bunch of http requests within a few seconds.
- the "http-result-u_41.txt" shows the result of initially calling the remote phonebook for user "41" (parameter "u=41"). It is mainly the XML Menu with three URLs.
- the "http-result-u_41-t_imported.txt" shows the result of calling the "imported Company-wide Phonebook" (Parameters u=41&t=imported). There are the first 15 entries and the URLs for the SoftKeys to refine the search.

The problem is that the Yealink phones immediately start requesting all further HTTP URLs they find in a XML Menu or Directory.

Further Info: I try to implement Yealink support for the (mainly) german open source PBX "Gemeinschaft 3" (https://github.com/amooma/GS3). You can find the remote phonebook implementation for the Snom phones here:
https://github.com/amooma/GS3/blob/maste...nom/pb.php

I try to do something similar for Yealink so the User does not need to care about which phone he/she actually uses.

Hello,

I met similar case before, the cause is the Yealink phone mechanism, that means it's designed so.

In our new V81 firmware, we have a better search function for remote phonebook.
1. please upgarde the firmware to 28.81.0.41, download link as below:
http://ftp.yealink.com/?ShareToken=482CA...985C5BA9AC

2. After firmware upgrading, set below parameters via autoprovision:
remote_phonebook.super_search.enable = 1
directory.search_type = 1

3. delete softkey items on your remote phonebook file (ONLY contacts included), and then test the new search function.

The new method doesn't occupy much memory, and I already got good feedback from other customers. Wait for your test result.

Any misunderstanding, please let me know.

Regards
Travis