Enpoint-Initiated Keep-Alives Configuration

You use the registrar-keep-alive attribute, available in SIP Interface configuration mode, to enable endpoint-initiated Keep-Alives on a SIP interface.

  1. In Superuser mode, use the following ACLI command sequence to access SIP Interface configuration mode. 
    ORACLE# configure terminal
ORACLE(configure)# session-router
ORACLE(session-router)# sip-interface
ORACLE(sip-interface)#
  2. The registrar-keep-alive attribute enables endpoint-initiated Keep-Alive on the current SIP interface.

    none — (the default) disables endpoint-initiated Keep-Alive processing

    always — assuming that the endpoint has included the keep parameter in the Via REGISTER request header, forces the SD to place a keep parameter and an assigned in the Via REGISTER response — thus enabling endpoint-initiated Keep-Alive exchange with that endpoint

    bnat — assuming that the endpoint has included the keep parameter in the Via REGISTER request header, forces the SD to place a keep parameter and an assigned value in Via REGISTER response only if the requesting endpoint is identified as being behind an intervening NAT device (based on comparing source IP packet addresses with IP addresses extracted from the SIP request). 

    ORACLE(sip-interface)# registrar-keep-alive bnat
ORACLE(sip-interface)#
  3. If Keep-Alive is enabled on the current SIP interface (registrar-keep-alive is always or bnat), use the nat-interval attribute to specify the value of the keep parameter provided by the SD to SIP endpoints served by a UDP connection.

    Allowable values are integers within the range 1 through 4294967295 (seconds).

    In the absence of an explicit assignment, this attribute defaults to a value of 30 seconds.

    The SIP endpoint transmits periodic STUN binding requests so that the interval between each request is randomly distributed between 80 and 100 percent of the value of the nat-interval attribute.

    Assuming the default value (30 seconds) the interval between STUN binding requests would vary from 24 to 30 seconds. This default value closely aligns to Section 4.4.2 of RFC 5626, which recommends that the time between each keep-alive request SHOULD be a random number between 24 and 29 seconds. 

    ORACLE(sip-interface)# nat-interval 20
ORACLE(sip-interface)#
  4. If Keep-Alive is enabled on the current SIP interface (registrar-keep-alive is always or bnat), use the tcp-nat-interval attribute to specify the value of the keep parameter provided by the SD to SIP endpoints served by a TCP or TCP/TLS connection.

    Allowable values are integers within the range 1 through 999999999 (seconds).

    In the absence of an explicit assignment, this attribute defaults to a value of 90 seconds.

    The SIP endpoint transmits periodic pings at intervals specified by this attribute. 

    ORACLE(sip-interface)# tcp-nat-interval 120
ORACLE(sip-interface)#
  5. Use done, exit, and verify-config to complete this configuration.
  6. If necessary, repeat Steps 1 through 5 to configure Keep-Alives on additional SIP interfaces.