Specifications

Aastra July 2014 PA-001011-03-04
320
This implementation means that the server must host all the pictures in the right format which can
be pretty tedious.
19.2 Application implementation
To simplify the deployment of the picture Caller ID, Aastra has developed an application which
answers to the phone requests but also:
 converts any size picture (png, jpeg, gif) to the right format and cache the converted
picture,
 allows number/picture matching (cell phone number, home number…),
 allows phone number pattern matching,
 allows to customize the matching picture by adding a custom label.
With this application, an administrator does not have to convert the pictures to the right format, he
just has to put the pictures in any format (jpeg, gif or png) in the “pictures” directory for instance
using XXXX.yyy where XXXX is the user extension number.
The administrator can also create number or pattern matching to display all kind of pictures using
the configuration file “pictureID.conf” as described in chapter 19.5.2.3.
Here is how the algorithm works (NUMBER is the incoming or outgoing number)
1. Checks if NUMBER.png is in the cache directory (if yes sends the image back)
2. Remove local prefixes and check the transformed number (if yes sends the image back)
3. Check basic mapping and check the transformed number (if yes sends the image back)
4. Check advanced pattern matching and check the transformed number (if yes sends the
image back)
5. Remove external prefix and check the transformed number (if yes sends the image back)
6. Remove international prefix and check the transformed number (if yes sends the image
back)
7. Sends a HTTP 404 (Image Not found) or the configured image
19.3 Requirements/Compatibility
19.3.1 HTTP Server
Operating System:
 Microsoft Windows Server 2003/2008
 Microsoft XP/Vista/7
 Most flavors of Linux
HTTP Server:
 Microsoft IIS
 Apache
 Lighttpd
PHP
 Release 5.0 or better,