ISCC Proxy [DRAFT]
ISCC (Inter Server Call Control) Proxy is the SIP Server module that is responsible for multi-site transactions between SIP Cluster and any T-Servers/SIP Servers that may run in the Genesys environment.
ISCC Proxy plays a role of a proxy when an external T-Server/SIP Server connects to it. Other ISCC Proxies in the cluster environment that do not have connections to external T-Servers/SIP Servers play the "node" role.
ISCC Proxy/ISCC node connection supports traditional ISCC functionality, namely:
- User Data propagation
- Event Party Propagation
- Transaction Monitoring
ISCC Proxy performs the following functions:
- Establishes connections with external T-Servers/SIP Servers.
- Manages its own pool of ISCC-related resources (access resources, External Routing Points for the route ISCC transaction type).
- Acts as a proxy between the Session Controller and an external T-Server/SIP Server.
- Processes ISCC transactions for its own calls that were distributed by SIP Proxy.
- Retransmits the user data synchronization events and remote party events to ISCC nodes.
- Reports unsuccessful non-distributed transactions by the Transaction Monitoring protocol.
ISCC Node performs the following functions:
- Establishes connections to the ISCC proxies.
- Knows the resources distribution among ISCC Proxies, so it can properly detect the owner of the call arrived.
- Uses ISCC Proxy to communicate with an external T-Server/SIP Server.
- Transmits all multi-site call updates (user data or party event ) through the appropriate ISCC Proxy.
- Distributes all Transaction Monitoring events for calls that are recognized as ISCC-controlled.
Note: Each T-Server/SIP Server connects to only one ISCC Proxy (SIP Server instance). The deployment could include several ISCC proxies. ISCC Nodes do not connect to external T-Servers/SIP Servers.
Backward Compatibility
SIP Cluster provides ISCC backward compatibility and is able to communicate with previous versions of T-Servers/SIP Servers. External T-Servers/SIP Servers should not be modified to interact with SIP Cluster via ISCC Proxy. SIP Cluster supports the following transaction types: route, reroute, pullback, and dnis-pool. In case of DNIS pooling, ISCC Proxy does not support targeting to a switch which is linked to the multiple T-Server applications (load balance deployment).
Configuration
The following configuration options can be configured, as necessary, in the extrouter section of the SIP Server Application:
DN Level > TServer section
iscc-proxy
Default Value: Empty string
Valid Values: Any available SIP Server application name in the cluster
Changes Take Effect: Immediately
For External Routing Points only. This option specifies the ISCC Proxy which owns this External Routing Point allocation. Default value (empty string) means that ISCC Proxy allocates all available resources (useful in case of one ISCC proxy per cluster only).