How Hosted Call Signing
actually works.

Three ways to integrate with Hosted Call Signing — Outbound Proxy, a request/response API, and SIP 302 redirect — and exactly how each one gets a signed Identity header onto your calls.

Three ways to integrate

Select one below to see exactly how it works.

Outbound Proxy

Your switch routes signaling through Telonium directly — there's no per-call request/response.

Your SBC or softswitch is configured to send outbound call signaling for your signed OCN(s) to a dedicated signing hostname instead of sending it straight to your upstream carrier. Telonium’s signing servers sit in that path as an outbound proxy: they receive the INVITE, attach a signed Identity header using the certificate issued to your OCN, and pass the call on toward its destination.

One-time setup

  1. 01

    Get your assigned hostname

    Telonium links your OCN to a dedicated signing account and gives you a signing hostname and IP to route traffic to.

  2. 02

    Whitelist your source IP

    Add the IP your switch originates calls from in the dashboard’s IP Management page — Telonium only accepts signaling from whitelisted sources.

Your SBC / Softswitch

Originates the call. Sends the unsigned INVITE to your assigned signing hostname.

unsigned INVITE

Telonium Signing Proxy

Verifies your source IP, looks up your OCN's certificate, and injects a signed Identity header.

signed INVITE

Terminating Carrier

Receives the signed call and verifies the Identity header normally.

INVITE arriving from your switch
INVITE sip:+15551234567@carrier.example SIP/2.0
From: <sip:+15559876543@your-switch.example>
To: <sip:+15551234567@carrier.example>
Contact: <sip:your-switch.example>
...no Identity header...
INVITE forwarded by the signing proxy
INVITE sip:+15551234567@carrier.example SIP/2.0
From: <sip:+15559876543@your-switch.example>
To: <sip:+15551234567@carrier.example>
Contact: <sip:your-switch.example>
Identity: eyJhbGciOiJFUzI1NiIsInBwdCI6InNoYWtlbiIsInR5cCI6InBhc3Nwb3J0In0...;
          info=<https://admin.stirshaken.tel/certs/8f2a1c6d93e7.pem>;alg=ES256;ppt=shaken

What you configure

  • Pick one integration method per OCN — Outbound Proxy, API, or 302 Redirect.
  • Whitelist every source IP your switch originates traffic from.
  • Set your default attestation level (A, B, or C) in the dashboard.
  • Monitor signing volume and individual requests from the request logs page.

Ready to start signing?

Get an approved OCN and tell us which integration method fits your switch.