OpenAI makes outbound SIP calling for GPT-Live available to all organizations
OpenAI says outbound SIP calling through its Live API is now open to every organization, letting gpt-live-1 connect to phone numbers via a SIP provider.
OpenAI's API changelog says outbound SIP calling is now available to all organizations through the Live API. Developers can have gpt-live-1 place calls to a phone number through their own SIP provider. The entry is marked as a feature release rather than a new model, and it sits under the v1/live/sessions endpoint. The changelog itself gives only two sentences of detail and points to OpenAI's SIP guide for setup.
The guide shows that the call is started by creating a session, not by waiting for an incoming call. The developer supplies a trunk configuration with each request. That includes the destination phone number in E.164 format, such as +14155550123, a provider endpoint beginning with sips: for TLS signaling, digest authentication credentials, and the caller number to present to the provider. The guide says SIP URI destinations aren't supported, so the target must be a phone number. The provider endpoint must omit credentials, paths and URI parameters from the URL, so the username and password go in the separate auth fields instead. The provider handles the connection to the phone network, while GPT-Live carries the conversation once the call is up.
Media setup has its own requirements. The guide asks for a trunk that supports TLS signaling and SDES-SRTP media, and it tells developers to enable SRTP in their provider's settings before placing a call. The general SIP page says GPT-Live requires SRTP for call audio, so a trunk that sends unencrypted audio would not be a workable configuration. The guide also notes that outbound calling is offered through the Live API, not through the call-creation endpoint in the Realtime API.
The inbound-call instructions in the same guide involve more steps than the outbound ones. An inbound call involves a webhook subscribed to live.transport.incoming and a decision to accept or reject the call. A sideband WebSocket is available for the backend when it needs events or commands. Those instructions also ask developers to confirm that GPT-Live SIP support is enabled for their project before using the flow. The outbound section doesn't include that step. Neither the changelog nor the guide says whether outbound calls depend on the same project-level enablement. The changelog also doesn't describe pricing or call limits for the new feature.
What changed
Outbound SIP calling through the Live API is now available to all organizations, letting gpt-live-1 place calls to phone numbers through a developer's own SIP provider.
Type: New capability · Applies to: gpt-live-1, Live API, v1/live/sessions
Why it matters
Companies building voice agents for outbound calls can now connect GPT-Live to telephone infrastructure they already use, without waiting for access to be granted.
What you can do
Teams evaluating voice automation for outbound calls can review the SIP guide and test gpt-live-1 with their existing SIP provider.
Original source
Where we saw it
OpenAI API changelog
AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it. How it works