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

CMGS ID in manager/cli - delivery reports #1

Open
GoogleCodeExporter opened this issue Apr 11, 2015 · 5 comments
Open

CMGS ID in manager/cli - delivery reports #1

GoogleCodeExporter opened this issue Apr 11, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Send a message through the manager
2. Send a message through cli

What is the expected output? What do you see instead?
Asterisk ID of the message and the CMGS ID given.

What version of the product are you using? On what operating system?
r3, ubuntu x86, asterisk 1.8

Please provide any additional information below.
Once the message is queued ( read the ok from the smstext ) the message is also 
given an id from the dongle itself that can be later united with the alert ( 
delivery report ) to see if a message was delivered.

Would be nice to see that CMGS ID in the manager response ( and cli ). Also 
would be useful for chan_dongle to report the cmgs id that was delivered ( or 
not delivered ) upon a delivery message !

Thanks in advance,
  Adrian

Original issue reported on code.google.com by dex...@d3xt3r01.tk on 13 May 2011 at 11:27

@GoogleCodeExporter
Copy link
Author

This not defect.
id provided by modem in CMGS response not parsed and stored by chan_dongle.

ID reported by DongleSendSMS and references in event DongleSMSStatus 
is defined by chan_dongle and may repeat for SMS sended not simultaneously

You free to use DongleSendPDU and specify SMS ID in external software directly 
in PDU for future references


Original comment by bg_...@mail.ru on 17 May 2011 at 4:42

@GoogleCodeExporter
Copy link
Author

Original comment by bg_...@mail.ru on 17 May 2011 at 4:42

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

Original comment by bg_...@mail.ru on 17 May 2011 at 4:42

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

I didn't say is a defect :) I know it isn't. I also noticed the ID reported by 
DongleSendSMS can repeat itself. The thing is that I can't correlate that ID 
with a status report ! I need the ID from the CMGS :) I already am using 
outside software to corelate stuff, would be nice to have this implemented ( 
including reading / event on sms delivery reports ) to have a full module :)

Thanks again in advance.

Original comment by dex...@d3xt3r01.tk on 17 May 2011 at 5:18

@GoogleCodeExporter
Copy link
Author

has 2 problems:
1) autodelete doesn't seem to work ..
2) the ID is (nil) when notifying about a report .. also, they have to
be read manually 'till a check is implemented in the loop
- the main windows app does just that .. loops at+cpms="SM","SM","SM"
and checks if something new is in ..then loops through that.

Original comment by dex...@d3xt3r01.tk on 21 Nov 2011 at 9:31

Attachments:

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

1 participant