User manual

125
• The PhoneSweep UI freezes during a sweep. If you encounter this symptom, please contact
Sandstorm.
• PhoneSweep stops dialing in the middle of a sweep when no one is around to restart the
sweep. To re-enable all disabled modems and cause PhoneSweep to restart dialing, use the Delay
command to automatically restart the sweep a few hours in. This is a stopgap solution; please see
the entries under “PhoneSweep stops dialing during a sweep” above to diagnose the cause.
• PhoneSweep hangs when it calls one particular number. If you encounter the problem, put the
problem number in a profile by itself. This lets you complete the original profile without the
problematic number. Next, please contact Sandstorm Enterprises so we can work with you to
isolate the cause.
• PhoneSweep is leaving blank voicemail messages. First, try enabling Single Call Detect. If
PhoneSweep running in Single Call Detect mode with a recommended modem still leaves blank
voicemail messages, try setting Single Call Voice Timeout in the Dialing sub-tab to a lower
value, for example 3 or 4 seconds (this can also be set via the variable SINGLE-CALL-VOICE-
TIMEOUT in the phonesweep.ini file). Note, however, that setting this variable to a lower value
may increase the chances that some modems may be missed during the sweep.
When PhoneSweep is scanning in fax mode, it leaves a message containing fax tones on
voicemail. Try enabling Single Call Detect by selecting the appropriate option on the Dialing
sub-tab.
• PhoneSweep is progressing through the profile too slowly. First, determine what would be a
reasonable number of calls per hour for PhoneSweep running under the particular conditions.
PhoneSweep running in Penetrate or Identify modes will take longer to progress through a profile
than it would in Connect mode. Therefore, if you do not need the level of information gathered in
Penetrate or Identify mode, consider reducing the level of effort. Also, enabling
username/password recycling when scanning in Penetrate mode increases the amount of time
necessary to finish a profile. Enabling Single Call Detect will reduce the amount of time needed
to complete the scan, as will turning down the timeouts. Reducing timeouts may cause
PhoneSweep to miss modems.
• PhoneSweep inaccurately identifies devices. The quality of the information gathered by
PhoneSweep is highly dependent on the quality of the modems used to dial. Try using a modem
that Sandstorm recommends as working well with PhoneSweep. PhoneSweep cannot identify
some exotic devices such as encrypted telephones. Check to see if your phone switch is making
odd noises or if you’re forgetting a dialing prefix.
In some cases, PhoneSweep may interpret voicemail tones as fax tones. Also, sometimes when
dialing out through a switch, the switch makes a click or tone as it hands off the call, causing
PhoneSweep to believe that the call has already been answered. Try calling the misidentified
numbers in a way other than dialing through the phone switch.
If the misidentifications are related to dialing internal versus external extensions, it is possible
that your phone switch is making a tone when it calls an internal or an external extension, or there
may be a different type of ring when calling internal versus external extensions. Calling the
misidentified numbers and some correctly identified numbers with the modem speaker enabled
can be instructive.
• Fax machines are reported immediately as BUSY. It is possible that PhoneSweep is not
waiting long enough between calls. Increase the Delay Between Calls parameter on the Time
sub-tab.