Revision as of 16:36, June 19, 2018 by Valentip (talk | contribs)
Jump to: navigation, search

Unsupported Functionality

[In progress]

[FDS: https://intranet.genesys.com/pages/viewpage.action?spaceKey=RDSIPS&title=SIP+Cluster+Feature+Support]

The following tabs provide high-level information about functionality that is not supported in this release of SIP Cluster. Consult documentation of particular products and corresponding product teams for possible limitations of their products in the SIP Cluster architecture.

SIP Cluster

The following general functionality is not supported in SIP Cluster: [NEW]

  • ISCC
  • ACD Queue
  • Options configured on the Agent Login level
  • Enterprise/PBX features:
    • Find-me-follow-me
    • Hunt-group
    • Nailed up connections (considered in the future)
    • Shared call appearance
    • Call Admission Control (CAC)


[OLD]

  • No Call Admission Control (CAC)
  • Multi-site Supervision
  • Remote Supervision (dial-in to routing strategy)
  • Transport Layer Security (TLS) for SIP signaling
  • Static call recording setting on a DN (the record option)
  • Extensions in TRouteCall for the selective recording
  • TSingleStepConference to gcti::record for the emergency recording
  • Profiles assigned to agent groups and virtual agent groups by dial plan
  • Bulk Registration—one registration for all DNs managed by T-Controller—is required (mandates a change on most clients)
  • Loss of functionality associated with config options for ACD Position and Extension DNs
  • Loss of functionality associated with some config options for Agent Login objects
  • IPv6
  • SIP Cluster does not provide explicit and implicit agent reservation functionality to TLib clients other than URS
  • Workspace Web Edition is the only supported agent desktop application
  • Technical seat licenses no longer required for SIP Server; licensing may be enforced only with usage-based reporting/LRM

SIP Server

The following SIP Server functionality is not supported in SIP Cluster:

  • Alternate Routing for Stranded Calls
  • Class of Service
  • Configuration of ACD queues
  • Contact Header Handling options
  • Dial plan (only Feature Server dial plan is supported)
  • Dummy SDP
  • 911 Enable Emergency Gateway
  • Emulated Agents
  • IMS
  • Instant Messaging
  • Interaction preview (before voice call delivered)
  • ISCC types are not supported: (direct-uui, direct-ani, and direct-notoken
  • ISCC Call Overflow
  • Media Server Reliability for NETANN
  • Nailed-up connections
  • NETANN
  • Network Attended Conference
  • P-Access-Network-Info Private Header
  • Personal Greetings for direct calls/transfers (only supported via TRouteCall)
  • Presence from Switches and Endpoints
  • Remote Server Registration
  • Smart OtherDN Handling
  • Trunk Capacity Support
  • Tromboning Control

SIP Proxy

The following SIP Proxy functionality is not supported in SIP Cluster:

  • DNS SRV resolution

Universal Routing

The following Universal Routing functionality is not supported in SIP Cluster:

  • Certain IRD functions and objects, see Routing Limitations
  • Some Predefined Statistics and Predefined Macros
  • Routing to and setting thresholds for non-configured DNs
  • Routing using agent capacity information
  • Strategy for ring-no-answer situations
  • Cost-based routing
  • Agents participating in multiple outbound campaigns
  • Load balancing

Historical Reporting

All ICON and Genesys Info Mart functionality is supported in SIP Cluster, but certain data is no longer reported or is reported differently. For more information, see Historical Reporting Deployment Considerations.

Web Services and Applications and Workspace Web Edition

The following Workspace Web Edition 8.5.2 on-premises features are not supported for SIP Cluster:

  • Remote agent phone number support
  • Nailed up connection establishment on first call
  • Routing Point monitoring and coaching

Genesys Interaction Recording

The Genesys Interaction Recording (GIR) solution is not yet available for SIP Cluster on premise deployment.




Comments or questions about this documentation? Contact us for support!