Hi,
I've been trying to setup SMS on asterisk - would be useful to have for
things like server outages, email from important customers, etc.
I can send SMS with no issues, although I have to send it over the Zap
line.. none of the VOIP providers will route the call. It arrives on my
mobile phone a couple of minutes later (usually.. had to wait half an
hour for one).
Incoming however just isn't working. I've got a nice list of numbers
from which SMS messages come:
080057875290 and 0845602111 - BT message centre I think
01612745990 - Mentioned in BT docs but never had one from there yet
07953966066 - T-Mobile phones SMS from here - I presume there are other
ones for Orange, etc. but I don't have one of those phones to check.
My incoming sms block is just:
[sms_in]
exten => s,1,SMS(sms,a)
exten => s,2,NoOp
exten => s,3,Hangup
Outgoing is fine.. eg. smsq 0000 reset:
-- Zap/1-1 answered Local/17094009@default-99f8,2
> Channel Local/17094009@default-99f8,1 was answered.
> Lauching SMS(0) on Local/17094009@default-99f8,1
-- SMS RX 93 00 6D
-- SMS TX 91 0F 01 02 05 81 00 00 F0 00 F1 05 F2 F2 BC 4C 07 FE
-- SMS TX 92 01 FF 6E
-- SMS RX 95 09 01 00 50 30 62 10 40 42 00 ED
-- SMS TX 94 00 6C
-- SMS TX 92 01 FF 6E
-- SMS RX 95 09 01 00 50 30 62 10 40 42 00 ED
-- SMS TX 94 00 6C
-- Hungup 'Zap/1-1'
Mar 26 01:04:26 NOTICE[15806]: pbx_spool.c:244 attempt_thread: Call
completed to Local/17094009
Then the 00000 service tries to text me back with an OK message:
-- Starting simple switch on 'Zap/1-1'
-- Executing Goto("Zap/1-1", "sms_in|s|1") in new stack
-- Goto (sms_in,s,1)
-- Executing SMS("Zap/1-1", "sms|a") in new stack
-- SMS TX 93 00 6D
-- Hungup 'Zap/1-1'
It continues doing this every few minutes until it eventually gives up
about half an hour later.
What seems to be happening is the SMS application is bailing out after
the first line of the output. I've enabled debugging and verbose
logging and there's nothing printed anywhere from the SMS app.
Has anyone seen anything like this?
Tony