Configuring the N11 Timers

This section describes how to configure the N11 timers.

The N11 timer configuration is invoked when AMF rejects the N1N2 message transfer with the cause code as "Temporary reject registration ongoing" or "Temporary reject handover ongoing", then SMF considers the timer and reattempts the message transfer. When the timer expires, the transfer is reattempted based on the configured retry count.

configure 
   profile failure-handling failure_handling_name 
      interface [ gtpc | N11 ] message message_type 
         cause-code [ temp-reject-register | temp-reject-handover ]   
            action [ retry { timeout timeout_duration | 
            max-retry retry_count } | clear | terminate ] 
            end 

NOTES:

  • profile failure-handling failure_handling_name — Enter the name of the profile for failure handling.

  • interface [ gtpc | N11 ] — Configures the interface over which the message transfer must happen.

  • message message_type — Configures the message type that must be transferred over the interface. The N11 interface supports the message type as n1n2transfer.

  • cause-code [ temp-reject-register | temp-reject-handover ] — Configures the HTTP cause code. You can configure multiple cause code values for a message.

  • action [ retry | clear | terminate ] — Configures the action that must be performed when the message transfer is not successful.

    Note

    Clear and terminate are not supported for the N11 interface.

  • action [ retry { max-retry retry_count | timeout timeout_duration } — Specifies the number of times the message transfer must be reattempted and the time interval between the consecutive attempts.