Edge Collaboration · Expressway

Expressway B2B Video Calling Planner

Plan inter-company video calls through Expressway: search rules, SIP URI dial patterns, encryption policy, DNS/SRV records, and firewall/cert requirements for B2B interop.

By Faz Karim · 30 yrs Cisco UCLast updated 2026-04-20
What this tool does

Call any video endpoint on the internet

B2B (business-to-business) video calling lets your endpoints dial SIP URIs at partner organizations (user@partner.com) through Expressway. This planner configures search rules, DNS, encryption, and firewall for secure interop with any SIP-reachable org — including room systems, Microsoft Teams (via Cloud Video Interop), and Google Meet.

Plan B2B calling

Inputs

Your B2B plan

Set inputs, click Plan B2B calling.

How to read your result

Five config layers

1

DNS

SRV for receiving B2B calls.

2

Search

Rules to route outbound SIP URIs.

3

Zones

DNS zone for outbound lookup.

4

Security

TLS, SRTP, ACL.

5

Test

Known-good test URIs.

Deep dive

Three moving parts in B2B

Inbound: when you@yourorg.com is called, the caller's Expressway looks up _sips._tcp.yourorg.com and/or _sip._tcp.yourorg.com in public DNS. These records should point to your Expressway-E. Publish TLS (5061) preferred, TCP (5060) as fallback. Skipping the SIP SRV records is the #1 reason inbound B2B fails — partners fall back to DNS A-record lookup which you don't control.

Outbound: your endpoint dials user@partner.com. On CUCM this matches the SIP URI dial pattern. CUCM forwards to Expressway-C via SIP trunk. Expressway-C has a search rule matching the partner domain (or .* for any) that forwards via Traversal zone to Expressway-E. Expressway-E uses its DNS zone to lookup _sips._tcp.partner.com, connect, and bridge media. If partner doesn't have SIP SRV, Expressway-E falls back to MX record, then A record.

Teams interop: Microsoft Teams does not natively support standard SIP B2B. You need either (a) a Cloud Video Interop gateway like Pexip, Poly RealConnect, or BlueJeans Gateway, or (b) Direct Routing with a SIP-aware SBC. Option (a) is the cleanest for organic calling; option (b) is more complex but gives you full control. Skype for Business federation rules are deprecated — do not rely on them in 2026+.

FK
Faz Karim30 years Cisco Network · UC · Data Center · LinkedIn
FAQ

Common questions

Do I need additional licenses for B2B?

Traversal licenses on Expressway-E and RMS (Rich Media Session) for transcoding. No extra Cisco licensing for the pattern.

Can I restrict which domains can call us?

Yes — use Expressway-E CPL (Call Policy Language) rules or Search rule ACLs.

What about STIR/SHAKEN for B2B?

SIP video B2B doesn't use STIR/SHAKEN — that's voice/PSTN only. Rely on TLS cert validation.

Zoom interop?

Zoom has a SIP Connector — dial meetingid@zm.cisco.com or similar bridge URIs.

Google Meet?

Supported via Pexip or Google's own SIP gateway. Dial format: meet-id@google.com.

Worked examples

Three B2B scenarios

Vendor calls us

Law firm calls our Webex Room.

Their Expressway → our _sips._tcp SRV → Exp-E → Exp-C → CUCM → endpoint.
Works if SRV + cert are right.

We call Teams meeting

Sales calls Teams room.

CUCM → Exp-C → Exp-E (DNS zone) → Pexip CVI → Teams.
Requires CVI subscription.

Two-way SIP interop

Integration with 3 partners.

CPL + per-partner TLS verify + agreed dial patterns.
Document per-partner.
Sources verified against current Cisco guidance

Citations

Related tools

You might also need

Adding B2B video?

Our UC Modernization Sprint brings up B2B video end-to-end: Expressway, CUCM routing, Teams interop, cert coord, and partner validation.

$25K–$75Kturnkey
Book a 30-min call →Or email info@famoustec.com