asterisk users - Dec 2007 - smsq, Zaptel in UK

Hi all,

I've been trying to get SMS operational on my Asterisk box, which has a
TDM400P card with a pair of FXO interfaces configured (ZAP/1 & ZAP/2).

I've not had luck with either of my lines, after issuing the command
"smsq --motx-channel=ZAP/1/1709400X 00000 register".  I see the
following output in my Asterisk console:

    -- Attempting call on ZAP/1/17094009 for application SMS(0) (Retry
    1)
    -- Hungup 'Zap/1-1'
[Dec 26 18:17:07] NOTICE[526]: pbx_spool.c:341 attempt_thread: Call
failed to go through, reason (1) Hangup

It keeps retrying with the same message as above until giving up.  It
doesn't seem to make any difference whether I specify ZAP/1 or ZAP/2. 
When I look in /var/spool/asterisk/outgoing, I see a file with the
following content:

  Channel: ZAP/1/17094009
  Callerid: SMS <0>
  Application: SMS
  Data: 0
  MaxRetries: 10
  RetryTime: 1
  WaitTime: 10

In /var/spool/asterisk/sms/motx I see a corresponding file with the
following contents:

  da=00000
  ud=register

I'm probably missing something really obvious, but I've not found
anything via Google that suggests what I'm doing wrong.

I'm running Asterisk 1.4.14 & Zaptel 1.4.6 on Ubuntu 7.10.  Any help
would be appreciated.

Cheers,
Chris
-- 
  Chris Notley
  chris at notley.org

On Wed, 2007-12-26 at 18:53 +0000, ml-asterisk at notleyc.fastmail.fm
wrote:
> It doesn't seem to make any difference whether I specify ZAP/1 or
ZAP/2.
Just a random thought (since I don't use smsq)...

When specifying a Zap channel, the technology should be capitalized
"Zap" and not "ZAP".  For example, use "Zap/1",
not "ZAP/1".  I'm not
sure whether or not this will solve your particular problem, but I
thought I'd point it out in the off chance that it does.

---
Jared Smith
Community Relations Manager
Digium, Inc.