Jump to content

How to sent a URL for an incomming Call


Henrikt
 Share

Recommended Posts

Hi,

I try to setup an ActionURL, so when the customer get an incomming call, the PBX sent an URL like https://server.com/rest/Token=xxxxxxxxxxx&message={from}

If i use the URL in a browser it's works fine, but in Action URL under the Extensions it dosen't work

I hope someone can help me in this case.

Authentication method: None
Username: -blank-
Password: -blank-
Region: -blank-
Method: POST

URL:  https://server.com/rest/Token=xxxxxxxxxxx&message={from}
Additional headers: -blank-
Encoding for the message body: JSON
Message body: -blank-

 

 

Link to comment
Share on other sites

Thanks for your support

I got this in the log, can you use it or did you need more logs.

HTTP/1.1 400 Bad Request
server: envoy
date: Tue, 05 Apr 2022 12:11:48 GMT
content-type: application/json
content-length: 179
x-envoy-upstream-service-time: 5
strict-transport-security: max-age=31536000
Via: 1.1 google
Alt-Svc: clear

[7] 14:11:49.013 WEBC: /rest/mtsms?token=XXXXXXXXX&message=TEST3&recipients.0.msisdn=99999999: Return code 400 (179 bytes)
{"code":"0x0308","incident_uuid":"36f99037-1aa2-4253-a15f-471ad1cc67c0","message":"The browser (or proxy) sent a request that this server could not understand.","variables":null}
[8] 14:11:49.013 WEBC: /rest/mtsms?token=XXXXXXXXX&message=TEST3&recipients.0.msisdn=99999999: Return headers
server: envoy
date: Tue, 05 Apr 2022 12:11:48 GMT
content-type: application/json
content-length: 179
x-envoy-upstream-service-time: 5
strict-transport-security: max-age=31536000
Via: 1.1 google
Alt-Svc: clear
[9] 14:28:28.266 WEBC: ActionURL: Parameters for request to https://gatewayapi.com/rest/mtsms?token=XXXXXXXX&message=TEST3&recipients.0.msisdn=99999999:
Link to comment
Share on other sites

I would say the phone number that you are providing is not set up properly? At least we can say it is not related to anything like TLS or certificates. Does it work properly e.g. when you are using curl from command line?

Link to comment
Share on other sites

  • 3 weeks later...

I would turn on the logging for the web client to 9 and see if e.g. the content-type header contains what you would see in curl. Maybe there is no content type or the wrong content type and that is why the server is rejecting it.

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.

 Share

×
×
  • Create New...