You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to add a new provider Teli. I copied the provider file and modified them to work based on the required options of the teli api. But I am stuck on the package teli.a file that I am not sure what that is. I have not use go before so I am kind of stuck.
cmd/sms-over-xmpp/main.go:38:2: cannot find package "src.agwa.name/sms-over-xmpp/providers/teli" in any of:
/usr/lib/go-1.10/src/src.agwa.name/sms-over-xmpp/providers/teli (from $GOROOT)
/root/go/src/src.agwa.name/sms-over-xmpp/providers/teli (from $GOPATH)
Here is what they are doing:
Send SMS:
https://api.server.com/sms/send?token=[API Token]&source=[Source]&destination=[Destination]&message=[Message]
Send MMS:
$file=filename.jpg # or whatever the file type is .gif etc...
$fdata=base64 of file
https://api.server.com/sms/send?token=[API Token]&source=[Source]&destination=[Destination]file_name=$file&file_data=$fdata
Receive SMS Messages:
I tried to add a new provider Teli. I copied the provider file and modified them to work based on the required options of the teli api. But I am stuck on the package teli.a file that I am not sure what that is. I have not use go before so I am kind of stuck.
cmd/sms-over-xmpp/main.go:38:2: cannot find package "src.agwa.name/sms-over-xmpp/providers/teli" in any of:
/usr/lib/go-1.10/src/src.agwa.name/sms-over-xmpp/providers/teli (from $GOROOT)
/root/go/src/src.agwa.name/sms-over-xmpp/providers/teli (from $GOPATH)
Here is what they are doing:
http://url-of-sms-orver-xmpp
POST:
source=3035551212&destination=3039991111&type=sms&message=hey+there+how+are+you
http://your-url.com
POST:
source=3035551212&destination=3039991111&type=mms&message=http://picmsg.org/3hhew9fh-fefj32-fwf.jpg
I don't mind doing the work. Just trying to follow the code to make the changes. Do you have time to help?
The text was updated successfully, but these errors were encountered: