<?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: IP Phone registration delay over SDA in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/ip-phone-registration-delay-over-sda/m-p/4976093#M2838</link>
    <description>&lt;P&gt;Not specific configuration is needed. If there is IP reachability between IP Phones and CUCM registration should be the same time as in a legacy network.&lt;/P&gt;
&lt;P&gt;I would recommend you to check network routes in the path "border &amp;lt;--&amp;gt; Fusion router &amp;lt;--&amp;gt; CUCM"&lt;/P&gt;</description>
    <pubDate>Tue, 12 Dec 2023 10:57:29 GMT</pubDate>
    <dc:creator>alberx</dc:creator>
    <dc:date>2023-12-12T10:57:29Z</dc:date>
    <item>
      <title>IP Phone registration delay over SDA</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/ip-phone-registration-delay-over-sda/m-p/4963304#M2795</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;We are implementing our new SDA network&lt;/P&gt;
&lt;P&gt;We have an issue for the ip phones registration that it takes a very long time to register to CUCM [about 55 minutes] &lt;/P&gt;
&lt;P&gt;When it connected, it got ip address from infoblox, then it send request to CUCM untill it register&lt;/P&gt;
&lt;P&gt;When we tried the phone with the cucm outside SDA, it register normally with no delay [about 3 minutes]&lt;/P&gt;
&lt;P&gt;So do we need any specific configuration for the ip phones on the SDA&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Nov 2023 23:34:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/ip-phone-registration-delay-over-sda/m-p/4963304#M2795</guid>
      <dc:creator>Hythim Ali El Hadad</dc:creator>
      <dc:date>2023-11-20T23:34:23Z</dc:date>
    </item>
    <item>
      <title>Re: IP Phone registration delay over SDA</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/ip-phone-registration-delay-over-sda/m-p/4976093#M2838</link>
      <description>&lt;P&gt;Not specific configuration is needed. If there is IP reachability between IP Phones and CUCM registration should be the same time as in a legacy network.&lt;/P&gt;
&lt;P&gt;I would recommend you to check network routes in the path "border &amp;lt;--&amp;gt; Fusion router &amp;lt;--&amp;gt; CUCM"&lt;/P&gt;</description>
      <pubDate>Tue, 12 Dec 2023 10:57:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/ip-phone-registration-delay-over-sda/m-p/4976093#M2838</guid>
      <dc:creator>alberx</dc:creator>
      <dc:date>2023-12-12T10:57:29Z</dc:date>
    </item>
    <item>
      <title>Re: IP Phone registration delay over SDA</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/ip-phone-registration-delay-over-sda/m-p/4976113#M2840</link>
      <description>&lt;P&gt;u can capture traffic of interest from the adjacent port to check what happens in the background (registration process chapter of&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-version-115/220669-understand-sip-ip-phone-registration-pro.html" target="_blank"&gt;Understand SIP IP Phone Registration Process in CUCM - Cisco&lt;/A&gt;&amp;nbsp;starting step 4)&lt;/P&gt;</description>
      <pubDate>Tue, 12 Dec 2023 11:25:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/ip-phone-registration-delay-over-sda/m-p/4976113#M2840</guid>
      <dc:creator>Andrii Oliinyk</dc:creator>
      <dc:date>2023-12-12T11:25:17Z</dc:date>
    </item>
  </channel>
</rss>

