Keep the platform you chose. Make the calls arrive properly.

AI agent platforms, contact centres and cloud PBXs all accept SIP, and each one is particular about it. Myrmur sits between the phone network and your platform, and makes every call arrive the way that platform expects.

AI agent platforms.

Real-time voice AI is only as good as the call it receives. Myrmur puts the right identifiers in the right place, brings your context along, and has a person to send the caller to if the AI can't pick up.

OpenAI Realtime

Expects your project ID in the SIP request address, and TLS for signalling.

A header rule writes your project ID where the dialled number would be. No proxy of your own.
TLS with the certificate checked on every call.
Your X- headers reach the incoming-call webhook, so your code knows the number and the customer before it accepts.

ElevenLabs Agents

Matches the number in the request address to the number you imported, exactly, and exposes X- headers as dynamic variables.

The dialled number always goes out in the same international form.
X-Account-Ref becomes {{sip_account_ref}} in your agent's prompt, with no code in between.
Allow one Myrmur delivery address instead of leaving the trunk open.

Any SIP-ready AI

Most voice AI platforms take calls on a SIP address and read context from headers.

Point a server list at the platform's SIP address over UDP, TCP or TLS.
Send the number, the caller and your own references as headers.
Keep your people's phone system next on the list.

Contact centres.

Bring-your-own-carrier contact centres need to know which trunk a call belongs to, and your flows are better when they know more about the call. Genesys Cloud is a good example.

Lands on the right trunk: Genesys Cloud matches calls to a trunk by domain name, trunk group, dialled number or a termination header. Myrmur can add the header as a fixed value for every number on a list.
Context for your flows: Architect can read the raw SIP headers, so flows can branch on the account, the dialled number or the caller you sent along.
Spread and fail over: Share calls across your contact centre's addresses by priority and weight. A silent address is skipped in about two seconds.
One place to look: When a call goes missing, the delivery attempts show what the contact centre answered, so it's a lookup, not a ticket to two vendors.

Sent to the contact centre
INVITE sip:+61255504817@your-byoc-trunk
From: "Jordan Lee" <sip:+61491570110@myrmur>
X-Inbound-Trunk: harbour-au-01
X-Account-Ref: harbour-support
X-Called-Number: +61255504817

Cloud PBX.

Cloud PBXs such as 3CX, Vodia and Yeastar route an incoming call by matching its DID against their inbound rules, and the match has to be exact. Myrmur makes sure it is, on every call.

DIDs that match the first time: The dialled number is written the same way in the request address and the To header, so a rule written as +61255504817 always matches.
Diversion when it's needed: Some systems read the DID from the Diversion header. One action adds it.
Two sites, no double-ringing: Primary first, second site next. A busy signal stays busy, so a declined call never rings another office.
Proof when the PBX says it never saw the call: The delivery attempts show what the PBX answered, even if it never logged the call.

Sent to the PBX
INVITE sip:+61255504817@pbx.example.com.au
To: <sip:+61255504817@pbx.example.com.au>
From: "Jordan Lee" <sip:+61491570110@myrmur>
Diversion: <sip:+61255504817@myrmur>

Patterns people use.

A server list can hold different platforms at once. That opens up a few things a plain trunk can't do.

AI first, people second

Put your AI platform at priority 1 and your phone system at priority 2. When the AI doesn't pick up or errors, the caller reaches a person instead of a failure tone.

Compare two AIs on live calls

Put two AI platforms on the same priority with a share of 50 each. Real callers split between them, and each attempt shows which one took the call.

Move platforms gradually

Moving contact centres? Start the new one on a small share, raise it as confidence grows, and keep the numbers where they are throughout.

Connecting a platform.

It's the same four steps whatever sits at the other end, and all of it happens in the portal.

Add the platform as a serverIts SIP address, the connection type, a ring time, a priority and a share. On the platform's side, allow Myrmur's delivery and media addresses.
Add header rules if it needs themProject IDs, number formats, trunk identifiers and your own references. Preview the result with a pasted INVITE before saving.
Point your numbers at the listEach number keeps its current destination until the list is confirmed, then switches on its own.
Watch the first calls landDelivery attempts show every server tried, what it answered and what the rules did.

Bring the platform you run. We'll bring the calls.

Myrmur is opening now, by invitation. Tell us what you run and where your calls need to land, and we'll set up your first numbers and route them with you.

Request access Sign in to the portal