INFO

SwyxWare v4.40 Hotfix 5 (kb3017)

Le informazioni contenute nel presente articolo riguardano i seguenti prodotti:

  • SwyxWare CD v4.40
  • SwyxWare v4.40

[ Riepilogo | Informazioni ]


Riepilogo

Swyx releases the SwyxWare v4.40 Hotfix 5.

Please note the common hints on hotfixes in the following Knowledgebase article:

 

You can use the following article to check which hotfix you have currently installed on your system:


Informazioni

This hotfix 5 contains also

and resolves the following problems:

 

  • ConnectTo script action uses wrong output in case of address resolution returning 'NoChannelAvailable'.
    (Swyx00009454, Hotfix 5)
     
  • Some numbers can not be dialed because the dialnumber gets malformed through canonicalization.
    (Swyx00008474, Hotfix 5)
     
  • Call deflection does not work in case of running script.
    (Swyx00009487, Hotfix 5)
     
  • SMTP mail manager will NOT retry send message process if TCP socket error occured.
    (Swyx00009534, Hotfix 5)



     


     

  • SwyxGate LEC (Line Echo Canceller) channel counter is not decremented if external call is forwarded to external party.
    (Swyx00008881, Hotfix 4)
     
  • Incoming call to a T.30 destination does not cause increase of buffers on both calls.
    (Swyx00008797, Hotfix 4)
     
  • SwyxGate does not increase buffers in case of outgoing T.30 call.
    (Swyx00009058, Hotfix 4)
     
  • 'No NCCI available' in SwyxGate log in case of timed out in 'Alerting' state on external gateway calls.
    (Swyx00009096, Hotfix 4)
     
  • 'No NCCI available' in SwyxGate log after some calls to unallocated number from Sub-PBX.
    (Swyx00009155, Hotfix 4)
     
  • Server throws access violation if calendar access query failed by long timeout.
    (Swyx00009139, Hotfix 4)
     
  • SwyxGate generates MemoryDump when SwyxGate is started and PC reboots.
    (Swyx00009265, Hotfix 4)
     
  • Configuration of SwyxGate H.323/H.225 ports using SwyxWare administration not possible.
    (Swyx00009310, Hotfix 4)
     
  • Callrouting get stuck after incoming SwyxLink call is delivered to an external party using another SwyxLink.
    (Swyx00009338, Hotfix 4)
     
  • Fax calls may use LCR provider which do not support fax (applies only to installations in Germany!).
    (Swyx00009343, Hotfix 4)
     
  • Call Transfer to script sometimes not not working.
    (Swyx00009370, Hotfix 4)
     
  • SwyxServer checks during client login if that client can be reached on TCP Port 135 (RPC endpoint mapper). The login fails if not. Without connectivity on port 135 DCOM won't work at all. If a client with blocked port 135 connects to a server, Microsoft's DCOM subsystem may stall on the server.
    (Workaround, Hotfix 4)
     
  • Asynchronous handling of errors if Microsoft DCOM subsystem did disconnect COM connection.
    (Workaround, Hotfix 4)
     
  • ONLY applies to HST Saphir V-ISDN board with driver version >= v2.7.7.x. Since this driver version it is possible to preselect the B channel protocol during SwyxGate service startup. This will prevent a possible switch between different B channel protocols during call setup, which might cause the B channel not to deliver voice data.
    (Workaround, Hotfix 4)



     


     

  • WaitForDisconnect never returns after call transfer.
    (Swyx00008860, Hotfix 3)
     
  • SwyxServer crashes when SwyxPhone white list is too long.
    (Swyx00008878, Hotfix 3)
     
  • Callrouting not continued on call after redirection to switched off DECT handset.
    (Swyx00008943, Hotfix 3)
     
  • Cancel call during call establishment to gateway forces server to unregister gateway.
    (Swyx00008971, Hotfix 3)
     
  • Group calls ring forever on multi cell DECT ip1500.
    (Swyx00008974, Hotfix 3)
     
  • ConnectTo timeout is ignored if single cell DECT ip600 sends Release Complete message with reason 'No user responding'.
    (Swyx00008984, Hotfix 3)
     
  • ConferenceMgr throws access violation on late call details.
    (Swyx00008990, Hotfix 3)



     


     

  • SwyxServer service not restarted by watchdog if script file cache mutex is blocked.
    (Swyx00008742, Hotfix 2)
     
  • SwyxServer breakdown in case of blind call transfer initiated by H.323 device.
    (Swyx00008777, Hotfix 2)
     
  • Configuration changes for H.323 (like ip600) and SIP based clients made by SwyxWare administration are only applied after logoff and reregistration
    (Swyx00001321, Hotfix 2)
     
  • SwyxServer PBXConfig scripting object returns wrong user state. See: Request configuration and user data (incl. user status) within an Extended Call Routing script (kb2910)
    (Swyx00008817, Hotfix 2)

  • SwyxGate LEC (Line Echo Canceller) channel counter is not decremented if external call is forwarded to external party.
    (Swyx00008881, Hotfix 2)
     
  • PhoneManager polls SwyxServer during a call to keep Microsoft DCOM subsystem from disconnecting COM connection. This ensures all calls being disconnected properly.
    (Workaround, Hotfix 2)



     


     

  • Contains new firmware 2.1.11 for SwyxPhones L400, L420e, L420s and L440.
    (Hotfix 1)
     
  • Please note that there is a hotfix for the IP600 DECT system available, fixing stability problems:
  • SwyxServer restarted by watchdog after 'hanging' call was cancled via admin.
    (Swyx00008538, Hotfix 1)
     
  • SwyxFax server service does not start if SwyxFax user has more than 127 extensions.
    (Swyx00008587, Hotfix 1)
     
  • SwyxGate generates access violation during connect/disconnect stress test.
    (Swyx00008634, Hotfix 1)
     
  • Unexpected 'CallProceeding' message sent to H.323 endpoint while disconnecting call.
    (Swyx00008656, Hotfix 1)
     
  • Callrouting Script loading sometimes fails with signature verification error.
    (Swyx00008657, Hotfix 1)
     
  • Incoming calls may not be delivered when msns are configured on a DDI line.
    (Swyx00008640, Hotfix 1)
     
  • SwyxServer throws access violation if H.323 connection is interrupted.
    (Swyx00008671, Hotfix 1)
     
  • Incoming SIP call without matching codecs may cause an access violation
    (Swyx00008672, Hotfix 1)
     
  • PhoneManager threw access violation in a special scenario.
    (Swyx00008680, Hotfix 1)
     
  • PhoneManager throws access violation on dialing a line that was hooked off by CTI client.
    (Swyx00008685, Hotfix 1)
     
  • Improved robustness of CDR writing into database.
    (Hotfix 1)
     

Further informations and a detailed installation instruction can be found in the included README.TXT file.


Commento

L'articolo è stato utile? Lasci un commento all'articolo



Come possiamo contattarLa se dal Suo commento dovessero nascere altri quesiti?

Indirizzo e-mail Adresse (facoltativo)


Nota

Il campo destinato ai commenti non è ammesso per richieste all'assistenza. Per quesiti inerenti l'assistenza rivolgersi esclusivamente al proprio rivenditore di fiducia o al distributore competente.