-
Notifications
You must be signed in to change notification settings - Fork 98
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
Error with Asterisk 14.7.0-rc1 #98
Comments
Well, maybe this has been fixed in 14.7.0-rc2 (see https://issues.asterisk.org/jira/browse/ASTERISK-27372). I will test it as soon as I can and keep you informed. |
Hey jaunis,
That issue has a patch that's been pushed through Gerrit (
https://gerrit.asterisk.org/#/c/6912/). It should fix your problems with
ARI client. I hope this helps.
Ben Ford
…On Thu, Oct 26, 2017 at 9:57 AM, jaunis ***@***.***> wrote:
Well, maybe this has been fixed in 14.7.0-rc2 (see
https://issues.asterisk.org/jira/browse/ASTERISK-27372). I will test it
as soon as I can and keep you informed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#98 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALIICPe_6R77KmosYHPCkiDrQbKEJgeqks5swJ3bgaJpZM4P6x6s>
.
|
I've tested with version 14.7.1, it's working. Thanks a lot ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The node-ari-client library is not working any more with Asterisk 14.7.0-rc1. It is failing during initialization with the following error :
I think it is due to Asterisk sending the HTTP headers and the body in two separate TCP packets. The issue is probably not on the Asterisk side, since standard tools like CURL are able to handle the response.
Everything was working fine until Asterisk 14.6.2.
The text was updated successfully, but these errors were encountered: