A new request with request id 7315 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is :

Title : Koha-devel Digest, Vol 203, Issue 3
Category :
Description :
Send Koha-devel mailing list submissions to
    koha-devel@lists.koha-community.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
    koha-devel-request@lists.koha-community.org

You can reach the person managing the list at
    koha-devel-owner@lists.koha-community.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."


Today's Topics:

1. Re: an SMS Send issue - wondering if it is possible to do
with Koha (Tomas Cohen Arazi)


----------------------------------------------------------------------

Message: 1
Date: Sun, 2 Oct 2022 18:47:46 -0300
From: Tomas Cohen Arazi <tomascohen@gmail.com>
To: Indranil Das Gupta <indradg@l2c2.co.in>
Cc: Koha-devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] an SMS Send issue - wondering if it is
    possible to do with Koha
Message-ID:
    <CABZfb=UdK7hup2oKhGvv9CD2UPyBdrWpD4Ry5Z5kpyskV4sgAA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I'd say we could add a hook for plugins to inject variables for notices.



El dom, 2 oct 2022 4:01, Indranil Das Gupta <indradg@l2c2.co.in> escribió:

> Hi all,
>
> I've written a new SMS::Send driver module for NIC SMS service (a
> federal IT service provider to Govt agencies in India). It's working
> fine on its own.
>
> India's current anti-spam rules demands that every message template
> (e.g. "Dear member {#var#} you have checked out {#var#}") must have to
> its unique 19 digit identifier mapped against the designated sender
> (e.g. the library) in the federal blockchain system for SMS
>
>
> https://smsgw.sms.gov.in/failsafe/HttpLink?username=xxxx&pin=xxxxx&message=This
> is a test
> message&mnumber=91XXXXXXXXXX&signature=sender_id&dlt_entity_id=xxxxxxx&dlt_template_id=xxxxxxx
>
> That last part - dlt_template_id will be different for each message
> template mapped against a specific dlt_entity_id. The sender_id and
> dlt_entity_id is easily taken care of via yaml (bug 13029).
>
> I can map the letter_code against dlt_template_id using the yaml, but
> is there a way by which I can push it to SMS.pm?
>
> thanks in advance.
>
> --
> Indranil Das Gupta
> L2C2 Technologies
>
> Phone : +91-98300-20971
> WWW : http://www.l2c2.co.in
> Blog : http://blog.l2c2.co.in
> IRC : indradg on irc://irc.freenode.net
> Twitter : indradg
> _______________________________________________
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221002/e0d88266/attachment-0001.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


------------------------------

End of Koha-devel Digest, Vol 203, Issue 3
******************************************


NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.