Add browser Call Control dialer sample - #4
Draft
SpaceEggs wants to merge 2 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
examples/web-dialerWhy
This provides a minimal reference for building a browser calling client with the Call Control API without registering a SIP endpoint.
RoutePoint calls are already connected by the PBX, so the ringing phase is intentionally virtual: media is withheld until the browser user accepts the call.
Validation
yarn workspace @3cx-examples/web-dialer buildyarn buildNotes
No live PBX credentials were available, so the final 3CX inbound/outbound media path still needs validation against a configured RoutePoint. The sample intentionally binds to localhost and documents the additional controls required before remote or production deployment.