SMS Support

...

SMS Support 

...

 Kepler-Rominfo (- a product called KR-EMS) and Netopia ( and Netopia  - see https://www.web2sms.ro/). We We're open to add more providers, and if you are interested in such a functionality, let us know.

After each configuration change, you will need to stop / start katl-commons (or restart JIRA) SIL Engine™ or restart Jira.

KR-EMS Provider Configuration

This provider has been bundled inside, and requires a simple configuration file, named `enms`enms.properties` properties` in the <JIRA_HOME>/kepler folder. It's the same path where the cPrime -owned licenses (e.g. for Power Scripts for JIRA (formerly known as JJUPIN) ) Jira) are located. Edit the file and add the following entries:

enms.user=<username>
enms.password=<passwd>
enms.endpoint=http://ems.kepler.ro/emsws/service.asmx?wsdl
enms.default.sender=<phone number>
enms.unicode=false

Of course, You also need to replace <username>, <password> and <phone number> with the values provided by the KR EMS team.

Fields are:

• enms.user is the username to authenticate against the web service end point
• enms.password is the password to authenticate against the web service end point
• enms.endpoint is the URL where the web service is located
• enms.default.sender is the default sender phone number that is used by the web service to send messages with
• enms.unicode enables or disables the unicode text representation

NETOPIA Provider Configuration

NETOPIA provider is built-in, too, and it can be configured in the similar way as above. You need to create a file, named 'netopia.properties', readable by the JIRA Jira process, in the <JIRA_HOME>/kepler directory, containing the following entries:

netopia.user=<user>
netopia.authKey=<authkey>
netopia.default.sender=<default sender>
netopia.validity=<validity of the message>
netopia.scheduleDate.format=<format of the scheduled date>
netopia.scheduleDate=<scheduled date>
netopia.callbackUrl=<url of the callback, if any>

...

For more details, contact the NETOPIA SMS provider.