Jdruker/SIPCluster
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 is partially supported in this release of SIP Cluster. Consult the documentation of particular products and corresponding product teams for possible limitations of their products in the SIP Cluster architecture.
New format
Solution | Limitations or differences |
---|---|
SIP Server | Certain features or functionality are either not supported in SIP Cluster or are not fully supported. For full details, see: |
Universal Routing | The following Universal Routing functionality is not supported in SIP Cluster:
|
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:
|
Genesys Interaction Recording (GIR) | The GIR solution is not yet available for SIP Cluster on premise deployment. |
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 table presents SIP Server functionality partially supported in SIP Cluster. The table entries use these notations:
- N—Not supported
- Y—Supported
- P—Partially supported
- App—Application-level setting
- DN—DN-level setting
- AL—Agent Login-level setting
- Ext—AttributeExtensions
- RP—Routing Point
Feature Name | Setting Level | Supported | Comments |
---|---|---|---|
Alternate Routing | |||
sip-invite-timeout | App | Y | |
no-response-dn | DN | P | It 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 | Only DN level is supported, but Agent Login level is not. |
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 | |||
id | Ext | N | |
record | Ext | P | It is supported 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 | |
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 | Only Application level is 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 | It is 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 does. |
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 |
- Multi-Site Supervision--Supervision works when a supervisor is in SIP Cluster and an agent is in the standalone switch. It does not work when a supervisor is on the standalone switch and an agent is in SIP Cluster.