The following features are supported via defined SIP methods between 3300 ICP and Generic SIP Endpoints unless otherwise indicated:
All SIP devices must be registered with the 3300 ICP, which acts as the Registrar. Once registration is completed, SIP devices can make and receive calls. Calls made to an unregistered SIP device will fail, similar to calls placed to a non-existent IP device. Calls made from a SIP device that has not registered with the 3300 ICP will receive SIP error message 404 - Not Found.
Note: When a handset is out of range or switched off, calls from other phones to that extension provide ringback instead of overflow tone. This behavior applies to KIRK sets and to wired SIP sets that are unplugged.
To support Busy Override on SIP phones, set the "Enable Digit Collection During Busy or Alerting State" option to "Yes" in the SIP Devices Capabilities form of the SIP phones.
When the dialed destination is busy, a caller can activate Busy Override by entering the Busy Override feature access code.
Note: The 5302 SIP phone does not support Busy Override.
SIP users can participate in all different kinds of groups and have the same restrictions as Minet sets.
To support Callback on SIP phones, set the "Enable Digit Collection During Busy or Alerting State" option to "Yes" in the SIP Devices Capabilities form of the SIP phones.
If a SIP Phone user reaches an extension that is busy does not answer, the user can activate a Callback by dialing the Callback feature access code. Note that the SIP phone display does not prompt the user to enter the feature access code. If the Callback is successfully activated, the user hears feature confirmation tone. If the Callback is not activated, the user hears error tone.
Note: The 5302 SIP phone does not support Callback.
The Generic SIP Phone can have Call Forwarding options programmed against its DN. The programming of call forwarding destinations, as well as the activation and deactivation of call forwarding, is performed using feature access codes. In addition to supporting the 3300 ICP forwarding behavior, SIP phones can also provide local call forwarding directly from the set using SIP REDIRECT messages defined in RFC 3261.
SIP devices can place a call on hold and music may be provided by their endpoint.
The SIP user can retrieve the held party by dialing the feature access code for Call Retrieve.
Calls can be parked against the user DN and retrieved by using the Call Park Retrieve feature access code.
The following exceptions apply to these features when you use them from SIP phones:
SIP phones cannot be configured with feature keys to park and retrieve calls.
Calls cannot be parked to SIP phones that are not registered or in service.
A SIP phone user cannot make additional calls or activate features while his or her call is parked.
SIP phones that do not support RFC 3515 cannot park calls.
The 3300 ICP provides RFC compliant SIP signalling support for blind (unattended) and supervised (attended) transfers. Blind transfer is based on the REFER method defined in RFC 3515. Supervised transfers rely on the "Replaces" header defined in RFC 3891, and allows the following:
CANCEL transfer operation and reversion back to the original caller (in case of Mitel SIP phone, the Cancel key can be used). This must be accommodated during the ringing and answered states.
RELEASE transfer resulting in the connection of the current and held party.
TRADE between two calls
CONFERENCE between parties involved in the transfer
The name and number of the calling party is present to the SIP phone at setup time, if available. If the call originated on a 5ESS PRI trunk, the calling name and number may not be available.
When the SIP Phone initiates a call, the name and number supplied in the FROM header will be used as the calling party name and number.
To support Camp-on on SIP phones, set the "Enable Digit Collection During Busy or Alerting State" option to "Yes" in the SIP Devices Capabilities form of the SIP phones.
When a dialed destination is busy, a caller can activate the Camp-on feature by entering the Campon feature access code. When the feature is activated, the user at the called device hears a Campon tone that indicates a caller is waiting.
Note: The 5302 SIP phone does not support Camp-on.
SIP phones support the following forms of conference:
Conference hosted by the 3300 ICP (proprietary feature). To obtain 3300 ICP hosted conference on SIP phones:
In the SIP Device Capabilities form assigned to the SIP phones, enable the "Replace System based with Device based In-Call Features" option.
Configure the SIP phones with a second line appearance. The line appearance must be a multi-call appearance of the prime line.
Users must invoke the conference using the conference feature access code. The code can either be pre-programmed into a menu item or key on the phone, or it can be entered manually. For example, to enter a feature access code manually on an IP DECT (Global) Solution wireless handset, the user presses the "r" key twice and then dials the code.
Locally hosted conference (if supported by the SIP phone - in the SIP Device Capabilities form assigned to the SIP phone, enable the "Replace System based with Device based In-Call Features" option.)
Conference bridge
Conference hosted on a conference resource known to the 3300 ICP (3300 ICP hosted conference is only available if "Replace System based with Device based In-Call features" is disabled in the SIP Device Capabilities form).
When a SIP user makes a call to the 3300 ICP, the current number and name being alerted is displayed (wait for answer display). When the call is answered, it may not be answered by the same number that was presented to the caller in wait for answer state. If this is the case, then the answering party's name and number are displayed to the caller.
For example:
A calls B
C has an appearance of B
When B and C start ringing, the Display on A indicates B is ringing.
C answers the call and the answer message contains C's name and number.
SIP users can be members of a Pickup groups. When a member in the groups is ringing and the SIP device can pick up the call using the Dialed Pickup feature access code.
SIP devices can pick up calls by using the Directed Call Pickup feature access code and the DN of the device to be picked up.
SIP devices can activate Do Not Disturb by dialing the Do Not Disturb feature access code.
Other devices in the network can be configured to monitor the SIP device. The DSS/BLF behavior is limited when a SIP device is being monitored. On and off-hook events, and certain key presses in some cases are not monitored.
This feature provides the following improvements:
Caller Emergency Service Identification (CESID) when a generic SIP phone makes an emergency call. The information provided is an ID number and if programmed, a comment. If no comment is programmed for the device, then the emergency caller's telephone directory name is displayed.
an SNMP event is generated to the Emergency Response Advisor when a generic SIP phone makes an emergency call. The CESID number in the SNMP event must be the default CESID number or a programmed CESID number for the generic SIP phone.
Emergency Services - Location Notification is also supported on Generic SIP Phones.
Generic SIP Phones: While
users are logged into a SIP device, feature access keys that are available
on MiNet sets will not be accessible
The administrator can assign any specific usage for programmable keys, since they are not defined. The key assignment shown below is an example only.
5302 SIP Phones: The 5302 SIP Phone has four programmable keys that are hard coded as CDE Speed Calls, which can be programmed in the System Administration Tool to provide the following features:
Key
#3 - Voicemail
Key #4 - Conference
Key #5 - Personal Speed Call 1
Key #6 - Personal Speed Call 2
See SIP Phone Support Programming for instructions on programming these keys.
SIP users can be members of a hunt group and calls are presented to the SIP device as they normally would to the Minet user.
With the exception of the 5302 SIP Phone, a SIP device may have the line appearances of other devices, or broadcast groups in the system.
SIP devices can use Last Number redial by using the appropriate feature access code.
Message Waiting indications are only provided for the prime line associated with the Generic SIP phone user.
A SIP phone can initiate a direct page using the Direct Page feature access code and the DN of the device to be paged. The regular COS checks apply. SIP devices can perform loudspeaker pages to specific zones or all zones by using the feature access codes.
If the 3300 ICP reboots, either due to a planned upgrade or unplanned occurrence such as a power outage, the 3300 ICP remembers the registration information for non-resilient SIP devices and automatically re-creates the registrations. This allow the SIP devices to place and receive calls without having to wait for the devices to re-register on their own at some later time.
This feature supports using name strings in the URI An Internet address, such as www.mitel.com, with a protocol prefix, such as http://, to indicate the type of Internet service being addressed.. The feature uses the URI/Number translation table configured by the system administrator.
SIP devices may retrieve held calls, which reside on other devices by dialing the Remote Hold Retrieve access code. When the SIP device places a call on hard hold, others in the system can pick the call up.
SIP devices can initiate a system speed call by dialing an abbreviated Speed Call Number.
This feature is not supported.
