
Version 5.6 269 November 2008
SIP User's Manual 4. ini File Configuration
Parameter Description
Module = Module number.
For example:
[CallWaitingPerPort]
CallWaitingPerPort 0 = 0,1,1$$;
CallWaitingPerPort 1 = 1,2,1$$;
[\CallWaitingPerPort]
If enabled, when an FXS interface receives a call on a busy
endpoint, it responds with a 182 response (and not with a 486
busy). The device plays a call waiting indication signal. When
hook-flash is detected, the device switches to the waiting call. The
device that initiates the waiting call plays a Call Waiting Ringback
tone to the calling party after a 182 response is received.
Notes:
If this parameter is not configured (default), use the global
parameter EnableCallWaiting (refer to “Supplementary
Services” on page 138).
The numbering of channels starts at 0.
This parameter can appear up to eight times for 8-port devices,
and up to 24 times for MP-124.
The device's Call Progress Tones file must include a 'call
waiting Ringback' tone (caller side) and a 'call waiting' tone
(called side, FXS interfaces only).
The EnableHold parameter must be enabled on both the
calling and the called sides.
To define call waiting using the Web interface, refer to “Call
Waiting” on page 361.
For a description on using ini file table parameters, refer to
“Structure of ini File Table Parameters” on page 233.
CHRRTimeout
For a description of this parameter, refer to “Supplementary
Services” on page 138.
EnableCallWaiting
For a description of this parameter, refer to ''Supplementary
Services'' on page 138.
3WayConferenceMode
Defines the mode of operation when the 3-Way Conference
feature is used.
[0] = Conference-initiating INVITE (sent by the device), uses
the ConferenceID concatenated with a unique identifier as the
Request-UR (default).
[1] = Conference-initiating INVITE (sent by the device), uses
only the ConferenceID as the Reques-URI.
If 3wayConferenceMode is set to 0, the Conference-initiating
INVITE sent by the device uses the ConferenceID concatenated
with a unique identifier as the Request-URI. This same Request-
URI is set as the Refer-To header value in the REFER messages
that are sent to the two remote parties.
If 3wayConferenceMode is set to 1, the Conference-initiating
INVITE sent by the device only uses the ConferenceID as the
Reques-URI. The media server sets the Contact header of the
200 OK response to the actual unique identifier (Conference URI)
to be used by the participants. This Conference URI is included
Kommentare zu diesen Handbüchern