SMS HTTP API Token

Hello . can you help me . when I test the sms api URL in the browser it works.
Send SMS using following API:

    POST /
    {
        "to": "+10000000000",
        "message": "Your message"
    }

in the app it does not send notification. some help ?

Illegal character in scheme name at index 0: 192.168.1.15:8082 - URISyntaxException (... < HttpSmsClient:86 < *:95 < NotificatorSms:45 < NotificationResource:63 < ...)

my configuration in traccar.xml is .

<entry key='notificator.types'>web,mail,sms</entry>
<entry key='notificator.sms.manager.class'>org.traccar.sms.HttpSmsClient</entry>
<entry key='sms.http.url'>http://192.168.1.15:8082</entry>
<entry key='sms.http.authorization'>5797ad05</entry>
<entry key='sms.http.template'>
    {
        "to": "{phone}",
        "message": "{message}"
    }
</entry>
Anton Tananaev 4 years ago

Are you sure that's your config at the time you got that error? Because the error seems to indicate you don't have a schema name.

is there anything I can do to test. I've tried everything but traccar-4.14 doesn't send the notification by sms.

the configuration correct in traccar.xml is ...

<entry key='sms.smpp.enable'>true</entry>
<entry key='sms.smpp.host'>http://192.168.1.15</entry>
<entry key='sms.smpp.port'>8082</entry>
<entry key='sms.smpp.username'>traccar</entry>
<entry key='sms.smpp.password'>5797ad05</entry>
<entry key='notificator.types'>web,mail,sms</entry>
<entry key='notificator.sms.manager.class'>org.traccar.sms.HttpSmsClient</entry>
<entry key='sms.http.url'>http://192.168.1.15:8082</entry>
<entry key='sms.http.authorization'>5797ad05</entry>
<entry key='sms.http.template'>
    {
        "to": "{phone}",
        "message": "{message}"
    }
</entry>

I tried this one but to no avail.

Anton Tananaev 4 years ago

Which one? How's SMPP is related to anything? What error do you get for the correct config (second option)?

the phrase that appears is this. ** communication failure **
as the image below.

image

already tried in traccar 4.11, 4.14 and no solution.

Anton Tananaev 4 years ago

You should check both browser network console for actual error and server logs for error.