Distinctive Ringing protocol

PBX sends URI of a ring melody in SIP ‘Alert-Info’ header field in the following format:

Alert-Info: <URI>[;<RINGER_INFO>[;<POSTFIX>]]

[] – includes optional parameters

<URI>

URI of the ringer melody. If a special (configurable) URI is used, e.g.: <http://www.notused.com>, or <http://127.0.0.1>

then it means for the phone that Alert-Info contains local ring melody tag, otherwise URI points at a ringer melody (in .wav format) in the network, which shall be downloaded and played by the phone.

<RINGER_INFO>

Tag of internal ringer melody in the form <info=TAG>. TAG is configured via phone’s Web UI.

<POSTFIX>

Groupcall:

Alert-Info: <http://www.notused.com>;info=alert-group

Internal call:

Alert-Info: <http://www.notused.com>;info=alert-internal

external call:

Alert-Info: <http://www.notused.com>;info=alert-external

Examples

Alert-Info from Broadsoft PBX; the phone generates ringer pattern as required by Broadsoft:

<http://127.0.0.1/Bellcore-dr2>
<http://127.0.0.1/Bellcore-dr3>
<http://127.0.0.1/Bellcore-dr4>
<http://127.0.0.1/Bellcore-dr5>

External melody to be downloaded from the network; the phone downloads and plays the melody:

<http://www.example.com/sounds/moo.wav>

Phone internal melodies; the user has to assign ringer tags to the internal melodies via the phone’s Web UI:

<http://www.notused.com>;info=alert-external;
<http://www.notused.com>;info=alert-group;
<http://127.0.0.1>;info=alert-boss;
<http://127.0.0.1>;info=alert-sell-office;

Gigaset T300/T500 programming:

In the Gigaset T300/T500 you can enable distinctive ringing by changing the Manual configuration of the line settings, like the example below.

Here we added the line:

exten => _.,3,SIPAddHeader(Alert-Info: <http://127.0.0.1>\;info=alert-external)

This causes that for every incoming external call, the Alert-Info header is added and the device now can react on this using a special ringtone.