<?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>Call ControlのトピックRe: API for Consult Database for Call Control in CUCM</title>
    <link>https://community.cisco.com/t5/call-control/api-for-consult-database-for-call-control-in-cucm/m-p/3880425#M2762</link>
    <description>&lt;P&gt;Let me see if I understand the problem:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;* You need to differentiate between mobile calls and land line calls, presumably so you can route them via different service providers/trunks, block them, bill them differently, etc.&amp;nbsp; Previously you used Route Patterns for this.&lt;/P&gt;
&lt;P&gt;* Prior to Aug 3, outbound calls to mobiles are prefixed with 044 or 045, and outbound calls to land lines were prefixed with 01.&amp;nbsp; This makes them easy to differentiate.&lt;/P&gt;
&lt;P&gt;* After Aug 3, outbound calls to mobile and land lines will both have the same basic format, i.e. 10 digits starting with the area code.&amp;nbsp; This makes them difficult to differentiate.&lt;/P&gt;
&lt;P&gt;* Some kind of government provided database will be made available that identifies all mobile phone numbers/ranges&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I'm mostly right, some thoughts/questions:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;* How many entries are in this database?&amp;nbsp; If the number is in the hundreds to a few thousands, it may be possible to just create/maintain a bunch of translation/route patterns - which could be automated using the &lt;A href="https://developer.cisco.com/site/axl/" target="_blank" rel="noopener"&gt;CUCM AXL SOAP API&lt;/A&gt;.&amp;nbsp; My understanding is that the max number of patterns is constrained by the CUCM performance profile based on the underlying server hardware, and that you can use the CUCM sizing tools to validate a particular configuration (total devices, lines, patterns, etc.)&lt;/P&gt;
&lt;P&gt;* If the number is too large to use patterns, then you need to consider coding an application that will examine every outbound call, do a dynamic database lookup to check if its mobile, then route the call to the appropriate destination.&amp;nbsp; There are two APIs that might be suitable here: &lt;A href="https://developer.cisco.com/site/curri/" target="_blank" rel="noopener"&gt;CURRI&lt;/A&gt; and &lt;A href="https://developer.cisco.com/site/tapi/" target="_blank" rel="noopener"&gt;TAPI&lt;/A&gt; / &lt;A href="https://developer.cisco.com/site/jtapi/" target="_blank" rel="noopener"&gt;JTAPI&lt;/A&gt; (CURRI is probably the more approachable one.)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jun 2019 02:23:07 GMT</pubDate>
    <dc:creator>dstaudt</dc:creator>
    <dc:date>2019-06-27T02:23:07Z</dc:date>
    <item>
      <title>API for Consult Database for Call Control in CUCM</title>
      <link>https://community.cisco.com/t5/call-control/api-for-consult-database-for-call-control-in-cucm/m-p/3878640#M2757</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I need integrate a API for consult database for call control, in Mexico with the new dial plan for calls to mobile and national calls, it´s the same pattern. The route-pattern example is 9.[2-9]XXXXXXXXX and the patter dial for this two destiny it´s equal.&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mobile: 5567431287&lt;/P&gt;&lt;P&gt;National call: 5599158320&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;T&lt;SPAN class="tlid-translation translation"&gt;&lt;SPAN class=""&gt;he only way to differentiate the call is with ranges at the database level provided by the IFETEL (Federal Telecommunications Regulations in Mexico).&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="tlid-translation translation"&gt;&lt;SPAN class=""&gt;Actually the route-pattern for call mobile and national it´s the follow with this pattern it´s easy differentiate the calls.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="tlid-translation translation"&gt;&lt;SPAN class=""&gt;Mobile: 9.044XXXXXXXXXX &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="tlid-translation translation"&gt;&lt;SPAN class=""&gt;National: 01XXXXXXXXXX&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="tlid-translation translation"&gt;&lt;SPAN class=""&gt;I hope can you help me&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="tlid-translation translation"&gt;&lt;SPAN class=""&gt;Regards&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jun 2019 16:05:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/api-for-consult-database-for-call-control-in-cucm/m-p/3878640#M2757</guid>
      <dc:creator>omar.velez</dc:creator>
      <dc:date>2019-06-24T16:05:37Z</dc:date>
    </item>
    <item>
      <title>Re: API for Consult Database for Call Control in CUCM</title>
      <link>https://community.cisco.com/t5/call-control/api-for-consult-database-for-call-control-in-cucm/m-p/3880425#M2762</link>
      <description>&lt;P&gt;Let me see if I understand the problem:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;* You need to differentiate between mobile calls and land line calls, presumably so you can route them via different service providers/trunks, block them, bill them differently, etc.&amp;nbsp; Previously you used Route Patterns for this.&lt;/P&gt;
&lt;P&gt;* Prior to Aug 3, outbound calls to mobiles are prefixed with 044 or 045, and outbound calls to land lines were prefixed with 01.&amp;nbsp; This makes them easy to differentiate.&lt;/P&gt;
&lt;P&gt;* After Aug 3, outbound calls to mobile and land lines will both have the same basic format, i.e. 10 digits starting with the area code.&amp;nbsp; This makes them difficult to differentiate.&lt;/P&gt;
&lt;P&gt;* Some kind of government provided database will be made available that identifies all mobile phone numbers/ranges&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I'm mostly right, some thoughts/questions:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;* How many entries are in this database?&amp;nbsp; If the number is in the hundreds to a few thousands, it may be possible to just create/maintain a bunch of translation/route patterns - which could be automated using the &lt;A href="https://developer.cisco.com/site/axl/" target="_blank" rel="noopener"&gt;CUCM AXL SOAP API&lt;/A&gt;.&amp;nbsp; My understanding is that the max number of patterns is constrained by the CUCM performance profile based on the underlying server hardware, and that you can use the CUCM sizing tools to validate a particular configuration (total devices, lines, patterns, etc.)&lt;/P&gt;
&lt;P&gt;* If the number is too large to use patterns, then you need to consider coding an application that will examine every outbound call, do a dynamic database lookup to check if its mobile, then route the call to the appropriate destination.&amp;nbsp; There are two APIs that might be suitable here: &lt;A href="https://developer.cisco.com/site/curri/" target="_blank" rel="noopener"&gt;CURRI&lt;/A&gt; and &lt;A href="https://developer.cisco.com/site/tapi/" target="_blank" rel="noopener"&gt;TAPI&lt;/A&gt; / &lt;A href="https://developer.cisco.com/site/jtapi/" target="_blank" rel="noopener"&gt;JTAPI&lt;/A&gt; (CURRI is probably the more approachable one.)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2019 02:23:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/api-for-consult-database-for-call-control-in-cucm/m-p/3880425#M2762</guid>
      <dc:creator>dstaudt</dc:creator>
      <dc:date>2019-06-27T02:23:07Z</dc:date>
    </item>
  </channel>
</rss>

