15.10 Import and Export of Global Dial Plan Catalogs

This topic describes the import and export of global dial plan catalogs.

URIs and numbers can be imported from third-party systems.

  • Each import is stored in an imported global dial plan catalog.
  • The Cisco Unified Communications Manager administrator assigns a route string to each imported global dial plan catalog.
  • Information from imported global dial plan catalogs is treated as if it were learned via ILS global dial plan replication.
  • Imported global dial plan catalogs are also propagated to other clusters on the next pull.

Local URIs and numbers can be exported:

  • They can be exported, then imported on third-party systems that support the import of global dial plan catalogs.
  • ILS-learned and imported information cannot be exported.
  • To export information from all clusters, export local URIs and numbers at each cluster.

URIs can be manually imported from third-party systems such as Cisco TelePresence Video Communication Server (VCS) and Microsoft OCS or Microsoft Lync server.

Each import is stored in an imported directory URI catalog. The Cisco Unified Communications Manager administrator assigns one route string to each imported directory URI catalog. Imported URIs and their associated route strings are treated as if they were learned via ILS URI syncing. They are also propagated to other clusters on the next pull.

Imported directory URI catalogs can be updated by uploading a new file. In this case, the changes are propagated at the next pull.

Locally configured URIs can be exported and then imported on third-party systems that support URI import. ILS-learned URIs and imported URIs are not included in the URI export function. Therefore, to export all URIs of a multicluster deployment, you must export the local URIs at each cluster.

Advertisements