Mitel 6867i Premium, Руководство администратора

Страница: 573 / 1042

Operational Features
5-312
CUSTOM AD-HOC CONFERENCE
Previously, the phone will wait for server response prior to completing the ad-hoc and centralized
conference feature. This results in an interoperability issue with certain call managers, such as
Genband. Now the phone no longer waits for server response before referring the call to the
conference host when the "
custom adhoc conference
" parameter is enabled.
CONFIGURING THE “CUSTOM AD-HOC CONFERENCE” FEATURE USING
THE CONFIGURATION FILES
You use the following parameters to configure the “Custom AD- Hoc Conference” feature in
the configuration files:
• custom adhoc conference
For specific parameters you can set in the configuration files, see Appendix A, the section,
“Custom Ad-Hoc Conference”
on
page A-93
.
“SIP JOIN” FEATURE FOR 3-WAY CONFERENCE
The IP Phones support a feature referenced in RFC 3911, which allows an additional caller to
join an active call between two parties if the caller knows the dialog information. This feature
begins a conference using a join header as described in RFC 3911.
The “SIP Join“ feature provides the following:
• Security via the whitelist (which is a feature that already exists on the phone).
• Initiates an offhook action uri when it is answered.
• Initiates an onhook action uri at call termination.
• Creates a caller list entry.
This feature is disabled by default. You can enable the “SIP Join” feature by setting the “sip
join support” parameter in the configuration files.
LIMITATIONS OF THE “SIP JOIN” FEATURE
The following are limitations of the “SIP Join” feature:
• Not applicable to a conference call already in progress.
• Not applicable to a phone mixing RTP.
• Allows secondary parties to join calls if they can determine the dialog parameters. In order
to provide security, it is recommended that the Administrator configure the SIP whitelist.
• Not applicable while the active call between two parties is in the early dialog state.
CONFIGURATION FILES