3.2.2.5 Message Processing Events and Sequencing Rules

  • Article

The processing rules follow the procedures specified in [RFC3261] section 10.3, [RFC3265] section 4.4.8, and [IETFDRAFT-OUGRUAUSIP-10] section 7.1.2.

A binding SHOULD be considered terminated when the registration expiry timer or the keep-alive timer fires, as specified in section 3.1.2.6. In this case, the SIP registrar might do either of the following options:

  • Expire the registration binding, but keep the SIP endpoint identifier, as defined in section 3.1.2.1, with routable state set to "false". This is useful when the registrar keeps additional state associated with the SIP endpoint that is independent of the binding itself. With this option, when a subsequent re-registration is received for the expired endpoint, the Presence-State header SHOULD contain a Register-Action field with the value "fixed".

  • Expire the registration binding and remove the SIP endpoint identifier, as defined in section 3.1.2.1. With this option, when a subsequent re-registration is received for the expired endpoint, the Presence-State header SHOULD contain a Register-Action field with the value "added".