Supported Features

The Audiocodes SBC is simulating a PBX by acting as a SIP registrar to the TPO however it is not a full PBX. Therefore there is some potential loss of PBX style functionality to be expected. Below is the list of supported features on SBC as a PBX:

•Inbound and Outbound calling

•Call Forward

•Call Transfer

➢ Unattended Transfer : This key profile.setting.transfer.unattented.waituntilestablished must be set to true        

•Hold and music on hold

•Message Manipulation

•Call Forking

•Alternative routes

•Encryption - TLS and SRTP

•Alerting via Tradesense

•Troubleshooting via Audiocodes syslog viewer

It is supported to have both SBC as a PBX and SIP PW configuration on the same SBC though care must be taken to ensure the configuration does not clash. It may be simpler to separate these functions onto independent devices.

The standard design is to place the Audiocodes SBC behind the customers edge SBC. This way the customer still maintains responsibility for the security parameter with the carrier. Direct carrier connection and direct routing to teams are the responsibility of the customer to provide.

Physical gateways and QSIG connections for PSTN are not supported by BT development. Digital circuits should be converted to sip to allow the installation of a virtualised SBC. If you still require a physical device then support must be obtained through Audiocodes directly.