SwyxWare v6.02 Maintenance Pack 1 (kb3415)
Le informazioni contenute nel presente articolo riguardano i seguenti prodotti:
- SwyxWare CD v6.02
- SwyxWare v6.02
Swyx releases SwyxWare v6.02 Maintenance Pack 1.
Note: when installing v6.02 MP1 in Austria you need to note the following Knowledgebase Article in the Swyx Partner Net. If you do not have access to the Swyx Partner Net contact your Swyx Reseller immediately.
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:
- Important information about Maintenance Packs (kb3217)
- Definition of terms used regarding SwyxWare Releases (kb3198)
The Maintenance Pack 1 includes the following components:
- SwyxWare v6.02 Maintenance Pack 1
- SwyxWare Administration v6.02 Maintenance Pack 1
- SwyxIt! v6.02 Maintenance Pack 1
- Swyx ISDN SX2 Treiber v188.8.131.52
Please note: in order to setup the Maintenance Pack correctly you need to update all components.
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 Maintenance Pack 1 addresses the following issues:
Wrong CallerID in Voicemail when forwarding a voicemail via remote inquiry.
Certain numbers in Germany cannot be reached from Switzerland.
Call dialed per overlap sending is routed to trunk although dialed number should be terminated.
There is case when it isn't possible to delete user on IFB configuration.
It is possible that changes in user configuration will not be notified by the server directly. (DefaultFwd etc.).
Trunk enumeration fails if a remotely managed SwyxLink is changed to locally managed.
SQL Server (MSDE) causes heavy cpu load.
CDSClient maps the same computer name to two differrent IpAddresses.
Call transfer with IP600 fails - call disconnect faster than call transfer instruction.
Attaching media streaming takes too long in case of PlaySound/ConnectTo script if destination is external party.
SwyxServer does sometimes not forward the DTMF infos in case they are sent very early after start of connections.
No outgoing T.38 fax calls from innovaphone IP21 possible.
Dialing out via overlapped sending failed using a NT mode connection to a subPBX.
Privacy header not containing 'id' disturbs correct decoding.
Incorrect file name for recorded conversation via SwyxLink.
LinkMgr: Access Violation when getting about 300 incoming calls.
It is not possible to use the LinkMgr on a remote station.
Recording file name is generated with invalid characters if a SIP URI is transmitted as calling party.
User hears no Late B3 disconnect tones because LinkManager releases RTP ports.
Faxtransmission via INode SIP Trunk is unreliable during transmission of multiple pages.
SwyxLinkMgr does sometimes not forward the DTMF infos in case they are sent very early after start of connections.
Onesided mediastreaming in case of incoming call from SIP Provider Priority Telecom NL.
Incoming SIP call fails via LinkMgr in case of "special" number suppression / RFC3325.
LinkMgr: missing CNG T.38 info element in outgoing fax calls.
L420-Phone cannot reject first call if you get two calls in the same time.
No response to the user, when setting up a callback request using a SwyxPhone.
SwyxPhone: you hear the wrong mediastream after a blind call transfer to an external number.
PhoneMgr doesn't deliver a group (sequential) call correctly in case of a single user logged on.
Mediastreaming is only switched after 10 seconds after a transfer to a swyxphone.
Script property 'IsGroupOrUserBusy' delivers wrong result in case number to query is different from called number.
One-way media streaming when accepting forwarded call (via drag & drop).
PhoneManager dump after disconnecting all phones at once.
Line is blocked for 2 seconds after an outgoing call.
Impossible to accept 3rd call on SwyxPhone in case of call Signaling.
SwyxPhone L520s: The label remain blank after a cold start.
Magic strings "*24*2#" and "*24*3#" are not supported.
SNMP: SwyxWare performance counters are not visible.
SNMP OIDs are not visible to SNMP clients.
SwyxGate does sometimes not detect DTMF tones if they are pressed very early after connect.
Gateway do not use localhost to address CDS Service, if gateway runs locally.
Trunk recording file name contains wrong number in some cases.
It's not possible to disable secondary call for SIP devices.
Call list entries are not written for ConnectTo devices after a PlaySound action.
Missbehaviour in sip-stack, when initiating hold in alerting state (script already connected).
Channel counter decrement without prio increment if ip600 hooks off and on.
The SwyxPhone has no ringback tone if the callee uses the parallel call feature.
SwyxServer AccessViolation after switch-over on passive server.
Call stucks if two ConnectTo blocks contain special ALERTING tone.
A call to group interrupts if one group member doesn't answer, but second member is busy.
After recording new voicemail announcement the RI menu does not proceed.
Caller list entry not written for picked-up call.
Parallel call fails if parallel call device accepts call very fast.
Call deflection does not work if call has been accepted via PlaySound before.
Call notifications (SIP invites IPPBXCallType: 5) are sent to CTI-SwyxIt!.
Call stucks if ConnectTo with activated Proceed with destination script option connects to user with immediate redirection.
Calls starting with magic ## have the wrong external status.
Swyxit! display shows unexpected calling party name, when caller initiates a call from remote inquiry script.
Secondary call is delivered even if secondary call is disabled and first call is present.
Server throws access violation in case of pressing ALT+F4 while active call on SwyxIt.
SwyxIt! hangs in connecting state.
Server generates minidump every 10min after RI.
Sip user passwords should not been traced in plaintext.
CDR not written on successfull outbound SIP trunk call because destination address and name are missing.
No CallQueue announcement is heared after first connection attempt of trunk call with G.729 only.
Call got stuck while COnnectTo loop to group number with announcements between connectTo attempts.
Volume of music on hold files is not constant.
MEM cannot signal the original callers number to the GSM phone.
Incoming SIP calls via SIP links cannot be transferred via script action.
Hunt group not working as expected if used with GSE CallQueue.
ConnectTo with 'Proceed with destination script' fails if ConnectTo destination is user with immediate redirection to extern.
Trunk device channel count not decremented on parallel call if internal device if logged off.
Parallel call is canceled on accept with internal device due to codec mismatch if ISDN trunk is configured to G.729 only.
SIP Messages are sent from the wrong IP address of FES if Virtuozzo instance has multiple IPs.
Call is terminated after ConnectTo script action with unkown number if call was accepted by PlaySound before.
Server does not route undeliverable calls to assgined number.
Special dialstring for supplementary services not sent to gateway - keypad mode broken.
If external number in CDR should be replaced by 'x', it is replaced by 128 'x'.
Trunk device channel counter not decremented if parallel call causes two resolutions to trunk device within one ConnectTo.
Caller list entry written for wrong user if call is passed through server by number routing entry.
Trunk recording: allow ranges for auto numbers.
Silence detection causes deadlocks and dumps.
Outgoing calls through SIP provider Dus.net are not possible.
Status signaling fails when H.323 alias is identical to internal number.
SwyxServer uses internal number when client dials user name.
Server killed by watchdog when using a lot of phones + CTI.
Call deflection works incorrect in case of configured parallel call.
Server does not free memory on SwyxIt logon / logoff stress test.
One way Conference does not work if initiated via ConnectTo block.
Blind Call Transfer Timeout within SwyxServer is too short.
It isn't possible to install IFB configuration with IpPbxBackup.
Rules cannot be reordered in CRM, arrow buttons are disabled.
Size of the CRM window is not remembered.
Marked CRM rule after GSE cancel.
File version tab of callroutingmgr.exe displays language German.
The Open dialog don't save path in the Standard Voicemail.
The Open dialog don't save path in the CRM.
CRM should list custom specific ASE file as "sequence of action".
CRM opens the Standard Forwarding properties if to try to activate this rule via checkbox.
Call Forwarding Configuration tabs contain old style phonebook buttons.
There are some old style buttons on 'Standard Voicemail' tab.
Link for set parameter in decription of GSE action.
Access violation if intruder holds and actives intrusion call.
If SwyxIt is initiator of a conference, the redial button tooltip shows #conference#.
Echo when using P250 in headset mode.
SwyxIt! does not retry SIP Subscriptions if server is busy.
Call will be disconnected if Swyxit! (Prefer compressed) will be holded.
Wrong peer number if fake number is configured.
SwyxIt! in Powerdial mode should not respond to windows session messages and should not use sound devices.
P250 does not work on Vista when 2nd device was installed.
Get DTMF string block with empty edit box.
Error for disabled edit box.
Enabled button after unmarked check box in the "Follow me"action.
It is possible to close User List with OK without selected user.
It is impossible to add two users in the To field in the "Send email" block.
Get DTMF char block doesn't allow using variable to define option "Max detection time".
There are some old style buttons in GSE dialog.
Wrong timestamps in Outlook Journal.
Delete button on keyboard doesn't work for personal phonebook.
Blind Call Transfer takes too long because of trailing silence in "NotifyTransferring.wav".
Button "New.." in Call Routing Manager -> Sequens of Actions dialog cannot be pressed in some situation.
It should not be possible to configure twin-call at ConnectTo operation which do use 'Proceed with destinations call routing'.
IMAP-Passwort can be discovered by hacker tools.
Wrong title bar caption in parallel call settings.
Loading of standard redirection settings fails for Operator and ConfMgr.
GSE background not updated when resized over two monitors.
Scripts in user directory are not shown in GSE-Block RunGSEAction.
Missing dot in statusbar comment of Action | Connect to another Computer...
It´s not possible to click "Check for updates" if scrollbar is used.
SwyxWare directory can not be opened in mmc by selecting icon.
Email Adress dialog is missing when adding a dummy user.
Max calls values can be set to invalid combinations.
SwyxWare Administration crashes when SwyxServer is stopped.
It is possible to create descending number range for trunk that can't be used then.
Add range operation isn't correct.
In the New Trunk Wizard -> If first and last subscriber number have different length a strange error message occurs.
Next button within Add new number mapping range must be disabled if no internal number is defined.
Opening user properties takes too long if SwyxWare has approx. 1000 users.
User properties changes are not applied.
Not implemented DTMF methods can be configured via SwyxWare Admin for SIP Trunkgroups.
SwyxCompact system - Admin counts FaxUser as user which occupies one license.
Swyx SX2 ISDN Driver
Drivers shows two DualPRI boards are connected via PCM although they are not.
The driver's GUI WAN page displays part of PCM clock settings.
Memory leak when running NT and PtP mode.
SENDING_COMPLETE is not included in CONNECT_IND message.
- SwyxWare v6.02 Maintenance Pack 1 Danish
- SwyxWare v6.02 Maintenance Pack 1 Dutch
- SwyxWare v6.02 Maintenance Pack 1 English UK
- SwyxWare v6.02 Maintenance Pack 1 French
- SwyxWare v6.02 Maintenance Pack 1 German
- SwyxWare v6.02 Maintenance Pack 1 Italian
- SwyxWare v6.02 Maintenance Pack 1 Norwegian
Informazioni di altri produttori proposte in questo articolo hanno il compito di appoggiare la ricerca di informazioni tecniche. I contenuti potrebbero essere modificati senza preavviso. Swyx non garantisce per la veridicità dei contenuti di articoli di terzi e declina ogni responsabilità per essi.