sip media · published

Webex Calling ICE media path optimization

Verified 2026-09-16 · 22 sources · tier 2

Also known as ICE-lite, WebRtcUdpPortRange, stun usage lite.

Webex Calling media optimization uses Interactive Connectivity Establishment (ICE) to establish direct media paths between endpoints, bypassing cloud media relays 8​7. Media optimization changes only the media path, while signalling data is always sent to the Webex Calling cloud to route calls 19.

How it works

Webex Calling media optimization runs in 4 phases: candidate discovery, candidate exchange, connectivity checks, and media path optimization 8. During candidate discovery, an endpoint collects its local address and a server reflexive address obtained by querying a STUN server in the Webex Calling cloud 8. Endpoints then exchange those addresses using SIP during the candidate exchange phase 8. The endpoints test the exchanged candidates during connectivity checks, and a re-INVITE moves the media onto the chosen path during media path optimization 8.

An active internet connection is always required to make Webex Calling calls, and signalling data always travels to the Webex Calling cloud 19. Cisco notes that media makes up most of a call's traffic 19. Cisco states that where STUN and ICE negotiation succeeds for a call within the organisation, the media relay in the cloud is removed from the communication path and media flows directly between the apps and devices 7.

Endpoint and gateway requirements

Media optimization is supported across desk phones, the Webex App, and the Local Gateway solution, but excludes DECT and analog telephone adapter (ATA) devices 18. It is enabled by default on desk phones and the Webex App without configuration 18.

Media optimization on a Local Gateway is enabled with the command STUN usage lite 10. A Local Gateway running Cisco Unified Border Element (CUBE) supports ICE-lite with several restrictions, and requires a minimum CUBE software version of 17.3 or 16.12.5 10. Operating media optimization with a Local Gateway requires network reachability between the device and the Local Gateway, which is achieved either by assigning a public IP address to the Local Gateway or by ensuring the Local Gateway host address is accessible to a device on the same network as the gateway 9.

Media transport and network ports

Cisco states that UDP is its preferred transport protocol for Webex Calling media and recommends using only SRTP over UDP 11. Cisco states that TCP and TLS as transport protocols for media are not supported for Webex Calling in production environments because their connection-oriented nature affects media quality over network loss 11.

When media optimization succeeds within an organisation, media source and destination ports depend on the endpoint type: 7​17

Endpoint class Source port range Notes
Desk phones 19560 to 19661 Direct endpoint communication 7​17
Webex App 8500 to 8699 Audio uses 8500 to 8599; video uses 8600 to 8699 7​15​17
Room Series devices 52050 to 52299 Audio uses 52050 to 52099; video uses 52200 to 52299 17
VG400 analog telephone adapters 19560 to 19849 Source range only 17

Cisco states that browsers use an ephemeral source port for Webex Calling media, which can be controlled by setting the WebRtcUdpPortRange policy in a mobile device management profile 5. The Webex Calling service behaves normally if no such policy is set 5.

For network topologies using firewalls within a customer premise, Cisco states that the administrator must allow the media source and destination port ranges inside the network for media to flow, citing the example of allowing Webex App audio on 8500 to 8599 and video on 8600 to 8699 as both source and destination 15. When media is sent to the Webex Calling cloud rather than directly, outbound SRTP media from Local Gateways, devices, and Webex App clients uses destination ports 5004, 9000, 8500 to 8699, and 19560 to 65535 over UDP 6. Cloud media to a certificate-based Local Gateway uses destination ports 19560 to 65535 6.

NAT, firewall, and signalling considerations

Cisco states that Webex Calling devices sharing a public address through NAT or PAT may use the same SIP signalling source port within the 5060 to 5280 range, and the NAT device must be able to translate overlapping source ports to unique translated ports 12. The port reference revision history records that on 7 September 2026, the phone source port range was expanded from 5060 to 5080 into 5060 to 5280 to accommodate an updated Cisco feature enabling support for up to 130 lines 22. Cisco notes that strict source-port preservation configurations can cause device registration failures 12. In addition, Cisco instructs administrators to validate NAT pool sizing and assign adequate public addresses to prevent port exhaustion, which contributes to internal users and devices being unable to connect to Webex Calling and Webex Aware services 13.

Cisco states that Cisco phones send a follow-up REGISTER refresh every 1 to 2 minutes, and networks implementing NAT or stateful packet inspection should set a connection timeout of at least 30 minutes to maintain reliable connectivity while reducing mobile battery consumption 14. Cisco also recommends turning off SIP Application Layer Gateway (SIP ALG) or similar functions on any SIP-aware router or firewall, stating that although Webex Calling traffic is encrypted, certain SIP ALG implementations cause firewall traversal issues 21.

Operational limitations and diagnostics

Cisco states that calls can only be optimized within a single organisation, and that for interorganization calls, media must flow through the PSTN for regulatory reasons 20. Where call recording is enabled, media is routed to the cloud and is not optimized 16. Cisco states that media optimization and call recording each independently introduce a small audio delay at the beginning of a call, and together the delay is slightly longer and more noticeable to customers 16.

Data for optimized calls is available through the Media Quality analytics page in Control Hub or through the Control Hub troubleshooting tool 3.

Applicability

Applies to: Cisco Webex Calling. Sources checked 2026-09-16. Local Gateway media optimization requires a minimum CUBE software version of 17.3 or 16.12.5 10.

What remains uncertain

Which internal firewall rules a site needs once media optimization is on is not covered by the sources below. Which addresses the Webex Calling STUN servers answer on is not covered by the sources below. The several restrictions on ICE support in CUBE that the article defers to are not covered by the sources below. Whether Webex Calling uses TURN relay at all is not covered by the sources below. The global enablement dates for media optimization are not covered by the sources below. In the field, the Webex Calling media optimization article names no edition restriction and does not mention Webex for Government, so the corpus holds no source for the claim that media optimization is unavailable in that edition 4. How long the audio delay at call start is with ICE and with recording is not covered by the sources below. Which regulation requires interorganization media to traverse the PSTN is not covered by the sources below.

See also

See also

Related to

Referenced by

Sources

  1. 1
    The word TURN occurs 0 times in the Webex Calling port reference article and 0 times in the Webex Calling media optimization article, so no Cisco source the corpus holds names a relay candidate or a TURN server for Webex Calling even though both describe a media relay in the cloud that ICE removes.field report
    Port Reference Information for Webex Calling · whole article, and the Webex Calling media optimization article, counted against the rendered text · Checked 2026-09-16
  2. 2
    In Cisco's worked example of a call between 2 phones in Australia for a customer assigned to the United States region, the media path is kept on the access session border controllers in the Australia region under the control of the United States instance while the SIP signalling for the call goes back to the call control entity in the United States region, and Cisco describes that regional media path as the fallback that ICE optimization can replace with a direct path.
    Cisco Preferred Architecture for Webex Calling — Design Overview · Architectural Overview, Figure 3 Regional Access SBCs, worked example · Checked 2026-09-16
  3. 3
    Data for optimized calls is available through the Media Quality analytics page in Control Hub or through the Control Hub troubleshooting tool.
    Webex Calling media optimization with Interactive Connectivity Establishment (ICE) · Analytics for media optimization · Checked 2026-09-16
  4. 4
    The Webex Calling media optimization article names no edition restriction and does not mention Webex for Government, so the corpus holds no source for the claim that media optimization is unavailable in that edition.field report
    Webex Calling media optimization with Interactive Connectivity Establishment (ICE) · whole rendered article, 4260 characters, searched for government and for edition · Checked 2026-09-16
  5. 5
    Cisco states that browsers use an ephemeral source port for Webex Calling media that can be controlled by setting the WebRtcUdpPortRange policy in a mobile device management profile, and that the Webex Calling service behaves normally if no such service is set.
    Port Reference Information for Webex Calling · IP Subnets for Webex Calling Services, WebRTC row · Checked 2026-09-16
  6. 6
    Outbound SRTP media from Local Gateways devices and Webex App clients to the Webex Calling cloud uses destination ports 5004, 9000, 8500 to 8699 and 19560 to 65535 over UDP, and media from Webex Calling to a certificate-based Local Gateway uses 19560 to 65535.
    Port Reference Information for Webex Calling · IP Subnets for Webex Calling Services, Call media to Webex Calling destination ports · Checked 2026-09-16
  7. 7
    Cisco states that where STUN and ICE negotiation succeeds for a call within the organisation the media relay in the cloud is removed from the communication path and media flows directly between the apps and devices, with the Webex App sending directly on 8500 to 8699 and devices sending directly to one another on 19560 to 19661.
    Port Reference Information for Webex Calling · IP Subnets for Webex Calling Services, Call media to Webex Calling row · Checked 2026-09-16
  8. 8
    Webex Calling media optimization runs in 4 phases: candidate discovery in which an endpoint collects its local address and a server reflexive address obtained by querying a STUN server in the Webex Calling cloud, candidate exchange in which endpoints exchange those addresses using SIP, connectivity checks in which the endpoints test the exchanged candidates, and media path optimization in which a re-INVITE moves the media onto the chosen path.
    Webex Calling media optimization with Interactive Connectivity Establishment (ICE) · Phases of Webex Calling media optimization · Checked 2026-09-16
  9. 9
    Media optimization with a Local Gateway requires network reachability between the device and the Local Gateway, achieved either by assigning a public IP address to the Local Gateway or by ensuring the Local Gateway host address is accessible to a device on the same network as the gateway.
    Webex Calling media optimization with Interactive Connectivity Establishment (ICE) · Prerequisites and limitations, reachability bullets · Checked 2026-09-16
  10. 10
    Media optimization on a Local Gateway is enabled with the command STUN usage lite, the Local Gateway running Cisco Unified Border Element supports ICE-lite with several restrictions, and the feature requires a minimum CUBE software version of 17.3 or 16.12.5.
    Webex Calling media optimization with Interactive Connectivity Establishment (ICE) · Prerequisites and limitations, Local Gateway paragraphs · Checked 2026-09-16
  11. 11
    Cisco states that UDP is its preferred transport protocol for Webex Calling media and recommends using only SRTP over UDP, and that TCP and TLS as transport protocols for media are not supported for Webex Calling in production environments because their connection-oriented nature affects media quality over network loss.
    Port Reference Information for Webex Calling · Firewall configuration, transport protocol paragraph · Checked 2026-09-16
  12. 12
    Cisco states that Webex Calling devices sharing a public address through NAT or PAT may use the same SIP signalling source port within the 5060 to 5280 range, that the NAT device must be able to translate overlapping source ports to unique translated ports, and that strict source-port preservation configurations can cause device registration failures.
    Port Reference Information for Webex Calling · Firewall configuration, NAT pool sizing paragraph · Checked 2026-09-16
  13. 13
    Cisco instructs administrators to validate the NAT pool size required for app and device connectivity and to assign adequate public addresses to prevent port exhaustion, stating that port exhaustion contributes to internal users and devices being unable to connect to the Webex Calling and Webex Aware services.
    Port Reference Information for Webex Calling · Firewall configuration, NAT pool sizing paragraph · Checked 2026-09-16
  14. 14
    Cisco states that Cisco phones send a follow-up REGISTER refresh every 1 to 2 minutes and that a network implementing NAT or stateful packet inspection should set a connection timeout of at least 30 minutes, which it says allows reliable connectivity while reducing the battery consumption of mobile devices.
    Port Reference Information for Webex Calling · Firewall configuration, NAT timeout paragraph · Checked 2026-09-16
  15. 15
    Cisco states that for network topologies using firewalls within a customer premise the administrator must allow the media source and destination port ranges inside the network for the media to flow, and gives the Webex App example of allowing audio 8500 to 8599 and video 8600 to 8699 as both source and destination.
    Port Reference Information for Webex Calling · IP Subnets for Webex Calling Services, Call media to Webex Calling row · Checked 2026-09-16
  16. 16
    Where call recording is enabled the media for recorded calls is routed to the cloud and is not optimized, and Cisco states that media optimization and call recording each independently introduce a small audio delay at the beginning of a call and that together the delay is slightly longer and more noticeable to customers.
    Webex Calling media optimization with Interactive Connectivity Establishment (ICE) · Prerequisites and limitations, call recording paragraphs · Checked 2026-09-16
  17. 17
    The Webex Calling media source port ranges differ by device class: devices use 19560 to 19661, Room Series devices use 52050 to 52099 for audio and 52200 to 52299 for video, VG400 analog telephone adapters use 19560 to 19849, and the Webex App uses 8500 to 8599 for audio and 8600 to 8699 for video.
    Port Reference Information for Webex Calling · IP Subnets for Webex Calling Services, device rows read as cells · Checked 2026-09-16
  18. 18
    Webex Calling media optimization is supported across desk phones excluding DECT and analog telephone adapter devices, the Webex App, and the Local Gateway solution, and is enabled by default on desk phones and the Webex App without configuration.
    Webex Calling media optimization with Interactive Connectivity Establishment (ICE) · Prerequisites and limitations, first 3 paragraphs · Checked 2026-09-16
  19. 19
    Signalling data is always sent to the Webex Calling cloud to route calls and an active internet connection is always required to make Webex Calling calls; media optimization changes only the media path, which Cisco notes makes up most of a call's traffic.
    Webex Calling media optimization with Interactive Connectivity Establishment (ICE) · Prerequisites and limitations, routing paragraph · Checked 2026-09-16
  20. 20
    Cisco states that calls can only be optimized within a single organisation and that for interorganization calls media must flow through the PSTN for regulatory reasons.
    Webex Calling media optimization with Interactive Connectivity Establishment (ICE) · Prerequisites and limitations, organisation paragraph · Checked 2026-09-16
  21. 21
    Cisco recommends turning off the SIP Application Layer Gateway or similar function on any SIP aware router or firewall, stating that although all Webex Calling traffic is encrypted certain SIP ALG implementations can cause issues with firewall traversal.
    Port Reference Information for Webex Calling · SIP Application Layer Gateway · Checked 2026-09-16
  22. 22
    The Webex Calling port reference revision history records that on 7 September 2026 the phone's source port range was expanded from 5060 to 5080 into 5060 to 5280 to accommodate an updated Cisco feature enabling support for up to 130 lines.
    Port Reference Information for Webex Calling · Document revision history, 7 September 2026 entry · Checked 2026-09-16

Documents

tier 2 current vendor documentation

Cisco Preferred Architecture for Webex Calling — Design Overview

Cisco Systems, Inc. (CTG TME) · 2025-08 · accessed 2026-09-16

tier 2 current vendor documentation

Port Reference Information for Webex Calling

Cisco Systems, Inc. (help.webex.com) · 2026-09-08 · accessed 2026-09-16

tier 2 current vendor documentation

Webex Calling media optimization with Interactive Connectivity Establishment (ICE)

Cisco Systems, Inc. (help.webex.com) · 2026-08-17 · accessed 2026-09-16

Cite this page

APA

WarmTransfer. (2026, September 16). Webex Calling ICE media path optimization. WarmTransfer. https://warmtransfer.net/knowledge/webex-calling-media-optimization

BibTeX

@misc{warmtransfer-webex-calling-media-optimization,
  title  = {Webex Calling ICE media path optimization},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-calling-media-optimization},
  note   = {Verified 2026-09-16}
}