| Summary: | ASTERISK-03613: smsq in PortugalTelecom | ||
| Reporter: | app (app) | Labels: | |
| Date Opened: | 2005-03-01 13:15:33.000-0600 | Date Closed: | 2005-05-23 22:11:22 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_sms |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | I've been testing app_sms and smsq over BRI. Service nrs: outgoing 129990; incoming: 1299900 Incoming messages working fine. Outgoing messages via .call working fine. Outgoing messages via smsq don't work. ****** ADDITIONAL INFORMATION ****** Command used with smsq: smsq --motx-channel=ZAP/g1/129990 123456789 "hello world" CLI: -- Attempting call on ZAP/g1/129990 for application SMS(0) (Retry 1) -- SMS RX 93 00 6D 00 00 00... -- SMS TX 94 00 6C 00 00 00... -- Hungup 'Zap/1-1' Mar 1 18:55:53 NOTICE[5275]: pbx_spool.c:242 attempt_thread: Call completed to ZAP/g1/129990 | ||
| Comments: | By: Matt O'Gorman (mogorman) 2005-03-08 21:28:11.000-0600 Can you provide more information as to this bug, it seems as if your syntax is correct on the command. As does your output. By: Clod Patry (junky) 2005-03-08 22:30:40.000-0600 Also, since 1.0.3 is pretty old, could ya try that with latest cvs-head or latest stable (1.0.6) ? By: app (app) 2005-03-09 08:57:51.000-0600 Actually, smsq is not even included yet on the release version. I just downloaded and compiled the latest smsq.c from http://bugs.digium.com/bug_view_page.php?bug_id=0002973 as the .call way to queue a message is supposed to be depricated in favour of the smsq cli command. For .call, I used: Channel: ZAP/g1/129990 MaxRetries: 1 RetryTime: 60 WaitTime: 30 Context: smsdial Priority: 1 Callerid: <987654321> Extension: 123456789 SetVar: MSG=hello world with the context: ;============================================================================= [smsdial] ;============================================================================= ; create and send a text message ; connects to the SMSC at 129990 (to send the message) ; this context is to be used by a .call file or thru the manager API! ;============================================================================= exten => _X.,1,SMS(${CALLERIDNUM},,${EXTEN},${MSG}) exten => _X.,2,SMS(${CALLERIDNUM}) exten => _X.,3,Hangup exten => s,1,Verbose(Catching a SMS sending error... hangup!) exten => s,2,Hangup For smsq, I tested with: smsq --motx-channel=ZAP/g1/129990 123456789 "hello world" but, as I suspect this problem is related somehow with the caller ID, I've also tested with most of the options set: "smsq --queue=987654321 --da=123456789 --ud="hello world" --mo --tx --UTF-8 --motx-channel=ZAP/g1/129990 --motx-callerid=987654321 --motx-wait=10 --motx-delay=1 --motx-retries=2 --mr=0". with the same result. The file /var/spool/asterisk/sms/motx/987654321.1110379894-15003 containing: da=123456789 mr=0 ud=hello world stays there forever. Unfortunately I haven't got enough information on how to debug the conversation with the SMSC. By: Brian West (bkw918) 2005-03-17 21:48:12.000-0600 More info? /b By: Michael Jerris (mikej) 2005-05-23 22:10:11 you are reporting an error in running cvs head code on extremely old stable. If you can reproduce this error on cvs head, please open a bug on that. | ||