Skip to main content
Belcenter AIHelp center
Configure a bot

SIP compatibility and PBX testing

Understand SIP exchanges, rejections, and practical tests with your PBX.

BeAI uses SIP to establish and terminate calls. Signalling corrections apply to manual connections, provisioning and BeAI Numbers, with no further adjustments required on your bots.

What BeAI supports

Repeated requests following a network loss are handled as the same exchange: they must not create multiple calls. Registration renewal follows the duration accepted by the PBX. BeAI also handles INVITE requests without an initial audio offer and mid-call session modifications used notably by 3CX and other PBXs.

Signalling can use UDP or TCP. A large request may require TCP: your firewall must allow the transport arranged with your administrator. TLS requires valid configuration and certificates on both the platform and carrier sides. A rejected secure connection is not silently replaced with an unencrypted connection. Encrypting signalling does not mean that the audio is encrypted.

Provisioning update notifications remain supported. Credit rules, bot permissions and rates are identical regardless of the transport used.

Understanding rejections

SIP response Useful check
400 The message sent by the PBX is incomplete or malformed.
401 or 407 An authentication challenge is normal; if it persists, check the account and secret.
405 or 501 The requested operation is not available.
415 The content type or its encoding is not supported.
420 The PBX requires an unsupported SIP extension; review the required options.
481 The dialogue or transaction no longer exists, or its identifiers do not match.
503 or no response Check PBX availability, transports, and network rules.

A dropped response may trigger several normal retransmissions. A sustained absence of acknowledgement eventually ends the call to prevent leaving a session hanging.

Validate your connection

Following a PBX or network modification, verify registration and OPTIONS in the bot's status, then test an incoming call, an outbound call and a transfer. Check two-way audio and call termination. For a BeAI Number, the platform handles the connection; the administrator can verify the runtimes serving the bot.

For diagnostic support, provide the time, the affected bot and the observed result to support, without any SIP passwords or secrets. SIP support does not guarantee compatibility with every extension of every PBX.

See also Choosing bot telephony and Getting a BeAI Number.

Documentation updated with the application