Support, News and Updates

Support

Using CallClerk with the Conexant USB Voice Fax Modem.

If you use CallClerk Caller ID software, or other voice software that uses direct TAPI to play and record audio, you will be required to install the GetFaxing.com Fax Voice Modem Drivers. This document will guide you with the installation of the proper drivers for your voice modem.

First time install.

Insert the GetFaxing.com Conexant USB Modem into an available USB port. For first time installations, Windows will automatically install the Windows default plug & play modem “Conexant USB CX93010 ACF Modem“.

When you first insert the fax voice modem into a new computer, Windows will attempt to search for drivers via Windows Update and local folders. The default modem will be installed as Conexant USB CX93010. Shown is the Windows 7 dialog box. This process could take several minutes and an animated icon will appear in your system tray during this process.
When completed, Windows will display a Driver Software Installation message that the Conexant USB CX93010 ACF Modem or a similar modem name is ready to use. The Windows 7 screen is shown in the image.

This Windows default modem driver is acceptable for most TAPI fax and voice software that uses TAPI pass-through mode, including FaxTalk FaxCenter Pro, FaxTalk Messenger Pro and FaxTalk Multiline Server. If your software uses TAPI pass-through mode or you don’t require voice operation, you can stop here and continue using the default modem driver.

For some voice software that uses direct TAPI, such as CallClerk, you will require to install the GetFaxing.com Voice Modem Drivers.

Installation of voice modem driver.

Start the GetFaxing.com modem installation wizard by double clicking the executable file for your operating system. For Windows 10, Windows 8.x and Windows 7 (SP1 plus latest SHA-2 updates) modem installation wizard files are:

ModemInstaller-x64.exe for 64-bit Windows 10, 8.x, 7 machines
ModemInstaller-x86.exe for 32-bit Windows 10, 8,x, 7 machines

NOTE: We recommend you download the drivers from the link provided to you from your original order e-mail. Some shipments of modems will also include a CD with a GetFaxing Modem folder. If this folder is not present on your installation CD, download the files from the link included with your order e-mail.

You are prompted with a User Account Control dialog box (Windows 7 dialog shown in image) when you start the ModemInstaller-x64.exe or ModemInstaller-x86.exe file. This dialog box should always show the verified publisher as GetFaxing.com.

NOTE: The software installation file is digitally signed with SHA-2 digest algorithm using a GetFaxing.com certificate. Your operating system must support SHA-2 (also commonly referred as SHA256) to successfully verify the publisher as GetFaxing.com. Windows 7, by default, does not fully support SHA-2 without updates. If the software appears to be unsigned, then following may be true a) you do not have all installed operating system updates to support SHA-2, or (b) your machine does not have updated root certificates to recognize the SHA-2 digest. To update the root certificate, right-click the installations file and click Properties, click the Digital Signatures Tab, select GetFaxing.com from the signatures list, click the Details button. If the digital signature should appears as valid and is signed by GetFaxing.com, now try installing again.

Click Next to walk through the GetFaxing.com USB Fax Modem Installer Wizard.
Windows will prompt you if you would like to install the device software. This is a Windows Security dialog box that verifies that driver software is signed digitally by GetFaxing.com. Click Install to continue.
Windows will now attempt the installation of the modem drivers. This may take a few minutes.
If successful, you will see this message. If no update was required, you will see a message that the device has the latest driver installed. Click Finish to close the Installer Wizard.

The modem name will now appear in Windows as a Conexant USB CX93010 ACF Fax Voice Modem after a successful installation. This modem name differs from the default modem installed by Windows; Conexant USB CX93010 ACF Modem.

Modem should now appear in the Device Manager as “Conexant USB CX93010 ACF Fax Voice Modem”

Unimodem Full-Duplex Audio Device.

A Unimodem Full-Duplex Audio device should be present when you successfully install the modem drivers. This device is required for CallClerk and other software using TAPI voice operations. This device is automatically installed with the voice drivers and will appear in the “Sound, video and game controllers” section of the device manager.

In the Sound, Video and Game Controllers section of the device manager, a Unimodem Full-Duplex Audio Device will be installed. This device is required for proper operation of direct TAPI voice software. Software that uses pass-through TAPI mode does not require this device.

See the instructions under Troubleshooting the Modem for more information on how to view the Device Manager.

Please reboot the machine after installation of the voice modem drivers and read the specific operating system considerations below. You may be required to follow additional steps.

Windows 10 considerations.

It is recommended to use the latest version of Windows 10, however, this may not be possible when using an older unsupported machine or a machine that is not connected to the internet. Windows 10 has a number of different versions, and you should be aware of which version you are using. There are known problems with some versions of Windows when using a voice modem. We have included information on the known issues, and the solutions/workarounds below.

NOTE: You can verify your version of Windows 10 by right-clicking Windows Start, Click Run, and type ‘WinVer’ (Or Windows Key+R and type WinVer and press Enter)

Windows 10 Version 1903 and 1909 will require “serwvdrv.dll” registry fix.

Versions 1903 and 1909 Windows 10 have a problem specific with voice modems playback and recording. Microsoft was notified of this problem and they corrected the issue with the release of version 2004. If this version is available for your device, we recommend you update.

A workaround fix is available if you are using version 1903 and 1909. More information about this fix and instructions are provided here.

Windows 10 Version 1511 requires update.

Version 1511 Windows 10 introduced a problem where the Unimodem full duplex or half duplex audio driver would not install with the voice modem. If you are using this version, you should update to Version 1607 or later. More information and a workaround fix for Version 1511 is available here

Windows 7 requirements.

If you are using Windows 7, ensure you have all the latest security updates to support SHA-2 signing before attempting to install the modem drivers. If you attempt to install the drivers without SHA-2 support in the operating system, the installation files will not be detected as digitally signed and they will be blocked from installing.

NOTE: Legacy OS versions (Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Server 2008 SP2) are required to have SHA-2 code signing support installed on their devices to install updates released on or after July 2019. Any devices without SHA-2 support will not be able to install Windows updates on or after July 2019.

You can verify if your operating system is updated to support SHA-2 by right-clicking the Modem Installer exe file. Click Properties, click the Digital Signatures tab. Select GetFaxing.com from the signature list and Click the Details button. This will verify the digital signature, update the root certificate and confirm your system will support SHA-2.

More information from Microsoft here.

Stand Alone security updates KB4474419 and KB4490628 released to introduce SHA-2 code sign support.

Troubleshooting the Modem.

Remove all previous fax modem drivers.

If you are replacing a modem, you should uninstall any software drivers for that modem. Multiple fax modem drivers from different models of fax modems can cause unreliable and unstable results in Windows. Check the Add/Remove Apps, Add Remove Programs and Device Manager to remove specific fax modem drivers that are no longer being used. Once you’ve done this, check the Device Manager to view and uninstall orphaned modem drivers.

To open the Device Manager in Windows.

Open the “Run” dialog box by pressing and holding the Windows icon key, then press the R key (“Run”).
In the open prompt, type devmgmt.msc and Click OK.

NOTE: In Windows 10 you can right-click the Windows icon on the desktop and select “Device Manager” from the pop-up window to open the Device Manager.

In Device Manager, click View, Devices By Type. (make sure there is a check mark).
Click on View, Show Hidden Devices (make sure there is a check mark ) Click on Modems.
Right click on the specific modem in the list and click Uninstall. If you no longer use this modem you should check the option to remove the driver files.

Disable other application(s) that may use the modem.

Some modem applications may conflict with proper operation of CallClerk and other voice software. Disable and make sure other applications are not operational.

CallClerk is a TAPI application that should allowing sharing with other TAPI compatible software, but some software may take priority of the modem and prevent CallClerk from answering or detecting an incoming call.

Insert modem to a direct USB port.

USB hubs or extensions may cause communication problems. Install the USB Modem directly to a USB 3.0, 2.0 or 1.1 port on the computer. Recommended is a USB 2.0 or 1.1 port.

Troubleshooting Call Clerk

Adjusting the volume.

CallClerk does not have a recording volume control setting, but you can adjust the recording gain of the voice modem by setting the +VGR= value. If you find that recordings from your callers are too low when played back, you can increase the +VGR value accordingly. Values are 0-255. Default value is 128 which is the normal gain value.

The volume level for the incoming caller is the transmitted playback. If your transmitted playback volume is too low or too high, you can adjust using the +VGT= value. Values are 0-255, but recommended values are between 120 – 136. Default value is 128 which is the normal playback gain value.

Since +VGR= and +VGT= are voice commands, you must be in Voice Mode before this command can be sent to the modem. The +FCLASS=8 command sets the modem to voice mode and must be sent to the modem before the +VGR= or +VGT= value. To avoid problems with other software expecting the initial state of the modem to be data, we set the modem back to the default class with a +FCLASS=0 command. To ensure Caller ID remains enabled, we set +VCID=1

Here is an example of Extra Initialization command:

ATE0;+FCLASS=8;+VGR=255;+VGT=128;+FCLASS=0;+VCID=1

You can add this to the Extra Initialization command within Phone & Modem Properties. Click the Advanced Tab (next to Diagnostics) to enter the Extra Initialization command line. If you are unable to change this, click on the General Tab and click the Change Settings button.

Command breakdown

Note: Multiple modem commands are included a single line, and each command is separated by a semi-colon.

ATE0 = Attention modem command followed by Echo off.
+FCLASS=8 = Set modem to voice class mode
+VGR=255 = Set recording gain to highest value (255)
+VGT=128 = Set the playback gain to default value (128)
+FCLASS=0 = Set modem to default class mode.
+VCID=1 = Turn on Caller ID.

FAQ

Q: Where do I download the voice modem drivers?
A: When you purchase the Conexant Fax Modem from GetFaxing.com they will be included as a download link in your completed/shipped order e-mail.

Q: Does the voice/fax modem detect the Caller ID of an incoming caller when I am currently on an existing call?
A: This feature is called Call Waiting Caller ID, Type II, or Type 2 Caller ID. This type of caller ID is not supported. While most desktop and cordless telephones with Caller ID can provide support for Type II caller ID, many (if not all) fax/voice modems do not include this Type II support. In addition, the Microsoft Windows TAPI interface does not include support for type II caller ID.

no comments

Leave a reply