Info from Cisco:
Already added in Firmware 6.0 which is beta right now
DSP
The phone has undergone a complete new DSP upgrade. This
addresses some of the limitations that currently exist in the DSP today.
The following tones/ringing patterns have been added:
Bellcore-BusyVerify
Bellcore-Stutter
Bellcore-MsgWaiting
Bellcore-dr1
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
Bellcore-dr5
Alert-Info
The phone now has the ability to play all internal ring tones based on
the presence of the Alert-Info header. The initial support for
this was added in the Release 4.4 timeframe, but this additional
support allows the Alert-Info header to use the new tones/ringing
patterns.
(1) Short problem description:
Selectable ring tones using Alert-Info: header
(3) Possible solution (what did you expect):
Existing Alert-Info: header can change ringer cadence, but is limited
to two tones (normal and "double-ring".) It would be useful to be
able to specify what ringer should be used by either a fully-qualified
URL to the ringtone
(as described in the RFC as an example) or a numeric that indicates
which ringtone in the Cisco's call list should be used. This is useful
to identify _who_ is calling, and just as much it can identify what
number they called to get to that deskset.
(5) Workaround used currently (if applicable):
Using multiple lines on the same phone to indicate what # is being
called
(7) Would you classify this as:
(F) Nice if feature existed
(see 6)
(9) Contact information:
John Todd <jtodd@SPAM.loligo.com>
(11) Report:
Message-Id: <p05210656bb1cfefe5479@loligo.com>
Date: Mon, 23 Jun 2003 13:15:22 -0700