Jump to content

correct Action URL to send Telegram BOT message on new call


almoondsllc
 Share

Recommended Posts

Hello, I'm trying to receive Telegram message on my bot when a new call comes into the system

I'm using HTTPS POST JSON according to telegram 

https://core.telegram.org/bots/api#making-requests

So in Vodia -> Advanced ->Action URL I put:

** When a new call comes in **

Authentication metod: None

Method: POST

URL: https://api.telegram.org/bot<mytoken>/sendMessage

Encoding for the message body: JSON

Message Body: {"chat_id": "mychatid", "text": "This is a test from curl", "disable_notification": true}

 

But it doesn't work, some help? Thanks.

 

Alessandro

 

Link to comment
Share on other sites

Handshake Failure...

[9] 19:57:25.204 Initialize TLS connectionⓘ
[9] 19:57:25.204 Last message repeated 2 timesⓘ
[9] 19:57:25.204 HTTP 149.154.167.220: Send Client Hello(03035F97..00020017)ⓘ
[5] 19:57:25.209 HTTP 149.154.167.220: Alert Fatal (2): Handshake failure (40)ⓘ
[7] 19:57:25.209 https:api.telegram.org:443: TCP disconnectⓘ
[7] 19:57:25.209 https:api.telegram.org:443: Return code 500ⓘ

 

Link to comment
Share on other sites

Is there a way to change the chipers Vodia offers?  I'm trying with pipedream, things are going better...

[9] 20:08:47.488 Initialize TLS connectionⓘ
[9] 20:08:47.489 Last message repeated 2 timesⓘ
[9] 20:08:47.489 HTTP 18.235.89.39: Send Client Hello(03035F97..00020017)ⓘ
[9] 20:08:47.574 HTTP 18.235.89.39: Receive Server Hello(03035153..03000102)ⓘ
[9] 20:08:47.575 HTTP 18.235.89.39: Receive Certificate(0012D700..5DF4038C)ⓘ
[9] 20:08:47.575 HTTP 18.235.89.39: Received chain with 4 certificatesⓘ
[8] 20:08:47.585 HTTP 18.235.89.39: Certificate name *.m.pipedream.net matchesⓘ
[9] 20:08:47.585 HTTP 18.235.89.39: Receive Server Key Exchange(03001741..C2BBB7BC)ⓘ
[9] 20:08:47.610 HTTP 18.235.89.39: Pre Master Secret(8CCC9BC7..CD3D4A66)ⓘ
[9] 20:08:47.610 HTTP 18.235.89.39: Client Random(5F971EBF..272B7BAE)ⓘ
[9] 20:08:47.610 HTTP 18.235.89.39: Server Random(5153BF0F..90BE3932)ⓘ
[9] 20:08:47.610 HTTP 18.235.89.39: Master Secret(0FA8E970..01FF2C34)ⓘ
[9] 20:08:47.610 HTTP 18.235.89.39: Receive Server Hello Done()ⓘ
[9] 20:08:47.610 HTTP 18.235.89.39: Send Client Key Exchange(41047A93..D64234EE)ⓘ
[9] 20:08:47.610 HTTP 18.235.89.39: Send Change Cipher Spec(01)ⓘ
[9] 20:08:47.610 HTTP 18.235.89.39: Perform Change Cipher Spec(c027)ⓘ
[9] 20:08:47.610 HTTP 18.235.89.39: Key Block(69BE62E3..0B3CD2EE)ⓘ
[9] 20:08:47.610 HTTP 18.235.89.39: Client Write MAC Secret(69BE62E3..CCC9915B)ⓘ
[9] 20:08:47.610 HTTP 18.235.89.39: Server Write MAC Secret(80E3C9AB..C0BE85EE)ⓘ
[9] 20:08:47.610 HTTP 18.235.89.39: Client Write Key(D028C2B0..CA784F3C)ⓘ
[9] 20:08:47.610 HTTP 18.235.89.39: Server Write Key(25CE52D0..22FD34C6)ⓘ
[9] 20:08:47.611 HTTP 18.235.89.39: Send Finished(9427E587..309049E1)ⓘ
[9] 20:08:47.696 HTTP 18.235.89.39: Receive Change Cipher Spec(01)ⓘ
[9] 20:08:47.696 HTTP 18.235.89.39: Receive Process Finished(31BFE9E2..F3C2587E)ⓘ
[9] 20:08:47.833 Received 435 bytesⓘ
HTTP/1.1 200 OK
Date: Mon, 26 Oct 2020 19:08:47 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 179
Connection: keep-alive
X-Powered-By: Express
Access-Control-Allow-Origin: *
x-pd-status: sent to coordinator
ETag: W/"b3-174a20b59d8"

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...