INFO

SwyxWare v6.01 Maintenance Pack 1 (kb3214)

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 1.

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.

Maintenance Pack 1 addresses the following issues:

  • Server signals wrong calling party number in case of redirection to external party.
    (Swyx00013332)

  • Users cannot logon to SwyxServer anymore.
    (Swyx00013364)

  • Performance improvement of LinkManager for RTP audiodatapumping to scale with the number of installed processors of the hardware.
  • Incoming call via SIP Trunk is not terminated if caller sends BYE in early state of dialog.
    (Swyx00013354)

  • Master and Standby server show different status for users, trunks etc. in administration.
    (Swyx00013235)

  • SIP Gateway licenses (voice channels) are not released after switching from Master to Standby server.
    (Swyx00013209)

  • No incoming calls with PIKA board possible.
    (Swyx00012838)

  • Incoming call via Trunk will not be resolved to Internal Number in case of Trunk's Location set to country code 1 (="US).
    (Swyx00013208)

  • Incoming calls do not work with some DDI SIP Providers (recognition URI's did not work at all).
    (Swyx00013267)

  • ENUM DNS resolutions to destinations with more than one service entry, but with same order and prio don't work.
    (Swyx00013077)

  • Do not issue an Eventlog-Message on each reload of the configuration.
    (Swyx00012393)

  • SwyxServer wrongly interprets dialed Internal Number as external.
    (Swyx00013175)

  • Conference User must not occupy a User license.
    (Swyx00013163)

  • Call forwarding over some SIP providers fails because of invalid calling party number in outgoing invite.
    (Swyx00013059)

  • If user configured for undeliverable calls is logged off, call to an unassigned number will be terminated.
    (Swyx00012944)

  • SwyxFax logoff frees a user license which had not been allocated during logon.
    (Swyx00012812)

  • If user configured for undeliverable calls is logged off, call to an unassigned number will be terminated.
    (Swyx00012944)

  • On dialing only subscriber number, the call is not delivered to user for undeliverable calls.
    (Swyx00012221)

  • There is only one message recorded in: RI change announcement, RI record notice and GSE Script record message.
    (Swyx00012954)

  • Gateway PIKA initialization fixed.

  • Added Gateway CallingPartyName support.

  • Fax transmission gets distorted on emulated ISDN connection.
    (Swyx00013247)

  • Gateway throws exception on PIKA board init.
    (Swyx00013270)

  • SwyxPhone displays wrong time and caller list entries also contain wrong time after daylight change.
    (Swyx00013217)

  • The current Bias (UTC Bias + DLST Bias) of an logged in user must change at switch date.
    (Swyx00013245)

  • Not all SwyxPhones were moved to fallback phonemanager in case of outage and dumping phonemgr.
    (Swyx00013205)

  • PhoneController doesn't reconfigure SwyxPhones to MSS after unpugging/plug-in LAN cable on MSS.
    (Swyx00012927)

  • PhoneManager hangs and is killed by watchhdog if trace modules CorNetTC and CorNetTS are set to Info3.
    (Swyx00012858)

  • PhoneManager dumps and is killed subsequently by the watchdog.
    (Swyx00013231)

  • Daylight saving time change is not reflected on the phone on phones that logon before the change.
    (Swyx00013279)

  • Incoming calls does not work with some DDI SIP Providers (recognition URI's did not work at all).
    (Swyx00013267)

  • ENUM DNS resolutions to destinations with more than one service entry, but with same order and prio don't work.
    (Swyx00013077)

  • Do not issue an Eventlog-Message on each Reload of the configuration.
    (Swyx00012393)

  • Changes in ProviderProfiles.config: New provider Broadnet, entry Sipgate and QSC fixed.

  • Generic number replacement always adds wildcard (*).
    (Swyx00013320)

  • User status remains "Logged on" in case of PlaySound/ConnectTo script.
    (Swyx00013178)

  • Name of alerted user displayed at calling party is incorrect when calling to parallel hunt group.
    (Swyx00013056)

  • Speed dial of user stays in state "speaking" in some cases.
    (Swyx00013022)

  • User status remains Logged on if user picks up notification call.
    (Swyx00012270)

  • It is not possible to store new recorded voicemail announcement in remote inquiry menu using the #-key.
    (Swyx00012909)



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.