Hi, The updated connector was tested using SMS Service Providers Nexmo,
Clickatell and smsapi and it works perfectly.
Regards,
Pulasthi
On Wed, Apr 6, 2016 at 4:42 PM, Pulasthi Harasgama
wrote:
> Hi all,
>
> The development was completed, reviewed and ready to be merged.
Hi all,
The development was completed, reviewed and ready to be merged. The
documentation will also be updated to reflect the changes.
Regards,
Pulasthi
On Mon, Mar 7, 2016 at 2:00 PM, Pulasthi Harasgama
wrote:
> Noted.
>
> On Mon, Mar 7, 2016 at 1:54 PM, Dimuthu
Noted.
On Mon, Mar 7, 2016 at 1:54 PM, Dimuthu Leelarathne
wrote:
> Hi,
>
> +1
>
> Small suggestion for the form - Indicate the location of target telephone
> number as {num} and the text message as {msg}. It could be URL, header or
> payload.
>
> thanks,
> Dimuthu
>
>
> On
Hi,
+1
Small suggestion for the form - Indicate the location of target telephone
number as {num} and the text message as {msg}. It could be URL, header or
payload.
thanks,
Dimuthu
On Mon, Mar 7, 2016 at 1:50 PM, Elilmatha Sivanesan
wrote:
> +1
>
> On Mon, Mar 7, 2016 at
Adding Elilmatha and Malaka.
On Mon, Mar 7, 2016 at 12:55 PM, Pulasthi Harasgama
wrote:
> Hi all,
> The current SMSOTP connector of the Identity Server can only be used with
> an API which uses the GET method and which uses only the parameters: API
> Key, API Secret,
Hi all,
The current SMSOTP connector of the Identity Server can only be used with
an API which uses the GET method and which uses only the parameters: API
Key, API Secret, Recipient Phone Number and Text Message. When using the
connector with a different API, the connector has to be manually