Configuring Bypass Behavior

To configure bypass behavior for configuration parameters on the SBC, use the sti-config object under session-router. You can configure individual headers and entire scenarios to bypass.

1. Access the sti-config configuration element.

   ORACLE# configure terminal
   ORACLE(configure)# session-router
   ORACLE(session-router)# sti-config
   ORACLE(sti-config)#

2. To set a header to bypass STI-VS, type stivs-bypass-header followed by the header name, and then press Enter.

   ORACLE(sti-config)# stivs-bypass-header P-Header-Name

3. To set a header to bypass STI-AS, type stias-bypass-header followed by the header name, and then press Enter.

   ORACLE(sti-config)# stias-bypass-header P-Header-Name

4. To set scenarios to bypass STI-AS:
   1. Type sti-bypass-token-scenarios followed by the list of scenarios, and press Enter. Use + to add a scenario and - to remove a scenario. If you do not include + or -, any existing value is replaced.

      ORACLE(sti-config)# sti-bypass-token-scenarios sti-error-response sti-server-timeout internal-client-error 

      Valid scenarios are:

      • sti-error-response
      • sti-server-timeout
      • invalid-sti-response
      • tn-missing
      • sti-constraints-exceeded
      • sti-server-unreachable
      • internal-client-error
      • sti-server-bypass
      • sti-server-disabled
      • sti-signaling-attest-info-mandatory
   2. Type sti-static-bypass-token followed by a default token to include in the P-Identity-Bypass header of the egress INVITE when bypassing, and press Enter.

      ORACLE(sti-config)# sti-static-bypass-token token

5. Type done.
6. Save and activate your configuration.