<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 7315 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 203, Issue 3<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: an SMS Send issue - wondering if it is possible to do<br> with Koha (Tomas Cohen Arazi)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sun, 2 Oct 2022 18:47:46 -0300<br>From: Tomas Cohen Arazi <tomascohen@gmail.com><br>To: Indranil Das Gupta <indradg@l2c2.co.in><br>Cc: Koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] an SMS Send issue - wondering if it is<br> possible to do with Koha<br>Message-ID:<br> <CABZfb=UdK7hup2oKhGvv9CD2UPyBdrWpD4Ry5Z5kpyskV4sgAA@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>I'd say we could add a hook for plugins to inject variables for notices.<br><br><br><br>El dom, 2 oct 2022 4:01, Indranil Das Gupta <indradg@l2c2.co.in> escribió:<br><br>> Hi all,<br>><br>> I've written a new SMS::Send driver module for NIC SMS service (a<br>> federal IT service provider to Govt agencies in India). It's working<br>> fine on its own.<br>><br>> India's current anti-spam rules demands that every message template<br>> (e.g. "Dear member {#var#} you have checked out {#var#}") must have to<br>> its unique 19 digit identifier mapped against the designated sender<br>> (e.g. the library) in the federal blockchain system for SMS<br>><br>><br>> https://smsgw.sms.gov.in/failsafe/HttpLink?username=xxxx&pin=xxxxx&message=This<br>> is a test<br>> message&mnumber=91XXXXXXXXXX&signature=sender_id&dlt_entity_id=xxxxxxx&dlt_template_id=xxxxxxx<br>><br>> That last part - dlt_template_id will be different for each message<br>> template mapped against a specific dlt_entity_id. The sender_id and<br>> dlt_entity_id is easily taken care of via yaml (bug 13029).<br>><br>> I can map the letter_code against dlt_template_id using the yaml, but<br>> is there a way by which I can push it to SMS.pm?<br>><br>> thanks in advance.<br>><br>> --<br>> Indranil Das Gupta<br>> L2C2 Technologies<br>><br>> Phone : +91-98300-20971<br>> WWW : http://www.l2c2.co.in<br>> Blog : http://blog.l2c2.co.in<br>> IRC : indradg on irc://irc.freenode.net<br>> Twitter : indradg<br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221002/e0d88266/attachment-0001.htm><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 203, Issue 3<br>******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>