| For common questions see ---> |
|
| For applications/samples see ---> |
|
*Why
dialer does not dial when click on Excel spreadsheet?
Excel dialer senses when selected cell has changed.
It means that when you open spreadsheet and the cell (containing phone
number) is active, clicking on that cell will NOT start dialing. You
need to click on another cell to make it active, then click again on the
cell with phone number in it.
After that, clicking on any other cell containing phone number will invoke
dialer.
back to the top
*
Using script
A script is a plain text file where each line
contains an individual command.
To see the list of available commands and a sample script, click on
the Help button beside that option.
Note:
Script can be
invoked by 2 methods:
1.
- select this option and specify the script file.
- save Options and close dialer.
- make outgoing call. When the call changes to 'Connected' state, script
execution will begin.
2.
- start dialer from the command line using one of the following commands:
<path>dial.exe /script
(this will use the script file specified in Options)
<path>dial.exe /script:<full path to
the script file> (this will use the script
file specified on this line)
Important:
When using scripts it is very important to synchronize
timing between commands by using the <wait: # > command.
The <play> command should be grouped with <monitor_dtm: #>
or <monitor_dtm> commands, always followed by the
<wait: #> command. See samples by using Help button
beside the 'Use Script' option.
Using Script Simulator:
Click TEST button to start Script Simulator. A new
window will pop open showing the real time script execution.
When the script waits for the keypad input, click on the desired
key on the EDP keypad.
This is the best way to test your script, fine tune it
and make sure that it does what the script was intended to do.
Note:
<dial> command starts a simulated action; it will not use the
modem and phone line.
<play:> command will play a wave file over the PC speakers,
instead of playing it to the phone line.
Remarks:
Because Script Simulator does not use a modem at all, it is
possible to test scripts even if the modem is not a voice modem or the
modem is not able to generate (or receive) DTMF tones.
|
Script commands accepted by Excel Dialer Pro |
| COMMAND |
TASK |
|
err_key:# |
when a specified key is pressed, the
<monitor_dtmf: #> or
<monitor_dtmf> action will stop and the err_mess will be
played. |
| err_message: <file> |
message to be played
when err_key (above) is invoked. |
| err_wrong_key_message:
# |
when not expected key
is pressed, the last played message will play again if the
value # is 0 <default> |
| err_wait: # |
time delay in seconds: must be long
enough to play error message
(65 secs max) |
| err_line: # |
when err_key is
invoked, the script will continue from the specified line after
err_wait time delay (above). |
| err_timeout: # |
when no response is
received, monitoring DTMF tones will stop after # seconds (default
is 65 seconds) and the next line command after <wait:# > command will be
executed. |
| dial:<phone number> |
make outgoing phone call.
When a call already exists this command will be ignored. |
| monitor_dtmf:#
<action> |
wait for specified tone# and
perform action.
<action> can be any valid script command except <play:>.
Often, it will be <go_line:#> or <hangup>
This command (or group) must be followed by <wait:# > command. |
| monitor_multi_dtmf:#
<action> |
wait for specified
series of tones# and
perform action.
<action> can be any valid script command except <play:>.
Often, it will be <goto_line:#> or <hangup>
This command (or group) must be followed by <wait:# > command. |
| monitor_dtmf |
store all keystrokes in
file tones.txt, until # (pound) key is pressed.
This command must be followed by a <wait:# > command |
| dialdtmf:<0...9,#,*> |
send DTMF tones |
| wait:# |
program waits # of secs
before executing next command |
| go_line:# |
jumps to specified
script line |
| go_line:# loop:# |
repeated jumping to
specified line # times (loop #) |
| go_line:# loop:#
go_line:## |
after # times (loop #)
jumping to script line #, it will continue script execution from
line ##. |
| alert:<file> |
this is one of the
<action>. It will play the selected file over PC speakers
to alert the operator. |
| callerid:<CallerID>
<go_line:#> |
when the Caller ID
matches expected value, then
the script execution will jump to the specified script line |
| callerid |
this command will put
Caller ID on clipboard |
| answer:<#> |
incoming call will be
answered after # of rings |
| runapp:<path to
executable> |
it will launch the
specified file |
| runapp:<path to
executable>/callerid |
it will launch the
specified file with the Caller ID as a trailing parameter |
| flash |
it will perform
flashook or off-hook |
| hangup |
disconnect and drop the phone line |
| end |
disconnect, drop the phone line and
end script processing |
| delete |
delete the script file |
| // |
this line is ignored
(it is used for making comments) |
| |
|
Important:
err_... commands when used, should precede all other
commands.
but it is not necessary to use them at all.
Script must end with <end> command.
Ask me, if you need another command or action.
Script will be invoked automatically the next
time Excel Dialer Pro is called or manually by using systray
EDP icon's pop-up menu.
back to the top
*How to
recover from errors?
Resetting EDP options to default values may help. To do that start EDP with "default"
as a trailing parameter:
[...] \phoneex.exe
/default
back to the top
* Using
the test file to diagnose hardware or
software problems
1. Click
here
to download the test
file (371 kB)
2. Run it and use it the same way you were using the original file,
until the problem (error) appears.
3. Close program.
4. Find TapiLog.txt log file in the same folder the test file
was run from.
5. Send that file to
author.
Please make sure to add
comments saying what you are doing externally and where you think the
problem is.
Note:
When the error is a 'run-time' type error it causes the premature program
termination and TapiLog.txt log file will not be generated.
In that case run the test file with /tapilog suffix (<path><filename>_test.exe
/tapilog) and the second diagnostic window will open. Just save it's content and
send it to
author.
back to the top
*
How to get rid-off 'Run Busy Detect' startup message?
Properly detected busy signal is very
important for the determination of Connected phone line state.
It is recommended to use this utility. See it in Options>Hardware
tab.
If for some reason your device cannot detect busy (like some, not voice
modems do) there are 2 methods you can use it:
1.
In Options>Voice tab deselect 'Voice modem' option
and run 'Detect Busy' utility again.
2.
Measure time it takes to the first audible ring. Manually insert that
number into Busy Detect option in Tools>Options>Hardware tab and
click OK to save the options.
The value should be between 8-11 seconds for most modems.
back to the top
*
How to override options?
Find PhoneEx.ini file located in:
"C:\Documents and Settings\<user nane>\Application Data\Excel Dialer
Pro\PhoneEx.ini"
Open it in a word editor
(Notepad, MsWord) and edit the entries you are interested in.
To set all options to default values run
application with /default suffix: <path>phoneex.exe /default
back to the top |