<?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: Cisco Webex devices Calling - network requirements in Webex Devices</title>
    <link>https://community.cisco.com/t5/webex-devices/cisco-webex-devices-calling-network-requirements/m-p/4146765#M64</link>
    <description>&lt;P&gt;Nobody has idea how would device change SDP information in SIP messages when outbound connection traversing NAT is going to the Webex cloud? &amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 05 Sep 2020 11:12:19 GMT</pubDate>
    <dc:creator>marco_81</dc:creator>
    <dc:date>2020-09-05T11:12:19Z</dc:date>
    <item>
      <title>Cisco Webex devices Calling - network requirements</title>
      <link>https://community.cisco.com/t5/webex-devices/cisco-webex-devices-calling-network-requirements/m-p/4145632#M63</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;i need to understand some points about Cisco Webex device calling and network requirements. The deployment i'm focused on is only made of Cisco Webex devices registering to the cloud (no Teams apps).&lt;/P&gt;&lt;P&gt;These devices make intra-customer, intra-site calls, they also can make outbound audio\video calls to join Cisco Webex meetings hosted on other domains.&lt;/P&gt;&lt;P&gt;On my edge firewall&amp;nbsp;i'd open only &lt;STRONG&gt;outbound&lt;/STRONG&gt; connection to destinations documented here:&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;A href="https://help.webex.com/en-us/b2exve/Port-Reference-Information-for-Cisco-Webex-Calling" target="_blank" rel="noopener"&gt;https://help.webex.com/en-us/b2exve/Port-Reference-Information-for-Cisco-Webex-Calling&lt;/A&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;the destination ports in my case are:&lt;/P&gt;&lt;P&gt;TCP\8934&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; signalling to webex SIP-TLS&lt;/P&gt;&lt;P&gt;UDP\19560-65535&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; media to webex&amp;nbsp; SRTP&lt;/P&gt;&lt;P&gt;TCP\80, 443&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; firmware management&lt;/P&gt;&lt;P&gt;UDP\123&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; NTP&lt;/P&gt;&lt;P&gt;TCP-UDP\53&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DNS&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;No &lt;STRONG&gt;Inbound&lt;/STRONG&gt; connection from the internet to internal network.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To register devices to Webex Cloud i need a minimum version of CE firmware on each device, do 80-443 ports manage this stage?&lt;/P&gt;&lt;P&gt;If devices from the internal network go directly to the cloud, do they apply SIP ALG or similar functionality on their own?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks for help&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;UPDATE:&lt;/P&gt;&lt;P&gt;finally i found the right document where it is explained:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;With the Cisco &lt;/SPAN&gt;&lt;SPAN&gt;Webex Calling &lt;/SPAN&gt;&lt;SPAN&gt;product, the challenges presented by the presence of a &lt;/SPAN&gt;&lt;SPAN&gt;NAT are addressed. A technique called NAT Traversal is used to overcome the issues &lt;/SPAN&gt;&lt;SPAN&gt;created by the presence of a NAT. &lt;/SPAN&gt;&lt;SPAN&gt;Part of the Cisco &lt;/SPAN&gt;&lt;SPAN&gt;Webex Calling &lt;/SPAN&gt;&lt;SPAN&gt;call control &lt;/SPAN&gt;&lt;SPAN&gt;platform is responsible for maintaining constant communication with all SIP devices. &lt;/SPAN&gt;&lt;SPAN&gt;This constant communication ensures that the NAT bind timer never expires, &lt;/SPAN&gt;&lt;SPAN&gt;effectively making the dynamic bind permanent. Without this, a SIP device in a private &lt;/SPAN&gt;&lt;SPAN&gt;network would not be able to receive calls. &lt;/SPAN&gt;&lt;SPAN&gt;Also, the Cisco &lt;/SPAN&gt;&lt;SPAN&gt;Webex Calling &lt;/SPAN&gt;&lt;SPAN&gt;call control &lt;/SPAN&gt;&lt;SPAN&gt;platform uses a technique called Media Relay to overcome the issue where the &lt;/SPAN&gt;&lt;SPAN&gt;NAT does not manipulate application layer information. &lt;/SPAN&gt;&lt;SPAN&gt;This functionality allows &lt;/SPAN&gt;&lt;SPAN&gt;the call control platform to discover the public IP address and port of the RTP stream &lt;/SPAN&gt;&lt;SPAN&gt;once the SIP device sends out its first RTP packet. &lt;/SPAN&gt;&lt;SPAN&gt;The call control platform performs &lt;/SPAN&gt;&lt;SPAN&gt;this function on both ends of a call and bridges the two legs of the call together, &lt;/SPAN&gt;&lt;SPAN&gt;effectively relaying the traffic from one device to another.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Source: (&lt;A href="https://callinghelp.webex.com/wp-content/uploads/2019/05/WC-Customer-Network-Minimum-Requirements-Guide-v2.2_062019.pdf" target="_blank" rel="noopener"&gt;https://callinghelp.webex.com/wp-content/uploads/2019/05/WC-Customer-Network-Minimum-Requirements-Guide-v2.2_062019.pdf&lt;/A&gt;)&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Sep 2020 08:50:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-devices/cisco-webex-devices-calling-network-requirements/m-p/4145632#M63</guid>
      <dc:creator>marco_81</dc:creator>
      <dc:date>2020-09-07T08:50:46Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Webex devices Calling - network requirements</title>
      <link>https://community.cisco.com/t5/webex-devices/cisco-webex-devices-calling-network-requirements/m-p/4146765#M64</link>
      <description>&lt;P&gt;Nobody has idea how would device change SDP information in SIP messages when outbound connection traversing NAT is going to the Webex cloud? &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 05 Sep 2020 11:12:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-devices/cisco-webex-devices-calling-network-requirements/m-p/4146765#M64</guid>
      <dc:creator>marco_81</dc:creator>
      <dc:date>2020-09-05T11:12:19Z</dc:date>
    </item>
  </channel>
</rss>

