Fixed SIP IP

Fixed SIP IP is a paid concurrency plan for connections that need a stable public SIP service address for carrier allowlisting. The shared plan uses a separately managed edge pool. Tenants share that pool and its service address; the address is not a server or a public address reserved for one tenant.

Availability

Fixed SIP IP checkout is available only when the shared service is enabled and the authenticated billing and setup views report that the pool is ready. Use the public pricing response for the current Fixed SIP amount, interval, and minimum slot count. For Exclusive SIP IP, the public pricing response also reports current qualified stock and price availability; the authenticated billing view confirms that checkout can start for the tenant.

Shared and exclusive addresses

Option	Address	Billing	Availability
Fixed SIP IP	One service address shared by the enabled fixed edge pool	Alternative primary concurrency plan, billed per purchased concurrent call slot	Available when the shared service is enabled and the authenticated pool readiness check passes
Exclusive SIP IP	One address assigned to one tenant from available purchased inventory	Add-on to Fixed SIP IP, billed per address	Requires an active Fixed SIP IP subscription, configured price, and available qualified inventory

An Exclusive SIP IP is an add-on to Fixed SIP IP, not a second shared pool. The allocator uses qualified addresses from purchased inventory first. Network, gateway, broadcast, and unqualified rows are never customer stock. A qualified address is reserved before checkout and activated only after the matching Stripe subscription event. The tenant then uses that assigned address for provider and Retell signaling; it does not silently fall back to the shared Fixed SIP address.

How the shared pool works

When a connection is assigned to Fixed SIP IP, new SIP dialogs use the pool's service identity. The active/standby edge owner carries that identity, and a former owner is fenced from sending new signaling after it loses ownership. In-dialog requests keep the connection's recorded pool and transport binding. Existing dialogs retain their recorded route while that route and transport remain available. A hard failure of the serving edge can terminate an established TCP/TLS connection; transport survival across that failure is not guaranteed, and the client must reconnect. Standard connections continue to use the standard SIP edge pool.

The service exposes only the concurrency capacity currently assigned to the tenant's Fixed SIP IP subscription. Capacity and readiness are reconciled with the configured pool before a connection is activated; failover keeps the same shared signaling identity.

Pricing and capacity

Fixed SIP IP replaces the tenant's standard concurrency plan. It is billed for the full purchased number of concurrent call slots, with a minimum of five whole slots and integer quantities thereafter. Free, complimentary, or burst capacity does not increase Fixed SIP IP capacity. A free tenant may upgrade by buying a paid Fixed SIP IP plan, but it has no Fixed SIP IP entitlement while it remains on free capacity.

The default catalog rate is $10 per slot per month:

• five slots: $50/month;
• six slots: $60/month;
• seven slots: $70/month.

The platform administrator can change the rate. Always use GET /api/v1/public/pricing for the current Fixed amount, interval, and minimum slot count instead of treating these defaults as a quote. Use the authenticated billing and setup status for shared-pool readiness. The same public response reports Exclusive price and qualified-stock availability.

Exclusive SIP IP adds $100 per address per month by default, also administrator-configurable. At the default rates, five Fixed SIP IP slots plus one exclusive address total $150/month. Exclusive checkout is disabled when qualified inventory or the configured Stripe price is unavailable. The public pricing response exposes that state; it does not expose Stripe identifiers or tenant billing data.

Billing and activation

The application keeps standard concurrency and Fixed SIP IP as mutually exclusive primary plans. A Fixed SIP IP checkout requests a whole slot count of at least five, reserves certified shared-pool capacity, and then creates the monthly checkout session. A free or complimentary allowance does not contribute slots to that purchase. After payment, the entitlement can remain in provisioning while the service identity and capacity are reconciled; connections activate only when the pool ID, service address, and capacity are ready.

An Exclusive SIP IP checkout is available only to a tenant whose Fixed SIP IP primary subscription is active or scheduled to end after the current paid period. The application reserves one qualified purchased address before creating checkout, and a mode-matched subscription webhook activates it. Inventory, reservation, and subscription state are reconciled together so an abandoned or failed checkout does not make an address appear available prematurely.

Configure a connection

Choose Fixed SIP IP when creating or editing a SIP connection, then keep the connection's normal transport setting: UDP, TCP, or TLS. The selected transport is sent explicitly to both provider and Retell integrations for the shared or exclusive address. Fixed IP placement does not add a new transport, alter SDP or RTP, or change Retell phone-number identity, workspace, or published agent versions.

For an Exclusive SIP IP connection, the assigned address and its tenant SIP hostname become the effective signaling identity. For a shared Fixed SIP IP connection, the effective identity is the qualified pool service address. The connection response and the authenticated settings view show the identity assigned to that connection.

Carrier allowlisting

The standard and fixed identities are separate allowlist entries:

1. GET /api/v1/public/sip-network returns the current standard source addresses for carriers serving standard connections.
2. A shared Fixed SIP IP connection uses its assigned qualified pool service address.
3. An Exclusive SIP IP connection uses its assigned tenant-exclusive address.

Use the identity shown for the connection when updating the carrier policy. Keep the standard source list for standard connections, and do not treat a tenant-exclusive address as the shared pool address. The API's standard source list remains authoritative for standard connections.

Cancellation, release, and downgrade

Cancelling a paid Fixed SIP IP subscription takes effect at the current billing period's end. Until then, the entitlement and its pool reservation remain in place. After the entitlement ends, new fixed-IP calls and connections are blocked while established dialogs drain on their recorded identity; the application does not silently move them to a standard SIP address.

If an Exclusive SIP IP add-on expires while the Fixed SIP IP primary plan remains active, new dialogs move to the shared Fixed SIP identity after existing exclusive dialogs drain. The application does not silently send new traffic from the standard SIP pool. If the Fixed SIP IP primary plan expires first, dedicated connections remain blocked until the primary plan is restored or the connections are reconfigured for standard routing and an explicit downgrade completes.

To move back to standard concurrency, reconfigure Fixed SIP IP connections, allow active calls and reservations to drain, and use the downgrade control. The provider subscription must be terminal before the standard plan is activated. Exclusive SIP IP release follows its own add-on lifecycle; the address enters release/drain handling and is reusable only after paid-through expiry, active calls and registrations drain, provider bindings are removed, and platform bindings are cleared.

Fixed SIP IP changes SIP signaling identity and routing selection only. It does not anchor, transcode, record, or otherwise process RTP media.