Yes, starting from firmware 1.0.11.27, backup files are compatible among UCM61xx/UCM62xx models. Users can restore backup files from one UCM61xx/UCM62xx model to another. However, if you are restoring a backup file from a higher UCM model number to a lower one, you will be warned and prompted that the additional feature (e.g., FXO ports, extensions or conference rooms) is not available and the restore will not be allowed. This happens when the backup file is from a model that has more FXO ports, extensions or conference rooms configured than the maximum supported capability on the target UCM. For example, when the user is trying to restore a backup file from UCM6108 on UCM6104, if FXO port 5 to 8 are configured on UCM6108, the user will not be able to restore the backup file on UCM6104 because UCM6104 only supports FXO port 1 to 4. In this case, please manually delete the configuration of FXO port 5 to 8 and create backup on UCM6108 again to be restored on UCM6104.
UCM6200/6510 can store up to 20,000 LDAP contacts. When an endpoint device queries contacts from UCM LDAP server, the number of returned contacts will be limited by the number of contacts supported by the endpoint device.
The UCM series has built in feature codes, so there are times where UCM feature codes conflict with the trunk provider feature codes. The way around this would be to create an outbound pattern that essentially dials the providers feature code. For example, *72 on the UCM is used for "Unconditional Call Forwarding", but the trunk provider has their *72 set as "Do Not Disturb". If the user attempts to enable "Do Not Disturb" by dialing *72, they would be setting "Unconditional Call Forwarding" instead. Here's how to get around this:
- Navigate to Web UI -> PBX -> Basic/Call Routes -> Outbound Routes
- Click on "Create New Outbound Rule"
- Calling Rule Name is for reference purposes. In this example it would be set as "TrunkDND"
- Pattern: Configure a pattern that does not conflict with the current feature codes. E.g. 88
- Use Trunk: Select the trunk that the feature code is needed
- Strip: Before appending the trunk feature code, 88 must be striped from the dialed string. In this case 2 digits will be stripped
- Append: After stripping the 88 from the dialed string append the trunk provider's "Do Not Disturb" feature code. In this case it would be *72
- Click "Save" at the bottom then "Apply Changes" at the top.
For this example, if a user dials "88" it will be routed through the specified trunk, strip "88", append "*72" then send the manipulated string through the trunk to enable DND.
UCM6200/6510 firmware 1.0.9.26 is using Asterisk 1.8 which has AMI supported. UCM6200/6510 firmware 1.0.10.39 has upgraded to Asterisk 13 which is using AMI v2 (starting in Asterisk 12, the AMI is upgraded to AMI v2). According to Asterisk Wiki https://wiki.asterisk.org/wiki/display/AST/Upgrading+to+Asterisk+12, on AMI v2, many events were changed, and the semantics of channels and bridges were defined. In particular, how channels and bridges behave under transfer scenarios and situations involving multiple parties has changed significantly. Please see the AMI v2 Specification for more information:
https://wiki.asterisk.org/wiki/display/AST/AMI+v2+Specification
Since AMI is provided as-is, please consult with the software vendor to update your application using AMI v2. Or if you wish to downgrade UCM6200/6510 from 1.0.10.39 to 1.0.9.26, please contact our technical support for information and instructions.
It’s not recommended to open all levels to all the syslog modules. Too many syslog print might cause traffic and affect system performance.
In model update, the available model packages such as gs wave, surveillance and etc are located in a remote server. When there is an package update or new package available for a grandstream product, it will be uploaded in the remote server for user to download. UCM shows the available packages in model update web page. The "manual upload package option" under the same page with Model Update is for users who are using UCM in a private network that Internet access is restricted. They will not be able to get packages by downloading and installing from the remote server. Therefore, users that placed their UCM in a private network, please contact Grandstream customer support to get the model package and upload it manually through web interface.
The UCM series supports auto provisioning for Grandstream phones via SIP SUBSCRIBE, mDNS or DHCP Option 66. The UCM series auto provisioning doesn't support non-Grandstream phones at the moment.
UCM62xx: 970mA
UCM6510: 680mA
UCM61xx: 750mA
If this issue happens to your UCM, please check your inbound route configuration and make sure the DID pattern is unique for the inbound route assigned to each of those two trunks. Once the inbound route has unique DID pattern configured, the issue should be resolved. This is because the calls from both trunks have the same IP/port. In the cases when "To header/Request line" doesn't always have the extension that the UCM is registered to, we will need different inbound route DID pattern to differentiate them.
All current Grandstream IP Phones are certified to work with the UCM series and can also be configured via the 'Zero Configuration' feature. The UCM series is a SIP-based IP PBX which adheres to SIP standards and therefore should support SIP-based functionality on most SIP IP phones available today. The UCM series runs on a customized version of the Asterisk OS and users can also refer to Asterisk's list of supported IP Phones and Asterisk configuration notes for specific hard phones and ATAs for a more detailed list.