SD-Initiated Keep-Alives Configuration

Use the following procedure to configure SD-initiated Keep-Alives.

  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 options sbc-initiated-keep-alive-name attribute enables SD-initiated Keep-Alive on the current SIP interface and specifies the name of the proprietary Via header parameter used during the SD-initiated Keep-Alive negotiation.

    Prefix the command with a plus (+) sign to avoid over-writing existing options configuration.

    The following example enables SD-initiated Keep-Alives and identifies the proprietary rkeep header as the header that contains negotiation information.

    Note:

    Endpoints require prior knowledge of this proprietary header name because the SD lacks the capability to relay configuration data to relevant endpoints. 
    ORACLE(sip-interface)# options +sbc-initiated-keep-alive-name=rkeep 
ORACLE(sip-interface)#
  3. The option sbc-initiated-keep-alive-interval attribute specifies the frequency of SD-initiated Keep-Alives.
  4. If SD-initiated Keep-Alive is enabled on the current SIP interface (options sbc-initiated-keep-alive-name identifies a proprietary Via header parameter used for Keep-Alive negotiations), use the options sbc-initiated-keep-alive-interval attribute to specify the default interval between SD-initiated pings.

    Prefix the command with a plus (+) sign to avoid over-writing existing options configuration.

    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 30 seconds.

    This default interval will be used only the proprietary parameter proposed by the endpoint lacks a value. 

    ORACLE(sip-interface)# options +sbc-initiated-keep-alive-interval=45

    ORACLE(sip-interface)#

  5. Use done, exit, and verify-config to complete this configuration.
  6. If necessary, repeat Steps 1 through 5 to configure SD-initiated Keep-Alives on additional SIP interfaces.