300-810 · Question #241
Refer to the exhibit. A company deployed the Cisco Webex calling with Cisco Unified Border Element as a local gateway for PSTN calls and a firewall to restrict and control the HTTP-based traffic…
The correct answer is C. Open TCP port 8934 outbound on the firewall. When Cisco CUBE is configured as a Local Gateway for Cisco Webex Calling, it must communicate outbound to the Webex cloud infrastructure. The CUBE uses TCP port 8934 for the HTTPS-based control and management signaling connection to Webex. Since the firewall is blocking…
Question
Refer to the exhibit. A company deployed the Cisco Webex calling with Cisco Unified Border Element as a local gateway for PSTN calls and a firewall to restrict and control the HTTP-based traffic that leaves and enters the network. However, Alice in LA cannot dial 82024001 to reach Charlie in NY. Which action must an administrator take to resolve the issue?
Exhibit
Options
- AOpen UDP port 5062 outbound on the firewall.
- BOpen TCP port 5062 outbound on the firewall.
- COpen TCP port 8934 outbound on the firewall.
- DOpen UDP port 8934 outbound on the firewall.
How the community answered
(21 responses)- A5% (1)
- B19% (4)
- C71% (15)
- D5% (1)
Explanation
When Cisco CUBE is configured as a Local Gateway for Cisco Webex Calling, it must communicate outbound to the Webex cloud infrastructure. The CUBE uses TCP port 8934 for the HTTPS-based control and management signaling connection to Webex. Since the firewall is blocking outbound HTTP-based traffic, opening TCP port 8934 outbound allows the CUBE to register and maintain its connection to the Webex cloud, enabling calls to traverse the gateway. UDP port 5062 (A) and TCP port 5062 (B) are used for SIP over TLS in some deployments but are not the relevant port for this Webex Local Gateway control path. UDP port 8934 (D) is incorrect because this communication uses TCP, not UDP.
Topics
Community Discussion
No community discussion yet for this question.