Contents
Routing Principles in SIP Cluster
[New Page] Given below is a sample deployment diagram to illustrate the routing principles in SIP Cluster:
In the above sample, there are two data centers (DC) with two SIP Cluster nodes each. All SIP Server applications are assigned to the same SIP Cluster switch. The VQ DNs are configured using a separate switch.
SIP Cluster Deployment
- Each SIP Cluster node has a dedicated routing solution consisting of URS, ORS, and Stat Server.
- SIP Server applications of each SIP Cluster node are assigned to the same SIP Cluster switch where all routing point DNs and agent DNs are configured. Based on that, all SIP Cluster nodes serve the same set of routing points, and inbound calls are distributed across all SIP Cluster nodes.
ORS Deployment
- A dedicated one-node ORS Cluster is deployed to serve each SIP Cluster node.
- A dedicated Cassandra ring is deployed for each ORS Cluster.
- cassandra-keyspace-name: Orchestration
- cassandra-nodes: FQDN_SIP_Cluster_Primary_VM; FQDN_SIP_Cluster_Backup_VM
VQ Switch Configuration and Connectivity
VQ switches offer a distributed agent reservation solution for a blended environment (voice and multi-media). A VQ switch is a centralized place for VQ DN configuration and they help simplify provisioning. VQ switches also result in a performance improvement by helping unload VQ traffic from the SIP cluster.
In the above sample diagram, there is one VQ SIP Server pair per DC. Having independent SIP Server pairs configured with the same switch is possible because we are not provisioning any real DNs on this switch. As a result, the SIP Server pair do not interfere with each other.
- One HA VQ SIP Server is deployed per DC.
- All VQ SIP Servers are assigned to the same VQ switch. Only VQ DNs are configured in the VQ switch.
- The routing Stat Server instance is connected to all VQ SIP Severs, but each URS and ORS instance is connected only to the VQ SIP Server located to in the local DC.