Registration Event Package

If subscription to the Registration Event package (defined in RFC 3680, A Session Initiation Protocol (SIP) Event Package for Registrations) is enabled, the P-CSCF receives asynchronous NOTIFYs from the core reporting registration state changes. Each NOTIFY provides a </reg-info> XML element that reports state changes. A sample XML report is shown below.

   <registration aor="sip:[e-mail]" id="as10" state="active">

          <contact id="86" state="active" event="created">
               <uri>sip:[5555::aaa:bbb:ccc:ddd]</uri>
          </contact>

   </registration>



   <registration aor="sip:[e-mail]" id="as11" state="active">

          <contact id="86" state="active" event="created">
               <uri>sip:[5555::aaa:bbb:ccc:ddd]</uri>
          </contact>


          <ere:wildcardedIdentity>sip:ep_user!.*!@home1.net</ere:wildcardedIdentity>

   </registration>

</reginfo>

If a </wildcardedIdentity> sub-element is included in the <registration> element (as in the second </registration>, the wildcarded PUI is taken from the </wildcardedIdentity> sub-element, and that wildcarded PUI replaces any previously stored wildcarded PUIs in the registration.

In the absence of </wildcardedIdentity> sub-element(as in the first registration), the PUI is taken from the ‘aor’ attribute of the registration element, and the registration cache is left unchanged.