WorkMan Agent+ShellAPI

From WorkManSoft Wiki
Revision as of 19:07, 21 December 2010 by Frla (talk | contribs) (Created page with "'''This feature requires a specific license and can be purchased seperately''' == Configuration == This must be configured manually in the registry. This is a sample of an regi...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

This feature requires a specific license and can be purchased seperately

Configuration

This must be configured manually in the registry. This is a sample of an registry-file

 [HKEY_CURRENT_USER\Software\WorkMan\WorkManAgent]
 "UseShellAPI"="TRUE"
 "ShellApp"="c:\\phonetest.bat"
 "ShellParams"="%VMID% %CALLERID% %CALLEDID%"
 "ShellWindow"=dword:00000001

UseShellAPI TRUE means it's being used. FALSE means it's not.

ShellApp is the shortcut to the application, excluding the parameters!

ShellParams is the parameters being sent to the application and the value %VMID% is used when the callerid triggers a call with extended information (e.g. VoiceMail Pro on IP Office) where %VMID% is the ID entered by VoiceMail Pro, %CALLERID% is caller id and %CALLEDID% is of course Called ID.

Testing

You can easily test this using a bat-script e.g. something like this:

 @echo off
 echo ID %1 
 echo CallerID %2
 echo CalledID %3
 pause