<?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: Webex calling migration/HA in Webex Calling</title>
    <link>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5326046#M2581</link>
    <description>&lt;P&gt;Yes, it is possible to keep internal calling running even if the internet goes down. Webex Calling can be paired with a Local Gateway or SRST (Survivable Remote Site Telephony) so that phones can still call each other internally and even make critical PSTN calls during an outage. For more complex needs, some companies opt for a hybrid setup or Webex Calling Dedicated Instance to maintain full resiliency.&lt;/P&gt;&lt;P&gt;We have helped businesses set up this kind of failover-ready Webex Calling solution. If you would like to see how it works in practice, you can check us out here:&amp;nbsp;&lt;A href="https://www.sparxitsolutions.com/cloud/migration" target="_blank" rel="noopener"&gt;sparxitsolutions.com&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 01 Sep 2025 07:03:18 GMT</pubDate>
    <dc:creator>kellysmith9312</dc:creator>
    <dc:date>2025-09-01T07:03:18Z</dc:date>
    <item>
      <title>Webex calling migration/HA</title>
      <link>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5322058#M2575</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;
&lt;P&gt;So I have a customer that wants to migrate from their on-premise UCM infrastructure to Webex calling. However, they have a concern regarding the cloud hosting platform of the webex calling. If for some reason, an internet disconnection event occurs in their office, then they would essentially lose access to the Webex cloud, and in-turn this would result in a disruption of their internal calling services. A problem that doesn't exist with the existing on-prem CUCM infrastructure.&lt;/P&gt;
&lt;P&gt;Hence, my question is this, is it possible in a Webex calling infrastructure, to have it so that they can still make calls internally, even without cloud access? I think I read somewhere that it is possible by placing a router to route the calls internally. But I don't really know much about it and would appreciate some guidiance here.&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Aug 2025 17:39:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5322058#M2575</guid>
      <dc:creator>momosebi</dc:creator>
      <dc:date>2025-08-19T17:39:53Z</dc:date>
    </item>
    <item>
      <title>Re: Webex calling migration/HA</title>
      <link>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5322064#M2576</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1745304"&gt;@momosebi&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Similar to CUCM, Webex Calling supports&amp;nbsp;&lt;STRONG&gt;&lt;EM&gt;survivability mode &lt;/EM&gt;&lt;/STRONG&gt;&lt;EM&gt;using on-premise router (Survivability Gateway) .&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P class="p"&gt;By default, Webex Calling endpoints operate in Active mode, connecting to the Webex cloud for SIP registration and call control. However, if the network connection to Webex breaks, endpoints switch automatically to Survivability mode and registrations fall back to the Survivability Gateway within the local network. While endpoints are in Survivability mode, the Survivability Gateway provides a basic backup calling service for those endpoints. After the network connection to Webex resumes, call control and registrations revert to the Webex cloud.&lt;/P&gt;
&lt;P class="p"&gt;While endpoints are in Survivability mode, you can make the following calls:&lt;/P&gt;
&lt;UL class="ul"&gt;
&lt;LI class="li"&gt;
&lt;P class="p"&gt;Internal calling (intrasite) between supported Webex Calling endpoints&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="li"&gt;
&lt;P class="p"&gt;External calling (incoming and outgoing) using a local PSTN circuit or SIP trunk to external numbers and E911 providers&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Please check below document for more details:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://help.webex.com/en-us/article/d68vi1/Site-survivability-for-Webex-Calling" target="_blank"&gt;https://help.webex.com/en-us/article/d68vi1/Site-survivability-for-Webex-Calling&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Aug 2025 17:48:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5322064#M2576</guid>
      <dc:creator>Vaijanath Sonvane</dc:creator>
      <dc:date>2025-08-19T17:48:07Z</dc:date>
    </item>
    <item>
      <title>Re: Webex calling migration/HA</title>
      <link>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5322083#M2577</link>
      <description>&lt;P&gt;Thank you very much for this, really does address my concern.&lt;/P&gt;
&lt;P&gt;If you would be so kind, I've got another question.&lt;/P&gt;
&lt;P&gt;For external calls, the customer uses a Yeaster GSM device, that connects to the CUCM servers, and routes external calls.&lt;/P&gt;
&lt;P&gt;Can this be migrated to Webex calling, and how?&lt;/P&gt;</description>
      <pubDate>Tue, 19 Aug 2025 19:03:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5322083#M2577</guid>
      <dc:creator>momosebi</dc:creator>
      <dc:date>2025-08-19T19:03:27Z</dc:date>
    </item>
    <item>
      <title>Re: Webex calling migration/HA</title>
      <link>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5322101#M2578</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1745304"&gt;@momosebi&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;For PSTN services, Webex Calling has number of options to choose from:&lt;/P&gt;
&lt;P&gt;1. You can go with Cisco Calling Plan. In this case,&amp;nbsp;&lt;SPAN&gt;Cisco acts as your PSTN carrier, simplifying number provisioning and management within Control Hub.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://help.webex.com/en-us/article/nousk9ab/Get-Started-with-the-Cisco-Calling-Plans" target="_blank"&gt;https://help.webex.com/en-us/article/nousk9ab/Get-Started-with-the-Cisco-Calling-Plans&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;2. Or You can choose one of the Cloud Connected Service Provider. Check below URL for list of providers:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.webex.com/products/calling-global-availability.html" target="_blank"&gt;https://www.webex.com/products/calling-global-availability.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Aug 2025 19:41:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5322101#M2578</guid>
      <dc:creator>Vaijanath Sonvane</dc:creator>
      <dc:date>2025-08-19T19:41:57Z</dc:date>
    </item>
    <item>
      <title>Re: Webex calling migration/HA</title>
      <link>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5322340#M2579</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/294890"&gt;@Vaijanath Sonvane&lt;/a&gt;.&lt;/P&gt;
&lt;P&gt;However, I though Webex offered an option that allows one to maintain existing PSTN services, and easily migrate it to the Webex cloud.&lt;/P&gt;
&lt;P&gt;Also from the link you shared earlier, I understand that to implement the survivability mode, you need a survivability gateway, which has to be an IOS XE device like the C8200 router. However, I'm unsure of the necessary router physical configuration, like in terms of the necessary modules (NIM/Voice modules), or the necessary software or subscriptions (like maybe DNA subscriptions), or other necessary accessories for the router. I don't know if you or anyone has an idea about this.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2025 08:35:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5322340#M2579</guid>
      <dc:creator>momosebi</dc:creator>
      <dc:date>2025-08-20T08:35:23Z</dc:date>
    </item>
    <item>
      <title>Re: Webex calling migration/HA</title>
      <link>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5326046#M2581</link>
      <description>&lt;P&gt;Yes, it is possible to keep internal calling running even if the internet goes down. Webex Calling can be paired with a Local Gateway or SRST (Survivable Remote Site Telephony) so that phones can still call each other internally and even make critical PSTN calls during an outage. For more complex needs, some companies opt for a hybrid setup or Webex Calling Dedicated Instance to maintain full resiliency.&lt;/P&gt;&lt;P&gt;We have helped businesses set up this kind of failover-ready Webex Calling solution. If you would like to see how it works in practice, you can check us out here:&amp;nbsp;&lt;A href="https://www.sparxitsolutions.com/cloud/migration" target="_blank" rel="noopener"&gt;sparxitsolutions.com&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Sep 2025 07:03:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5326046#M2581</guid>
      <dc:creator>kellysmith9312</dc:creator>
      <dc:date>2025-09-01T07:03:18Z</dc:date>
    </item>
    <item>
      <title>Re: Webex calling migration/HA</title>
      <link>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5369035#M2720</link>
      <description>&lt;P&gt;Thanks for sharing this scenario — Webex Calling migrations in HA environments can definitely get tricky, especially when downtime and call continuity are critical.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From experience, the safest approach is to treat the migration as a phased transition rather than a single cutover. Start by validating number assignments, device mappings, and routing behavior in a test location or subset of users. This helps surface issues early, particularly around call routing, survivability, and failover behavior.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It’s also important to double-check dependencies like SBC configuration, PSTN connectivity, and user feature parity before moving production traffic. Clear rollback steps and proper monitoring during the migration window make a big difference in avoiding service disruption.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We’ve handled similar web and communication platform migrations where stability and minimal downtime were the top priorities. Sometimes a small adjustment in sequencing or validation saves hours of troubleshooting later.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If anyone’s interested in structured migration planning or needs technical support beyond Cisco docs, you can also find practical implementation insights here:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;A href="https://kerneltech.net/" target="_blank"&gt;https://kerneltech.net/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Feb 2026 12:59:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/webex-calling-migration-ha/m-p/5369035#M2720</guid>
      <dc:creator>kerneltech</dc:creator>
      <dc:date>2026-02-10T12:59:28Z</dc:date>
    </item>
  </channel>
</rss>

