Indicates whether or not you wish the Modem Manager to answer calls.
If set to 0 (false), the Modem Manager will never attempt to answer an incoming modem call.
If set to 1 (true), the Modem Manager will answer incoming calls.
Default: AnswerCalls = 0
Local telecommunications authorities may have regulations regarding the frequency at which call attempts are made to a particular number (e.g. BABT British Telecom rules). The CycleLength, CycleDelay, and CallIntervalX variables allow a re-dial cycle to be defined. CallInterval1 Indicates the number of seconds to wait after the first connection attempt in a call cycle fails.
Any CallInterval variables with intervals larger than CycleLength are ignored.
(For further information, please refer to Modem Manager Configuration Variables).
Related Variables: CycleLength indicates the number of times that CallInterval1 through CallInterval10 occurs. CycleDelay indicates the amount of time that the system will wait before beginning the entire call cycle again.
Default: CallInterval1 = 5
Local telecommunications authorities may have regulations regarding the frequency at which call attempts are made to a particular number (e.g. BABT British Telecom rules). The CycleLength, CycleDelay, and CallIntervalX variables allow a re-dial cycle to be defined. CallInterval2 indicates the number of seconds to wait after the second connection attempt in a call cycle fails.
Any CallInterval variables with intervals larger than CycleLength are ignored.
(For further information, please refer to Modem Manager Configuration Variables).
Related Variables: CycleLength indicates the number of times that CallInterval1 through CallInterval10 occurs. CycleDelay indicates the amount of time that the system will wait before beginning the entire call cycle again.
Default: CallInterval2 = 60
Local telecommunications authorities may have regulations regarding the frequency at which call attempts are made to a particular number (e.g. BABT British Telecom rules). The CycleLength, CycleDelay, and CallIntervalX variables allow a re-dial cycle to be defined. CallInterval3 indicates the number of seconds to wait after the third connection attempt in a call cycle fails.
Any CallInterval variables with intervals larger than CycleLength are ignored.
(For further information, please refer to Modem Manager Configuration Variables).
Related Variables: CycleLength indicates the number of times that CallInterval1 through CallInterval10 occurs. CycleDelay indicates the amount of time that the system will wait before beginning the entire call cycle again.
Default: CallInterval3 = 120
Local telecommunications authorities may have regulations regarding the frequency at which call attempts are made to a particular number (e.g. BABT British Telecom rules). The CycleLength, CycleDelay, and CallIntervalX variables allow a re-dial cycle to be defined. CallInterval4 indicates the number of seconds to wait after the fourth connection attempt in a call cycle fails.
Any CallInterval variables with intervals larger than CycleLength are ignored.
(For further information, please refer to Modem Manager Configuration Variables).
Related Variables: CycleLength indicates the number of times that CallInterval1 through CallInterval10 occurs. CycleDelay indicates the amount of time that the system will wait before beginning the entire call cycle again.
Default: CallInterval4 = 120
Local telecommunications authorities may have regulations regarding the frequency at which call attempts are made to a particular number (e.g. BABT British Telecom rules). The CycleLength, CycleDelay, and CallIntervalX variables allow a re-dial cycle to be defined. CallInterval5 indicates the number of seconds to wait after the fifth connection attempt in a call cycle fails.
Any CallInterval variables with intervals larger than CycleLength are ignored.
(For further information, please refer to Modem Manager Configuration Variables).
Related Variables: CycleLength indicates the number of times that CallInterval1 through CallInterval10 occurs. CycleDelay indicates the amount of time that the system will wait before beginning the entire call cycle again.
Default: CallInterval5 = 600
Local telecommunications authorities may have regulations regarding the frequency at which call attempts are made to a particular number (e.g. BABT British Telecom rules). The CycleLength, CycleDelay, and CallIntervalX variables allow a re-dial cycle to be defined. CallInterval6 indicates the number of seconds to wait after the sixth connection attempt in a call cycle fails.
Any CallInterval variables with intervals larger than CycleLength are ignored.
(For further information, please refer to Modem Manager Configuration Variables).
Related Variables: CycleLength indicates the number of times that CallInterval1 through CallInterval10 occurs. CycleDelay indicates the amount of time that the system will wait before beginning the entire call cycle again.
Default: CallInterval6 = 600
Local telecommunications authorities may have regulations regarding the frequency at which call attempts are made to a particular number (e.g. BABT British Telecom rules). The CycleLength, CycleDelay, and CallIntervalX variables allow a re-dial cycle to be defined. CallInterval7 indicates the number of seconds to wait after the seventh connection attempt in a call cycle fails.
Any CallInterval variables with intervals larger than CycleLength are ignored.
(For further information, please refer to Modem Manager Configuration Variables).
Related Variables: CycleLength indicates the number of times that CallInterval1 through CallInterval10 occurs. CycleDelay indicates the amount of time that the system will wait before beginning the entire call cycle again.
Default: CallInterval7 = 600
Local telecommunications authorities may have regulations regarding the frequency at which call attempts are made to a particular number (e.g. BABT British Telecom rules). The CycleLength, CycleDelay, and CallIntervalX variables allow a re-dial cycle to be defined. CallInterval8 indicates the number of seconds to wait after the eighth connection attempt in a call cycle fails.
Any CallInterval variables with intervals larger than CycleLength are ignored.
(For further information, please refer to Modem Manager Configuration Variables).
Related Variables: CycleLength indicates the number of times that CallInterval1 through CallInterval10 occurs. CycleDelay indicates the amount of time that the system will wait before beginning the entire call cycle again.
Default: CallInterval8 = 600
Local telecommunications authorities may have regulations regarding the frequency at which call attempts are made to a particular number (e.g. BABT British Telecom rules). The CycleLength, CycleDelay, and CallIntervalX variables allow a re-dial cycle to be defined. Callinterval9 indicates the number of seconds to wait after the ninth connection attempt in a call cycle fails.
Any CallInterval variables with intervals larger than CycleLength are ignored.
(For further information, please refer to Modem Manager Configuration Variables).
Related Variables: CycleLength indicates the number of times that CallInterval1 through CallInterval10 occurs. CycleDelay indicates the amount of time that the system will wait before beginning the entire call cycle again.
Default: CallInterval9 = 600
Local telecommunications authorities may have regulations regarding the frequency at which call attempts are made to a particular number (e.g. BABT British Telecom rules). The CycleLength, CycleDelay, and CallIntervalX variables allow a re-dial cycle to be defined. CallInterval10 indicates the number of seconds to wait after the tenth connection attempt in a call cycle fails.
Any CallInterval variables with intervals larger than CycleLength are ignored.
(For further information, please refer to Modem Manager Configuration Variables).
Related Variables: CycleLength indicates the number of times that CallInterval1 through CallInterval10 occurs. CycleDelay indicates the amount of time that the system will wait before beginning the entire call cycle again.
Default: CallInterval10 = 3300
Local telecommunications authorities may have regulations regarding the frequency at which call attempts are made to a particular number (e.g. BABT British Telecom rules). The CycleLength, CycleDelay, and CallIntervalX variables allow a re-dial cycle to be defined. CycleDelay defines the final delay (in seconds) before the cycle restarts.
Default: CycleDelay = 3300
Local telecommunications authorities may have regulations regarding the frequency at which call attempts are made to a particular number (e.g. BABT British Telecom rules). The CycleLength, CycleDelay, and CallIntervalX variables allow a re-dial cycle to be defined. CycleLength defines the number of steps in the cycle (to a maximum of 10). In other words, the number of attempts for a connection to a single phone number before CycleDelay occurs and call attempts restart with retry intervals beginning at CallInterval1 again. If CycleLength is invalid, all retries beyond 10 use CallInterval10.
Number of attempts for a connection to a single phone number before CycleDelay occurs and call attempts restart with retry intervals starting at CallInterval1 again (assists in support of BABT (British Telecom) rules). Any CallInterval variables with intervals larger than CycleLength are ignored; if CycleLength is invalid, all retries beyond 10 use CallInterval10.
Default: CycleLength = 5
Number of seconds to wait after data stops arriving (after initial data starts on an incoming call) before data tested to determine which driver should handle it.
Default: DataIdleTime = 1
Indicates the number of seconds to wait to hang up the modem when there are no active attempts at communications (i.e. no active attempts to read or write).
Related Variables: The DialWaitTime variable indicates the number of seconds to wait before retrying a failed modem operation (see D Config.ini [SYSTEM] Variables or Config.ini [SYSTEM] Section Variables for the Modem Manager).
Default: HangUpDelay = 10
Maximum number of bytes to accept as the initial message to be passed on to the drivers to determine the type of protocol and station address initiating the incoming call. The maximum allowable value is 1024.
Default: HelloPacketLength = 1024
Indicates the number of seconds the system should wait to receive initial data on an incoming call before hanging up.
Default: InitialDataDelay = 10
Indicates the number of seconds the system should wait after answering a call to receive the initial data before continuing and treating the call as valid. If this feature is required, the value must be less than InitialDataDelay or the call will still be hung up. This setting can be used for RTUs that don't speak until spoken to.
Default: InitialDataDelay1 =
When the Modem Manager answers a call, but no registered VTS driver accepts it, the Modem Manager hands off the call to the next application that handles incoming modem calls. If another application accepts the call, Modem Manager increments a count of concurrent handed-off calls. While this count equals MaxHandOffCount, no further calls are handed off.
Note: If MaxHandOffCount is not defined in Config.ini, then there will be no restrictions on call hand offs.
Default: MaxHandOffCount = 0
Indicates the minimum number of free modems that must be maintained to handle incoming calls. This parameter allows the Modem Manager to try and keep a free pool of modems available for incoming calls. An outgoing call will be queued while there are less than MinModemsFree modems unused.
Related Variables: If the AnswerCalls variable (see A Config.ini [SYSTEM] Variables) has been set to 0 (false) (as it is by default), then the MinModemsFree variable is ignored.
Default: MinModemsFree = 0
Enables you to set a time limit (in seconds) on how long a call will be held in the Modem Manager's queue when the Modem Manager determines that no modems are available (e.g. when no server is running for the defined modems, or modems have failed). The default value is the equivalent to approximately 12 years.
Default: MMMaxQTime = 0x18000000
Indicates the number of failed connection attempts that do not get to the ringing/busy signal stage before the modem is declared to have failed.
If ModemRetries successive connection attempts via one modem fail, then that modem is marked as failed. These call attempts may be to different destinations, and may be interleaved with attempts via other modems. A failed modem is retried from time to time.
Default: ModemRetries = 10
Indicates the number of unsuccessful connection attempts to a specific remote phone number before deeming the connection a failure.
If SiteRetries successive connection attempts for the same call fail, then that call is abandoned. These call attempts may be tried via a number of different modems.
Default: SiteRetries = 10
Indicates the number of seconds to wait for the first byte of noise on the modem line after answering an incoming call.
Related Variables: The SquelchIdleTime variable enables you to set the number of seconds to wait for idle time after squelch noise has been detected, while the SquelchPacketLength variable enables you to set the maximum number of bytes of noise to accept before the modem hangs up on an incoming call.
Default: SquelchDetectDelay = 0
Indicates the number of seconds to wait for idle time after squelch noise is detected to decide that real data is to follow. InitialDataDelay starts counting after this time (see I Config.ini [SYSTEM] Variables).
Related Variables: The SquelchDetectDelay variable enables you to set a number of seconds the modem should wait for the first byte of noise on the modem line after answering an incoming call, while the SquelchPacketLength variable indicates the maximum number of bytes of noise to accept before the modem hangs up on an incoming call.
Default: SquelchIdleTime = 0.25
Indicates the maximum number of bytes of noise to accept before the modem is hung up after answering an incoming call.
Related Variables: The SquelchDetectDelay variable enables you to set a number of seconds the modem should wait for the first byte of noise on the modem line after answering an incoming call, while the SquelchIdleTime variable indicates the number of seconds to wait for idle time after squelch noise is detected to decide that real data is to follow.
Default: SquelchPacketLength = 65536
Allows the serial port tag to specify which modem group (as specified by a modem tag's Area property) that the call should use. (UseSerialAreaInModemCall is set to "0" by default for backward compatibility.)
Default: UseSerialAreaInModemCall = 0