When configured for both online and offline charging, it may be desirable to allow sessions to proceed when there is a communications outage with the OCS.

By default Sentinel-Volte will end a session if there is no connection to the OCS, or there is a timeout waiting for a response from the OCS. The following procedure can be used to allow sessions to proceed in these cases.

Note that when configured this way, for a session that detects an OCS communication problem:

  • No further Ro communication will occur even if communication is re-established

  • Rf and CDRs will continue to track the session

  • A midsession failure for a conference call will result in the session ending


The following changes to the ${platform.operator.name}_FeatureExecutionPointTable profile table will allow a session to proceed.

  1. Modify these execution points to use the MMTel_SipAccess_ControlNotRequiredPostCC execution script.

    • SipAccess_OCSFailurePostCC:sipcall:mmtel-orig:

    • SipAccess_OCSFailurePostCC:sipcall:mmtel-term:

    • SipAccess_OCSFailurePostCC:sipcall:mmtel-conf:

  2. Modify these execution points to use the VoLTE_No_Action_Required execution script.

    • SipMidSession_OCSFailurePostCC:sipcall:mmtel-orig:

    • SipMidSession_OCSFailurePostCC:sipcall:mmtel-term:

  3. Modify these execution points to use the MMTel_Post_SipMidSession_CreditAllocatedPostCC execution script.

    • post:SipMidSession_OCSFailurePostCC:sipcall:mmtel-orig:

    • post:SipMidSession_OCSFailurePostCC:sipcall:mmtel-term:

Previous page Next page
Sentinel VoLTE Version 2.9.0