You should think of this pre-release like a reliable beta release. This release is for
distribution to beta sites, development partners, and sites requiring specific new
features or patches, etc. InSciTek will only recommend updates to a pre-release type
release version when it is known that the pre-release software addresses a specific
issue being experienced or a specific new feature is required for a new installation.
Compatibility
Server 5.2.0.7
Phone 1.2.0.5
Client 5.1.0.3
OfficeSafe 5.1.0.3
Installation Tips
It should be valid to upgrade from any previous official customer release to this
Allworx 5.2 release. InSciTek has specifically tested upgrading from production
versions of 4.6, 5.0 and 5.1.
You should never directly downgrade a server disk with older software than is
already installed. You should reformat the disk, and then install the older release
directly from Safe Mode.
If you wish to have the capability to downgrade an installation back to your current
software, it is recommended that you make a fresh backup before upgrading to this
software. Then later a downgrade can be accomplished by restoring from the
backup.
Allworx phones must be rebooted after installation of this software version to obtain
their new code. Note
may not be compatible with pre-5.2 server software once upgraded.
If an Allworx IP phone is reporting a config/init error, then restore factory defaults
and allow the phone to reboot. This should only be necessary if the phone was
previously being used with 4.6 release or older. However, if the station was
manually configured to an improper network or boot server configuration, that may
also prevent it from working as well.
For site-to-site configurations, it is highly recommended that all Allworx servers be
upgraded to the same release of software. Certain problems may be exhibited if
versions of software are mixed. This results because of changes to certain
proprietary features that exist in the Allworx servers and their related Allworx
phones.
: Allworx phones will not allow you to downgrade software and
Notice about Linksys™ Branded Firewalls and Routers
Any brand of SIP IP phone located remotely behind Linksys NAT devices may not
function reliably due to a Linksys Router/Firewall Bug. The Linksys BEFSR41 series
NAT devices (and likely other Linksys models) have a bug where they can dynamically
remap UDP ports on 20-minute boundaries. This can cause loss of audio during a call
or the inability to place or receive calls. Multiple phones behind the same device will
exhibit the problem much quicker than a single device. For proper operation, Linksys
recommends UDP ports used for VoIP operations (e.g. SIP, RTP range, etc) should be
set independently for each phone and then manual firewall rules be entered to
statically map each needed port for each phone through the Linksys device. Consult
your Linksys manual for specific instructions.
The SonicWall™, Netgear™, D-Link™ and Allworx™ all acting as NAT/Firewall
devices have been tested and none of these other brands exhibit this problem. That is,
manual firewall rules will typically not be required when remote Allworx IP phones are
placed behind these other firewall brands. The NAT devices tested were: SonicWall
Tele2, Netgear RP614, and Linksys EW5Hub. The models that were tested and
verified had the latest manufacturer software.
Known Limitations with release 5.2.0.7
The following sequence of events can happen if a user performs a Reboot with
Diskwipe and then does an OfficeSafe backup and Restore.
The backup will not have the software code and will not be loaded on the system until
the next software update/install is performed. After the Restore, the options available
to the user will be Reboot in Safe Mode or update the software.
Workaround: After the restore completes, REBOOT system (in Safe Mode), mount the
disk from safe mode and install the same or newer version of Allworx software on the
disk. Then boot the system normally with all user data restored
Defects Resolved since release 5.1.2.6
1. Title: Administrative tool timeouts during slow firmware downloads.
Change/Enhancement: Admin tool remains active during entire time download is
proceeding. No timeout occurs assuming download progress is being made.
Tracking: Bugtrack 2612.
Action required by admin or user: None.
2. Title: Alert light does not display proper status of failed disk drive in a mirrored
setup.
Change/Enhancement: By design intent, if a disk drive fails, the alert lamp should
flash with a sequence to notify the admin of a problem.
Action required by admin or user: During systems faults, the admin should use this
indication as an additional trouble-shooting tool, and then refer to the system event
log.
3. Title: Call handling to certain proxy servers rejected due to required “address of
record” in the SIP “From” header (DSLi service issue).
Change/Enhancement: Added “address of record” in the SIP “From” header.
Tracking: Bugtrack 2626.
Action required by admin or user: None, compliant to all existing proxies and DSLI
service.
4. Title: Additional support for SNOM proxy server.
Change/Enhancement: Fixed support for SIP abbreviated headers. “t” was incorrectly
being interpreted as “Content-Type” instead of “To” (SNOM proxy issue).
Tracking: Bugtrack 2651.
Action required by admin or user: None, compliant to all existing proxies and
SNOM service.
5. Title: Malformed SDP content not parsed correctly – Telwise ITSP.
Change/Enhancement: SDP content that is shorter than expected is still parsed for
content (TelWise issue).
Tracking: Bugtrack 2630.
Action required by admin or user: None, compliant to all existing proxies and
Telwise service.
6. Title: Mirrored drive reporting in About box corrected.
Change/Enhancement: About Box is reporting a mirrored drive when second drive is
installed but not mirrored has been addressed. This happened if the installed drive
was not partitioned and left installed without actually doing the safe-mode procedure.
Tracking: Bugtrack 2531.
Action required by admin or user: Admin should carefully check about box after
upgrading firmware to ensure drives are indeed configured correctly. If not follow
updated service procedure for mirroring disks in the server and perform and
OfficeSafe disk image backup.
7. Title: Missed calls now logged within phone history.
Change/Enhancement: All missed calls now appear in caller history screen even if
they are not dialable.
Tracking: Bugtrack 2344
Action required by admin or user: None, user will notice an improvement in call
history.
8. Title: Prompts added for New User Welcome Page.
Change/Enhancement: After adding a new user, the system admin will now see a
friendlier prompt reminding them that a summary welcome page is available for the
new user. The welcome sheet may be printed or emailed.
New Features in server 5.2.0.7/Phone 1.2.0.5 Release:
1. Title: SIP message logging included as part of admin tools.
Change/Enhancement: SIP messages can now be recorded from the “Tools” page
for a selectable time period.
Action required by admin or user: Administrator can now use the SIP message
logging to record and diagnose message interchange between SIP devices. This
should be used as part of the standard reports when submitting for technical support.
2. Title: System event logs now report time in Date/Time format rather than ticks.
Change/Enhancement: System Event Log entries report in Date and Time format
instead of system tick counts. Any pre-existing log entries (and Safe Mode log entries)
that have ticks associated with them report as “unknown” date and a time offset since
12am until they wrap out of the log and are replaced with entries in the new format.
Action required by admin or user: An administrator using or reporting the system
events logs will find this format much more readable.
3. Title: Safe Mode appearance, messages and usability improved.
Change/Enhancement: Safe Mode screens improved with redesigned screens, more
sequential and logical prompts and error messages, and improved fault protection for
the admin.
Action required by admin or user: An administrator using safe mode will find it
more friendly and useable in addition to providing progressive disclosure of tasks.
4. Title: Allworx server in LAN host mode can now route VoIP traffic via existing
enterprise firewall.
Change/Enhancement: LAN Host mode now fully supports use with external 3rd
party firewalls. The public IP of the firewall must be entered in the Allworx admin
pages. VoIP ports of 5060 (UDP) and an RTP range (e.g. UDP 15000 – 15111) must
be mapped through the firewall. For remote phone usage, ports 2088 (UDP) and 8081
(TCP) must also be mapped through the firewall. Forced RTP (audio) routing through
Allworx to ease network configurations where Allworx is not the default route to the
WAN. This applies to LAN-to-WAN and WAN-to-LAN SIP calls.
Action required by admin or user: Allows the network administrator greater
flexibility when selling or installing into existing network configurations. Legacy
firewalls may require proper static rules and SIP/VoIP port configuration and Allworx
product may be installed on LAN.
5. Title: Full Vonage Business Plus Integration and compliance.
Change/Enhancement: The Vonage compatibility requirement is now currently met.
That is, SIP INVITEs that result from transfers (via REFER method) now contain the
"Referred-By" header info from the REFER message. This allows transfer initiators to
distinguish new calls from transferred calls.
Action required by admin or user: None, Installation and setup with Vonage
accounts are automatic, reference attached application bulletin.
6. Title: Multiple phones behind a single remote firewall now have greater
functionality.
Change/Enhancement: The new proprietary feature in 5.2 releases that allows two
remote Allworx phones behind the same 3rd party NAT/Firewall to be able to establish
audio between each other is now fully enabled.
Action required by admin or user: Server and phone firmware need to be updated
and devices rebooted. Phones will now be able to call each other and access any
other device. Note limitation of Linksys firewalls when using remote phones.
7. Title: PCM format .WAV files now supported.
Change/Enhancement: Added support for selectable Voicemail attachment format
including the current default of WAV G.711 uLaw and now WAV PCM. This will enable
audio playback on selected handheld devices which did not play G.711 uLaw files.
Action required by admin or user: Admin must select proper format required for
end user.
8. Title: User specific call detail records.
Change/Enhancement: Added Per User access to station specific CDR records and
controlled access to live call status w/Caller ID access. Added support for checkbox on
User / Modify page to enable/disable user viewing caller id info on Live Call Status
page.
Action required by admin or user: User may access records by logging in to
Intranet website. Admin may control user’s capability to view and monitor caller
information from within the live call status view.
9. Title: Inbound SIP calls on hold hear music/messaging on hold.
Change/Enhancement: – Inbound calls from SIP proxies and gateways that use “SIP
Hold” as the transfer method now hear hold-music (via Line-In) during blind transfers,
including dialing through the auto attendant. Configurable per SIP device checkbox
option (handsets, gateways, proxies) to have line-in hold music available when device
puts calls on-hold. Previously, SIP-to-SIP calls that were put on hold would receive no
audio at all.
Action required by admin or user: None.
10. Title: Network PacketJitter statistics available on phone.
Change/Enhancement: Adaptive Jitter Buffer Handling and statistics reporting. The
Jitter statistics on the Config/Statistics phone menu is now operational.
Action required by admin or user: When diagnosing audio problems on a particular
Allworx phone, the admin will now have improved logging and reporting of Packet
Jitter statistics.
11. Title: Phone PFK system speed dials now may contain any system speed dial.
Change/Enhancement: All system speed dials are now available on a handset’s PFK
speed dial key.
Action required by admin or user: User’s handset may require re-configuration to
include expanded selections.
12. Title: Do Not Disturb now applies to all inbound calls to handset including Line
Appearances.
Change/Enhancement: All calls that normally would ring a user’s phone will now be
ignored when the handset is in DND mode.
Action required by admin or user: No change required, phone behavior will change
by default.
13. Title: User presence control available via Intranet site.
Change/Enhancement: Users may now change their state of presence from the
company’s Intranet site. Login with user name and password is required.
Action required by admin or user: Admin should inform users they now have a forth
option for changing their presence. Presence call route definition must still be done by
the admin or via the message center software.
14. Title: Enable debug mode available for administrator.
Change/Enhancement: Telnet access is now available for problem diagnosis from
the Maintenance/Tools page.
Action required by admin or user: Admin may manually turn on debug and capture
logs of suspected problem scenarios. This feature will be useful when reporting issues
to technical support.
15. Title: Server configuration summary now directly available within administration
tool.
Change/Enhancement: The config.asp page is now directly available via Reports /
Configuration page
Action required by admin or user: Admin may generate the server’s configuration
via this tool. This feature will be useful when reporting issues to technical support.
16. Title: “Need Help” link added to administration tool.
Change/Enhancement: Additional on line help has been added for the administrator.
In addition to guidance on the installation sequence, topic specific help has been
added.
Action required by admin or user: Admin should use the online help when installing
and maintaining a system.
17. Title: Functional and Operability improvements inLAN Host mode
Change/Enhancement: Multiple functional changes allow set up in LAN host mode to
be error free. Configuration error checking prevents system admin from misconfiguring
network.
Action required by admin or user: None for new installations.
18. Title: Compliance of Epygi T1/PRI gateway
Change/Enhancement: Full support for Epygi gateway including functional
compliance and Improved T1/PRI Epygi SIP Gateway Support which includes per
device:
- configurable outbound caller ID name and number information and
- selectable field for DID number extraction on inbound calls
Action required by admin or user: Per configuration on SIP Gateways page.
19. Title: Improved DID integration and for ITSPs
Change/Enhancement: Improved ITSP/Proxy support which includes per-proxy
configurable:
- outbound caller-ID name and number information
- selectable field for DID number extraction on inbound calls
- configurable outbound caller ID name and number information and
- selectable field for DID number extraction on inbound calls
Action required by admin or user: Per configuration on SIP Proxies page.
20. Title: Display of dialed digits during line appearance calls
Change/Enhancement: Better Dialing/Redial Support on phones for Line
Appearances including more uniform availability of ‘missed calls’ and ‘call history’
features. Added support for "Line Appearance(s) Use Dial Plan" setting for Allworx
phones on the server handsets page.
Action required by admin or user: Users will now see digits dialed along with all
calls appearing in call history.
21. Title: Domain Name support for ITSP access proxies.
Change/Enhancement: Domain Name support for ITSP access proxies including the
registrar address. Also includes DNS failover support for proxies that do not respond.
Action required by admin or user: Allows configuration and use with Vonage and
other ITSP services requiring registration by name rather than IP address.
Defects Resolved:None. No changes to 5.1.0.3.
Functional Changes/Enhancements Made:None. No changes to 5.1.0.3.
OfficeSafe
Defects Resolved:None. No changes to 5.1.0.3.
Functional Changes/Enhancements Made:None. No changes to 5.1.0.3.
User Operational Tips about the Phones
How to Transfer: From within an ACTIVE call, press the TRANSFER button. From
here you can transfer by dialing the number of the intended recipient (blind transfer) or
selecting a party that is already on hold (attended transfer). You can also select a line
or call appearance to place a new call on for an attended transfer. When you complete
setup of the new outgoing call pressing TRANSFER again will complete the attended
transfer. Before the transfer is completed, RELEASE can be used to abort the
operation.
How to Conference: Conferences can be setup between any pair of calls managed by
the station. It does not matter who called whom. From within an ACTIVE call, press
CONFERENCE and select the other call on HOLD whom you wish to conference with.
To conference in somebody you are not already connected with, put the first party on
hold, call the third party for the conference, press CONFERENCE and then select the
first party call that is on hold. While in conference (CONFERENCE illuminated), you
can disconnect a single party by selecting the PFK of the party you wish to maintain a
call with. If you hang up on an active conference, all parties are disconnected. If a
remote party hangs up, the conference is ended, but you will still have the remaining
party available in a normal call. Note: You can’t TRANSFER a conference or put a
conference on HOLD. You can however MUTE a conference and the other parties will
still be able to talk to each other.
Conference is between an active call and somebody else on HOLD when setting up
the conference. That is, that call will be slow flashing GREEN. You can’t select a call
that is PARKED. If you want to conference with somebody who is parked, then put the
current ACTIVE call on HOLD so that it is slow flashing GREEN. Retrieve the parked
call, press CONFERENCE, the reselect the call you just put on hold.
If you are in the middle of a transfer operation, the phone will not allow you to hang-up
on the remote user and lose the transferee. This is an intentional feature. The transfer
will either complete normally if a valid PFK is selected or a complete target number
was dialed, or the call will be left on hold and you can return to it by reselecting the
associated PFK. To illustrate the point, pressing TRANSFER and hanging up is
logically the same as pressing HOLD and hanging up. You can’t drop the call once you
use TRANSFER until you press RELEASE twice or RELEASE and hang-up.
You can web surf to a phone’s internal website at http:/phoneIpAddress:8080/ to
examine the phone’s log information. This may be helpful to capture error messages in
the case of test failures when the serial terminal output of the phone was not already
being logged.