<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Best Method to Query Directory Information in Management</title>
    <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537133#M1755</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="portlet-msg-alert" style="color: #000000; font-family: Arial; font-size: 13.3333330154419px;"&gt;AXL isn't meant to be used as a real-time API for applications (or as a way to emulate directory services), so you may run into problems unless you break up queries to return multiple data subsets.&amp;nbsp; From the developer docs:&lt;/P&gt;&lt;P class="portlet-msg-alert" style="color: #000000; font-family: Arial; font-size: 13.3333330154419px;"&gt;&lt;/P&gt;&lt;P class="portlet-msg-alert" style="color: #000000; font-family: Arial; font-size: 13.3333330154419px;"&gt;&lt;EM&gt;AXL acts as a provisioning and configuration API, not as a real-time API.&lt;/EM&gt;&lt;/P&gt;&lt;P style="margin-bottom: 20px; color: #000000; font-family: Arial; font-size: 13.3333330154419px;"&gt;&lt;BR /&gt;&lt;EM&gt;The AXL interface provides Developers with two ways of accessing database obejcts:&amp;nbsp; Standard methods which provide backward compatibility between releases (e.g. Get User) and direct access through the ExecuteSQLQuery and ExecuteSQLUpdate methods, which do not provide backward compatibility.&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;The AXL service dynamically throttles 'write' requests (add/update/remove requests, and executeSqlUpdate) based on the current size of the UCM database transaction queue.&amp;nbsp; Note that the UCM database transaction queue can contain pending updates arising from recent administrative actions, bulk administration tasks, other AXL applications, etc.&amp;nbsp; If the database transaction queue is too large, AXL may reject new write requests with a "503: Service Unavailable" error message.&amp;nbsp; In such cases applications may re-try rejected requests, however re-tries should be attempted after a reasonable delay (e.g. several seconds)&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Read requests are also dynamically throttled based on the size of the data set to be returned.&amp;nbsp; Large queries issued using the List &amp;lt;object&amp;gt; and ExecuteSQLQuery methods that result in a data set greater than 8 MB&amp;nbsp; will return "Query request too large. Total rows matched: &amp;lt;Matched Rows&amp;gt;. Suggested row fetch: less than &amp;lt;Number of Rows&amp;gt;."&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Cisco recommends developers who use the ExecuteSQLQuery method follow these guidelines:&lt;/EM&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Applications should break up all SQL queries so that the data returned is always less than 8 MB&lt;/LI&gt;&lt;LI&gt;Use the Unified CM Data Dictionary to help determine the maximum allowable size of any field in the database&lt;/LI&gt;&lt;LI&gt;ASCII characters are stored as 1-byte&lt;/LI&gt;&lt;LI&gt;i18n characters (UTF-8) are stored as 3-bytes&lt;/LI&gt;&lt;LI&gt;DB has a mix of ASCII and UTF-8 characters&lt;/LI&gt;&lt;LI&gt;While UCM is processing a large query, concurrent queries should not result in data sets larger than 2 MB&lt;/LI&gt;&lt;LI&gt;Applications should wait to receive a response before issuing subsequent queries&lt;/LI&gt;&lt;LI&gt;Applications should not submit duplicate queries.&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 28 May 2015 14:26:04 GMT</pubDate>
    <dc:creator>npetrele</dc:creator>
    <dc:date>2015-05-28T14:26:04Z</dc:date>
    <item>
      <title>Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537123#M1745</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="j-508-label" style="font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit;"&gt;Hello,&lt;/P&gt;&lt;P class="j-508-label" style="font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit;"&gt;&lt;/P&gt;&lt;P class="j-508-label" style="font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit;"&gt;What is the best method to get a list of all phone extensions and extension descriptions from CUCM via AXL? It is important to query extensions for users who even extension mobility configured regardless of their login status. I know the executeSQLQuery API is the an option. What is the best query to use?&lt;/P&gt;&lt;P class="j-508-label" style="font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit;"&gt;&lt;/P&gt;&lt;P class="j-508-label" style="font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit;"&gt;Also from CUCM user configuration standpoint, what type of user/user group should be created to allow such privileges when consuming the API?&lt;/P&gt;&lt;P class="j-508-label" style="font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit;"&gt;&lt;/P&gt;&lt;P class="j-508-label" style="font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit;"&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 May 2015 15:17:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537123#M1745</guid>
      <dc:creator>sharpgate</dc:creator>
      <dc:date>2015-05-20T15:17:05Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537124#M1746</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you be a little more specific about what you're looking for?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps listUser would be the AXL API you want?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 May 2015 16:03:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537124#M1746</guid>
      <dc:creator>npetrele</dc:creator>
      <dc:date>2015-05-20T16:03:13Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537125#M1747</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sure, to be more specific what I need is the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Extension No, Extension Description, CSS Description. This can help build some sort of corporate directory if you will.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it is clearer now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 May 2015 00:30:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537125#M1747</guid>
      <dc:creator>sharpgate</dc:creator>
      <dc:date>2015-05-21T00:30:33Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537126#M1748</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you want a corporate directory, the best approach is to sync call manager with an LDAP directory service or Active Directory.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 May 2015 00:53:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537126#M1748</guid>
      <dc:creator>npetrele</dc:creator>
      <dc:date>2015-05-21T00:53:44Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537127#M1749</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes you are right, but this particular CUCM is not configured for that since LDAP and AD is not present. I simply want to use AXL API to pull all configured extensions and user descriptions. I presume I will need to query Device and dnorPattern tables. I only need help the correct query.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 May 2015 01:01:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537127#M1749</guid>
      <dc:creator>sharpgate</dc:creator>
      <dc:date>2015-05-21T01:01:45Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537128#M1750</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You use getPhone (AXL API) to get the information as Extension (directory number), CSS, description of device/line....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thuy Doan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 May 2015 00:56:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537128#M1750</guid>
      <dc:creator>TDoan</dc:creator>
      <dc:date>2015-05-25T00:56:51Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537129#M1751</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks. So what is the syntax to be used&amp;nbsp;to query all phone extensions?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 May 2015 07:26:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537129#M1751</guid>
      <dc:creator>sharpgate</dc:creator>
      <dc:date>2015-05-25T07:26:52Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537130#M1752</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have already got a list of device then you can use getPhone to get information for every device&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a sample getPhone (AXL API). I do not know what CUCM version you are using, my example is CUCM version 10.5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;lt;soapenv:Envelope xmlns:soapenv="&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://schemas.xmlsoap.org/soap/envelope/" rel="nofollow" target="_blank"&gt;http://schemas.xmlsoap.org/soap/envelope/&lt;/A&gt;&lt;SPAN&gt;" xmlns:ns="&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/AXL/API/10.5" rel="nofollow" target="_blank"&gt;http://www.cisco.com/AXL/API/10.5&lt;/A&gt;&lt;SPAN&gt;"&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;soapenv:Header/&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;soapenv:Body&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;ns:getPhone sequence="1"&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;name&amp;gt;&lt;STRONG&gt;Your Device Name&lt;/STRONG&gt;&amp;lt;/name&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/ns:getPhone&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;/soapenv:Body&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/soapenv:Envelope&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It will return name, product, description, callingSearchSpaveName (CSS), directory number (extension).....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can use listPhone (AXL API) to get all devices in CUCM then you use getPhone (AXL API)&amp;nbsp; to get information for every&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this will help you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thuy Doan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 May 2015 07:47:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537130#M1752</guid>
      <dc:creator>TDoan</dc:creator>
      <dc:date>2015-05-25T07:47:34Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537131#M1753</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you don't want to use the API and just need a SQL query to obtain the information you need. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;here is a sample query, tested on CUCM 10.5. Should work fine on prior recent versions. but can't confirm.&lt;/P&gt;&lt;PRE __default_attr="sql" __jive_macro_name="code" class="jive_text_macro jive_macro_code _jivemacro_uid_14327385777048856" jivemacro_uid="_14327385777048856" modifiedtitle="true"&gt;
&lt;P&gt;run sql select device.name AS DeivceName, numplan.dnorpattern AS Extension, numplan.description AS&lt;/P&gt;
&lt;P&gt;LineDescription, callingsearchspace.name AS LineCSS &lt;/P&gt;
&lt;P&gt;from device, numplan, devicenumplanmap, callingsearchspace&lt;/P&gt;
&lt;P&gt;where device.pkid = devicenumplanmap.fkdevice and numplan.pkid = devicenumplanmap.fknumplan&lt;/P&gt;
&lt;P&gt;and device.name like '%SEP%' and numplanindex = 1&lt;/P&gt;
&lt;P&gt;and numplan.fkcallingsearchspace_sharedlineappear = callingsearchspace.pkid&lt;/P&gt;
&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This query only grabs the primary line on each device, remove the numplanindex condition and it will also grab secondary lines, also it's only restricted to device names containing SEP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 May 2015 15:03:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537131#M1753</guid>
      <dc:creator>Mamdouh Elgamal</dc:creator>
      <dc:date>2015-05-27T15:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537132#M1754</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Mando &lt;IMG src="https://community.cisco.com/legacyfs/online/emoticons/wink.png" /&gt;&lt;/P&gt;&lt;P&gt;This is exactly what I was looking for. I do prefer using SQLQuery.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, does any one happen to have helpful information about data throttling issues. In other words, if the query result is like 3000 devices what the implications will be?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 May 2015 10:08:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537132#M1754</guid>
      <dc:creator>sharpgate</dc:creator>
      <dc:date>2015-05-28T10:08:21Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537133#M1755</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="portlet-msg-alert" style="color: #000000; font-family: Arial; font-size: 13.3333330154419px;"&gt;AXL isn't meant to be used as a real-time API for applications (or as a way to emulate directory services), so you may run into problems unless you break up queries to return multiple data subsets.&amp;nbsp; From the developer docs:&lt;/P&gt;&lt;P class="portlet-msg-alert" style="color: #000000; font-family: Arial; font-size: 13.3333330154419px;"&gt;&lt;/P&gt;&lt;P class="portlet-msg-alert" style="color: #000000; font-family: Arial; font-size: 13.3333330154419px;"&gt;&lt;EM&gt;AXL acts as a provisioning and configuration API, not as a real-time API.&lt;/EM&gt;&lt;/P&gt;&lt;P style="margin-bottom: 20px; color: #000000; font-family: Arial; font-size: 13.3333330154419px;"&gt;&lt;BR /&gt;&lt;EM&gt;The AXL interface provides Developers with two ways of accessing database obejcts:&amp;nbsp; Standard methods which provide backward compatibility between releases (e.g. Get User) and direct access through the ExecuteSQLQuery and ExecuteSQLUpdate methods, which do not provide backward compatibility.&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;The AXL service dynamically throttles 'write' requests (add/update/remove requests, and executeSqlUpdate) based on the current size of the UCM database transaction queue.&amp;nbsp; Note that the UCM database transaction queue can contain pending updates arising from recent administrative actions, bulk administration tasks, other AXL applications, etc.&amp;nbsp; If the database transaction queue is too large, AXL may reject new write requests with a "503: Service Unavailable" error message.&amp;nbsp; In such cases applications may re-try rejected requests, however re-tries should be attempted after a reasonable delay (e.g. several seconds)&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Read requests are also dynamically throttled based on the size of the data set to be returned.&amp;nbsp; Large queries issued using the List &amp;lt;object&amp;gt; and ExecuteSQLQuery methods that result in a data set greater than 8 MB&amp;nbsp; will return "Query request too large. Total rows matched: &amp;lt;Matched Rows&amp;gt;. Suggested row fetch: less than &amp;lt;Number of Rows&amp;gt;."&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Cisco recommends developers who use the ExecuteSQLQuery method follow these guidelines:&lt;/EM&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Applications should break up all SQL queries so that the data returned is always less than 8 MB&lt;/LI&gt;&lt;LI&gt;Use the Unified CM Data Dictionary to help determine the maximum allowable size of any field in the database&lt;/LI&gt;&lt;LI&gt;ASCII characters are stored as 1-byte&lt;/LI&gt;&lt;LI&gt;i18n characters (UTF-8) are stored as 3-bytes&lt;/LI&gt;&lt;LI&gt;DB has a mix of ASCII and UTF-8 characters&lt;/LI&gt;&lt;LI&gt;While UCM is processing a large query, concurrent queries should not result in data sets larger than 2 MB&lt;/LI&gt;&lt;LI&gt;Applications should wait to receive a response before issuing subsequent queries&lt;/LI&gt;&lt;LI&gt;Applications should not submit duplicate queries.&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 May 2015 14:26:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537133#M1755</guid>
      <dc:creator>npetrele</dc:creator>
      <dc:date>2015-05-28T14:26:04Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537134#M1756</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would not use the API (i.e ExecuteSQLQueryReq), for this type of query&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just SSH into CUCM and run this query then copy the result or you can log the session through your ssh client.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 May 2015 15:04:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537134#M1756</guid>
      <dc:creator>Mamdouh Elgamal</dc:creator>
      <dc:date>2015-05-28T15:04:36Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537135#M1757</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes I usually do that but this is for manual method to achieve that. However, the target from what I am looking for is to have an updated list of the extensions and their descriptions from within my application on a regular basis. &lt;/P&gt;&lt;P&gt;SSH won't fit as a good interface with CUCM database to automate such a task.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 May 2015 17:36:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/3537135#M1757</guid>
      <dc:creator>sharpgate</dc:creator>
      <dc:date>2015-05-28T17:36:17Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/4800274#M4045</link>
      <description>&lt;P&gt;Hello I am new to this CUCM.&amp;nbsp; How to I extract the phone extensions from the system on a daily basis?&amp;nbsp; Is there any code like Powershell or SQL?&amp;nbsp; I am a TSQL guy but also do powershell.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thank you!!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 18:14:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/4800274#M4045</guid>
      <dc:creator>AndrewGeorgiou</dc:creator>
      <dc:date>2023-03-23T18:14:49Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/4800453#M4046</link>
      <description>&lt;P&gt;Hello&amp;nbsp;AndrewGeorgiou,&lt;/P&gt;&lt;P&gt;You can use&amp;nbsp;&lt;SPAN&gt;AXL API to get a list of extensions from CUCM and to get a response from CUCM you need to use https or SOAP to post it to CUCM.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;To get a list of extensions you need to do the following steps&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1) Get listPhone (AXL API)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; Ex:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;lt;ns:listPhone sequence="1"&amp;gt;&lt;BR /&gt;&amp;lt;searchCriteria&amp;gt;&lt;BR /&gt;&amp;lt;name&amp;gt;%&amp;lt;/name&amp;gt;&lt;BR /&gt;&amp;lt;/searchCriteria&amp;gt;&lt;BR /&gt;&amp;lt;returnedTags&amp;gt;&amp;lt;uuid/&amp;gt;&amp;lt;name/&amp;gt;&amp;lt;description/&amp;gt;&amp;lt;product/&amp;gt;&amp;lt;model/&amp;gt;&amp;lt;class/&amp;gt;&amp;lt;protocol/&amp;gt;&amp;lt;callingSearchSpa ceName/&amp;gt;&amp;lt;devicePoolName/&amp;gt;&amp;lt;securityProfileName/&amp;gt;&amp;lt;/returnedTags&amp;gt;&lt;BR /&gt;&amp;lt;/ns:listPhone&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2) getPhone (AXL API)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Ex:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;lt;ns:getPhone sequence="1"&amp;gt;&lt;BR /&gt;&amp;lt;name&amp;gt;CIPC_101&amp;lt;/name&amp;gt;&amp;nbsp; &amp;nbsp;---- (Or you can use &amp;lt;name&amp;gt;%&amp;lt;/name&amp;gt; or &amp;lt;description&amp;gt;%&amp;lt;/description&amp;gt;. Name and Description you get it from listPhone)&lt;BR /&gt;&amp;lt;returnedTags&amp;gt;&amp;lt;name/&amp;gt;&amp;lt;description/&amp;gt;&amp;lt;product/&amp;gt;&amp;lt;model/&amp;gt;&amp;lt;class/&amp;gt;&amp;lt;protocol/&amp;gt;&amp;lt;callingSearchSpaceName/&amp;gt;&amp;lt;devicePoolName/&amp;gt;&amp;lt;securityProfileName/&amp;gt;&amp;lt;/returnedTags&amp;gt;&lt;BR /&gt;&amp;lt;/ns:getPhone&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You will get a response from CUCM and from there you will find "pattern" (Ex: &amp;lt;pattern&amp;gt;1002&amp;lt;/pattern&amp;gt;) 1002 is an extension.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Hope this will help you.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;TDoan&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Mar 2023 01:10:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/4800453#M4046</guid>
      <dc:creator>TDoan</dc:creator>
      <dc:date>2023-03-24T01:10:00Z</dc:date>
    </item>
    <item>
      <title>Re: Best Method to Query Directory Information</title>
      <link>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/4800898#M4047</link>
      <description>&lt;P&gt;Thank you TDoan.&amp;nbsp; I will give it a try.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Mar 2023 14:25:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/best-method-to-query-directory-information/m-p/4800898#M4047</guid>
      <dc:creator>AndrewGeorgiou</dc:creator>
      <dc:date>2023-03-24T14:25:49Z</dc:date>
    </item>
  </channel>
</rss>

