Remote agent deletion from a conference (TDeleteFromConference)

Starting with version 8.1.104.34, SIP Server supports remote agent deletion from a conference (TDeleteFromConference) in the mixed SIP Server and T-Server for Cisco Unified Communications Manager (CUCM) multisite environment.

SIP Server supports the following scenarios:

• When remote agent deletion from a conference is invoked on the SIP Server while a party is terminated on the other SIP Server peer.
• When remote agent deletion from a conference is invoked on the SIP Server while a party is terminated on the T-Server for CUCM peer.
• When remote agent deletion from a conference is invoked on the T-Server for CUCM while a party is terminated on the SIP Server peer.

A remote TDeleteFromConference request is a TDeleteFromConference request with a special key-value pair location=remote_tserver_location in AttributeExtensions.

While processing the TDeleteFromConference request, SIP Server does not verify AttributeOtherDN or the location value. The remote server executes this request only if the location value matches the server location and OtherDN could be found on the call. If the remote server ignores the request, the initiating server responds with Error Code 57 (ErrorTimeout) after the timeout expires.

This feature does not depend on the LCT party (Call Participant Info) functionality.

The new value of hybrid is added to the existing sip-remote-del-from-conf configuration option. In multisite deployments, when this option is set to true, SIP Server processes a TDeleteFromConference request to remove a remote party (specified in OtherDN) from a conference.

With a value of hybrid, SIP Server processes a TDeleteFromConference request even if the remote server is not a SIP Server (for example, T-Server for CUCM). The remote deletion from a conference could be done on the SIP Server peer, on the T-Server for CUCM peer, and any other T-Server that supports the same remote deletion from a conference rules as T-Server for CUCM supports.