Closed MatthewWeb closed 1 year ago
If you type http://192.168.2.129:5678/ws/
in browser does it also return 404 ?
Yes. SuiteCRM v. 7.12.8
What about curl -v http://127.0.0.1:5678/ws/
on the asterlink machine ?
Expected result:
curl -v http://127.0.0.1:5678/ws/
* Trying 127.0.0.1:5678...
* Connected to 127.0.0.1 (127.0.0.1) port 5678 (#0)
> GET /ws/ HTTP/1.1
> Host: 127.0.0.1:5678
> User-Agent: curl/7.86.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 403 Forbidden
< Access-Control-Allow-Headers: Accept, Content-Type, Content-Length, Accept-Encoding, X-AsterLink-Token
< Access-Control-Allow-Methods: POST, GET, OPTIONS
< Access-Control-Allow-Origin: *
< Content-Type: text/plain; charset=utf-8
< X-Content-Type-Options: nosniff
< Date: Tue, 20 Dec 2022 15:33:39 GMT
< Content-Length: 45
<
token contains an invalid number of segments
* Connection #0 to host 127.0.0.1 left intact
GET /ws/ HTTP/1.1 Host: 127.0.0.1:5678 User-Agent: curl/7.79.1 Accept: /
The requested URL was not found on this server. If you entered the URL manually please check your spelling and try again.
If you think this is a server error, please contact the webmaster.
I don't have this option. That's probably the point.
That's apache webserver on this port which is weird.
Is ./asterlink
process really running on the 5678 port ?
As I see from first screenshot, Enabling web server addr="0.0.0.0:5678"
means 5678 tcp port is listening by asterlink process and there is no way apache whould bind to that address.
Do you run asterlink process and suitecrm on separate machines ?
Yes. When starting asterlink on a server with ip 192.168.2.129, this error.
On suitecrm module's settings page in Endpoint URL
and WebSocket URL
fields
you need to specify ip of machine where asterlink process is running.
You can also try to use another port like 51034: conf.yml:
endpoint_addr: "0.0.0.0:51034"
Then update port on module's settings page as well.
There is some progress. But there is still no clicktocall window
Please show browser console when you click on a number. (as I see on 2-nd screen, click2call tries to send dial request)
I see click2call request was successfully sent. You shoud get a popup card once you receive call on 999 extension. (since click2call first rings user extension and after answer asterisk will dial clicked number)
Everything is fine. It remains to configure dialplan.
The last question, through https can I somehow make it work? Swears at the certificate.
You need to use domain instead of ip for https.
I'll deal with ssl later. Dialplan does not accept. The call goes through telnet.
dial-context in conf.yml is the click2call context to place calls. In your setup it should be:
dial_context: call-out
Note that asterlink higly relies on dialplan. Check basic-pbx dialplan example.
Thanks a lot! Everything worked out and the calls went! Thanks for your hard work!
In asterisk ami there is also no empty space.