Objectworld Communications Corp. Home | Contact | Terms of Use | Trademarks | Login
Search
Skip Navigation Links
Skip Navigation Links. Skip Navigation Links.
Support - Legacy Products - Unreleased Beta Products

WARNING:This page describes unreleased beta products. These products will never be completed or finished. They are still made available as existing customers may find them useful.

If this is your first time visiting this page, please take the time to read it entirely before installing the beta product.

Summary of Changes:

This is a brief summary of the changes since the previous public release of the product, for full details, consult the ReadMe.TXT file installed with the product.

  • Added support for Windows 2000 and Windows XP (TAPI 3.x).
  • Replaced Windows 9x third party fax printer driver, and provided Windows 2000 and Windows XP fax printer driver.
  • Harmonized versioning between all CallAttendant SOHO products.
  • Installer now uses new Windows Installer technology.
  • Changed default audio format to 8 kHz, 16 bit, mono, PCM.

Known Issues or Limitations:

This section lists known issues with their current status as it affects this release:

  • The Windows 2000 and Windows XP Unimodem driver does not support distinctive ringing.
  • CallAttendant Client/Monitor sometimes displays incorrect time information about calls.
  • If you select the H.323 device as a line, only 1 call at a time is supported.
  • If you select the H.323 device, you must activate a service which waits for the "zeroth" (0) ring. Otherwise the call will never be answered.
  • If you connect to a Windows XP machine using Remote Desktop Connection, and you have the sound routed to the remote, WAVE driver device detection will fail. This seems to be a problem with Windows XP.
  • Sending e-mail when using the non-primary MAPI profiles does not work.

Installation Notes:

In order to ensure successful installation and operation of the product, please take note of the following:

  • Backup your previous CallAttendant data.
  • Uninstall your previous version of CallAttendant. It should leave your data intact.
  • If you are installing on Windows 2000 or Windows XP, you must have administrative permissions to the machine.
  • The default installation locations have changed, so for it to pick up your previous data automatically, you need to install to the directory of the old install.
  • If you install to a new location, copy your data back into the appropriate places.

License Keys:

For existing customers of either product, please use your registered license key for the product.

For non-licensed users, please run the product using the following 60-day trial license keys (enter the keys as though you had purchased the product):

CallAttendant Home: 0470s08000u30000k450
CallAttendant Pro: 081g608000u308003idg

Tested Telephony Devices and Modems

So far, we have tested the following devices on the platforms noted:

  • U.S. Robotics (3Com) Model # 1749-00 (Internal ISA)
      Platforms tested: Windows XP
    Windows ME
  • Broadxent (Creative Labs) DI3631-1 (Internal PCI - soft modem)
      Platforms tested: Windows XP
      Limitations: Caller-ID is not always received by modem
    Fax detection sometimes fails
      Installation notes: Configure ring adjustment to -1
    Set fax to Class 1, hardware flow control
  • Creative Labs Modem Blaster DI5621-1 (External Serial)
      Platforms tested: Windows XP
      Limitations: Caller-ID is not always received by modem
      Installation notes: Configure ring adjustment to -1
  • AOpenFM56-PX (91.AC001.398) (Internal PCI - soft modem)
      Platforms tested: Windows XP
      Limitations: Audio playback takes ~1 second to stop (observed as slow reponse to DTMF input)
  • H.323 Line
      Platforms tested: Windows XP
      Limitations: No faxing supported
    Can only answer one call per 'line'
      Installation notes: Set number of rings to answer (in service) to 0, always

We did perform informal testing on other platforms with other devices, but, do not claim to have tested them sufficiently.

Note: We have not tested on Dialogic devices using the TAPI driver. It's possible this does not work due to the change in audio formats.

Microsoft Gold Certified Partner Logo