Expressway business-to-business calling
Verified 2026-09-25 · 60 sources · tier 1–5
Cisco Expressway business-to-business (B2B) calling routes real-time communications across organizational boundaries using public DNS records and firewall traversal 3555. Deployments use an Expressway-E as the traversal server and an Expressway-C as the traversal client to establish secure traversal paths into call-control systems such as Cisco Unified Communications Manager 588.
DNS and URI resolution
For inbound SIP B2B calls, SRV records for SIP call routing must be created on public DNS servers so other organizations can locate the Expressway-E 35. External systems reaching a domain by URI dialing require the domain to publish the appropriate DNS SRV and A or AAAA records 25. Cisco's example public DNS for the Expressway-E publishes _sips._tcp on port 5061, _sip._tcp on port 5060, and _sip._udp on port 5060, with each record targeting the Expressway-E host A record 34. SIP over UDP is disabled by default on the Expressway, meaning a published _sip._udp record does not work unless UDP is explicitly enabled 47.
For H.323 routing, Cisco's example public DNS publishes _h323cs._tcp on port 1720 for call signaling, along with _h323ls._udp and _h323rs._udp on port 1719, all targeting the Expressway-E 33. The Expressway uses _h323ls._udp SRV records for H.323 location services and _h323cs._tcp SRV records for H.323 call signaling 22. In a cluster of Expressway-Es, DNS A and SRV records must be set up for each peer in the cluster 4.
For URI dialing, the Expressway queries NAPTR records first, then SRV records, and finally A or AAAA records 59. Under RFC 3263, if no NAPTR records are found, a SIP client constructs SRV queries for the transports it supports 39. When no SRV records exist, the client performs an A or AAAA lookup of the domain and uses the transport's default port, which is 5060, or 5061 for TLS 38.
Zones and firewall traversal
Expressway zone types comprise Neighbor, Traversal client, Traversal server, DNS, ENUM, and Unified Communications traversal, in addition to a built-in Default Zone 60. Unsolicited inbound B2B calls arrive in the Default Zone, which represents incoming calls from endpoints or devices that are unregistered or unrecognized 12. All calls through the Default Zone consume Rich Media Session (RMS) licenses, so appropriate zones and rules should be created to avoid needless RMS consumption 13. Administrators use Default Zone access rules (Configuration > Zones > Default Zone access rules) to control which external systems may connect to the Expressway over SIP TLS via the Default Zone 11.
For outbound routing, a DNS zone is used to search for externally hosted systems, and a DNS search rule defines when that zone is searched 16. Cisco's example DNS zone sets H.323 mode to On, SIP mode to On, fallback transport to TCP, and Include address record to Off 15. A DNS zone's Fallback transport configures the SIP transport used when NAPTR records and SIP URI parameters provide no preferred transport 19. When Include address record is enabled on a DNS zone, the Expressway queries for A or AAAA records; if any are found, it does not query lower-priority zones 26. The Modify DNS request option routes outbound SIP calls to a manually specified SIP domain instead of the domain in the dialed destination 31. The TLS verify setting controls whether the Expressway checks the X.509 certificate of the destination server returned by the DNS lookup 17.
Firewall traversal operates by having a traversal client maintain an open connection through the firewall to a designated port on the traversal server using keepalives, enabling the server to forward incoming call requests over that connection 55. In a B2B deployment, Expressway-C acts as the traversal client and Expressway-E acts as the traversal server 58. Both systems must be Cisco Expressway units; neither can be a Cisco VCS 54. Traversal clients must always authenticate to the traversal server, and each traversal client zone specifies a username and password 52.
For H.323 firewall traversal, a traversal zone can use either Assent or H.460.18, whereas SIP traversal uses Assent over a TCP/TLS connection from client to server 23. Cisco guidance numbers traversal zone ports starting from TCP 7001 for SIP and UDP 6001 for H.323, incrementing by 1 for each additional traversal zone 57. Cisco's B2B technote uses a traversal zone separate from the Unified Communications (MRA) traversal zone, using a different port such as 7003 rather than 7001 44. Expressway supports traversal chaining, where the first Expressway-E is the traversal server to Expressway-C and a traversal client to a second Expressway-E 53. The default traversal media port range is 36000 to 59999 56. Cisco recommends disabling any H.323 and SIP Application Layer Gateway (ALG) protocol support on the firewall in front of the Expressway 21. Furthermore, Expressway-E and Expressway-C must not share an address behind NAT, because the firewall cannot distinguish between them 32.
Dial plan, search rules, and call routing
The Expressway call routing sequence applies pre-search transforms first, followed by Call Policy, then User Policy (FindMe), and finally search rules; it restarts the entire process whenever a new alias results 40. The platform supports up to 100 pre-search transforms with unique priorities from 1 to 65534, and only 1 transform can match per search 49. Pre-search transforms normalize aliases from H.323 and SIP devices before zones are searched, such as appending the organization's domain to an E.164 alias to form a SIP URI 50.
Search rule priorities range from 1 to 2000, with lower numbers indicating higher priority; every applicable target is queried when multiple rules match at the same priority 41. On a successful match, selecting Stop halts the processing of lower-priority search rules, though other rules at the same priority continue to apply 43. A search rule's Source can be set to Any (including unregistered devices and the public internet), All zones (local zone and configured zones only), Local Zone (registered devices only), or Named 42. The Request must be authenticated option restricts a search rule to requests originating from authenticated devices 37. Cisco advises avoiding the Any wildcard for a search rule's Source to minimize toll-fraud risk 2.
In Cisco's basic configuration example, rule priorities are configured as follows:
- Local-zone rule: priority 50, set to Continue on successful match 18.
- Traversal-zone rule: priority 100, set to Continue on successful match 18.
- DNS-zone rule: priority 150, set to Continue on successful match 18.
Cisco's example DNS-zone search rule uses a negative-lookahead regular expression so calls to the organization's own domain are never looked up on public DNS, while calls to other domains are 14. Hop count values range from 1 to 255 with a default of 15, decreasing by 1 each time a request is forwarded; for URI or ENUM dialing, the hop count of the DNS or ENUM zone is used 24.
The Expressway's H.323-SIP interworking mode can be set to Off, Registered only (interworking only if at least 1 endpoint is locally registered), or On (interworking regardless of registration) 29. The default interworking mode is Registered only, and Cisco recommends leaving it at that setting 28.
Unified CM integration
Cisco's B2B technote specifies that the Unified CM SIP trunk to Expressway-C listens on non-standard ports 6060 for SIP/TCP and 6061 for SIP/TLS, separating B2B traffic from MRA edge traffic 8. The technote also uses a transform on Expressway-C to remove the port from the URI in incoming INVITE requests received from Unified CM 51.
When securing the connection with SIP/TLS between Unified CM and Expressway-C, the Expressway-C server certificate or its CA root must be placed into the Unified CM trust store on all servers, and the CallManager certificate or its CA root must be placed into the Expressway-C trusted CA list 7.
Toll-fraud mitigation and security
Call Policy modes on the Expressway include Off, Local CPL (using web-configured rules or an uploaded CPL script, which are mutually exclusive), and Policy service (where an external service makes call decisions) 3. If Local CPL is enabled without any policy configured or uploaded, a default policy automatically applies that allows all calls 30. Toll-fraud CPL is applied under Configuration > Call Policy > Configuration by choosing Call policy mode Local CPL and uploading a CPL file; the Expressway validates the file and rejects malformed scripts with an XML invalid error 6. Cisco's example toll-fraud CPL rejects gateway-zone calls that would hairpin back out of an ISDN gateway with status 403, and can optionally reject unauthenticated callers dialing the gateway prefix 9 5.
Cisco's Collaboration 14 Preferred Architecture recommends implementing CPL rules to allow or reject calls from the Default Zone in B2B deployments, such as rejecting inbound B2B calls directed to 9-prefixed destinations to block unauthorized PSTN routing 9. The Preferred Architecture also recommends Expressway-E automated detection, which blocks an offending source IP address in the internal firewall for a configurable period following a configurable number of rejections 1. Additionally, the architecture cites a SIP rate-limiting capability configured with maximum connections per second and maximum burst size to mitigate toll fraud 45. In the field, reports describe internet bots sending SIP INVITE and OPTIONS messages to Expressway-E at rates of around 2 to 3 per second, cycling through varied called patterns to find PSTN routes while spoofing the organization's domain or the Expressway IP address as the caller 20.
See also
- See also Expressway and Mobile and Remote Access.
- See also Setting up Mobile and Remote Access on Cisco Expressway.
- See also Unified CM SIP trunks and security profiles.
- See also Unified CM certificate renewal.
Applicability
Applies to: Cisco Expressway, IETF SIP, and Cisco Expressway with Unified CM. Deployments: on-premises and multi-tenant. Sources checked 2026-09-25. Cisco's B2B audio/video technote states minimum software versions of Expressway X8.1.1 and Unified CM 10.0 48. Cisco's Expressway release-note listing displays an X15.5.x release note alongside X15.4.x (dated 13 April 2026) and X15.3.x (dated 6 January 2026) 36.
What remains uncertain
See also
Related to
- Unified CM certificate renewal — B2B via Expressway-C to Unified CM over SIP/TLS needs mutual certificate trust (Expressway-C cert or CA in the Unified CM trust store and the CallManager cert or CA on Expressway-C). If either side's certificate is renewed without the other side re-trusting it the neighbor zone breaks. Proposed by this packet; not previously recorded.
Referenced by
- Unified CM SIP normalization and transparency scripts — The preinstalled vcs-interop script targets endpoints registered to TelePresence VCS; whether it applies to current Expressway trunks is not established in this packet
Sources
- 1Cisco's Preferred Architecture recommends Expressway-E automated detection, which blocks an offending source IP in the internal firewall for a configurable period after a configurable number of rejections.Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Security · Toll Fraud Mitigation > Cisco Expressway · Checked 2026-09-25
- 2Cisco advises avoiding the Any wildcard for a search rule's Source to minimise toll-fraud risk.Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing · Search rule examples (emergency/911 rule example note) · Checked 2026-09-25
- 3Expressway Call Policy mode can be Off, Local CPL (web-configured rules or an uploaded CPL script, mutually exclusive) or Policy service (an external service decides).Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing · Configuring Call Policy: Call policy mode · Checked 2026-09-25
- 4With a cluster of Expressway-Es, DNS A and SRV records must be set up for each peer in the cluster.Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - DNS Records · DNS Records: note on Expressway-E clusters · Checked 2026-09-25
- 5Cisco's example toll-fraud CPL rejects gateway-zone calls that would hairpin back out of the ISDN gateway with status 403, and can optionally reject unauthenticated callers dialling the gateway prefix 9.Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - Optional Configuration Tasks · Task 22: example CPL · Checked 2026-09-25
- 6Toll-fraud CPL is applied by setting Configuration > Call Policy > Configuration to Call policy mode Local CPL and uploading the CPL file, which the Expressway checks and rejects with an XML invalid error if malformed.Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - Optional Configuration Tasks · Task 22: Restricting access to ISDN gateways (toll-fraud prevention) · Checked 2026-09-25
- 7For SIP/TLS between Unified CM and Expressway-C, the Expressway-C server certificate or its CA root goes into the Unified CM trust store on all servers, and the CallManager certificate or its CA root goes into Expressway-C's trusted CA list.Configure Business to Business Audio/Video Calls through Expressway · Configure: certificates · Checked 2026-09-25
- 8Cisco's B2B technote has the Unified CM SIP trunk to Expressway-C listen on non-standard ports 6060 for SIP/TCP and 6061 for SIP/TLS, keeping B2B traffic apart from MRA edge traffic.Configure Business to Business Audio/Video Calls through Expressway · Configure: neighbor zone to Unified CM and Unified CM SIP trunk · Checked 2026-09-25
- 9Cisco's Collaboration 14 Preferred Architecture recommends CPL rules to allow or reject calls from the Default Zone in B2B deployments, for example rejecting inbound B2B calls to 9-prefixed destinations to block unauthorised PSTN calls.Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Security · Toll Fraud Mitigation > Cisco Expressway · Checked 2026-09-25
- 10If the target domain publishes no NAPTR records, the Expressway uses a default list of _sips._tcp, _sip._tcp and _sip._udp SRV queries for that domain.Cisco Expressway Administrator Guide (X15.2) - Dial Plan and Call Processing · URI Resolution Process Using DNS (SIP) · Checked 2026-09-25
- 11Default Zone access rules (Configuration > Zones > Default Zone access rules) control which external systems may connect to the Expressway over SIP TLS via the Default Zone.Cisco Expressway Administrator Guide (X15.4) - Zones and Neighbors · Default Zone access rules · Checked 2026-09-25
- 12The Default Zone represents incoming calls from endpoints or devices that are unregistered or not recognised, which is where unsolicited inbound B2B calls arrive.Cisco Expressway Administrator Guide (X15.4) - Zones and Neighbors · The Default Zone · Checked 2026-09-25
- 13All calls through the Default Zone consume Rich Media Session (RMS) licences, so appropriate zones and rules should be created to avoid needless RMS consumption.Cisco Expressway Administrator Guide (X15.4) - Zones and Neighbors · The Default Zone: RMS licence note · Checked 2026-09-25
- 14Cisco's example DNS-zone search rule uses a negative-lookahead regex so calls to the organisation's own domain are never looked up on public DNS, while calls to other domains are.Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - Routing Configuration · Routing Configuration: DNS zone search rule (priority 150, pattern excluding @example.com) · Checked 2026-09-25
- 15Cisco's example DNS zone uses H.323 mode On, SIP mode On, fallback transport TCP and Include address record Off.Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - Routing Configuration · Routing Configuration: DNS zone settings table · Checked 2026-09-25
- 16A DNS zone is used to search for externally hosted systems, as in business-to-business calling, and a DNS search rule defines when that zone is searched.Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - Routing Configuration · Routing Configuration: DNS zone · Checked 2026-09-25
- 17A DNS zone's TLS verify setting controls whether the Expressway checks the X.509 certificate of the destination server returned by the DNS lookup.Cisco Expressway Administrator Guide (X15.4) - Zones and Neighbors · Configuring DNS Zones: TLS verify mode · Checked 2026-09-25
- 18In Cisco's basic configuration example the local-zone rule is priority 50, the traversal-zone rule priority 100 and the DNS-zone rule priority 150, each set to Continue on successful match.Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - Routing Configuration · Routing Configuration: search rules tables · Checked 2026-09-25
- 19A DNS zone's Fallback transport sets the SIP transport used when NAPTR records and SIP URI parameters give no preferred transport.Cisco Expressway Administrator Guide (X15.4) - Zones and Neighbors · Configuring DNS Zones: Fallback transport protocol · Checked 2026-09-25
- 20Field reports describe internet bots sending SIP INVITE and OPTIONS to Expressway-E at around 2 to 3 per second, trying varied called patterns to find a PSTN route and spoofing the organisation's own domain or the Expressway IP as caller.field reportSecuring Expressway Deployment from Spam & Toll Fraud Calls · Observed attack patterns section · Checked 2026-09-25
- 21Cisco recommends turning off any H.323 and SIP protocol support (ALG) on the firewall in front of the Expressway.Cisco Expressway Administrator Guide (X15.4) - Firewall Traversal · Firewall configuration · Checked 2026-09-25
- 22The Expressway uses _h323ls._udp SRV records for H.323 location services and _h323cs._tcp SRV records for H.323 call signalling.Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing · Configuring H.323 SRV Records · Checked 2026-09-25
- 23For H.323 firewall traversal a traversal zone can use either Assent or H.460.18, while SIP traversal uses Assent over a TCP/TLS connection from client to server.Cisco Expressway Administrator Guide (X15.4) - Firewall Traversal · Firewall traversal protocols (Assent, H.460.18/19) · Checked 2026-09-25
- 24Expressway hop count ranges from 1 to 255 with a default of 15, decreasing by one each time a request is forwarded; for URI or ENUM dialling the hop count of the DNS or ENUM zone is used.Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing · Hop counts · Checked 2026-09-25
- 25For external systems to reach a domain by URI dialing, the domain must publish the appropriate DNS SRV and A/AAAA records.Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing · URI Dialing via DNS for Incoming Calls · Checked 2026-09-25
- 26When Include address record is enabled on a DNS zone, the Expressway queries for A or AAAA records, and if any are found it does not query lower-priority zones.Cisco Expressway Administrator Guide (X15.4) - Zones and Neighbors · Configuring DNS Zones: Include address record · Checked 2026-09-25
- 27With the default Registered only mode, a B2B call between a Unified CM SIP user and an external H.323-only system through Expressways with no locally registered endpoint would probably not be interworked unless the mode is changed to On.inferredCisco Expressway Administrator Guide (X15.4) - Protocols · Configuring H.323 and SIP Interworking · Checked 2026-09-25
- 28The default H.323-SIP interworking mode is Registered only, and Cisco recommends leaving it at that setting.Cisco Expressway Administrator Guide (X15.4) - Protocols · Configuring H.323 and SIP Interworking: H.323 <-> SIP interworking mode · Checked 2026-09-25
- 29The Expressway's H.323-SIP interworking mode can be Off, Registered only (interwork only if at least one endpoint is locally registered) or On (interwork regardless of registration).Cisco Expressway Administrator Guide (X15.4) - Protocols · Configuring H.323 and SIP Interworking · Checked 2026-09-25
- 30If Local CPL is enabled but no policy is configured or uploaded, a default policy is applied that allows all calls.Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing · Configuring Call Policy · Checked 2026-09-25
- 31The DNS zone's Modify DNS request option routes outbound SIP calls to a manually specified SIP domain instead of the domain in the dialled destination.Cisco Expressway Administrator Guide (X15.4) - Zones and Neighbors · Configuring DNS Zones: Modify DNS request · Checked 2026-09-25
- 33Cisco's example public DNS for H.323 publishes _h323cs._tcp on port 1720 for call signalling, plus _h323ls._udp and _h323rs._udp on port 1719, all targeting the Expressway-E.Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - DNS Records · DNS Records: public DNS records table (Expressway-E) · Checked 2026-09-25
- 34Cisco's example public DNS for the Expressway-E publishes _sips._tcp on port 5061, _sip._tcp on port 5060 and _sip._udp on port 5060, each targeting the Expressway-E host A record.Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - DNS Records · DNS Records: public DNS records table (Expressway-E) · Checked 2026-09-25
- 35For inbound SIP business-to-business calls, SRV records for SIP call routing must be created on the public DNS servers so other organisations can locate the Expressway-E.Configure Business to Business Audio/Video Calls through Expressway · Configure section: DNS SRV records for SIP call routing · Checked 2026-09-25
- 36Cisco's Expressway release-note listing shows an X15.5.x release note alongside X15.4.x (dated 13 April 2026) and X15.3.x (dated 6 January 2026).Cisco Expressway Series - Release Notes · X15.x release notes list entries · Checked 2026-09-25
- 37A search rule's Request must be authenticated option restricts the rule to requests from authenticated devices.Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing · Configuring Search Rules: Request must be authenticated · Checked 2026-09-25
- 38RFC 3263 specifies that when no SRV records exist, the client does an A or AAAA lookup of the domain and uses the transport's default port (5060, or 5061 for TLS).RFC 3263: Session Initiation Protocol (SIP): Locating SIP Servers · Section 4.2 Determining Port and IP Address · Checked 2026-09-25
- 39RFC 3263 specifies that if no NAPTR records are found, a SIP client constructs SRV queries for the transports it supports.RFC 3263: Session Initiation Protocol (SIP): Locating SIP Servers · Section 4.1 Selecting a Transport Protocol · Checked 2026-09-25
- 40The Expressway processes a call by applying pre-search transforms, then Call Policy, then User Policy (FindMe), then search rules, and restarts the process whenever a new alias results.Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing · Call Routing Process · Checked 2026-09-25
- 41Search rule priorities range from 1 to 2000, with lower numbers taking higher priority, and every applicable target is queried when several rules match at the same priority.Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing · Configuring Search Rules: Priority · Checked 2026-09-25
- 42A search rule's Source can be Any (including unregistered devices and the public internet), All zones (local zone and configured zones only), Local Zone (registered devices only) or Named.Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing · Configuring Search Rules: Source · Checked 2026-09-25
- 43On successful match, Stop halts processing of lower-priority search rules, but other rules at the same priority are still applied.Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing · Configuring Search Rules: On successful match · Checked 2026-09-25
- 44Cisco's B2B technote uses a traversal zone separate from the Unified Communications (MRA) traversal zone, on a different port such as 7003 rather than 7001.Configure Business to Business Audio/Video Calls through Expressway · Configure: traversal zone for B2B · Checked 2026-09-25
- 45Cisco's Preferred Architecture also cites a SIP rate-limiting capability, configured with a maximum connections per second and a maximum burst size, as a toll-fraud mitigation.Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Security · Toll Fraud Mitigation > Cisco Expressway · Checked 2026-09-25
- 46In the X15.4 SIP protocol configuration the default transport modes are UDP Off, TCP Off, TLS On and Mutual TLS Off.Cisco Expressway Administrator Guide (X15.4) - Protocols · Protocols > SIP > Configuring SIP (transport mode defaults) · Checked 2026-09-25
- 47SIP over UDP is disabled by default on the Expressway, so a published _sip._udp record does not work unless UDP is enabled.Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - DNS Records · DNS Records: public DNS records table, _sip._udp row note · Checked 2026-09-25
- 48Cisco's B2B audio/video technote states minimum versions of Expressway X8.1.1 and Unified CM 10.0.Configure Business to Business Audio/Video Calls through Expressway · Requirements / Components Used · Checked 2026-09-25
- 49The Expressway supports up to 100 pre-search transforms with unique priorities from 1 to 65534, and only one transform can match per search.Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing · About Pre-Search Transforms · Checked 2026-09-25
- 50Pre-search transforms normalise aliases from H.323 and SIP devices before zones are searched, for example by appending the organisation's domain to an E.164 alias to form a SIP URI.Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - Routing Configuration · Routing Configuration: Pre-search Transforms · Checked 2026-09-25
- 51The B2B technote uses a transform on Expressway-C to remove the port from the URI in INVITEs received from Unified CM.Configure Business to Business Audio/Video Calls through Expressway · Configure: Dialplan with transforms and search rules · Checked 2026-09-25
- 52Traversal clients must always authenticate to the traversal server, and each traversal client zone specifies a username and password.Cisco Expressway Administrator Guide (X15.4) - Zones and Neighbors · Configuring traversal client zones: authentication · Checked 2026-09-25
- 53Expressway supports traversal chaining, in which the first Expressway-E is the traversal server to Expressway-C and a traversal client to a second Expressway-E.Cisco Expressway Administrator Guide (X15.4) - Firewall Traversal · Firewall traversal chaining · Checked 2026-09-25
- 54Both the traversal client and the traversal server must be Cisco Expressway systems; neither can be a Cisco VCS.Cisco Expressway Administrator Guide (X15.4) - Firewall Traversal · Firewall traversal: requirements · Checked 2026-09-25
- 55A traversal client keeps a connection open through the firewall to a designated port on the traversal server using keepalives, and the server sends incoming call requests to the client over that connection.Cisco Expressway Administrator Guide (X15.4) - Firewall Traversal · How firewall traversal works · Checked 2026-09-25
- 56The default traversal media port range is 36000 to 59999.Cisco Expressway Administrator Guide (X15.4) - Firewall Traversal · Media port ranges / Traversal Subzone · Checked 2026-09-25
- 57Cisco guidance numbers traversal zone ports from TCP 7001 for SIP and UDP 6001 for H.323, incrementing by one for each additional traversal zone.Cisco Expressway Administrator Guide (X15.4) - Firewall Traversal · Ports for initial connections from traversal clients · Checked 2026-09-25
- 58In a B2B deployment Expressway-C is the traversal client and Expressway-E is the traversal server.Configure Business to Business Audio/Video Calls through Expressway · Configure: traversal zone on Expressway-C and Expressway-E · Checked 2026-09-25
- 59For URI dialing, the Expressway queries NAPTR records first, then SRV records, then A or AAAA records.Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing · URI Resolution Process Using DNS · Checked 2026-09-25
- 60Expressway zone types are Neighbor, Traversal client, Traversal server, DNS, ENUM and Unified Communications traversal, plus a built-in Default Zone.Cisco Expressway Administrator Guide (X15.4) - Zones and Neighbors · Zones and Neighbors: About zones / zone types · Checked 2026-09-25
Documents
RFC 3263: Session Initiation Protocol (SIP): Locating SIP Servers
Cisco Expressway Administrator Guide (X15.2) - Dial Plan and Call Processing
Cisco Expressway Administrator Guide (X15.4) - Dial Plan and Call Processing
Cisco Expressway Administrator Guide (X15.4) - Firewall Traversal
Cisco Expressway Administrator Guide (X15.4) - Protocols
Cisco Expressway Administrator Guide (X15.4) - Zones and Neighbors
Cisco Expressway Series - Release Notes
Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - DNS Records
Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - Optional Configuration Tasks
Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - Routing Configuration
Configure Business to Business Audio/Video Calls through Expressway
Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Security
Securing Expressway Deployment from Spam & Toll Fraud Calls
Cite this page
APA
WarmTransfer. (2026, September 25). Expressway business-to-business calling. WarmTransfer. https://warmtransfer.net/knowledge/expressway-b2b-calling
BibTeX
@misc{warmtransfer-expressway-b2b-calling,
title = {Expressway business-to-business calling},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/expressway-b2b-calling},
note = {Verified 2026-09-25}
}