registrar-default-timeout
Section: sipproxy
Default Value: 0
Valid Values: Any positive integer
Changes Take Effect: On the next REGISTER request
Specifies the expiration timeout for a REGISTER request as a value, in seconds, in the 200 OK response that is sent by SIP Proxy to the SIP endpoint, and as a value in the REGISTER request that is forwarded to SIP Server. When this option is set to 0, or is not defined, the expires value from the Contact or Expires headers from the REGISTER request is used as the expiration timeout. If the option is set to any value other than 0, the timeout is set to the lesser of the option value and the value specified by the client.
oos-force
Section: sipproxy
Default Value: 5
Valid Values: 1–32
Changes Take Effect: Immediately
Specifies how often, in seconds, SIP Proxy checks whether the out-of-service SIP Server starts to respond.
oos-check
Section: sipproxy
Default Value: 5
Valid Values: 0–300
Changes Take Effect: Immediately
Specifies how often, in seconds, SIP Proxy checks SIP Servers for out-of-service status. If this option is set to 0, SIP Proxy does not check SIP Servers for out-of-service status.
geo-location
Section: sipproxy
Default Value: No default value
Valid Values: Any alphanumeric string
Changes Take Effect: After restart
Specifies the data center to which SIP Proxy belongs.
Configuring SIP Proxy
SIP Proxy is an application with active-active HA mode. There should be two SIP Proxy applications deployed in one data center.
- Deploy two SIP Proxy applications by following the standard procedure. When creating a SIP Proxy application, use the Genesys Generic Server type.
- Suggested application names: SIPProxy_<datacenter>_1, SIPProxy_<datacenter>_2.
- On the Connections tab, add the following connections:
- confserv_proxy_<datacenter>—Set to the following parameters:
- Connection Protocol: addp
- Trace Mode: Trace On Both Sides
- Local Timeout: 60
- Remote Timeout: 90
- SIP Proxy must be connected to the Configuration Server Proxy deployed on the first SIP Cluster Node in the local data center.
- MessageServer_<datacenter>—Set to the following parameters:
- Connection Protocol: addp
- Trace Mode: Trace On Both Sides
- Local Timeout: 7
- Remote Timeout: 11
- SIP Proxy must be connected to the Message Server deployed on the first SIP Cluster Node in the local data center.
- confserv_proxy_<datacenter>—Set to the following parameters:
- On the Tenants tab, add the tenant to be served by the SIP Proxy application.
- On the Server Info tab, set the following parameters:
- Host—Specify the host on which this SIP Proxy is installed.
- Ports—Specify the following SIP Proxy ports:
| ID | Listening Port | Connection Protocol |
|---|---|---|
| default | Any available port number | |
| mgmt-port | Any available port number | mgmt |
| http-port | Any available port number | http |
| sip-port | Any available port number | sip |
5. On the Options tab, create a section named sipproxy. In the [sipproxy] section, add the following options:
- geo-location=<the name of the data center>
- oos-check=5
- oos-force=5
- registrar-default-timeout=140
6. Add created SIP Proxy applications to the sipproxy-applications option of the SIP Cluster DN.
See required provisioning and examples of SRV records in Configuring DNS Records.