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.

Sign up for GitHub

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

Jump to bottom

Multipart SMS not handled correctly #175

Open
2 tasks
kengu opened this issue Apr 26, 2019 · 0 comments
Open
2 tasks

Multipart SMS not handled correctly #175

kengu opened this issue Apr 26, 2019 · 0 comments
Labels
bug
Milestone
1.0.0

Comments

@kengu
Copy link
Member

kengu commented Apr 26, 2019

Problem
We only register the first message id in a multi-part SMS, which results in incomplete status handling.

Resolution

  • Add client_ref for multi-part sms indication to messages
  • Add our messages primary key as client_ref to message request
@kengu kengu added the bug label Apr 26, 2019
@kengu kengu added this to the 1.0.0-RC08 milestone Apr 26, 2019
@kengu kengu changed the title Multipart SMS from Nexmo not handled correctly Multipart SMS not handled correctly Apr 26, 2019
@kengu kengu mentioned this issue Apr 26, 2019
Open
55 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
1 participant
@kengu