Can I restore a backup file from one UCM model on another different UCM model?

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.

Users can also convert UCM62xx/6510 backups to UCM63xx-compatible backups from GDMS. To do so, log in your GDMS account and navigate to GDMS Sidebar->UCMRC System->Storage, click on the Convert Config File button in the top right corner. Please note UCM62xx/6510 firmware must be 1.0.20.38 or higher before it can be used for UCM63xx conversion.

How many LDAP entries can the UCM6200/6510 have in its internal memory? How many contacts can the UCM6200/6510 return to the endpoint device per query?

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.

How to allow users to dial trunk provider feature codes?

Since the UCM series has built-in feature codes, users would need to work around this to avoid feature code conflicts and unintended behavior. For example, *72 on the UCM would be to set “Unconditional Call Forwarding”. However, for the trunk provider, *72 may be used to set “Do Not Disturb” instead. To get the trunk provider’s feature code behavior, users would need to manipulate outgoing numbers by doing the following:

- Navigate to WebUI->Extension/Trunk->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 will be used for.
- Strip: Remove the entire 88 by entering 2 into this field, making the number empty.
- Append: Enter *72 into this field. Since 88 was cleared out in the last step, *72 will be the full outgoing number.
- Click "Save" at the bottom then "Apply Changes" at the top.

In summary, dialing 88 (assuming it’s not an existing extension) will allow it to be processed for outbound routing through a specified trunk. The outbound route’s strip 88 and append *72 settings will allow the caller to invoke the trunk provider’s *72 feature code’s functionality (Do No Disturb).

My application with UCM6200/6510 AMI was working on UCM6200/6510 firmware version 1.0.9.26, but it doesn't work anymore after it's upgraded to 1.0.10.39. What should I do?

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.

Should I always enable all Syslog on the UCM in case troubleshooting is needed?

It is not recommended to open all levels of all syslog modules as it would significantly impact system performance and wear down system memory longevity. Required syslog for common issues:

- SIP calling and registration issues: All levels of pjsip/PBX
- Analog calling issues: All levels of chan_dahdi and FAX. Typically, an analog record trace would also be needed.
- Web page issues: CGI
- Zero Config issues: CGI and Zero Config

If your issue does not fall into these categories, please consult our Technical Support team.

The model update feature under web UI-> PBX-> Zero Config-> Model Update, How can I use it?

The Model Update page is for downloading and updating base model template forms (located on a separate remote server) to the local UCM system, allowing users to create model templates for device provisioning.

If the UCM environment restricts Internet access, users can manually upload the base template form instead. To get these, please contact Grandstream Technical Support.

The UCM series supports auto provisioning for Grandstream phones. Does it work for SIP end points other than Grandstream phones?

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.

What is the power output of the USB port on the UCM series?

UCM62xx: 970mA
UCM6510: 680mA
UCM61xx: 750mA

When I have two SIP trunks registered to the same provider, the incoming calls to both trunks are always received from the first trunk. Why?

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.

Which IP phones are supported by the UCM series?

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.

My custom P-values do not seem to be working for certain model templates. Why is this happening?

UCM Zero Config does not support p-value for certain models. Instead, it's supporting alias names for the provisioning parameters. When creating templates for these models, please refer to the model’s alias templates found in the configuration template package here: http://www.grandstream.com/support/tools.

For example, when configuring the GXV3370 template, to add a custom field to configure Account 1’s DNS mode, enter “account.1.network.dnsMode” for the Name field and "ARecord", "SRV", or "NaptrOrSrv" for the Value field.

Zero Config device templates that do not support P-values and requires using alias names: GXV3370, GSC3505, GSC3506, GSC3506V2, WP820.