[asterisk-bugs] [Asterisk 0012779]: [patch] smsq does not work in asterisk 1.6
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon May 11 15:44:55 CDT 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=12779
======================================================================
Reported By: PH
Assigned To: dvossel
======================================================================
Project: Asterisk
Issue ID: 12779
Category: Applications/app_sms
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Target Version: 1.6.2.0
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2008-06-03 06:53 CDT
Last Modified: 2009-05-11 15:44 CDT
======================================================================
Summary: [patch] smsq does not work in asterisk 1.6
Description:
smsq which works well in asterisk 1.4, does not work
in the same way on 1.6 :
-- Attempting call on mISDN/1/0809101000 for application SMS(0) (Retry
1)
> Channel mISDN/1-u5 was answered.
> Launching SMS(0) on mISDN/1-u5
sms argc 1 queue <0> opts <> addr <> body <>
initial delay 300ms
-- SMS RX 93 00 6D
-- SMS TX 91 16 01 01 0A 81 60 70 47 90 10 00 F1 0B E8 32 9B FD 06
DD DF 72 36 19
-- SMS RX 95 09 01 00 80 50 62 90 71 32 80 7C
-- SMS TX 94 00
[May 26 09:37:30] NOTICE[6747]: app_sms.c:1904 sms_exec: ast_read failed
[May 26 09:37:30] NOTICE[6747]: pbx_spool.c:333 attempt_thread: Call
completed to mISDN/1/0809101000
======================================================================
----------------------------------------------------------------------
(0104550) lmadsen (administrator) - 2009-05-11 15:44
http://bugs.digium.com/view.php?id=12779#c104550
----------------------------------------------------------------------
So do we have any ability to move this issue forward, or are we at a
stand-still until someone can provide the equipment necessary to reproduce
the issue? What is it that we actually need in order to move this issue to
a conclusion?
Issue History
Date Modified Username Field Change
======================================================================
2009-05-11 15:44 lmadsen Note Added: 0104550
======================================================================
More information about the asterisk-bugs
mailing list