Purchase this product on this page
Use the Buy now button on this product page, review the order and complete checkout with the account that will manage the HelSup license.
Buy this product now →
CHANNEL · VERSION 1.0.0
3CX
3CX V20 Call Control API (HTTPS /callcontrol + /callcontrol/ws). Service Principal client_credentials via POST /connect/token. Requires 3CX 8SC+ Enterprise and Call Control API access. XAPI GET /xapi/v1/Users is used for extension identity when the principal has Configuration API rights. Not a SIP stack. PHP-FPM cannot hold the Call Control WebSocket; a worker must pump frames into generic Realtime ingest. HTTP webhooks are not the official event channel. Hold/resume, recordings, queues, and presence are not in the public Call Control endpoint set.
USD 19,99Buy now ↗
WHY TEAMS CHOOSE IT
Bring supported 3CX call control events into HelSup.
The adapter uses the official V20 Call Control endpoints and WebSocket event stream for the call operations declared by the package, with explicit infrastructure and feature boundaries.
INCLUDED IN THIS PRODUCT
- 01Declared call-control actions
- 02Realtime WebSocket ingest
- 03Customer and conversation context
—No published ratings
—Views not public
—Downloads not public
v1.0.0Latest version
PRODUCT OVERVIEW
Bring supported 3CX call control events into HelSup.
3CX V20 Call Control API (HTTPS /callcontrol + /callcontrol/ws). Service Principal client_credentials via POST /connect/token. Requires 3CX 8SC+ Enterprise and Call Control API access. XAPI GET /xapi/v1/Users is used for extension identity when the principal has Configuration API rights. Not a SIP stack. PHP-FPM cannot hold the Call Control WebSocket; a worker must pump frames into generic Realtime ingest. HTTP webhooks are not the official event channel. Hold/resume, recordings, queues, and presence are not in the public Call Control endpoint set.
Why this extension helps
The adapter uses the official V20 Call Control endpoints and WebSocket event stream for the call operations declared by the package, with explicit infrastructure and feature boundaries.
- Declared call-control actions
- Realtime WebSocket ingest
- Customer and conversation context
Utilities and operational scope
No package widget is declared for this product. The overview and feature list therefore avoid claiming an operational utility that is not present.
HOW TO USE 3CX WITH HELSUP
Connect the official Call Control API through a persistent event worker.
Purchase the product here, retrieve the issued package and activation code, install it on your own WordPress website, then complete the provider-specific configuration below. Every later step is limited to capabilities declared by this package.
Receive the package and activation code
After the order is completed, open the HelSup customer portal to retrieve the extension package and the activation code issued for the licensed website.
Install and activate it on your website
On your WordPress website, install and enable the downloaded HelSup extension, open its license or activation screen, paste the activation code and confirm that the license is accepted.
Confirm 3CX eligibility
Verify 3CX V20 Enterprise 8SC or higher and Call Control API availability. The package cannot enable provider licensing or API access.
Create the service connection
Configure the Service Principal credentials used with POST /connect/token and grant only the provider rights needed by the declared call-control flow.
Resolve extension identity
If Configuration API rights are available, test the XAPI Users read used for extension identity. Do not assume identity resolution without those rights.
Run the WebSocket worker
Operate a long-running worker for /callcontrol/ws and forward frames into HelSup Realtime ingest. PHP-FPM requests cannot maintain this persistent event connection.
Test declared call actions
Exercise only receive, originate, answer, hangup, transfer and status operations implemented by the adapter and allowed by the connected 3CX principal.
Recommended first workflow
With the worker running, place one controlled inbound call, confirm the WebSocket status reaches HelSup, resolve the extension when permitted, answer and hang up through the declared actions, and verify the resulting conversation context.
FEATURES
Everything included in this product.
Capabilities declared by this product package and presented within its supported HelSup surfaces.
voice.call
Expose the common voice-call capability represented by the 3CX Call Control adapter.
call.receive
Receive a supported inbound call event from the official Call Control WebSocket stream.
call.originate
Originate a call only through the supported public Call Control operation.
call.answer
Answer a supported call through the connected Call Control session.
call.hangup
End a supported call through the declared Call Control action.
call.transfer
Transfer a supported call when the operation is available to the connected principal.
call.status
Read supported call-state changes delivered through the official event channel.
customer_profile
Associate the available caller or extension context with the HelSup customer view.
profile.read
Read provider profile information available to the authorized 3CX connection.
conversation.receive
Create or update HelSup conversation context from a supported received call event.
Version 1.0.0
Published product information, compatibility and package access remain connected to your HelSup customer account.
Detailed release notes will appear here when supplied by the publisher.Be the first to review
There are no published reviews for this product yet. Feedback is accepted from customers so product discussions stay useful and accountable.
Share product feedback →channel · v1.0.0
3CX
Premium3CX V20 Call Control API (HTTPS /callcontrol + /callcontrol/ws). Service Principal client_credentials via POST /connect/token. Requires 3CX 8SC+ Enterprise and Call Control API access. XAPI GET /xapi/v1/Users is used for extension identity when the principal has Configuration API rights. Not a SIP stack. PHP-FPM cannot hold the Call Control WebSocket; a worker must pump frames into generic Realtime ingest. HTTP webhooks are not the official event channel. Hold/resume, recordings, queues, and presence are not in the public Call Control endpoint set.
3CX V20 Call Control API (HTTPS /callcontrol + /callcontrol/ws). Service Principal client_credentials via POST /connect/token. Requires 3CX 8SC+ Enterprise and Call Control API access. XAPI GET /xapi/v1/Users is used for extension identity when the principal has Configuration API rights. Not a SIP stack. PHP-FPM cannot hold the Call Control WebSocket; a worker must pump frames into generic Realtime ingest. HTTP webhooks are not the official event channel. Hold/resume, recordings, queues, and presence are not in the public Call Control endpoint set.
Features
- voice.call
- call.receive
- call.originate
- call.answer
- call.hangup
- call.transfer
- call.status
- customer_profile
- profile.read
- conversation.receive
Compatibility
- min_php
- 8.0
- min_wp
- 6.0
- helsup
- 1.0.0
- package_id
- helsup.3cx