What does Direct Routing with IPComms cost per user?

There is no per-user fee. You pay per minute ($0.010 outbound, $0.009 inbound in the US and Canada), $1.50 per number per month, and nothing per channel. A user placing 300 outbound minutes a month costs $3.00 in usage plus their number. Compare that with the Microsoft calling plan quote you were given.

Do I need to buy an SBC?

No. IPComms is the Direct Routing SBC: Teams pairs with our East and West points of presence directly. If you already own a certified SBC (AudioCodes Mediant, Ribbon, Oracle/Acme Packet, Cisco CUBE) you can keep it in the path; notes for each are on this page.

Is the call encrypted end to end?

Teams to IPComms is TLS with SRTP, as Microsoft requires. IPComms to our upstream carriers is also SIP over TLS with SRTP. If you bring your own SBC, its leg to us can be TLS 5061 with SRTP or plain 5060 with RTP; we recommend TLS.

Can I keep my existing numbers?

Yes. Port them in at $5.00 per number and route them to your Teams trunk. Toll-free numbers port too.

Is there a concurrent-call limit?

There is no per-channel fee and no set channel count on the trunk. New accounts start with a fraud-protection limit that support raises on request.

What about E911 for Teams users?

Each number can carry a dispatchable location for $2.50 per month, meeting Kari’s Law and RAY BAUM’S Act. Teams dynamic emergency calling still needs your own location configuration in Teams.

SIP trunking / Microsoft Teams

Microsoft Teams Direct Routing

Pair Microsoft Teams directly with our East and West points of presence over TLS and SRTP: we are the Direct Routing SBC, so there is none to buy. $0.010 per minute outbound, $0.009 inbound, $0 per channel, no term contract. Prefer your own AudioCodes, Ribbon, Oracle or Cisco SBC? Configurations below.

Rates

Item	Price
Outbound calling, US and Canada	$0.010 / min
Inbound to your numbers	$0.009 / min
Per channel / concurrent call	$0
Local number, US	$1.50 / month, $1.00 setup
Toll-free number	$2.00 / month, $1.00 setup
Toll-free inbound	$0.020 / min
E911, per number	$2.50 / month
Port a number in	$5.00 one-time
Term contract	None

Full rate sheet: SIP trunking pricing

How it connects

Microsoft Teams pairs with both IPComms points of presence over TLS with SRTP media. From there, calls leave to our upstream carriers over SIP TLS with SRTP as well: the encrypted path does not end at our edge. Inbound calls to your numbers are delivered to both points of presence.

One trunk, two points of presence, encrypted on both legs.

Specifications

Signaling: SIP over UDP or TCP on 5060; TLS on 5061
TLS: TLS 1.2 (ECDHE-ECDSA suites) and TLS 1.3 Server certificate chains to ISRG Root X1. Trust the root, not an intermediate.
Media: RTP, or SRTP (SDES, RTP/SAVP) when signaling is TLS
Codecs: G.711 µ-law, G.711 A-law, G.729
Pairing: Direct: your Microsoft 365 tenant is paired with the IPComms SBC FQDN we assign to you. Own SBC: IP allow-list of its public address, or digest registration.
Number format: Per trunk: +1E.164, 1NPANXXXXXX or 10-digit, for called and calling numbers
Points of presence: Two, geographically separate (US East, US West). Teams is paired with both; inbound calls are delivered to both.
Upstream: Multiple carriers, reached over SIP TLS with SRTP media; automatic failover on the outbound path
Caller ID: Any number on your account; per-trunk default; CNAM on inbound optional
STIR/SHAKEN: Every call is signed at A attestation, outbound and inbound
E911: Dispatchable location per number (Kari’s Law, RAY BAUM’S Act)

Bring your own SBC

Optional. If you already run a certified SBC and want it in the path, connect it to us like any SIP trunk. Carrier-side settings for the SBCs we see most; the Teams side is covered in the setup guide.

Cisco CUBE (IOS-XE)

Full walkthrough with dial-peers, TLS trustpoint and SRTP: Cisco CUBE SIP trunk guide.

Parameters your trunk uses (values are in your portal):

session target      ipv4:<your trunk host>:5061   ! or dns:<your-domain>.s1.ipcomms.net
session transport   tcp tls
srtp                                          ! SDES
codec               g711ulaw
crypto pki trustpool policy → revocation-check none   ! IOS-XE cannot complete revocation on this chain

IOS-XE validates the chain through its built-in trustpool; set revocation-check none on the trustpool policy or the TLS handshake fails with bad_certificate after a successful chain check.

AudioCodes Mediant

Use the Teams Direct Routing setup guide for the Teams side. Toward IPComms: Proxy Set to your trunk host on 5061, transport TLS, SRTP Enable (SDES), coder G.711U-law, IP Profile with RTP/SAVP. Authenticate by registering with your trunk credentials, or send us the Mediant’s public IP for the allow-list.

Ribbon SBC (SWe Lite / 1000 / 2000)

Signaling Group toward IPComms: FQDN or IP of your trunk host, port 5061, TLS, media SRTP (SDES), codec G.711u. Trust ISRG Root X1 in the SBC certificate store. Either register with credentials or allow-list the SBC public IP.

Oracle / Acme Packet

Session agent for your trunk host on 5061 with TLS profile (TLS 1.2 or 1.3), media security policy SDES, PCMU/PCMA. IP allow-list or digest registration.

Setup steps

Request the Teams trunk. Use the form below or sign up in the portal. A SIP engineer sends you the SBC FQDN for your Microsoft 365 tenant and the exact entries Teams needs, within one business day.
Add the domain in Microsoft 365. Enter the assigned domain in the Microsoft 365 admin center as instructed; at least one licensed user must be assigned to it for Teams to accept the SBC.
Pair the SBC in Teams. In Teams admin center or PowerShell (New-CsOnlinePSTNGateway) add the IPComms SBC FQDN on port 5061. Both points of presence answer on it; it shows as active once Teams sees OPTIONS responses.
Voice routing. Create a PSTN usage, a voice route matching your dial plan, and a voice routing policy that uses the SBC.
Assign users and test. Enable Enterprise Voice and the routing policy per user, assign numbers, and place inbound and outbound test calls from the Teams client.

Typical time from trunk creation to a working Teams call, with an SBC already deployed: under an hour. Porting existing numbers runs in parallel and does not block testing.

Numbers, porting, E911

US local numbers at $1.50 a month, Canadian at $2.50; toll-free at $2.00. Port your existing numbers in at $5.00 each and route them to the Teams trunk. E911 with a dispatchable location per number is $2.50 a month and satisfies Kari’s Law and RAY BAUM’S Act; Teams’ own dynamic emergency calling is configured on the Teams side.

Questions engineers ask

What does Direct Routing with IPComms cost per user?: There is no per-user fee. You pay per minute ($0.010 outbound, $0.009 inbound in the US and Canada), $1.50 per number per month, and nothing per channel. A user placing 300 outbound minutes a month costs $3.00 in usage plus their number. Compare that with the Microsoft calling plan quote you were given.
Do I need to buy an SBC?: No. IPComms is the Direct Routing SBC: Teams pairs with our East and West points of presence directly. If you already own a certified SBC (AudioCodes Mediant, Ribbon, Oracle/Acme Packet, Cisco CUBE) you can keep it in the path; notes for each are on this page.
Is the call encrypted end to end?: Teams to IPComms is TLS with SRTP, as Microsoft requires. IPComms to our upstream carriers is also SIP over TLS with SRTP. If you bring your own SBC, its leg to us can be TLS 5061 with SRTP or plain 5060 with RTP; we recommend TLS.
Can I keep my existing numbers?: Yes. Port them in at $5.00 per number and route them to your Teams trunk. Toll-free numbers port too.
Is there a concurrent-call limit?: There is no per-channel fee and no set channel count on the trunk. New accounts start with a fraud-protection limit that support raises on request.
What about E911 for Teams users?: Each number can carry a dispatchable location for $2.50 per month, meeting Kari’s Law and RAY BAUM’S Act. Teams dynamic emergency calling still needs your own location configuration in Teams.