Skip to content
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

Two-way Settings: Reply Callbacks #29

Open
VoRCeK opened this issue Aug 23, 2019 · 1 comment
Open

Two-way Settings: Reply Callbacks #29

VoRCeK opened this issue Aug 23, 2019 · 1 comment

Comments

@VoRCeK
Copy link

VoRCeK commented Aug 23, 2019

I've just install the latest everything:

Drupal 7.67
CiviCRM 5.15.2
clickatell 4.1

I can send outbound SMS just fine.. but, I am not getting any of the Two-way Reply's back to my site (I am USA located). I have followed the instructions and am using the following url in the Clickatell Integration for Reply Callbacks:

https://MYSITE.org/civicrm/sms/callback?provider=org.civicrm.sms.clickatell

The only obvious difference is the the Clickatell site is forcing a username & password (so have have to put something there - and I've tried everything). If this extension isn't expecting it, I would guess it's being ignored.

After every time I send a SMS reply, this is logged in CiviCrm:

[warning] Could not find an entry for from in REQUEST

When I configure Clickatell to us GET.. the log includes this:

MYSITE.org/civicrm/sms/callback?provider=org.civicrm.sms.clickatell&integrationName=D_SMS&replyMessageId=f32005cbbe1d4c4a93caeb3db8738610&messageId=4f38cdc4a5ee4b63b5aa9cf72d9a56b9&fromNumber=14586290351&toNumber=17594000784&timestamp=1567735558326&text=Ffj&charset=ISO-8859-1&udh=&network=737&keyword

This error is not very helpful.. but, it's a start.

Anyone have any idea where I should look for a solution?

josephlacey pushed a commit to josephlacey/org.civicrm.sms.clickatell that referenced this issue Jul 7, 2020
The inbound() function needed an update to match Click-a-tell's current API.  I'm not certain whether the urldecode() opens any potential security issues.

This address issue veda-consulting#29
@josephlacey
Copy link

@VoRCeK See PR #30 if you're still having an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants