J SIP Phone registered via AudioCodes SBC – TSAPI Call Control 401 Error (PPM Issue?)

[choi8]

Hello,

In our current test environment, we have configured J179 SIP phones to register to an AudioCodes SBC (in order to use the SBC’s SIPREC recording capabilities). The SBC is configured to route signaling towards Avaya Session Manager.

Topology: J179 SIP Phone ⇄ AudioCodes SBC (SIPREC enabled) ⇄ Avaya Session Manager

Registration is successful, and both inbound and outbound calling work fine. However, when we attempt to perform Call Control (e.g., via TSAPI or CTI integration), we receive a 401 Error.

From my analysis, it seems that the phone may not be able to successfully download PPM (Phone Profile Manager) data, which could explain the failed TSAPI call control actions.

Questions:

1. Has anyone experienced a similar issue where CTI/TSAPI Call Control fails with 401 when using an AudioCodes SBC as the SIP proxy for J100 series phones?
2. Could unsuccessful PPM provisioning/download be the cause of CTI/TSAPI integration problems in this topology?
3. Does anyone have a documented solution or best practice for enabling full CTI (via TSAPI) support when phones are registered through a third-party SBC (for example, required HTTP/PPM path, or configurations to enable PPM download in this scenario)?

Any advice, similar case experience, or reference to official documentation would be greatly appreciated. Thank you!

[mlombardi1]

I have not tried to implement RW with an Audiocodes SBC. The phone should be registered via TLS and use HTTPS for PPM. The Avaya SBC uses an HTTPS reverse proxy for PPM traversal. Is there an equivalent in the Audiocodes?