Three steps to ship SIP / PSTN in your pilot
Point your SIP trunk
Configure your SIP trunk to route inbound calls to the Nexora agent endpoint via SIP INVITE. Authenticate with mutual TLS or IP allowlisting. No carrier-side custom development required — standard SIP is enough.
Negotiate codec and routing
The agent negotiates G.711 or Opus per the trunk's preferences and selects the regional Nexora point-of-presence closest to your carrier. Audio path stays inside the locked-market region (NZ/AU/US/UK/EU).
Transfer or hand off
When the conversation needs a human, the agent issues a SIP REFER to transfer the call to your contact-centre queue. The transcript and signal events are delivered alongside via webhook so the human picks up context-aware.
Common SIP / PSTN use cases
Inbound call deflection on a corporate SIP trunk, with call transfer to a human queue via SIP REFER when escalation is needed.
Outbound dialer campaigns originating from your PSTN carrier, with the same agent persona running across all calls.
Carrier-agnostic deployments that avoid vendor lock-in: SIP is the integration, the carrier is interchangeable.
SIP — INVITE payload from carrier to Nexora
Stylised example — not a runnable script. Endpoints, payload shapes, and authentication are documented in the integration runbook shipped during the pilot.
Common questions
Which SIP trunk providers are supported?
Any standards-compliant SIP trunk. We've deployed against the major NZ, AU, US, UK, and EU carriers — both incumbents and CPaaS providers. SIP is the protocol; the carrier is your choice. We don't require a particular vendor, and we don't impose minimums on your existing carrier relationship.
Does the SIP integration support DTMF input?
Yes. DTMF (touch-tone) input is supported over RFC 2833 / RFC 4733 in-band signalling. The agent can prompt for a reference number or account ID and accept it via key-press if the customer prefers, or accept it spoken — whichever they choose, the same code path handles it.
Where is the audio media path?
The Nexora audio plane runs in points-of-presence in the five locked markets (NZ, AU, US, UK, EU). The agent selects the closest PoP to your carrier, so audio stays inside the region wherever possible. Multi-region routing rules let you pin audio to a specific region for residency requirements.
Can the agent hand off to a SIP-based contact centre?
Yes. The agent issues a SIP REFER (RFC 3515) to transfer the call to your contact-centre queue, your switchboard, or a specific agent extension. The transcript and signal events are delivered alongside via webhook so the human picks up the conversation with full context.
Pilot in 14 days. Live in 30.
A 30-minute scoping call. We bring the SIP / PSTN integration patterns. You bring the system credentials and the first use case.