Grandstream UCM6104 IP PBX Firmware 1.0.14.21 Beta Download

Posted at December 19, 2024 by PCI-DB Team

Grandstream UCM6104 IP PBX Firmware 1.0.14.21 Beta Description

IMPORTANT UPGRADING NOTE

- Backup your data including configuration before firmware upgrade is recommended.
- For UCM62xx on 1.0.13.14, please upgrade to 1.0.14.21 directly.
- For UCM62xx on firmware lower than 1.0.13.14, please follow the upgrading instructions in UCM62xx release note to upgrade to 1.0.13.14 first, then upgrade to 1.0.14.21.

ENHANCEMENT

- Improved web UI with new graphical style and added support for displaying real-time system status for call queue module
- Added lightweight call center support [BLACKLIST/WHITELIST IN IVR]
- Added SIP Presence support [SIP PRESENCE]
- Added ability to restore blind transfer call to transferer [RESTORING BLIND TRANSFER CALL TO TRANSFERER]
- Added custom privilege for wakeup service [CUSTOM PRIVILEGE – WAKEUP SERVICE]
- Added ability to periodically clean files from external storage [CLEANING FILES FROM EXTERNAL STORAGE PERIODICALLY]
- Added support for sending DOD number of the call forwarder or Ring Simultaneously extension [SENDING DOD NUMBER OF THE CALL FORWARDER OR RING SIMULTANEOUSLY EXTENSION]
- Added support for call forward whitelist [CALL FORWARD WHITELIST]
- Added support for call queue auto-fill [CALL QUEUE AUTO-FILL]
- Added Fail2Ban for web login attack defense [FAIL2BAN LOGIN ATTACK DEFENSE]
- Added limitation for maximum number of call queue static agents [MAXIMUM NUMBER OF STATIC AGENTS IN CALL QUEUE]
- Added IPv6 support for T.38
- Added DAHDI settings [DAHDI SETTINGS]

BUG FIX

- Fixed Basic Call: UCM appears crash after attended transfer and the remote party hangs up
- Fixed Basic Call: One-way audio after call hold and resume in some cases
- Fixed Basic Call: If auto record is enabled, the codec negotiation isn't right when do preview
- Fixed Basic Call: Even though UCM receives 200OK with video attribute sendrecv, it will respond 200OK with recvonly that is the same as 183 carried
- Fixed Basic Call: UCM fails to negotiate the same codec if auto record is enabled
- Fixed Basic Call: Asterisk appears deadlock when caller and callee hold call at the same time
- Fixed Eventlist: UCM sends NOTIFY with uncompressed message body to subscriber after reboot
- Fixed Delay in audio when using paging/intercom group
- Fixed UCM doesn't respond SIP OPTIONS from Asterisk under some special cases
- Fixed Call flow CQ->IVR->Extension doesn't prompt for voicemail after ring timeout
- Fixed Trunk: The diversion header carries wrong caller ID number in some case
- Fixed when the phone uses call transfer, UCM's re-invite does not carry SDP message which causes the call has no audio
- Fixed No Referred-by header in the INVITE during call transfer
- Fixed UCM Drops the call with 488 Error when receiving an UPDATE in some scenarios
- Fixed Feature Code: Sometimes extension hears record prompt twice when using feature code 45 or 44
- Fixed Auto Record: Only six files are downloaded when batch downloading recording files
- Fixed Seamless Transfer: UCM only sends call to one phone when using 44 feature code to seamlessly transfer the call
- Fixed Seamless Transfer: Sometimes UCM plays record prompt even though recording prompt is not enabled
- Fixed Seamless Transfer: Pressing 44 twice to transfer call to C, C answers the first call with no audio
- Fixed Follow Me: The voice prompt language that Follow me members hear is the configured language from the caller
- Fixed Codec: Failed to negotiate the same codec when auto record is enabled
- Fixed Conference: The call should not be established when the conference member press 2 to invite normal extension for conference room
- Fixed Conference CEI: The status should be 'disconnected' after the CEI user leaves the conference room
- Fixed Conference CEI: UCM doesn't send NOTIFY message when subscriber is invited by extension or Web UI conference
- Fixed Call Queue: The agents can't be deleted after deleting call queue and creating a new queue
- Fixed Call Queue: After deleting Custom Prompt, the call should use the default prompt
- Fixed Call Queue: In linear ringing Strategy, the next seat is not immediately ringing after rejecting the call
- Fixed Call Queue: Timeout time into the destination is abnormal
- Fixed Call Queue: Call terminates after being transferred from caller to EXT's VM
- Fixed Call Queue: After calling into call queue, if MOH file is mp3 format, sometimes the MOH heard by the caller is not clear
- Fixed Call Queue: Dynamic agent which is the remote extension will disappear after applying changes
- Fixed Call Queue: Call should fail when "Leave When Empty" is set to yes
- Fixed Call Queue: Enabling destination for linear ringing doesn't take effect
- Fixed Call Queue: FXS extension cannot dial 83 to use Agent Pause feature code and it hears busy tone after entering 8
- Fixed Music on hold: the compressed file's custom MOH class music file cannot play unless MOH class data is applied
- Fixed Music on hold: The new sound cannot take effect
- Fixed SIP Settings: During call hold, UCM prefers to execute RTP timeout
- Fixed CRM: UCM will not send call messages to CRM after upgrade from v1.0.11.27
- Fixed CTI: UCM sends incorrect information when CRM system contacts has Chinese characters
- Fixed CTI: The CTIcgi address sent from UCM is null after UCM restarts and successfully obtains IP address
- Fixed PMS: Room status is changed to checkout after dialing 26 and pressing 1
- Fixed PMS: Site field empty in POST request sent to Hmobile PMS server
- Fixed PMS: Feature code 23 will be abnormal after creating or deleting PMS room
- Fixed PMS: UCM cannot delete wakeup service when checking in on a room that has been checked in
- Fixed PMS: Web page displays abnormally after deleting extension name using Mitel interface
- Fixed Wakeup Service: There is no prompt extension has set transfer
- Fixed CDR: It would display digital trunk E&M call when filtered by PSTN call in CDR Statistics
- Fixed CDR: After dialing into IVR, if the dialing number is not in the whitelist, CDR displays incorrectly
- Fixed CDR: When the number of conference schedule members is more than 3, CDR record should not be generated
- Fixed CDR: CDR displays incorrectly after dialing non-whitelist number in IVR
- Fixed Email Setting: Unable to receive Email when the Gmail server port is 465
- Fixed Email Setting: Mail log error when a number of Email addresses are used in send mail in CDR
- Fixed Email Setting: The tooltip is wrong about receiver option
- Fixed Email Setting: UCM's data partition is full after UCM sends too many Emails
- Fixed Warning: UCM produces multiple warnings after SIP Registration fails
- Fixed Warning: The alert log is unnecessary when entering voicemail
- Fixed Warning: The format of the warning Email shows abnormal when Email template sending format is plain text
- Fixed Warning: Two Emails are received after recovering configuration
- Fixed Warning: There should not have warning produced if ringing is rejected or timed out
- Fixed Warning: SIP Registraiton failure has not warning Email sent if the cycle is set to 0
- Fixed Warning: Administrator receives Email if password is changed for super administrator when Email send Mode is Periodic
- Fixed Warning: SIP trunking registration failure alert log should include the detailed registration information
- Fixed Warning: Modifying memory usage alert causes UCM not generate system restore warning in time
- Fixed Warning: UCM should generate fail2ban blocking alert log using IPv6 address
- Fixed Operation Log: If attempting logging in using user info that's not existed in UCM, operation log should show login record
- Fixed Operation Log: Some operations are displayed incompletely when deleting files which have file name including '&' in USB/SD Cleaner
- Fixed Email Setting: When there are multiple receivers, if clicking search, the result is abnormal
- Fixed Email Setting: The mail log is wrong upon one-key dial to voicemail group
- Fixed Email not working with office365 after upgrading from 1.0.12.X to 1.0.13.X
- Fixed CGI Crash randomly when UCM sends Email while updating FXS extension
- Fixed UCM behaves abnormal after UCM sends alert Email frequently
- Fixed Contacts with apostrophe cannot be imported into LDAP phonebook
- Fixed UCM does not accept dash character to be configured on the LDAP client common name (CN) and domain component (DC)
- Fixed selecting LDAP numbers under DOD is not working
- Fixed LDAP Server: Telephone book synchronization exception
- Fixed Zeroconfig: No information on the device cannot be modified
- Fixed Zeroconfig: Phonebook downloading interval in global policy disappears after saving the change
- Fixed Web: There are only up to 6 DNS servers displayed on the page
- Fixed Cleaner: When the used storage hasn't reached File Clean Threshold, backup file should not be cleaned
- Fixed Setup guide allows setting with IPv4 and it shouldn't allow entering IPv6 related item in web page
- Fixed Syslog: Clear log function does not come into effect
- Fixed IPV6: dhcpd6.lease file will not delete and its size keeps going up
- Fixed Time Settings: UCM works abnormally when Self-defined Time Zone has special characters included
- Fixed Fail2ban: Whitelist including [::]/16 cannot work

KNOWN ISSUES

- When there are multiple IVR entries and one of them is the inbound route destination for a trunk, if this IVR is deleted, the inbound route that uses this IVR as destination will disappear from web UI. To recover this, please delete all IVRs. Please note this issue also exists when other destination (besides IVR) is used.

About VoIP System Updates:

Firmware updates for VoIP Systems are very complex and usually contain many bug fixes, security improvements and compatibility enhancements, because the base system must be able to connect to webcams, video conference devices and the like.

Upgrading your VoIP System firmware should be done as often as possible to keep your device up to date with new security standards, and improve the native plug and play capabilities of your device.

Although beta firmware are usually full of new and exciting features, updating to them should only be done after thoroughly reading the changelog and making sure that you still retain phone functionality. Remember to check if you can revert to a more stable version as well, in case the new update is not what you were expecting.

If you intend to apply this update, please make sure that the package is compatible with your VoIP System, hit the download button, follow the installation instructions and enjoy. Check out our website as often as possible in order to keep your device “Updated one minute ago.”

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related Grandstream Drivers