Skip to content
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

There is no way to know how many SMS were sent #4

Open
K-Phoen opened this issue Jan 7, 2012 · 5 comments
Open

There is no way to know how many SMS were sent #4

K-Phoen opened this issue Jan 7, 2012 · 5 comments

Comments

@K-Phoen
Copy link
Member

K-Phoen commented Jan 7, 2012

As a message can be sent in several parts, there should be a way in this library to transcribe it:

  • by returning several results objects
  • or simply by allowing multiple message ID to be stored in a result object
@ghost ghost assigned K-Phoen Jan 7, 2012
@willdurand
Copy link
Contributor

I can see a lot of complex cases here..

@K-Phoen
Copy link
Member Author

K-Phoen commented Jan 7, 2012

Can you explain yourself?

@peshi
Copy link

peshi commented Sep 14, 2015

@willdurand Any update / input regarding this?

@K-Phoen
Copy link
Member Author

K-Phoen commented Sep 14, 2015

Nothing new for this issue. Feel free to tell us how you would like to see it implemented :)

@peshi
Copy link

peshi commented Sep 15, 2015

Well, nexmo do return the amount of messages sent - so this part would be easy to do.
For the others that do not return the amount of messages.

Depending of the mechanism of the provider there could be several possibilities to do this.

  1. Count successfull delivery reports.
  2. Count messageID's that are successfully returned.
  3. Detect encoding and count characters for a string if the response is successfull.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants