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/

Reply via email to