Home / Session border controllers / Call admission stays on the datasheet
Call admission stays on the datasheet
An SBC can refuse a new INVITE when its configured budget is exhausted. The number itself is platform-specific.
Learn in 5 minutes
- Describe admission as a local policy
- Read 503 as one documented failure response
- Refuse invented capacity formulas
Visual
The SIP code is standard. The session budget is not.
Worked example
Read the refusal Step the ladder. Which response refuses the call?
- Play until the final response.
- Read the status code.
- Note that no session count is inside SIP.
Fault
Operators keep raising an undocumented calls-per-second number. New INVITEs still receive 503.
The message is a local refusal. It does not contain a formula.
Quiz
Ecosystem
Glossary, sister systems, and the integration seam for this room.
AI omni-channel agents A voice bot still needs a session. SIP creates, modifies, and ends sessions. Omni-channel, in the contact-center sense, means the same contact can also live on chat or another digital channel. Those channels do not replace the voice session. On Amazon Connect the platform owns the managed PSTN voice channel. Bridging an outside carrier into Connect with a Chime Voice Connector is not a supported pattern unless AWS reviews it. When an SBC forks the voice leg to a recorder, that fork is SIPREC, a different plane from the customer dialog.
AI agents A voice bot still needs a session. On Amazon Connect the platform owns the managed PSTN voice channel. Bridging an outside carrier into Connect with a Chime Voice Connector is not a supported pattern unless AWS reviews it. The FreeSWITCH manual page also describes SignalWire, founded by the FreeSWITCH team, as a hosted platform with AI agents behind REST APIs and SWML.
Sources and go deeper
- RFC 3261 §21 — last checked 2026-10
- RFC 5853 — last checked 2026-10
- RFC 3261 — last checked 2026-10