Jump to: navigation, search

Deleting Party From Conference

SIP Server now supports TDeleteFromConference requests in multi-site deployments in the same way as in single-site deployments; that is, any agent can remove any other party from the conference using a TDeleteFromConference request containing a targeted party DN.

Feature Configuration

To enable TDeleteFromConference requests support in multi-site deployments, configure the SIP Server Application, as follows:

  1. In the TServer section, set the following configuration options:
    • sip-enable-call-info—Set this option to true.
      The Call Participant Info functionality must be activated, enabling SIP Server to maintain an LCTParty list containing DNs and their locations for all parties present in the call. The LCTParty list is distributed to a T-Library client in EventUserEvent.
    • sip-remote-del-from-conf—Set this option to true.
  2. In the extrouter section, set the use-data-from configuration option to current. This enables Party Events propagation.

sip-remote-del-from-conf

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Related Option: sip-enable-call-info

In multi-site 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. The OtherDN attribute of the TDeleteFromConference request must contain the party ID received in the LCTParty list. When this option is set to false, this feature is disabled.

Feature Limitations

  • In a multi-site conference in which two DNs have identical names, if TDeleteFromConference is requested to remove a DN with the duplicate name, either one or both parties can be deleted from the conference.
  • In multi-site scenarios, real-time statistics related to call supervision (particularly CallObserved) may be incorrect if the supervisor is released from the call before the call is finished. See Stat Server documentation for details.
This page was last modified on May 20, 2015, at 13:50.

Feedback

Comment on this article:

blog comments powered by Disqus