Bug 32381 - Koha should be able to receive and record reasons for failed SMS notices
Summary: Koha should be able to receive and record reasons for failed SMS notices
Status: RESOLVED DUPLICATE of bug 36307
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-30 18:46 UTC by Andrew Fuerste-Henry
Modified: 2024-03-14 19:12 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2022-11-30 18:46:53 UTC 
When a third-party SMS-sending service fails to send a notice and returns a reason for the failure, there is apparently no way for that reason to get passed into Koha and recorded in message_queue.failure_code. I gather this is a limitation based on the SMS::Send drivers.

For example, if a library is using Twilio to send their SMS notices and a patron unsubscribes to library texts via Twilio, all future SMS notices generated in Koha will fail to send. In the staff interface, they show "NO_NOTES" in message_queue.failure_code. The error logs on the server show "Attempt to send to unsubscribed recipient at /usr/share/perl5/SMS/Send.pm line=270."

It would be quite useful if the Koha interface could show staff why the notice didn't send.
Comment 1 Christopher Brannon 2022-12-01 22:21:20 UTC 
Yes, I agree.  This would be extremely helpful.
Comment 2 Emmi Takkinen 2022-12-02 11:45:30 UTC 
Could this be a duplicate of bug 31481?
Comment 3 Andrew Fuerste-Henry 2022-12-02 14:11:26 UTC 
(In reply to Emmi Takkinen from comment #2)
> Could this be a duplicate of bug 31481?

I don't *think* so, but I'm really not certain. I've got only the vaguest explanation of why Twilio's unsubscribed user response can't make its way into Koha.
Comment 4 Kyle M Hall (khall) 2024-03-14 19:12:23 UTC 

*** This bug has been marked as a duplicate of bug 36307 ***