<?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 thank you to everyone for in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442357#M86533</link>
    <description>&lt;P&gt;thank you to everyone for helping out on this post! Wonderful!&lt;/P&gt;</description>
    <pubDate>Wed, 14 May 2014 19:48:11 GMT</pubDate>
    <dc:creator>RSundstrom</dc:creator>
    <dc:date>2014-05-14T19:48:11Z</dc:date>
    <item>
      <title>Cisco ISE authenticating Ip Phone 7942</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442348#M86524</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am installing Cisco ISE soon and have a question. Why can't I authenticate Cisco IP phone model 7942 using 802.1x? I see that the phone has this option (it is not enabled). I am told that Cisco IP Phones must be authenticated on ISE by using profiling or MAB. This uses a costly advanced license to accomplish this.&lt;/P&gt;&lt;P&gt;Has anybody had any luck in this area?&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 04:39:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442348#M86524</guid>
      <dc:creator>RSundstrom</dc:creator>
      <dc:date>2019-03-11T04:39:20Z</dc:date>
    </item>
    <item>
      <title>Profiling use advanced</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442349#M86525</link>
      <description>&lt;P&gt;Profiling use advanced license but MAB uses base license. Administration &amp;gt; Identity Management &amp;gt; Identities and select Endpoints. Select Create and assign your IP phone’s MAC address to the Identity Group Cisco-IP-Phone:&lt;/P&gt;</description>
      <pubDate>Tue, 22 Apr 2014 04:07:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442349#M86525</guid>
      <dc:creator>Venkatesh Attuluri</dc:creator>
      <dc:date>2014-04-22T04:07:51Z</dc:date>
    </item>
    <item>
      <title>Hi, Is your model 7942g? In</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442350#M86526</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is your model 7942g? In that case those phones sould have a built in certificate from Cisco (&lt;STRONG&gt;Manufacturer Installed Certificate&lt;/STRONG&gt;) that can be used for EAP-TLS. The common name begin ether with SEP och CP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Philip&lt;/P&gt;</description>
      <pubDate>Tue, 22 Apr 2014 12:48:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442350#M86526</guid>
      <dc:creator>Philip Vilhelmsson</dc:creator>
      <dc:date>2014-04-22T12:48:48Z</dc:date>
    </item>
    <item>
      <title>You are correct. I did not</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442351#M86527</link>
      <description>&lt;P&gt;You are correct. I did not add all the info I should have in my first post. My apologies. I can't use MAB to authenticate IP Phones because we have over 1,200. The initial programming and ongoing maintenance would be huge.&lt;/P&gt;&lt;P&gt;What I am looking for is the ability to authenticate Cisco IP phones using 802.1x authentication. The model we have most of is the Cisco IP Phone 7942.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Apr 2014 12:49:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442351#M86527</guid>
      <dc:creator>RSundstrom</dc:creator>
      <dc:date>2014-04-22T12:49:44Z</dc:date>
    </item>
    <item>
      <title>Hello Philip,The phone on my</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442352#M86528</link>
      <description>&lt;P&gt;Hello Philip,&lt;/P&gt;&lt;P&gt;The phone on my desk is a 7942G model. We have a variety of Cisco IP phones. Is there a way for me to find out which models have a built-in certificate?&lt;/P&gt;&lt;P&gt;Thank you for the reply,&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;</description>
      <pubDate>Tue, 22 Apr 2014 12:57:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442352#M86528</guid>
      <dc:creator>RSundstrom</dc:creator>
      <dc:date>2014-04-22T12:57:25Z</dc:date>
    </item>
    <item>
      <title>Check Tabe 2 here: http://www</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442353#M86529</link>
      <description>&lt;P&gt;Check Tabe 2 here: &lt;A href="http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Security/TrustSec_1-99/IP_Tele/IP_Telephony_DIG.html"&gt;http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Security/TrustSec_1-99/IP_Tele/IP_Telephony_DIG.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Apr 2014 13:34:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442353#M86529</guid>
      <dc:creator>Philip Vilhelmsson</dc:creator>
      <dc:date>2014-04-22T13:34:37Z</dc:date>
    </item>
    <item>
      <title>Hello Philip,Thank you for</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442354#M86530</link>
      <description>&lt;P&gt;Hello Philip,&lt;/P&gt;&lt;P&gt;Thank you for the link. It is very useful.&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;</description>
      <pubDate>Tue, 22 Apr 2014 15:53:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442354#M86530</guid>
      <dc:creator>RSundstrom</dc:creator>
      <dc:date>2014-04-22T15:53:15Z</dc:date>
    </item>
    <item>
      <title>Philip,Thank you for your</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442355#M86531</link>
      <description>&lt;P&gt;Philip,&lt;/P&gt;&lt;P&gt;Thank you for your help. I have what I need to know.&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;</description>
      <pubDate>Thu, 24 Apr 2014 15:25:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442355#M86531</guid>
      <dc:creator>RSundstrom</dc:creator>
      <dc:date>2014-04-24T15:25:03Z</dc:date>
    </item>
    <item>
      <title>I have successfully deployed</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442356#M86532</link>
      <description>&lt;P&gt;I have successfully deployed 802.1x for wireless IP phones using MIC. The only real problem I have with this approach is the inability of ISE to authenticate the username from certificate against anything but an external database. As a result I have been forced to use a static endpoint group for the MAC addresses of the allowed phones to meet the organisation's security stance. Just wish EAP-TLS could go against an internal database.&lt;/P&gt;</description>
      <pubDate>Sun, 27 Apr 2014 22:29:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442356#M86532</guid>
      <dc:creator>Stephen McBride</dc:creator>
      <dc:date>2014-04-27T22:29:31Z</dc:date>
    </item>
    <item>
      <title>thank you to everyone for</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442357#M86533</link>
      <description>&lt;P&gt;thank you to everyone for helping out on this post! Wonderful!&lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2014 19:48:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/2442357#M86533</guid>
      <dc:creator>RSundstrom</dc:creator>
      <dc:date>2014-05-14T19:48:11Z</dc:date>
    </item>
    <item>
      <title>Re: You are correct. I did not</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/3184590#M86534</link>
      <description>&lt;P&gt;I faced the same issue to bulk add IP phones MAC addresses to ISE.&lt;/P&gt;&lt;P&gt;As, rather, a voice guy I would like to add that the number of IP phones in the deployment is not really a problem.&lt;/P&gt;&lt;P&gt;In fact, if the IP phones have been already added to CUCM, the voice administrator can bulk export IP phone MAC addresses in CSV format. Afterwards, the ISE administrator can import them as identities to ISE in bulk in CSV format. Just some CSV formatting is needed.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Sep 2017 10:22:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authenticating-ip-phone-7942/m-p/3184590#M86534</guid>
      <dc:creator>ucanduc</dc:creator>
      <dc:date>2017-09-15T10:22:48Z</dc:date>
    </item>
  </channel>
</rss>

