Configuring Outbound Contact
Outbound Contact supports a VoIP deployment that enables automated outbound dialing and call-progress detection when using SIP Server in the SIP Cluster environment. Outbound Contact Server (OCS) supports all VoIP dialing modes in the SIP Cluster environment.
Complete the following configuration to enable outbound functionality in your SIP Cluster environment:
- Configure the OCS application
- Configure Switch objects
- Configure a Communication DN
- Configure Trunk Group DNs
Configure the OCS application
- Follow the standard deployment procedure for deploying OCS. OCS is connected to only one SIP Cluster Node in the data center.
- On the Connections tab, add the following connections:
- The primary SIP Server of the SIP Cluster Node that is deployed in the same data center. (OCS is connected to the T-Controller port, TCport.)
- The primary VQ SIP Server that is deployed in the same data center.
- The primary Stat Server that is deployed in the same data center.
Configure Switch objects
Configure a Communication DN
- Under Switches > VQ-switch > DNs, create a Communication DN. Only one Communication DN must be created in the VQ-switch.
- In the Annex tab of the Communication DN, create the [default] section. In the [default] section, create the outbound_contact_server option and set it to true.
Configure Trunk Group DNs
- Under Switches > SIP_Cluster > DNs, create a DN of type Trunk Group for each data center.
- In the Annex > [OCServer] section, set the outbound_contact_server to true.
- In the Annex > [TServer] section, configure the following configuration options:
|geo-location||<A string identifying the data center to which this DN belongs>|
(FQDN of the active-active RM pair resolved in SRV records)
Running Campaign Groups
- When campaign groups run in Active-backup mode, note the following:
- Only one OCS is used at a time.
- All campaign groups run on this OCS.
- OCS in another data center is used only in a disaster recovery scenario.
- When campaign groups run in Active-active mode, they run on the OCS in both data centers.
Limitation: If multiple OCS instances are running campaign groups in parallel in the same environment, one OCS is not aware what campaign groups have been already run on the other OCS.