|
CallChange and VoiceChange cooperation - CxVxDriver
|
If you are running CallChange (CX) and VoiceChange (VX) together, you can set them to transfer call data from VoiceChange
to CallChange. It will work in similar way like with TAPI or CSTA connection, but line controlling is limited (hangup
and call transfer). It allows to use Call Resolution, but call dialing is not possible. Also you can not monitor other
lines than these used by VoiceChange.
Installation sequence
CxVxDriver configuration
- Install UMS.LineDrv.CxVxDriver service by CxVxDriver.exe /Service command (uninstall is done by CxVxDriver.exe /UnRegServer).
Driver is located in
Voicechange\bin\CxVxDriver folder.
- Set configuration under
HKLM\Software\Datasys\UMS\Drivers\CxVxDriver registry key:
| Value |
Sample setting |
Description |
| LogFileName |
C:\cxlogs\cxvxdrv.log |
Filename for debug log, can contain tags %d (date) and %t (time). If value is empty, logfile is not created. |
| Lines\<line_id> |
|
Contains configuration for line with <line_id> identificator. Identificator can be for example 0, line0, L0 etc. |
| Lines\<line_id>\DriverProgId |
Vxbkrt.vxcapiDrv |
VX line driver ProgId (i.e. $Driver.ProgId value from lineX.ini file). |
| Lines\<line_id>\InitLineParams |
Line=0|Channel=0|fax_line=0| tmpdir=D:\VoiceChange\lines\line0\| Init=1|fax_loc_id=| silence_sensitive=1| silence_period=10000 |
Line initialization parameters (i.e. $Driver.Init value from lineX.ini file). |
Configure in this way all VoiceChange lines you want to monitor in CallChange. Every line of course must have its own line_id
(it is good idea to use the same names for VX and CX, so VX line 0 will match to Lines\0 CxVxDriver line).
VX configuration
Configure VX in lineX.ini file to use CxVxDriver. CxVxDriver then internally work with real VX line drivers.
| Item |
Value |
Description |
| $Driver.ProgID |
CxVxDriver.Driver |
use CxVxDriver for this line |
| $Driver.Init |
LINE=<line_id> |
<line_id> is line identificator. CxVxDriver line in Lines registry key must be configured with the same
identificator. Recommended values are 0, 1, ... |
Now start VoiceChange - it must work normally.
CX configuration
- Set value LineProgId=CxVxDriver.Driver under
HKLM\Software\Datasys\CallChange\Monitor registry key
and restart "CX line monitor" task in umsTaskCfg. Now CX allow watch only
lines available to CxVxDriver, not any other !!
- Add CxVxDriver lines using CX web configuration application:
- Jméno (Name) - enter in CXserver:V:line_id format, where CXserver = CX server name, line_id = CxVxDriver line identificator
as entered in Lines registry key, i.e. for example CXSRV:V:0, ZL02:V:line0 etc.
- Číslo (Number) - physical line number
- Popis (Description) - any line description
- Povoleno (Enabled) - check to activate line
- Assign line rights according to your needs (Monitorovat/Ovládat).
Now restart CallChange clients to add new lines into list of available lines and allow to use them.
Doesn't it work?
In case of problems with CxVxDriver you can switch logging to file on (see registry settings) and restart the driver or run it
from command prompt in debug mode using CxVxDriver.exe /Debug. Driver will write information about its work into log
or to console and you can discover what goes wrong.
back to top
