Contents
Unsupported and Partially Supported Functionality
[Ready for review]
[FDS: https://intranet.genesys.com/pages/viewpage.action?spaceKey=RDSIPS&title=SIP+Cluster+Feature+Support]
This topic provides high-level information about functionality that is not supported or partially 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 Server
- Universal Routing
- Historical Reporting
- Web Services and Applications and Workspace Web Edition
- Genesys Interaction Recording
Unsupported SIP Server functionality
The following SIP Server functionality is not supported in SIP Cluster:
- ACD Queues
- Alternate Routing - Stranded Calls
- Alternate Routing - Unresponsive ORS/URS
- Associating an ACD Queue with a Routing Point
- Asterisk Voice Mail Integration
- Call Completion Features
- Call Park/Retrieve
- Call Pickup
- Call Recording NETANN-Based
- Supervision of Routing Points
- Remote Supervision
- Class of Service
- Contact Header Handling Options
- Dial Plan (only Feature Server dial plan is supported)
- Dummy SDP
- E911 Emergency Gateway
- Find Me Follow Me
- Hunt Goups
- IMS Integration
- Instant Messaging
- ISCC (Multi-site support)
- Media Server Reliability NETANN
- Nailed-Up Connections
- Network Attended Transfer
- P-Access-Network-Info Private Header
- Presence from Switches and Endpoints
- Preview Interactions
- Remote Server Registration
- Shared Call Appearance
- Smart OtherDN Handling
- Trunk Capacity Support
- Tromboning Control
- Trunk Optimization for Multi-Site Transfers
Unsupported SIP Server configuration options
This list contains SIP Server configuration options that are not supported and not related to the functionality listed above.
Application level:
- external-registrar
- internal-registrar-enabled
- internal-registrar-domains
- internal-registrar-persistent
- emergency-recording-cleanup-enabled
- emergency-recording-filename
- dtmf-payload
- max-legs-per-sm
- registrar-default-timeout
- sip-retry-timeout
- shutdown-sip-reject-code
- sip-legacy-invite-retr-interval
DN level:
- use-register-for-service-state
Partially supported SIP Server functionality
The following SIP Server functionality is partially supported in SIP Cluster:
| Feature Name | Setting Level | Supported | Comments |
|---|---|---|---|
| Alternate Routing | |||
| stranded-calls-overflow | App | N | Alternate Routing for Stranded Calls not supported (ACD) |
| stranded-on-arrival-calls-overflow | App | N | Alternate Routing for Stranded Calls not supported (ACD) |
| stranded-call-redirection-limit | App | N | Alternate Routing for Stranded Calls not supported (ACD) |
| sip-invite-timeout | APP | Y | |
| no-response-dn | DN | P | Works but conflicts with Feature Server forwarding |
| default-dn | App, DN (RP) | Y | |
| router-timeout | App | Y | |
| default-route-point | App | Y | |
| Automatic Inactive Agent Logout | |||
| auto-logout-timeout | App, DN (RP) | P | Only Application level is supported. |
| auto-logout-ready | App, DN (RP) | P | Only Application level is supported. |
| logout-on-disconnect | APP/DN (RP) | P | Only Application level is supported. |
| Call Recording MSML-based | |||
| recording-filename | App | Y | |
| msml-record-support | App | Y | |
| record-consult-calls | App | Y | |
| record | DN | P | |
| rtp-info-password (not in the DG) | App | Y | |
| no-rtp-password-configured (not in the DG) | App | Y | |
| RTP-PASSWORD (not in the DG) | Ext | Y | |
| Dynamic Call Recording | AttributeExtensions are supported in TRouteCall, but not in TPrivateService from a client to TC. | ||
| id | Ext | N | |
| record | Ext | P | Only in TRouteCall. |
| dest | Ext | N | |
| params | Ext | N | |
| Emulated Agents | |||
| emulate-login | Ext | N | |
| emulated-login-state | App, DN | P | Only Application level is supported |
| agent-strict-id | App | N | |
| sync-emu-agent | App, DN | N | |
| override-switch-acw | App | N | |
| untimed-wrap-up-value | App | N | |
| wrap-up-time | App, DN, Ext | P | Only Application and AttributeExtensions are supported. |
| wrap-up-threshold | App | N | |
| legal-guard-time | App, Ext | Y | |
| timed-acw-in-idle | App | Y | |
| acw-in-idle-force-ready | App | Y | |
| agent-emu-login-on-call | App, DN, Ext | N | |
| agent-logout-on-unreg | App, Ext | N | logout-on-disconnect is provided however. |
| enable-agentlogin-presence | App | N | Implemented by feature-server instead. |
| enable-agentlogin-subscribe | App | N | Implemented by feature-server instead. |
| auto-logout-ready | App, DN | P | App only. AL and DN not supported. |
| auto-logout-timeout | App, DN | P | Only Application level is supported. |
| logout-on-disconnect | App, Ext | Y | |
| logout-on-out-of-service | App | Y | |
| reason-in-extension | App | N | Triggered by NOTIFY. But SIP Cluster does not know the agent state. |
| agent-logout-reasssoc | App | N | TRegisterAddress from the same client name does not re-associate ownership, only TAgentLogin will. |
| Endpoint Service Monitoring | |||
| oos-check | DN | Y | |
| oos-force | DN | Y | |
| recovery-timeout | DN | Y | |
| oos-options-max-forwards | DN | Y | |
| sip-oos-enabled | DN | N | Passive OOS is not supported. |
| No-Answer Supervision | |||
| *-no-answer-overflow | App, DN, AL | P | agent-no-answer-overflow -- Only Application level is supported. |
| *-no-answer-action | App, DN, AL | P | agent-no-answer-action -- Only Application level is supported. |
| *-no-answer-timeout | App, DN, AL | P | agent-no-answer-timeout -- Only Application level is supported. |
| nas-private | App | Y | |
| set-notready-on-busy | App | Y | |
| NO_ANSWER_TIMEOUT | Ext | Y | |
| NO_ANSWER_OVERFLOW | Ext | Y | |
| NO_ANSWER_ACTION | Ext | Y | |
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.
