INFO

SwyxWare v6.01 Maintenance Pack 2 (kb3269)

The information in this article applies to:

  • SwyxWare v6.01
  • SwyxWare CD v6.01

[ Summary | Information | Links ]


Summary

Swyx releases SwyxWare v6.00 Maintenance Pack 2.

To check which version you have currently installed on your system click the "Check for updates" link in SwyxWare Administration or click on the "Product updates" link in the support information of SwyxWare in in the Add/Remove Programs list in Windows control panel.

Please note the common hints on Maintenance Packs in the following Knowledgebase articles:


Information

Maintenance Packs of SwyxWare version v5.0 or newer are shipped as patches based on Microsoft Windows Installer, which has a couple of advantages:

  • No manual replacements of executables necessary
  • Services are automatically stopped and started
  • Unique version number to easy see which Maintenance Pack is installed
  • Maintenance Packs can be easily removed if necessary
  • Smaller download size

To install the Maintenance Pack execute setup.msp and follow the Installation Wizard.

The knowledgebase article

describes problems solved by Maintenance Pack 1. Additionally Maintenance Pack 2 addresses the following issues:
  • Script property 'IsGroupOrUserBusy' delivers wrong result in case number to query is different from called number.
    (Swyx00013854)

  • Status of user not set to "active" after user picked up call.
    (Swyx00013852)

  • Late disconnect not working with call retry on ISDN trunk.
    (Swyx00013831)

  • Data calls from sub PBX ISDN line not handled correctly and CIP calue not sent transparently to externel ISDN line.
    (Swyx00013827)

  • Wrong calling party number on incoming calls from SIP Provider T-Online.
    (Swyx00013933)

  • Outgoing SIP call using provider T-Online does not work.
    (Swyx00013807)

  • Master/Standby can not be installed on a domain controller.
    (Swyx00013634)

  • Server looses change interests in Standby scenario.
    (Swyx00013611)

  • Server suppresses internal number on internal calls if number suppression is activated within SwyxIt!.
    (Swyx00013486)

  • Use IP address 127.0.0.1 as WSBaseUrl when connecting the local computer.
    (Swyx00013511)

  • LinkMgr dumped in the sequel of a 484 response to an INVITE.
    (Swyx00013625)

  • PIKA analoge channel not freed if call is canceled while establishment.
    (Swyx00013661)

  • Fix problem installing a stand alone gateway in a standby environment.
    (Swyx00013671)

  • Script option CLIMode=0 does not work for calls initiated from internal users to external detsination.
    (Swyx00013172)

  • Passive hold with link at the provider side fails using G729.
    (Swyx00012861)

  • LinkManager: reduced CPU load if many channels are in use.

  • LinkManager dumped on incoming call.
    (Swyx00013584)

  • Sometimes Quescom connected via SIP Link stops audio transmission.
    (Swyx00013574)

  • External outgoing call with overlap sending is shown wrong in CDR.
    (Swyx00012344)

  • CDR does not contain origination device name until call is connected.
    (Swyx00013372)

  • Dialnumbers in CDRs are incorrectly formatted.
    (Swyx00013498)

  • CDR discarded in case of CDR writing to file and file is locked by other process.
    (Swyx00013587)

  • WaitForDisconnect script action not confirmed after call transfer scenario / prevent call retry action if call was already connected.
    (Swyx00013559)

  • Voice gets scrambled, after DTMF tones are send from external PSTN user in case of I-Node SIP Trunk usage.
    (Swyx00013561)

  • Reinvite from INode SIP Provider causes one way mediastreaming.
    (Swyx00013560)

  • LinkManager: implementation of special feature regarding CLIR for "customized" installation.

  • Cannot receive anonymous calls from provider Telenor.
    (Swyx00013523)

  • No registration with SIP provider sunrise.ch possible.
    (Swyx00013522)

  • "Overdial" digits of incoming called party will be attached to ConnectTo destination, which is wrong.
    (Swyx00013507)

  • In some cases multiple CDRs are written with the same call ID.
    (Swyx00013497)

  • There are three 'Call Detail Records' entries for one twin-call.
    (Swyx00011718)

  • Audio sounds scrambled in case comfort noise packets are sent to LinkManager.
    (Swyx00013495)

  • When (re-)connecting to CDS a new LibMgr is used.
    (Swyx00013493)

  • No media streaming after call transfer (blind or normal) to external party or group.
    (Swyx00013479)

  • It's not possible to register Nokia E60 device at SwyxWare as SIP user.
    (Swyx00013468)

  • SwyxIt! display shows group member instead of group name if a group is called.
    (Swyx00013465)

  • Sometimes gateway rejects to make outgoing calls even if free b-channel is available.
    (Swyx00013458)

  • Sometimes Trunk Recordings contains wrong date (19700101) and wrong time (010000) for incoming calls.
    (Swyx00013406)

  • Sometimes different participants of a conference recognize silence parts although the speaker continues to speak.
    (Swyx00013348)

  • External Call to callrouting script is cancled in case of cascaded script.
    (Swyx00013430)

  • Trunk recording stops after the call was on hold with SIP trunks.
    (Swyx00013401)

  • Internal/External check in script fails after call transfer.
    (Swyx00013397)

  • Voicemail orignator email address with underscore trigger wrong encoding.
    (Swyx00013353)

  • PBXCall.CallingPartyNumber returns wrong value after call transfer.
    (Swyx00013253)

  • Trunk recording stops after the call was on hold with SIP trunks.
    (Swyx00013401)


Links

As far as software supplied or used by us, includes open source elements the additional terms under https://www.swyx.com/open-source apply in addition. An overview which products from the Swyx portfolio include open source elements and which open source license is relevant can be found under https://www.swyx.com/open-source.

The third-party contact information included in this article is provided to help you find the technical support you need. This contact information is subject to change without notice. Swyx in no way guarantees the accuracy of this third-party contact information nor is responsible for it's content.


Comment

Comment on this article



If we have any follow-up questions, where can we contact you?

E-Mail Address (optional)


Note

This feedback form can't be used for support requests. Those requests must be directed to your Swyx reseller or distributor.