Share via

3.9.5.2.2.2 Delegate Ringing

  • Article

This section follows the product behavior described in endnote <55>.

If in the processing of the INVITE based on the routing rules, the proxy decides to honor delegate ringing, the following actions MUST be taken:

  • If the address-of-record in the URI of the From or the Referred-By header field is present in the delegates list, the INVITE MUST be routed to primary targets, as specified in section 3.9.5.2.2.1.

  • If the user's presence published in the state category for the container to which the caller belongs, as described in [MS-PRES], is "do-not-disturb", the call MUST be forked to the targets present in the delegates list and the secondary target timer MUST be started.

  • If the user’s presence state is not "do-not-disturb", the call MUST be routed to all the registered endpoints of the user and the primary user timer MUST be started. <56>

  • If the user’s presence state is not "do-not-disturb", the call MUST be routed to all of the targets present in the delegates list. The secondary target timer MUST be started.