The voip.conf file contains configuration parameters that you edit to customize discovery and other aspects of VoIP Availability Manager behavior. The parameters are a subset of attributes defined for the VoIP-Manager object that will run in the VoIP Availability Manager environment.
You use the voip.conf file to change discovery parameters, instrumentation parameters, and tracing and troubleshooting parameters. For example, you can change parameters in this file to accomplish tasks such as disabling automatic topology synchronization and enabling SNMP trap reception.
All of the parameters in the voip.conf file are commented-out (preceded with the # character). When changing the default value for a commented-out parameter, ensure that you also remove its # character.
Parameters in the voip.conf file describes the parameters in the voip.conf file. The parameters and their values are case-sensitive.
Parameter |
Value |
Description |
---|---|---|
SNMP Discovery Parameters |
||
SNMP_timeout |
Default: 1000 milliseconds |
Timeout for an SNMP poll during Phase 3 of discovery. Phase 3 of discovery is described in the VMware Smart Assurance VoIP Availability Manager Discovery Guide. The SNMP_timeout parameter is comparable to the “defaultTimeout” parameter in the discovery.conf file of an IP Manager installation. The VMware Smart Assurance IP Management Suite Discovery Guide provides recommendations about changing the defaultTimeout parameter value.
Note:
SNMP_timeout = 0 defaults to 1000 milliseconds. |
SNMP_retries |
Default: 5 retries |
Number of SNMP retry polls to use during Phase 3 of discovery. Phase 3 of discovery is described in the VMware Smart Assurance VoIP Availability Manager Discovery Guide. The SNMP_retries parameter is comparable to the “defaultRetries” parameter in the discovery.conf file of an IP Manager installation. The VMware Smart Assurance IP Management Suite Discovery Guide provides recommendations about changing the defaultRetries parameter value.
Note:
SNMP_retries = 0 defaults to 5 retries. |
NumberOfProbeThreads |
Default: 10 threads |
Number of discovery threads used by the discovery process. If you are experiencing slow response SNMP discovery polling and your current CPU usage is relatively low (say 5 to 10 percent) consider increasing the number of discovery threads to improve your discovery performance. Increasing this number is one of the best and simplest methods for improving discovery. Increasing threads to 20, 30 or even 50 discovery threads is acceptable, but keep in mind that more threads may require additional or more capable CPUs and that the requirements during discovery will increase. Increase threads conservatively while monitoring SNMP Processing Statistics changes.
Note:
NumberOfProbeThreads = 0 defaults to 10 threads. |
EnablePhoneDiscovery |
TRUE,FALSE Default: FALSE |
Controls whether VoIP Availability Manager discovers IP phones and IP phone groups for Avaya, Cisco, and Nortel vendors. It also controls whether phone-related topology (like ports, cards, and network adapter performance objects) are imported from IP Availability Manager whenever IP Availability Manager completes a discovery cycle:
If this parameter is set to TRUE, the AnalysisMode polling setting is automatically enabled. |
EnableVoiceMailboxDiscovery |
TRUE,FALSE Default: FALSE |
Controls whether VoIP Availability Manager discovers voice mailboxes for Cisco.
|
EnableBIMIntegration |
TRUE,FALSE Default: FALSE |
Controls whether VoIP Availability Manager creates BIM entities and establish dependencies with VoIP topology.
|
DXA control parameters |
||
AutoDiscover |
TRUE,FALSE Default: TRUE |
Controls whether VoIP Availability Manager automatically performs a topology synchronization to import topology from IP Availability Manager whenever IP Availability Manager completes a discovery cycle:
“Disabling automatic synchronization” on page 35 provides more information about this parameter. |
DiscoverAll |
TRUE,FALSE Default: FALSE |
Controls VoIP Availability Manager discovery after IP Availability Manager performs discovery.
|
Instrumentation parameters |
||
TrapPort |
0, 9001, 2049 to 65534 Default: 0 |
Enables the VoIP Availability Manager built-in trap receiver and specifies the port used by the trap receiver to receive traps:
“Enabling trap reception” on page 36 clarifies the use of this parameter.
Note:
For the Avaya Enablement Pack, Cisco Enablement Pack, Nortel Enablement Pack, and VoIP Performance Manager Integration Pack, the built-in trap receiver needs to be enabled so that traps issued by devices can be received and processed. |
Tracing and troubleshooting parameters |
||
TraceSNMPInstrumentation |
TRUE,FALSE Default: FALSE |
Determines whether SNMP poll tracing is enabled or disabled:
|
TraceSOAPMonitoring |
TRUE,FALSE Default: FALSE |
Determines whether the tracing of SOAP monitoring is enabled or disabled. |
TraceSOAPDiscovery |
TRUE,FALSE Default: FALSE |
Determines whether SOAP discovery tracing is enabled or disabled. |
TraceDiscovery |
TRUE,FALSE Default: FALSE |
Determines whether discovery probe tracing is enabled or disabled:
|
TraceEvents |
TRUE,FALSE Default: FALSE |
Determines whether internal event subscriber tracing is enabled or disabled:
|
TraceSetting |
TRUE,FALSE Default: FALSE |
Determines whether settings tracing is enabled or disabled:
|
TraceTraps |
TRUE,FALSE Default: FALSE |
Determines whether the built-in trap receiver tracing is enabled or disabled:
|
TraceCLI |
TRUE,FALSE Default: FALSE |
Determines whether CLI discovery tracing is enabled or disabled.
Note:
When TRUE, the CLI dialog conducted with each Nortel Signaling Server is captured in a file located in the log directory. |
TracePMTraps |
TRUE,FALSE Default: FALSE |
Determines whether the tracing occurs of VoIP Performance Manager trap receiver processing.
|
SyncDelay |
240 to 3600 Default: 300 |
The number of seconds that the VoIP Performance Manager Trap Processor will wait after the initial VoIP Performance Manager related topology update (after the initial PNODES traps are processed). The ExternalName attributes of VoipCluster, CallManager, ConvergedCallManager should be progagated after the initial VoIP Performance Manager related topology update. See the VoipPerformanceManager::ConnectedAt attribute to determine the initial connection time. |
PMTraps_Timeout |
240 to 3600 Default: 240 |
The minimum value for VoIP Performance Manager Traps Timeout is 240 seconds (4 minutes). The recommended maximum value is 3600 seconds (1 hour).
|
MaxNumPIDMonitors |
0 to 500 Default: 500 (maximum) |
The maximum number of PID monitors invoked each minute. |
PIDPollingInterval |
0 to 3600 Default: 240 |
Number of seconds to wait between attempts to probe the Host resource MIB to detect when an unresponsive process has been restarted. PIDPollingInterval = 0 disables polling. |