|DSX Info Center
|System Software 3.42
|System Software 3.41
|Home Automation Integration Overview
|System Software 3.34 Archive
|System Software 3.22 Archive
|System Software 3.20 Archive
DSX In The News
and NEC Finalize Integration, Announce Connectivity Partnership
DSX Phone System Becomes Home Automation Controller
IP Extensions with NAT Traversal (v3.2)
IP Extensions with NAT Traversal (v3)
IP Extensions with VPN
IP Extension Setup Guide
IP Keyset Firmware
(Version 2) Software
System Software 3.41 Overview
The new Wakeup Call feature provides Wakeup Call capability for Motels and Bed
& Breakfast establishments. Wakeup Calls are conveniently entered by request from the web-based Wakeup Call
Manager at the facility front desk. Once a Wakeup Call is set, DSX automatically rings the room telephone at
the designated time. When the guest answers, a voice prompt announces the wakeup. If the guest doesn't answer,
DSX waits 30 seconds and tries again. If the guest doesn't answer the second call, DSX cancels the wakeup.
Wakeup Call administration and reporting is handled by the embedded Wakeup Call Manager running in a web browser.
To set a wakeup, the front desk employee uses the Wakeup Call Assignment section to:
- Enter the room's extension number.
- Set the day, hour, and minute for the wakeup and then click Save. (Available times are any future
time for the current day and any time on the following day.)
- Click Save to set the wakeup.
Once set, a pending wakeup is added to the Wakeup Call Status section. This section shows extension,
name, day, and time of the wakeup as well as the wakeup status. The most common status messages can be:
- Pending (a future wakeup that has not yet occurred)
- Answered (a delivered wakeup that the guest answered)
- Not Answered (a delivered wakeup that the guest did not answer)
- Cancelled (an undelivered wakeup the front desk cancelled)
Additionally, the Wakeup Call Status section shows the total number of pending wakeups. It also allows the front
desk to click an item in the list to cancel it, change the wakeup time, or set a new time for a new guest.
To program Wakeup Call:
- System: Config: Setup: Time Zone (1022-02: Time Zone)
System: Config: Setup: Time Server (1023-01: Time Server)
- Wakeup Call Manager uses both the PC time and the DSX system time. Make sure both are synchronized
to an internet time server and are in the same time zone.
- Stations: Config: Setup: Access: Program Level (2102-04: Pgm Level)
- The login extension for Wakeup Call Manager must have Program Level 4 or 5.
- Stations: Config: Setup: Access: PIN Code (2102-Pin Code)
- Enter a valid 4-digit PIN for the login extension.
- System: Config: Communication: Ethernet: Web Access Port (1104-07: Web Service Port)
- Wakeup Call Manager uses the Web Services Port, just like Phone Manager. If you use a port other than
port 80, be sure to append it to login address (xxx.xxx.xxxx:port).
To start the Wakeup Call Manager:
- From a web browser on the DSX system LAN, type:
http://<dsx LAN IP address>/wakeup
- The Wakeup Call Login Screen will open.
- Enter the number of the extension authorized to use the Wakeup Call Manager, enter the extension's PIN, and
Wakeup Call and SLT Message Waiting
(3.40.24) Wakeup Call is compatible with the Message Waiting feature at single
line telephones. At a Bed and Breakfast establishment, for example, management's DSX keysets can have full IntraMail
capability and single line telephones in the guest rooms can be limited to Message Waiting. Wakeup Call will
operate normally at either extension type.
(3.40.27) If the room single line extension has a message waiting from the operator,
the guest can lift the handset and dial 0 to return the call. It is no longer necessary for the guest to dial
To set this up, for the single line guest telephones:
- Stations: Config: intraMail: Mailbox Type (4101-01: Voice Mail Type)
- System: Class of Service: SLTs: HiVolt Msg Waiting Lamp (1403-04) or FSK Msg Waiting Lamp (1403-05)
- Enable one or the other type of Message Waiting lamping. Set this for compatibility with the connected
single line telephone.
Wakeup Call requires IntraMail Pro.
Synchronization synchronizes the status of a voice mail message delivered by IntraMail Email Integration with
the message recipient's email inbox. When Email Integration is enabled and the Sync when Read disposition
option is chosen, the status of the voice message is shown in the user's email client when the message is opened.
- A co-worker leaves a message for Sarah on her office DSX keyset while she is traveling.
- Email Integration (with the Sync when Read disposition enabled) delivers the email to Sarah's smart
phone email client.
- Sarah opens the email, which causes the message to be saved in the DSX. When the email finishes loading,
the Message Status will show that it has been saved.
- Later on in the day, Sarah calls her mailbox to clean out old messages and deletes the message for which
she earlier received a notification.
- The next time she opens her smart phone email client and reviews her email, the Message Status will
show that the voice message has been deleted in the system.
To program Email Synchronization:
- Set up and verify Email Integration as you would normally.
- Stations: Config: IntraMail Pro: Email Notification: Message Disposition (2146-05: Disposition)
- (3.40.15) System: Config: Email: Email Notification Synchronization: WAN
Address (1108-01: IP/URL)
- Enter the WAN IP Address, URL, or Dynamic DNS (DDNS) URL of the router to which the DSX is connected.
- (3.40.15) System: Config: Communication: Ethernet: Web Access Port
(1104-07: Web Service Port)
- This is the port the DSX uses for web services (Phone Manager and Wakeup Call). Make a note of it -
you'll need it in the next step.
- (3.40.15) System: Config: Email: Email Notification Synchronization:
Port (1108-02: WAN Port)
- Enter the port you want Email Synchronization to use. It can be any valid port (1-65535)
but the port must be forwarded to the DSX LAN IP address at the Web Access
Port in the site router.
- Note that not all routers support this type of forwarding. If your router doesn't, the Email Synchronization Port and the Web Access Port must be the same. Additionally, that port must be forwarded to the DSX LAN IP address in the router.
- The setting
of this option does not affect any other DSX features that use web services.
DSX Email Synchronization works with all types of email accounts (i.e. client-based and web-based). While not
complete two-way synchronization (i.e. the voice mail message status does not affect the email message read/deleted
status), this method provides an easy to achieve solution for most users.
Email Synchronization requires IntraMail Pro.
The ML440 Wireless IP DECT handset along with the AP20 Access Point provides the convenience of mobility in
the home or office by combining the latest VoIP and DECT communication technologies. The ML440 and AP20 use WiFi
friendly DECT 6.0 (1.9 GHz) technology.
You can set up either a Single Cell or Multiple Cell solution.
- Single Cell
- 30 registered ML440 handsets
- 10 simultaneous calls
- Multiple Cell
- 20 access points
- 30 registered handsets per access point
- 8 simultaneous calls per access point
- Seamless handover
Since each ML440 handset registers in DSX as an IP extension, you can have 32 handsets maximum per system. VOIPDB
license requirements are the same as DSX IP keysets. Note that Intercom calls between ML440 handsets, as well
as ML440 handsets and DSX IP keysets on the same LAN, are peer-2-peer and do not require a VOIPDB license.
|ML440 Handset with Charger
730650 Lot B
|AP20 Access Point
730651 Lot B
ML440 AP20 Bundle
(1) AP20 Access Point
(3) ML440 Handset with Charger
730653 Lot B
|P/Ns 730650, 730651, and 730653 Lot B are required for DSX compatibility.
||Additional Feature Enhancements
Phone Manager: IE9 Compatibility and Automation Key Added
The Phone Manager Key Assignments, Personal Speed Dial, and Company Speed Dial pages are now compatible with
Microsoft's Internet Explorer version 9. The remaining Phone Manager pages were unaffected by the changes made
Additionally, the Key Assignments page now allows the user to set up Automation keys.
IntraMail: Queued Message Notification
Message Notification can optionally Ignore or Queue notification requests for messages left
when there is no active notification destination. Ignore is the traditional operation and has the same
operation as Message Notification in prior software releases. Queue stores the requests and will attempt
to deliver the stored requests as soon as a destination becomes active.
Queued notification could help a service desk collect after hour messages and deliver them at a preset time.
For example, the service desk mailbox could have queued notification enabled with destinations activating at
9:00 the following morning. When the destination becomes active, the system will notify it of all accumulated
- If you have a mixture of active and inactive destinations, the system notify the destinations as they become
active. If the notification is unanswered, the system will then queue for the inactive destinations.
- If the initial notification is unanswered, every remaining destination will be tried the appropriate number
of times as it becomes active.
- If new messages arrive during the notification process, notification is restarted. This ensures that messages
are not lost.
To enabled Queued Message Notification:
- For station mailboxes, enable Stations: Config: IntraMail Pro: Phone/Pager Notification: Queue Notifications
(2145-07: Queue Notif = Yes).
- For Department Group mailboxes, enable Stations: Department Groups: IntraMail Pro: Phone/Pager Notification:
Queue Notifications (2315-07: Queue Notif = Yes).
Group Ring: Caller ID Handling Improved
The Caller ID handling for calls to a Ring Group is improved. This enhancement is beneficial when putting a
Mobile IP Extension in a Ring Group.
SIP Extensions: Error Messages Improved
The SIP extension registration error messages are improved.
- A 30 second retry time is added.
- The display messages include:, Unknown User, Invalid Password, Extension in Use,
SIP Trunking: Enhanced Handling of Level3 DID Circuits
(3.40.30) A new method of line matching is implemented in software version 3.40.30
that allows Level3 DID SIP trunks to emulate a traditional loop start line rotary. To set this up:
Lines: Config: Setup: Type: Phone Number (3101-07: Line Telephone Number)
- Lines: Config: Setup, Type: Type (3101-01: Line Type)
- Enter the incoming DID digits you want the system to match (but without the leading + delivered by
the Level3 DID).
- For example, for a Level3 DID to +12039265400, enter 2039265400. The system will match on the number you
enter and ignore the +1.
- You can enter as many digits in the phone number as are required for an accurate match. The following are
all valid matches for +12039265400:
SIP Trunking: DSX SIP Automatically Uses SIP Info Dialing
DSX SIP lines automatically use SIP Info dialing, regardless of the setting for the profile in System: VoIP:
Profile x: Payload Types: DTMF Type (1815-01: DTMF Relay). This ensure that a caller using a DSX SIP line
to call a remote extension has post-connection dialing. For example, if the remote extension connects voice-announced
the caller can dial 1 to make the extension ring or dial 8 for voice mail.
SIP Trunking: WAN IP Address Detection Improved
(3.40.15) In most cases, the system should automatically detect the WAN IP address
of the router to which the DSX is connected. You entry should no longer have to be entered manually. However,
in systems using ATC, CommPartners, and Windstream that do not have any remote IP telephones
you must still manually enter the WAN IP.
Note: In DSX System Administrator 3.29, the system WAN IP Address entry is moved from System:
Config: Communication: Ethernet to System: VoIP: Providers: WAN Address.
The telephone programming option (1104-09: WAN IP) is unchanged.
SIP Trunking: Domain Field Added
(3.40.22) For compatibility with future SIP trunk providers, the setting System:
VoIP: Providers: Domain (1832-05) has been added. Instructions for using this new setting will be provided
in the SIP Trunk Setup Guides when it is required.
- Centrex Compatibility
- PRI and SIP trunks now correctly follow the setting in Lines: Config: Setup: Type: PBX
Line (3101-04). Previously, Store and Forward auto dial would always occur for 10-digit
and 1 + 10-digit calls, even if the PBX option was enabled. This would prevent 9 + 1 + 10-digit
calls on Centrex trunks and is now corrected.
- Extension Locking
- (3.40.15) When an extension is locked, the display is changed from Station
Locked to Extension Locked.
- Group Call Pickup
- (3.40.18) If an extension user presses INTERCOM and dials *# to answer
a call ringing a member of their pickup group, the call is answered and moves to the user's loop
key (if there is no available line key). In prior software versions, the call was answered but didn't
appear on the loop key. Ref: F12010900
- Group Listen
- (3.40.15) The operation of Group Listen is now identical at DSX
TDM keysets and DSX IP keysets.
- Home Automation Integration
- (3.40.22) On Super Display keysets, the temperature can now be
set directly from the Thermostat top level menu.
- IntraMail: Conversation Record
- If an extension with Email Integration enabled records a conversation to their mailbox, DSX
will deliver the email to their own email account. Prior release would deliver the email associated
with extension 301.
- IntraMail: Greeting
- Mailbox Greetings would occasionally not be shown as saved when recorded. Additionally, greetings
and would be deleted if extensions were swapped in System: Ports: Station Port Configuration
(9031 Extension Swap Utility). These issues are corrected.
- IntraMail: IntraMail CompactFlash Card Initialization
- Improvements have been made to ensure that System Administrator will be able to successfully
initialize an IntraMail Compact Flash from Database: Initialize. This correction does
not address the outstanding issue with System Administrator voice prompt updating
over USB connections.
- IntraMail: Message Notification
- (3.40.15) IntraMail will correctly follow the Message Notification
setup when routing after a notification is answered but not confirmed. This can happen, for example,
if an answering machine picks up a notification call and it is not confirmed. In prior releases,
Message Notification would continually retry the first destination (regardless of the programmed
setup). Ref: F111101001
- (3.40.18) Message Notification callouts operate correctly over SIP
trunks. Message Notification over SIP trunks was not supported in prior releases.
- Night Service
- After a software upgrade, the system could restart with the actual night mode status and the
Night key being out of sync. For example, the system could restart in the night mode but the
Night key would be off. This is corrected.
- Phone Manager
- (3.40.22) The System Speed Dial page will correctly display
Speed Dial Names that contain the ampersand (&) character. In prior versions, a name containing
an ampersand could be entered and saved but all characters from the ampersand to the end of the
name were omitted on page refresh. Ref: F120223001
- (3.40.32) When using the Phone Manager to update the name of an extension
with a stored PIN code, the display on the destination extension will update immediately. In prior
releases, the name would not update immediately.
- Selectable Display Messaging
- (3.40.24) When appending a Selectable Display Message with additional data from
a 3-line DSX keyset, the text entry mode will no longer time out after 2 seconds. Ref: F111129002
- SIP Trunking
- SIP processes could lock up if DSX sent a second Subscribe Refresh before receiving a response
from the initial Subscribe Refresh. This is corrected.
- SIP processes could lock up following one of many registration refreshes of DSX SIP Trunks. This
- In Software Version 3.40.11 only, the User Agent Friendly Scanner immunity was inadvertently
disabled for port 5060. This is now corrected and the immunity will work regardless of the SIP
- The mechanism used to deregister None mode SIP trunks that had lost communication with
their provider could cause a SIP lockup. This is corrected.
- (3.40.18) The system will automatically strip the leading + (or
+1) from incoming numbers on SIP trunks. This improves the Caller ID display and enables Caller
ID Callback on Level3 DID SIP trunks (such as nexVortex).
- (3.40.27) DSX correctly handles the condition when a re-invite is
received from the SIP provider on an outside call.
- (3.40.27) Ethernet setup is improved following a network disturbance.
- (3.40.27) The speech path will be correctly cut through when DSX
receives a 183 (in-band media available) message from the SIP provider. This can typically happen
if the provider immediately sends back an "out of service" or "unavailable"
- (3.40.31) An issue with certain types of "None" registration
mode SIP trunks (such as Broadvox) is corrected. Starting in software version 3.40.27 these types
of trunks were inoperable.
- (3.40.31) Error handling for SIP trunks with very poor response
has been improved:
- The "Ring" timeout has been increased from 16 to 64 seconds.
- A "Bye" received during the current call intended for the previous call will no
longer disconnect the current call.
- (3.40.32) SIP trunks can correctly
set up with a provider on the same LAN as the DSX (i.e., not using the DSX default gateway setting).
This may be useful in testing situations.
- Toll Restriction
- (3.40.22) If a user has Extension Locking enabled, and the system
resets, the extension's normal Toll Restriction settings will be reinstated when the system restarts.
In prior versions, a system reset could cause the restricted settings to be retained. Ref: F120123045
- Voice Mail
- A system with an analog voice mail installed (e.g., NVM-DFX) will correctly light a keyset's
Ring/Message lamp when the extension receives a new message. This capability was not available
in prior Version 3 releases.(Ref: F110707001)
- VoIP Extensions
- (3.40.24) An issue with the database handling for IP extensions
is corrected. In prior software versions, this issue could cause unique unwanted behaviors. Ref:
- (3.40.18) If an IP extension tries to register at an extension that
already has another extension registered, the new registration is rejected. In prior versions, this
condition would cause a registration refresh (and brief loss of service) for the registered extension.
- (3.40.18) If a third-party SIP extension loses its registration, but
the registration in the system is still active, the system will accept the reregistration attempt
if it comes from the same IP address as the initial registration.
- (3.40.30) A conflict with IP extension 401 is corrected which would
cause extension 401 to lock up and require a restart.
- Wakeup Call
- (3.40.24) Wakeup Call will operate correctly when the set time and
the wakeup time span a Daylight Saving Time adjustment.
- (3.40.27) The Save button operation is corrected for Webkit (Safari
and Chrome) browsers.
- (3.40.32) Wakeup Calls can be
set for Tomorrow if the current day is a single digit (1-9). This problem was introduced in 3.40.24.
- Wireless IP DECT (ML440)
- (3.40.22) The ML440 registration behavior is improved.
- (3.40.18) The ML440 handset will properly disconnect and return
to idle while on an Intercom call and the far end hangs up first.
- (3.40.15) If you place a call from an ML440 handset that has been
handed off to a secondary AP20 Access Point, you will no longer experience a one-way conversation.
- The ML440 handset Call Log will correctly dial a missed call that has been edited to include
the Line Group Access code (9 or 90-98). In Software Version 3.40.11, the call would only be partially
- Camp-On tones are now available in the ML440 handset. In Software Version 3.40.11, the ML440
handset did not provide Camp-On tones for waiting calls.
- An ML440 handset user will hear a single beep tone when they connect to a Door Box. In Software
Version 3.40.11, the user did not hear a beep.
- An ML440 handset user will hear a single beep tone when they press a Hotline key and connect
to their Hotline partner. In Software Version 3.40.11, the user did not hear a beep.
- If an ML440 handset user presses Hold to place a call on hold, their handset returns to idle
(just like a keyset). In Software Version 3.40.11, the handset did not return to idle.
- An ML440 handset user can press their Intercom Feature Key (if programmed) to answer an incoming
Intercom call. This did not occur in Software Version 3.40.11.