Welke functionaliteit hebben SIP toestellen op een OpenScape Office

Bron: Feature description OpenScape Office V3 R3

Hieronder staat beschreven welke functionaliteit een SIP client wel of niet heeft in combinatie met een OpenScape Office systeem. Let goed op dat het eerste deel de telefonie functionaliteit beschrijft en het tweede deel de UC functionaliteiten vanuit de OSO applicaties.

SIP Features Supported by OpenScape Office

The following SIP features are supported by OpenScape Office.

INFO: The full functionality of the features depends on the SIP phone used and cannot be guaranteed.

  • Authentication
    Before using a SIP phone, the phone must be registered at the communication system using the configured call number. To protect against SIP attacks (SIP Attack Protection), authentication is strongly recommended.
  • Basic call
    Both incoming and outgoing calls as well as late SDP connection setups are supported.
  • Display of name and telephone number
    During the call setup, the name and number of the SIP phones involved appear on the display. As a prerequisite, the names must have already been configured in the communication system, and no restrictions (caller ID suppression of the caller and/or called party) should apply.
    SIP phones generally allow the configuration of a device name. However, instead of any device name that may have been configured, OpenScape Office always shows the name configured in the communication system.
  • Call waiting
    The feature is disabled in the default setting of the communication system. Activation is possible on a station-specific basis using station flags.
  • Call forwarding
    In general, SIP phones allow the configuration of call forwarding destinations. Call Forwarding on Busy (CFB), Call Forwarding Unconditional (CFU) and Call Forwarding No Reply (CFNR) are supported. It is important to ensure that the call forwarding configured in the SIP phone does not conflict with any other call forwarding that may have been configured in the communication system. For example, if call forwarding is configured in the SIP phone phone after 20 seconds, it would not be executed if the call forwarding configured in the communication system occurs after 15 seconds.
  • Placing a call on hold, resuming a call and alternating between calls (toggle/ connect)
    Placing a call on hold, resuming a call and alternating between calls (toggle/ connect) are all supported. The communication system can play back Music on Hold (MOH) to subscribers on hold.
  • Transfer
    Both blind transfers and consultation transfers (also called supervised transfers) are supported.
  • Message Waiting Indication
    The signaling of new voice messages at the SIP phone is supported. The type of signaling depends on the phone being used (acoustic signaling using a special dial tone, optical signaling via a Mailbox key (if configured) and/or a display message).
  • Different Call Signaling
    Different call signaling for internal and external calls and callbacks is supported. This requires the SIP telephone to be configured correctly.
  • Video
    Video connections between the SIP phones of one OpenScape Office communication system or between the SIP phones of a homogeneous network of OpenScape Office communication systems are supported. Video connections to the ITSP are not possible.

Restrictions:

  • The "Speaker call" and "Direct answering" features cannot be used with ISDN or SIP telephones.
  • No programming of function keys is possible for SIP phones. Furthermore, no features can be activated or deactivated via codes. Specific display messages of a call pickup group are not supported.
  • SIP telephones can be integrated in a hunt group.
    INFO: No programming of function keys is possible for SIP phones. Furthermore, no features can be activated or deactivated via codes. Specific display messages of a hunt group are not supported.

  • UCD or Contact Center: It is not possible to use ISDN and SIP phones here.
  • SIP telephones can be integrated in a Basic MULAP. 

    As a prerequisite, a system telephone (IP phone, HFA) must have been defined as the first member of the Basic MULAP. Dual-mode mobile phones that are configured as Mobility Entry stations, for example, can be integrated. Dual-mode mobile phones support both GSM/UMTS networks and WLAN networks. A dual-mode mobile phone can be registered as an IP station (SIP client) at the communication system over a WLAN. 
    INFO: No programming of MULAP keys is possible for SIP phones. Furthermore, no features can be activated or deactivated via codes. Specific display messages of the Basic MULAP are not supported.

 

Features of the UC Clients that can be used with SIP Telephones

The following features of the UC clients myAttendant, myPortal for Desktop and myPortal for Outlook can be used with SIP telephones.

The used SIP telephone must satisfy the following prerequisites:

  • 3PCC as per RFC 3725 is supported. 
  • The "Call waiting" feature is supported.
  • Do Not Disturb is disabled.
    Alternatively, for subscribers with SIP phones, DND can be activated in the communication system.
    INFO: The full functionality of the features depends on the SIP phone used and cannot be guaranteed.
    A successful test of the features was performed with OpenStage 15 SIP.
  • Connection-/call-oriented features:
    • Make Call
    • Redirect call
    • Resume call
    • Application-controlled conference
    • Placing a call on hold
    • Alternate (Toggle/Connect)
    • Consultation
    • Disconnect
    • Transfer
  • Phone-oriented features:
    • Do Not Disturb
    • Call forwarding
Hebt u meer vragen? Een aanvraag indienen

Opmerkingen