|
|
|
|
|
|
At last check, audio drivers for some ModemBlaster DE5620-3 modems did not work with Active Call Center. Check the ModemBlaster support site for an updated set of drivers, if that doesn't solve the problem it may not have been resolved yet. ModemBlaster DE5620-2 modems with the Lucent logo printed on the box work nicely with Active Call Center.
Caller ID Problems
If Caller ID doesn't work properly with a ModemBlaster DE5620 modem, try the fix below. This fix was provided by a user and we cannot guarantee that it will solve your particular problem. Do not attempt to implement the fix if you are a computer novice that would not be able to restore your system configuration independently.
The user wrote to us:
I got it, my son ... found the bug. It was in the ModemBlaster driver. The modem sends "ddn_nmbr= " and TAPI was waiting for"nmbr = ". We edited the file .inf and we reinstalled the driver.
In fact we have replaced (somewhere at the end of the DE5620.inf file) the following line:
HKR, Responses, "NMBR = ", 1, 94, 00, 00,00,00,00, 00,00,00,00
with
HKR, Responses, "DDN_NMBR= ", 1, 94, 00, 00,00,00,00, 00,00,00,00
and beware, there is no space before between the "R" and the "=". Hoping this can help someone. I have transmitted this information to Creative Labs.
Note that the DE5620.INF file will have to be located on your system using a file search through Windows Explorer. Save a copy of the DE5620.INF file before modifying it so that it may be restored if the fix does not work.