
V6100 and V7122 User Guide
185
ini File Field Name
Web Parameter Name
Valid Range and Description
PreferRouteTable
[Prefer Routing Table]
Determines if the local Tel to IP routing table takes precedence over a
Proxy for routing calls.
0 = Only Proxy is used to route calls (default).
1 = The gateway checks the 'Destination IP Address' field in the 'Tel to IP
Routing' table for a match with the outgoing call. Only if a match is not
found, a Proxy is used.
Applicable only if Proxy is not always used
(‘AlwaysSendToProxy’ = 0, ‘SendInviteToProxy’ = 0).
EnableProxyKeepAlive
[Enable Proxy Keep Alive]
0 = Disable (default).
1 = Enable Keep alive with Proxy using OPTIONS.
2 = Enable Keep alive with Proxy using REGISTER.
If EnableProxyKeepAlive = 1, SIP OPTIONS message is sent every
ProxyKeepAliveTime. If EnableProxyKeepAlive = 2, SIP REGISTER
message is sent every RegistrationTime. Any response from the Proxy,
either success (200 OK) or failure (4xx response) is considered as if the
Proxy is correctly communicating.
This parameter must be set to 1 (OPTIONS) when Proxy
redundancy is used.
When EnableProxyKeepAlive = 2 (REGISTER), the homing
redundancy mode is disabled.
ProxyKeepAliveTime
[Proxy Keep Alive Time]
Defines the Proxy keep-alive time interval (in seconds) between Keep-Alive
messages.
The default value is 60 seconds.
This parameter is applicable only if EnableProxyKeepAlive = 1
(OPTIONS). When EnableProxyKeepAlive = 2 (REGISTER),
the time interval between Keep-Alive messages is determined
by the parameter RegistrationTime.
UseSIPTgrp
[Use Tgrp Information]
0 = Tgrp parameter isn’t used (default).
1 = (send only) The trunk group number is added as the ‘tgrp’ parameter to
the Contact header of outgoing SIP messages. If a trunk group number is
not associated with the call, the ‘tgrp’ parameter isn’t included. If a ‘tgrp’
value is specified in incoming messages, it is ignored.
2 = (send and receive) The functionality of outgoing SIP messages is
identical to the functionality described in option (1). In addition, for incoming
SIP messages, if the Request-URI includes a ‘tgrp’ parameter, the gateway
routes the call according to that value (if possible). If the Contact header
includes a ‘tgrp’ parameter, it is copied to the corresponding outgoing
messages in that dialog.
UserAgentDisplayInfo
[User-Agent Information]
Defines the string that is used in the SIP request header ‘User-Agent’ and
SIP response header ‘Server’. If not configured, the default string ‘3Com
product-name s/w-version’ is used (e.g., User-Agent: 3Com-Sip-Gateway-
V7122/v.4.80.004.008). When configured, the string ‘UserAgentDisplayInfo
s/w-version’ is used (e.g., User-Agent: MyNewOEM/v.4.80.004.008). Note
that the version number can't be modified.
The maximum string length is 50 characters.
Summary of Contents for V6100
Page 28: ...28 V6100 and V7122 User Guide Reader s Notes...
Page 48: ...48 V6100 and V7122 User Guide Reader s Notes...
Page 72: ...72 V6100 and V7122 User Guide Reader s Notes...
Page 80: ...80 V6100 and V7122 User Guide Reader s Notes...
Page 152: ...152 V6100 and V7122 User Guide Reader s Notes...
Page 262: ...262 V6100 and V7122 User Guide Reader s Notes...
Page 284: ...284 V6100 and V7122 User Guide Reader s Notes...
Page 291: ...V6100 and V7122 User Guide 291 Figure 95 V7122 Startup Process...
Page 324: ...324 V6100 and V7122 User Guide Reader s Notes...
Page 354: ...354 V6100 and V7122 User Guide Reader s Notes...
Page 374: ...374 V6100 and V7122 User Guide Reader s Notes...
Page 382: ...382 V6100 and V7122 User Guide Figure 130 Example of a User Information File Reader s Notes...
Page 392: ...392 V6100 and V7122 User Guide Reader s Notes...
Page 409: ...V6100 and V7122 User Guide 409 Reader s Notes...
Page 413: ...V6100 and V7122 User Guide 413 Reader s Notes...
Page 425: ...V6100 and V7122 User Guide 425 Figure 145 UDP2File Utility Reader s Notes...
Page 431: ...V6100 and V7122 User Guide 431 Reader s Notes...
Page 447: ...V6100 and V7122 User Guide 447 Reader s Notes...
Page 483: ...V6100 and V7122 User Guide 483 Reader s Notes...