Operational Features
5-95
41-001343-02 REV05 – 07.2014
With consideration to scenarios where a dial tone should be played even if the phone is in a “No Service” state (e.g. sce-
narios where the proxy may still accept INVITEs from the phone even if unregistered), the “
no service congestion tone
”
parameter has been programmed as disabled by default.
Configuring the No Service Congestion Tone
Use the following procedures to configure the no service congestion tone feature.
Priority Alerting
Priority alerting on the IP phones is a feature that allows incoming calls to trigger pre-defined ringing or call waiting alert
tones.
You can enable or disable priority alerting on the IP phone for the Asterisk, BroadWorks, and Sylantro servers using the
configuration files and the Aastra Web UI. Configuration of priority alerting is on a global-basis only.
How Priority Alerting Works
When the IP phone detects an incoming call, the phone firmware inspects the INVITE request in the IP packet for an
"Alert-Info" header.
If it contains an "Alert-Info" header, the firmware strips out the URL and keyword parameter and maps it to the appropri-
ate Bellcore tone.
If there is no keyword parameter in the "Alert-Info" header, or the INVITE message contains no "Alert-Info" header, then
the IP phone firmware uses the Bellcore standard ring tone.
Asterisk/BroadWorks Servers
The ring tone keywords that can display in the "Alert-Info" header for an Asterisk and BroadWorks server are:
•
Bellcore-dr2
•
Bellcore-dr3
•
Bellcore-dr4
•
Bellcore-dr5
When the ring tone keywords appear in an "Alert-Info" header from an Asterisk or BroadWorks server, the IP phone maps
the keywords to the default ring tone patterns.
Example:
The following are examples of the Asterisk/BroadWorks Server ring tone keywords:
Alert-Info: <http://127.0.0.1/Bellcore-dr2>
or
Alert-Info: <Bellcore-dr2>
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section,