waiting for the bill

Yakshcho need fast - I can sprout.

The invoice was paid on Friday at 11.10. Today is Tuesday. Specify by date when the task can be completed. Unfortunately, the office can not give an answer. Thank you.

Thank you!

Good afternoon, yesterday after connecting the certificate, the calls to the cpm stopped being delayed. Please check, crm is not connected to telephony (Asterisk). The last call was recorded at 17.25 (01.12.20)

Hello, I don't have a certificate.

when finding out the reason why notifications are not delayed, your employee confirmed that there is no certificate. Task 4002

[quote] Podosinnikova Irina Anatolievna Client wrote: Hello, I don't have a certificate. [/quote] Good afternoon. Here is your thread https://crm-onebox.com/ru/support/telephony/3901-posle-podklyucheniya-sertifikata-zadacha-3718-perestali-zatyagivatsya-zvonki-v-srm/ Here I wrote to you how it can be solved [file]1389[/file] You said "Please disable the redirect so that the box is available" [file]1390[/file] Here is confirmation that the certificate is installed [file]1391[/file] Your box is currently available as a secure connection https://felizata.org.ua/dashboard/ so unprotected http://felizata.org.ua/dashboard/ Because you wrote "Please disable the redirect so that the box is available"

Good. What then shall we do? When I contact, your employee says that the reason why viber does not work is a certificate that we do not have. Viber did not work, and does not work. We just need a solution - for Viber (which is integrated, and whose API is only on CPM) to send messages to CPM.

I turned on the http -> https redirect, now your box is always accessible via https But, if telephony events stop coming, then your solution is only: 2) You on the telephony server send PUSH-and the link to https

Redirected again PUSH-and the link to http. Unfortunately - there are no calls in the events, there are no notifications from viber either

on https (as you wrote).

Help, please, to solve a problem. Last time, you said that you are not pulling up, because there is no author. actions. Now everything is there, but there are no calls in the events.

Good afternoon. As I see it, now you are sending PUSHs from the telephony server using the link http://felizata.org.ua/asterisk/push/ (and parameters) Because when trying to connect to the server via an unsecured connection (http://felizata.org.ua/), a redirect occurs to secure connection (https://felizata.org.ua/) In order to avoid a redirect, send push notifications from the telephony server immediately via a secure link https://felizata.org.ua/asterisk/push/(and parameters)

The last push from your telephony server was 04/Dec/2020:14:22:48 1X3.XX1.2XX.6XX - - [04/Dec/2020:14:22:48 +0200] "POST /asterisk/push/ HTTP/1.1" 301 178 "-" "curl/7.19.7 (x86_64-redhat -linux-gnu) libcurl/7.19.7 NSS/3.21 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2"

Screenshots - what is now written on the asterisk [file]1468[/file] [file]1469[/file]

Good afternoon. After 2020-12-04 there are no more attempts to connect to the url "/asterisk/push/" in the logs 19X.20X.218.69 - - [04/Dec/2020:14:22:25 +0200] "POST /asterisk/push/ HTTP/1.1" 301 178 "-" "curl/7.19.7 (x86_64-redhat-linux -gnu) ibcurl/7.19.7 NSS/3.21 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2" 19X.20X.218.69 - - [04/Dec/2020:14:22:37 +0200] "POST /asterisk/push/ HTTP/1.1" 301 178 "-" "curl/7.19.7 (x86_64-redhat-linux -gnu) libcurl/7.19.7 NSS/3.21 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2" 19X.20X.218.69 - - [04/Dec/2020:14:22:43 +0200] "POST /asterisk/push/ HTTP/1.1" 301 178 "-" "curl/7.19.7 (x86_64-redhat-linux -gnu) libcurl/7.19.7 NSS/3.21 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2" 19X.20X.218.69 - - [04/Dec/2020:14:22:48 +0200] "POST /asterisk/push/ HTTP/1.1" 301 178 "-" "curl/7.19.7 (x86_64-redhat-linux -gnu) libcurl/7.19.7 NSS/3.21 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2" 19X.20X.218.69 - - [04/Dec/2020:16:46:44 +0200] "GET /asterisk/push/ HTTP/1.1" 301 178 "-" "WhatsApp/2.2047.12 N" 19X.20X.218.69 - - [04/Dec/2020:16:46:45 +0200] "GET /asterisk/push/ HTTP/1.1" 200 31 "-" "WhatsApp/2.2047.12 N" This suggests that no one tried to connect to the box using this url.

Good afternoon, unfortunately, calls are not reflected in the events.

and the incoming call window is not displayed. I understand it is related. Please help troubleshoot.

Good evening. At the moment the problem is on the side of the asterisk. Since Friday, there have been no attempts to connect to the box from the side of the asterist. I wrote to you about this yesterday. I can only suggest that your specialist execute a curl request manually and see what response he will receive. From the boxing side, everything works, I executed a test request (intentionally with an incomplete number of parameters), an entry appeared in the logs (knocking on the server) 4X.1XX.X6.3X - - [07/Dec/2020:22:14:19 +0200] "POST /asterisk/push/ HTTP/1.1" 200 5 "-" "curl/7.58.0" In boxing reports, in the "logging" section /admin/shop/report/logs/ in the asterisk-2020-12-07.log you can see that the data has been received and processed (mistakes are intentional) [2020-12-07 22:14:19] host: felizata.org.ua url: /asterisk/push/ contentID: asterisk-push point: /shop.starter.php data: Array ( [ident] => 2020120408450464 [channel] => SIP/dinstar-101-3-0000455c [status] => INCOMING ) [2020-12-07 22:14:19] host: felizata.org.ua url: /asterisk/push/ contentID: asterisk-push point: /shop.starter.php data: Array ( [ident] => 2020120408450464 [channel] => SIP/dinstar-101-3-0000455c [status] => INCOMING [0] => Exception code 0 [1] => Exception message Engine: Argument caller is missing [2] => Exception file /var/www/felizata/web1/web/packages/Engine/Engine_URLParser.class.php [3] => Exception line 266 ) When your telephony server starts sending data to the box, then everything will be fine.

Good morning, here is the answer of the specialist who maintains the asterisk: "just executed from console [root@cw ~]# curl https://felizata.org.ua/ curl: (35) SSL connect error error "curl: (35) SSL connect error" !!!!!!! SSL connect error - an error related to the certificate. ..." "30 seconds ago there was a call and I sent a push to https. Your link is visible on the screen and https is indicated at the beginning" (screen attached) Can you fix this or is it an unsolvable problem? I can give access to the asterisk.

[file]1559[/file]

[quote] Podosinnikova Irina Anatolievna Client wrote: Good morning, here is the answer of the specialist who maintains the asterisk: ... [/quote] Good afternoon. Again, this is not a problem related to our product. As far as I understand, your telephony server uses an old version of curl "curl/7.19.7 (x86_64-redhat-linux-gnu) ibcurl/7.19.7 NSS/3.21 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2" Here is a problem similar to yours, with options for solving it. https://stackoverflow.com/questions/36787413/curl-35-ssl-connect-error/36789501 in short then: "You are using a very old version of curl. My guess is that you run into the bug described 6 years ago. Fix is to update your curl." "You are using a very old version of curl. The fix is to update curl." Updating the server software, curl, and the libraries that are used should solve your problem.

Sergey, thanks. It's already tightening. Tell me, how can we update onebox so that improvements do not fly off?)

[quote] Podosinnikova Irina Anatolievna Client wrote: Sergey, thanks. It's already tightening. Tell me, how can we update onebox so that improvements do not fly off?) [/quote] Create a topic on the forum, something like this "Update box to the latest version" and ask in it a question about your improvements.