Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow snooping by existing channel name or unique ID #21

Open
chrsmj opened this issue Jun 6, 2024 · 2 comments · May be fixed by #22
Open

Allow snooping by existing channel name or unique ID #21

chrsmj opened this issue Jun 6, 2024 · 2 comments · May be fixed by #22

Comments

@chrsmj
Copy link

chrsmj commented Jun 6, 2024

Request to add a new '-s' command line option to change the meaning of <dialstring> to instead of originating a call, be an existing channel name or unique ID already active in Asterisk.

For example, by channel name:

$ bin/ari-transcriber -s 'PJSIP/7001-00000001'

...would sic a dog on that channel and start gewgle translating it.

Similarly, by unique ID:

$ bin/ari-transcriber -s '1716337601.107'

Patch to follow.

chrsmj added a commit to chrsmj/asterisk-external-media that referenced this issue Jun 6, 2024
Adds a new command line option boolean '-s' to change the meaning of
<dialstring> from originating a call to a new destination, to instead
snooping on an existing channel, either by channel name or unique ID.

For example...

$ bin/ari-transcriber -s 'PJSIP/7001-00000001'

Big thanks to Voisonics for sponsoring this patch.

Resolves: asterisk#21

UserNote: The ari-transcriber now takes an additional argument '-s' on
the command line to allow snooping on any Asterisk channel.
@chrsmj
Copy link
Author

chrsmj commented Jun 6, 2024

Big thanks to Voisonics for sponsoring this patch.

@chrsmj
Copy link
Author

chrsmj commented Jun 6, 2024

FYI the patch also adds a little more logging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant