User`s manual

SIP User's Manual 5. Web Management
Version 5.0 135 December 2006
Table 5-35: Protocol Management, ini File Parameters (continues on pages 132 to 137)
ini File Parameter
Name
Valid Range and Description
3WayConferenceMode
Defines the mode of operation when the 3-Way Conference feature is used.
Valid options include:
[0] = Conference-initiating INVITE (sent by the gateway), uses the ConferenceID
concatenated with a unique identifier as the Request-UR (default)
[1] = Conference-initiating INVITE (sent by the gateway), uses only the
ConferenceID as the Reques-URI
If 3wayConferenceMode is set to 0, the Conference-initiating INVITE sent by the
gateway, 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
gateway, 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
(by the gateway), in the Refer-To header value in the REFER messages sent by
the gateway to the remote parties. The remote parties join the conference by
sending INVITE messages to the media server using this conference URI.
WarningToneDuration
Defines the duration (in seconds) for which Off-Hook Warning Tone is played to
the user.
The valid range is -1 to 2,147,483,647 seconds. The default is 600 seconds.
Note: A negative value indicates that the tone is played infinitely.
FXONumberOfRings
Defines the number of rings before the FXO gateway answers a call.
The valid range is 0 to 255. The default is 0 seconds.
PhoneContext
Defines the Phone Context table.
When a call is received from the ISDN, the NPI and TON are compared against the
table, and the Phone-Context value is used in the outgoing SIP INVITE message.
The same mapping occurs when an INVITE with a Phone-Context attribute is
received. The Phone-Context parameter appears in the standard SIP headers
where a phone number is used (Request-URI, To, From, Diversion).
PhoneContext = <Number Plan>,<Number Type>,<Phone-Context>
For example:
PhoneContext = 0,0,unknown.com
PhoneContext = 1,1,host.com
PhoneContext = 9,1,na.e164.host.com
Note 1: This parameter can appear up to 20 times.
Note 2: Several rows with the same NPI-TON or Phone-Context are allowed. In
this scenario, a Tel-to-IP call uses the first match.
Note 3: Phone-Context '+' is a unique case as it doesn't appear in the Request-
URI as a Phone-Context parameter. Instead, it's added as a prefix to the phone
number. The '+' isn't removed from the phone number in the IP-to-Tel direction.
Note 4: To configure Phone Context table using the Web interface, refer to Section
5.5.4 on page 96.