INFO

SwyxWare v5.01 Hotfix 5 (kb3197)

The information in this article applies to:

  • SwyxWare Administration v5.03
  • SwyxWare CD v5.01
  • SwyxWare v5.01

[ Summary | Information | Links ]


Summary

Swyx releases the SwyxWare v5.01 Hotfix 5.

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

To check which hotfix 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.


Information

Hotfixes 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 hotfix is installed
  • Hotfixes can be easily removed if necessary
  • Smaller download size

To install the hotfix execute setup.msp and follow the Installation Wizard.

Hotfix 5 addresses following issues:

  • Hotfix 5 installs an updated SwyxPhone firmware v5.1.31, which is needed for certain new devices L520 and L540
  • PhoneManager may dump under special conditions and is subsequently killed by the watchdog.
    (Swyx00013269)
  • Fax transmission gets distorted on emulated ISDN connection.
    (Swyx00013246)
  • Not all SwyxPhones were moved to fallback PhoneManager in case of outage of master PhoneManager.
    (Swyx00013202)
  • User with extension '0' (Operator) is not reachable anymore if 'Use for external outgoing calls' is disabled on SwyxGate line
    (Swyx00013098)
  • SwyxServer may cause a memory heap corruption under certain conditions, when delivering a call to a SwyxIt! and to a SIP device in parallel
    (Swyx00013097)
  • Dialing a canonical number, which includes "(0)", isn't interpreted correctly by SwyxServer.
    (Swyx00013020)
  • Blind call transfer is not cancelled when connected to voicemail.
    (Swyx00012991)
  • Server writes caller list entries only for one group member if group call is initiated via ConnectTo script.
    (Swyx00012862)
  • Passive hold with link at the provider side fails using G729.
    (Swyx00012859)
  • Wrong entry in column "Call for" in caller list, if call is immediately redirected.
    (Swyx00012738)
  • Calls to a mobile phone via a SIP Trunk of provider "Telenor", which are put on hold by the mobile phone, cannot be activated again
    (Swyx00010557)
  • LinkManager may cause under special conditions an access violation within STimer::OnTimeout of STUN socket.
    (Swyx00010444)


Please note that there is also a new SwyxWare Administration v5.03 needed for this hotfix.


Hotfix 4 addressed following issues:

  • LinkMgr recognizes blockedNAT if one of two links uses STUN and the other one does not.
    (Swyx00012364)

  • Sometimes one way mediastreaming on the phone until it is rebooted.
    (Swyx00012114)

  • User Provided calling party number isn't signalled on incoming calls from HST PRI card.
    (Swyx00011780)

Please note that there is also a new SwyxWare Administration v5.03 needed for this hotfix.


Hotfix 3 addressed the following issues:

  • SwyxServer process may be killed by the Watchdog when a SwyxPhone is restarted while the system is under high CPU load.
    (Swyx00010871)

  • PhoneManager generates access violation in case of configuration inconsistency between PhoneManager and SwyxWare Administration.
    (Swyx00010730)

  • Fake numbers are not used anymore after a SwyxPhone line has been disabled.
    (Swyx00010706)

  • LinkManager has been changed to become more compatible to Telenor.
    (Swyx00010733)

  • Adding a Permanent License File, that covers a hardware change and adds some new license codes, fails sometimes.
    (Swyx00010576)

  • Missing support of Norwegian and Polish special characters on SwyxPhones.
    (Swyx00010655)

  • Watchdog is acting too sensitive, i.e. kills SwyxServer, in cases, where the entire SwyxServer is heavily loaded or blocked for more than 15 seconds.
    (Swyx00011408)

  • Phone manager generates a memory dump, when a notification call is passively disconnected with two disconnect events.
    (Swyx00011442)

  • Compatibility problems with SwyxConnect and Thomson SIP phone: Incorrect handling of un-register with contact "*".
    (Swyx00011363)

  • In rare cases voicemail attachments are not played back during remote inquiry.
    (Swyx00011307)

  • In some cases DTMF input digits are appended to the called party number on incoming calls.
    (Swyx00011034)


Added new functionality with Hotfix 2:

  • Support for SIP links with no registration

To create a registration less SIP link you have to configure the 'registrar' configuration entry as magic string "noregistration". This configuration is either possible with the registrar field on the SIP property page on the link, or with the registrar attibute in the SIPProviderProfile element in the SIPProviderProfiles.config - XML file.

Further information on this can be found in the knowledgebase article

For the successful operation the SIP INVITE messages coming from the SIP provider should fullfil one of the following conditions:

  • all messages come from the IP address of the configured proxy
  • the URI in the To header has to include the host part (after the @) of the provider's realm.
    Example: sip:12345@example-provider.com

Hotfix 2 addressed the following issues:

  • No caller list entry if incoming call is redirected by GSE script.
    (Swyx00010213)

  • Holding a call routed through T-Online SIP Link does not work correctly.
    (Swyx00010556)

  • SwyxIt! displays wrong time in caller list if New Zealand time zone and regional settings are configured.
    (Swyx00010522)

  • "Clip No Screening" does not work if call already was accepted by call routing script.
    (Swyx00010602)

  • Hide number does not work properly.
    (Swyx00010611)

  • Blind call transfer from ip600 to SwyxGate failed.
    (Swyx00010614)

  • PhoneManager deadlock caused by picking up a notification call.
    (Swyx00010617)

  • The contrast of the self labelling keys cannot be changed and some-times appears too dark.
    (Swyx00010618)

  • AccessViolation in SwyxServer, because RecordFileChannel could not be stopped.
    (Swyx00010665)

  • Group member H.323 device keeps ringing after call originator disconnects call.
    (Swyx00010738)

  • Server disconnect call if device using compression only picks up call after PlaySound script action.
    (Swyx00010743)

  • Improve conference quality by increased noise level for AGC silence detection.


New hardphones supported with Hotfix 1:

  • optipoint 410 economy plus
  • optipoint 420 economy plus

Hotfix 1 addressed the following issues:

  • No inband tones in case of special ISDN message sequence on DECT device attached to Kirk ip1500.
    (Swyx00010439)

  • When a blind call transfer call comes back there is no acoustic indication in the case that the user has call on another line.
    (Swyx00010488)

  • Unable to use Pika board AND ISDN board at the same time in one PC.
    (Swyx00010519)

  • Link call attempts to H.323 third party gatekeeper are not disconnected if stopped after ringing.
    (Swyx00010525)

  • Name resolution in redial list not working if dialnumber contains whitespaces.
    (Swyx00010529)

  • Link calls to H.323 third party gatekeeper are disconnected if Q.931 Status Enquiry message is received.
    (Swyx00010540)

  • Hiding phone number does not work for status signalling to other users.
    (Swyx00010541)

  • SIP client does not work correctly any more in case of second register of SIP client with different port.
    (Swyx00010543)

  • Redirecting external incoming call with CRM to PSTN via SIP link with DDI enabled fails.
    (Swyx00010547)

  • Sometimes there is only one way mediastreaming on calls via SIP links (in case SIP re-invite is used).
    (Swyx00010549)

  • LinkManager dumps in case of receiving malformed SIP message.
    (Swyx00010551)

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.