<?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: outbound dial-peer question in Unified Communications Infrastructure</title>
    <link>https://community.cisco.com/t5/unified-communications-infrastructure/outbound-dial-peer-question/m-p/3382031#M6358</link>
    <description>&lt;P&gt;I contacted ATT to look into this issue.&amp;nbsp; Thanks for your reply.&lt;/P&gt;</description>
    <pubDate>Fri, 11 May 2018 18:51:09 GMT</pubDate>
    <dc:creator>Peter Kim</dc:creator>
    <dc:date>2018-05-11T18:51:09Z</dc:date>
    <item>
      <title>outbound dial-peer question</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/outbound-dial-peer-question/m-p/3380885#M6354</link>
      <description>&lt;P&gt;I'm having a little trouble regarding out bound calls.&amp;nbsp; The following is what I have on my voice gate-way.&lt;/P&gt;
&lt;P&gt;I want the outbound call to use dial-peer 99999400 not 99999402.&amp;nbsp; However, all outbound calls are using 99999402 dial-peer.&amp;nbsp; Any suggestion?&amp;nbsp; Let me know if you need anything else to troubleshoot this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;dial-peer voice 99999400 pots&lt;BR /&gt; description DIALPEER 9.1 LD&lt;BR /&gt; preference 1&lt;BR /&gt; destination-pattern ^91[2-9]..[2-9]......$&lt;BR /&gt; port 0/0/0:23&lt;BR /&gt; forward-digits 11&lt;BR /&gt;!&lt;BR /&gt;dial-peer voice 99999402 pots&lt;BR /&gt; trunkgroup POTS&lt;BR /&gt; description DIALPEER 9.1 LD&lt;BR /&gt; preference 2&lt;BR /&gt; destination-pattern ^91[2-9]..[2-9]......$&lt;BR /&gt; forward-digits 11&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2019 20:20:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/outbound-dial-peer-question/m-p/3380885#M6354</guid>
      <dc:creator>Peter Kim</dc:creator>
      <dc:date>2019-03-19T20:20:05Z</dc:date>
    </item>
    <item>
      <title>Re: outbound dial-peer question</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/outbound-dial-peer-question/m-p/3381288#M6355</link>
      <description>This is the expected behaviour since you have an overlapping dial-plan. Where are you making these calls from ? CUCM ? And how is it connecting to GW ? SIP/H.323/MGCP ?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 10 May 2018 12:58:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/outbound-dial-peer-question/m-p/3381288#M6355</guid>
      <dc:creator>R0g22</dc:creator>
      <dc:date>2018-05-10T12:58:40Z</dc:date>
    </item>
    <item>
      <title>Re: outbound dial-peer question</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/outbound-dial-peer-question/m-p/3381325#M6356</link>
      <description>&lt;P&gt;It's overlapping, but the Preference command should cause the router to prefer the one the OP wants.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A router will ignore dial-peers where the target (an IP or a port) is not available. What is the status of the ISDN circuit? Do a 'show isdn status' on the 0/0/0:23 circuit. What is the status?&lt;/P&gt;</description>
      <pubDate>Thu, 10 May 2018 14:07:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/outbound-dial-peer-question/m-p/3381325#M6356</guid>
      <dc:creator>Maren Mahoney</dc:creator>
      <dc:date>2018-05-10T14:07:36Z</dc:date>
    </item>
    <item>
      <title>Re: outbound dial-peer question</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/outbound-dial-peer-question/m-p/3382024#M6357</link>
      <description>I second this.  You can also check the peers via "show dial-peer voice summary" to check if that peer is up.</description>
      <pubDate>Fri, 11 May 2018 18:38:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/outbound-dial-peer-question/m-p/3382024#M6357</guid>
      <dc:creator>gmgarrian</dc:creator>
      <dc:date>2018-05-11T18:38:09Z</dc:date>
    </item>
    <item>
      <title>Re: outbound dial-peer question</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/outbound-dial-peer-question/m-p/3382031#M6358</link>
      <description>&lt;P&gt;I contacted ATT to look into this issue.&amp;nbsp; Thanks for your reply.&lt;/P&gt;</description>
      <pubDate>Fri, 11 May 2018 18:51:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/outbound-dial-peer-question/m-p/3382031#M6358</guid>
      <dc:creator>Peter Kim</dc:creator>
      <dc:date>2018-05-11T18:51:09Z</dc:date>
    </item>
    <item>
      <title>Re: outbound dial-peer question</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/outbound-dial-peer-question/m-p/3385083#M6359</link>
      <description>&lt;P&gt;After ATT rebooted their router.&amp;nbsp; Everything was back to normal.&lt;/P&gt;</description>
      <pubDate>Thu, 17 May 2018 17:21:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/outbound-dial-peer-question/m-p/3385083#M6359</guid>
      <dc:creator>Peter Kim</dc:creator>
      <dc:date>2018-05-17T17:21:56Z</dc:date>
    </item>
  </channel>
</rss>

