<?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: CDR on-net ,off-net calls details in Management</title>
    <link>https://community.cisco.com/t5/management/cdr-on-net-off-net-calls-details/m-p/3548597#M1872</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The designation of whether a call is off-net vs. on-net is somewhat arbitrary, and in general depends on which gateway/trunk a call ingresses/egresses from.&amp;nbsp; The CUCM admin can designate a particular 'route pattern' as off-net or on-net; route patterns in turn are associated with a particular gateway, trunk, or route-list (which in turn can can point to a group of gateways/trunks.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, a comprehensive approach is typically something like:&lt;/P&gt;&lt;P&gt;- Determin the CDR origination and/or destination device name of the call&lt;/P&gt;&lt;P&gt;- Get a list of all the gateway, trunk device names and see if the orig/dest is a gateway or trunk&lt;/P&gt;&lt;P&gt;- If so, determine which route pattern is associated to the gateway/trunk&lt;/P&gt;&lt;P&gt;- Determine whether the route pattern is designated as off-net or on-net&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will require reading/caching some data via AXL, i.e. device names and types, route pattern-&amp;gt;device associations, route pattern properties, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A simpler approach could just have the app user enter/identify the unique orig/dest device names as off-net vs. on-net.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Mar 2016 18:54:03 GMT</pubDate>
    <dc:creator>dstaudt</dc:creator>
    <dc:date>2016-03-21T18:54:03Z</dc:date>
    <item>
      <title>CDR on-net ,off-net calls details</title>
      <link>https://community.cisco.com/t5/management/cdr-on-net-off-net-calls-details/m-p/3548596#M1871</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi I am working On CDR and CMR.I have to know how many on-net and off-net calls are made from cdr ,cmr logs.Please someone help me to know this thing.Any help will be appreciated &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 Mar 2016 07:41:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/cdr-on-net-off-net-calls-details/m-p/3548596#M1871</guid>
      <dc:creator>nareshhkn1</dc:creator>
      <dc:date>2016-03-05T07:41:40Z</dc:date>
    </item>
    <item>
      <title>Re: CDR on-net ,off-net calls details</title>
      <link>https://community.cisco.com/t5/management/cdr-on-net-off-net-calls-details/m-p/3548597#M1872</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The designation of whether a call is off-net vs. on-net is somewhat arbitrary, and in general depends on which gateway/trunk a call ingresses/egresses from.&amp;nbsp; The CUCM admin can designate a particular 'route pattern' as off-net or on-net; route patterns in turn are associated with a particular gateway, trunk, or route-list (which in turn can can point to a group of gateways/trunks.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, a comprehensive approach is typically something like:&lt;/P&gt;&lt;P&gt;- Determin the CDR origination and/or destination device name of the call&lt;/P&gt;&lt;P&gt;- Get a list of all the gateway, trunk device names and see if the orig/dest is a gateway or trunk&lt;/P&gt;&lt;P&gt;- If so, determine which route pattern is associated to the gateway/trunk&lt;/P&gt;&lt;P&gt;- Determine whether the route pattern is designated as off-net or on-net&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will require reading/caching some data via AXL, i.e. device names and types, route pattern-&amp;gt;device associations, route pattern properties, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A simpler approach could just have the app user enter/identify the unique orig/dest device names as off-net vs. on-net.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Mar 2016 18:54:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/cdr-on-net-off-net-calls-details/m-p/3548597#M1872</guid>
      <dc:creator>dstaudt</dc:creator>
      <dc:date>2016-03-21T18:54:03Z</dc:date>
    </item>
  </channel>
</rss>

