I made some progress on this today. I'm able to send text messages through clickatell with their test interface
http post api.clickatell.com/xml/xml?data=
<clickAPI>
<sendMsg>
<api_id>[your XMLapi ID]</api_id>
<user>[your username]</user>
<password>[password]</password>
<to>[1phone number]</to>
<from>[clickatell assigned #]</from>
<text>[Your SMS Message]</text>
<mo>1</mo>
</sendMsg>
</clickAPI>
I grabbed a packet capture from smartpass and decoded the url from base64.
http post api.clickatell.com/xml/xml?data=
<clickAPI>
<sendMsg>
<session_id>f4cade2af92a546b06b8ccd194b7038a</session_id>
<to>[1phone number]</to>
<text>smartpass!</text>
<concat>1</concat>
</sendMsg>
</clickAPI>
After reading the clickatell api documentation I realized that smartpass is authenticating on the first attempt and then referencing a session number. But, you can clearly see smartpass is not sending a from number or the mobile phone <mo>1</mo> tag. I verified with clickatell support that these tags are required for all clickatell api messages regardless of the account or service level!
I also learned that it's important that you create an xml api. Further more that the xml api is assigned to the from number clickatell assigns. I also noticed smartpass trying to ping api.clickatell.com, if it can't it logs an error. Overall I found clickatell support very helpful. Now I think juniper needs to address these missing fields.
