AASTRA 6700i series, 9143, 9480i, 9480i CT SIP Administrator Guide EN - Manual (Page 619)

5-342 41-001343-01 Rev 03, Release 3.2.2
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
“SIP Join” Feature for 3-Way Conference
The IP Phones support 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:
2 In the “Conference Server URI” field, do one of the following actions:
• To disable centralized conferencing on this line, leave this field empty (blank).
• To enable SIP centralized conferencing on this line, do one of the following actions:
— If you have specified a proxy server/registrar server, then to reach the media server via the
proxy server, set this field to one of the following:
conf (Sylantro server), or
Conference (Broadsoft server)
By setting this field to conf or Conference, you specify conf@<proxy_server _address>:
<proxy_port>.
— To reach the media server using a different address/port than that specified by the proxy,
set this field to the following:
conf@<media_server _address>: <media_port>
3 Click to save your changes.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section, “Custom Ad-Hoc
Conference” on page A-97.
Aastra Web UI