4.5  

SIP Phone Features 
 

Definition  
The SIP protocol (Session Initiation Protocol) is an ASCII-based signaling protocol used to configure sessions in an IP network. This protocol is supported by SIP telephones. These telephones let the user conduct calls simply and in the usual manner via a data network.
Note: The term Internet telephony used in this documentation refers to calls conducted via networks supporting IP (Voice over IP) and signaling using the SIP protocol.

Actively supported features  
The following features for Internet telephony subscribers are actively supported:
 •   CLIP (displays the station number of the calling party on the called party's station)
optiPoint 150 S supports the feature in stand alone systems only.
 •   CLIR (surpresses the display of the station number of the calling party on the called party's station). The optiPoint 150 S telephone does not support the feature.
 •   COLP (displays the called party's station number on the calling party's station)
 •   COLR (surpresses the display of the station number of the called party on the calling party's station). The optiPoint 150 S telephone does not support the feature.
 •   Consultation hold
 •   Call hold
 •   Toggle
 •   Transfer (unscreened transfer and screened transfer)
The telephone series optiPoint 410 S and optiPoint 420 S do not support the unscreened transfer feature.
 •   MWI (from HiPath 3000/5000 V8). This feature is supported for SIP telephones in single nodes and networks. If there is a message on a voicemail system (HiPath Xpressions), it sends an MWI notification to the relevant SIP terminal via HiPath 3000/5000. This activates the MWI display on the SIP terminal.
 •   DISA (Direct Inward System Access): No features can be activated for the SIP telephone.
 •   In-band DTMF
optiPoint 150 S supports codec G.711 only.

Passively supported features  
Although Internet telephony subscribers cannot activate the following features, they can be passively integrated:
 •   Call forwarding (forwarding to an Internet telephony subscriber is supported.)
 •   Conference (Internet telephony subscriber can be passively integrated.)
 •   Parking (Internet telephony subscribers can be parked. From the point of view of the Intenet telephony subscriber this feature acts just like "Call Hold")
 •   Live Call Recording (Internet telephony subscribers can be passively integrated.)
 •   Whisper/Off Hook Announcement (Internet telephony subscriber can be passively integrated.)
optiPoint 150 S does not support the feature.
 •   Automatic COS Changeover (Internet telephony subscriber can be integrated into automatic COS Changeover.)
 •   Traffic Restriction Groups (Internet telephony subscribers can be included in ITR groups.)

Restrictions for Internet telephony subscribers  
Please note the following restrictions for Internet telephony subscribers:
 •   Internet telephony subscribers from HiPath 3000/5000 V6.0 are configured as DSS1 (functional telephone) and therefore cannot be monitored by the system (no monitoring). Internet telephony subscribers cannot use applications for which monitoring is necessary (for example HiPath ComAssistant).
 •   The integration of Internet telephony subscribers in call pickup groups, hunt groups, team, top or MULAP groups is not possible.
 •   Internet telephony subscribers cannot activate or use system features that can be controlled by code numbers.
 •   If a Internet telephony subscriber is put on hold, MOH is played. When an unscreened transfer of the Internet telephony subscriber to a different station is being carried out, no MOH or ringtone is played to the Internet telephony subscriber.
 •   If a parked Internet telephony subscriber is not unparked by the station that parked them, the display of the Internet telephony subscriber will not be updated.
 •   SIP telephones are not supported by the Deployment Tool (DLS Interface DLI) of the HiPath Xpressions Compact Boards (HiPath 3000).
 •   It is possible to toggle/connect between two external calls with the optiPoint 150 S. The active call can be dropped by quickly pressing hookswitch. By simply hanging up the optiPoint 150 S receiver, the two external stations would be connected to one another, which can lead to increased call charges. Such a connection can only be ended by deliberately disconnecting the trunks or by reseting (restart) the system.
 •   In certain situations, the telephone-specific features available cannot be used on HiPath 3000/5000 V8. This includes features that are available over the telephone's menu interface. The features available with the HiPath 3000/5000 V8 basic system have general release status.
Native SIP only supports:
 •   Basic Call

Dependencies/Restrictions  

 Subject  
 Dependency/Restriction  
System codes  
Features that are controlled by the system with system codes cannot be activated and used with SIP phones. As SIP phones have a specific menu, these features are accessed not via system codes but via the phone menu system. These functions are saved in the telephone, not in the HiPath system.  
Workpoint-specific features  
In certain situations, the workpoint-specific features available cannot be used on the HiPath system. This also includes features that are available over the workpoint's menu interface.  
Call Management (CM)  
In HiPath 3000 V7 and earlier systems, if a remote station does not answer, outgoing internal calls from an SIP workpoint via Call Management are not forwarded to the next destination on the call destination list. Forwarding is blocked in call processing, the payload data path must be negotiated dynamically, instead of just once (as implemented). However, dynamic negotiation is not possible with SIP workpoints.  
This restriction is no longer in place on HiPath 3000 V8 and later systems.  

Model-Specific Data  

 Subject  
 HiPath 3800  
 HiPath 3550  
 HiPath 3500  
 HiPath 3350  
 HiPath 3300  
Feature available in  
 x  
 x  
 x  
Hardware requirements  
 Supported telephones: optiPoint 410 S/optiPoint 420 S  
 optiPoint 150 S  
Software requirements  
 V6.0 SMR9 or later  
 V6.0 SMR9 or later  
 V6.0 SMR9 or later