Wildix WP phones can play different ring melodies, the choice is available for each user and for each type of call. The system administrator can upload the ring tones to the PBX. Each SIP INVITE that is sent by the PBX to the WP phone contains the information about the ringtone. The wave file is downloaded by the phone from the HTTP resource and then cashed in the temp memory.
An example of SIP INVITE is:
Code: Select all
INVITE sip:firstname.lastname@example.org;line=4256 SIP/2.0.
Via: SIP/2.0/UDP 18.104.22.168;branch=z9hG4bKa30f.253c285b965fcf8f0f946762d69b6876.0;rport.
From: "Wildix Support" <sip:+email@example.com>;tag=as1af3c75a.
CSeq: 102 INVITE.
User-Agent: WildixGW 28608.
Date: Wed, 25 Feb 2015 11:45:33 GMT.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH.
Supported: replaces, timer.
P-Asserted-Identity: "Wildix Support" <sip:+firstname.lastname@example.org>.
The Alert-Info header notifies the ring melody.
If the phone doesn’t reproduce the custom ringtone, most probably it could not download the wave file and after reaching a timeout, the phone plays the standard melody (with a delay). To avoid this problem
: make sure that the phone is able to reach the PBX via the standard port 80, otherwise it might not be able to download the ring tone from HTTP.
During the first incoming call after the ringtone change or after the phone’s reboot, the new ringtone is played with delay (because it takes some time for the phone to download the file).