-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SMS with > 160 characters does not send #9
Comments
It says in the documentation that
|
are you using any wrapper class? if yes, will you mind telling us which wrapper class you used? a sample request will also help. |
No, I believe that I'm not using any wrapper classes. As I said, sending messages less than 160 characters sends but sending above that doesn't. As it was stated in the docs, the API can send messages more than 160 characters, that is a multi-part SMS, like you would in sending a normal sms. I don't see anything wrong with what I'm doing previously if that is the case. |
how can i send message po? sorry for this question |
tanong naman po. i'm using .net. nakuha ko na po yung token at na authorize na rin, kaso kapag mag send nako sa SMS nag error siya "Unauthorized" gamit kong API var data = api1.PushSms(shortCode, payload); <- dito po siya nag error |
I came across this situation that whenever I try to send an SMS with more than 160 characters, it simply does not send. As of now, my temporary fix is to chunk the SMS into 160-character messages.
Also, some information on receiving multi-part SMS such as
multPartRefId
are not included in the payload.The text was updated successfully, but these errors were encountered: