Confirmed bugs/issues in 2.0 Beta

Discussion in '3CX Phone System - General' started by Vali_3CX, Jun 28, 2009.

Thread Status:
Not open for further replies.
  1. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,420
    Likes Received:
    61
    This topic will contain in brief confirmed bugs and issues found into the version 2.0 Beta of 3CX Gateway for Skype.
    Please read this to know how to avoid them at this stage.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,420
    Likes Received:
    61
    Wrong case-sensitive check on computer account names

    Simptoms:
    The gateway has ports defined, but every time the monitor window is opened, all appears as <Skype port disabled>. Additionaly, on every atempt to start the service, it stops immediately, the monitor displaying "Failed to start the service". Attempting to start the service from Windows service control panel leads to a message such has "Service started then stopped".

    Resolution:
    In the File/Settings.. dialog, set an all-lowercase prefix name, without any uppercase character.

    Issue link:
    http://www.3cx.com/forums/failed-to-start-gateway-service-10507.html
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,420
    Likes Received:
    61
    Skype support not available

    Simptoms:
    A message-box warn user:
    "Although Skype™ is installed on this machine, its interactive support is not available.
    That means this channel won't be able to handle Skype™ calls and events.
    Try to fix this issue by checking if Skype™ Extras is also installed on this machine, then try again to configure 3CX Gateway for Skype™."


    Resolution:
    A 4.0.0.206 or greater Skype is required, with Skype Extras included. Run Skype installer (again) and check "Skype Extras" option (see below)
     

    Attached Files:

    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,420
    Likes Received:
    61
    Application failed to initialize properly

    Simptoms:
    When attempting to start gateway monitor, a message-box warn user:
    "The application failed to initialize properly (0xc0150002). Click on OK to terminate the application"

    This error might appear, most commonly, on a very fresh installation of a Windows OS, not containing a DLL the new gateway wrongly assume is there. The DLL (~620K) will be included in future releases of gateway installers.

    Resolution:
    Open following link on Microsoft's website and download and install vcredist_x86.exe (~2.6MB). These DLLs are used/installed my many applications, but they are not, by default, part of the Windows OS.

    http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE-A3F9-4C13-9C99-220B62A191EE&displaylang=en
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,420
    Likes Received:
    61
    DTMF not transmitted

    Description:
    DTMF signals are not transmitted through 3CX Gateway for Skype 2.0 Beta.

    Simptoms:
    From a SIP extension, call a Skype account. Once call is established, DTMF signals - if any - are not handled by the gateway.

    Resolution:
    This issue will be fixed in the next release, at this moment there is no local fix available.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,420
    Likes Received:
    61
    Missing CallerID on inbound calls

    Simptoms:
    From a Skype account - let's say SkypeCaller - call one of the gateway's. The SIP extension (phone) receiving the call will display SkypeCaller only as "number", not as a CallerID, since this field is not sent by the actual Beta version of the gateway.

    Resolution:
    This issue will be fixed in the next release, at this moment there is no local fix available.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.