What kind of channel should I be trying to configure 1 tdm410 with 1 fxo

This machine is in secure environment, no HDD, no nic, no mass storage, boot from live cd with only a small usb stick to hold the the config files (asterisk 1.4.24.1 on astlinux)

What kind of channel should I be trying to configure if I have one analog phone line, 1 tdm410 and 1 fxo module (yes I'm a newbie and have spent a week on this already, trying to learn, the problem is, all the documentation is written for people who already know everything).

What do i need to put in the 'channel:' field for a call file is the real question - the card works for answering incoming, (shows DAHDI/1-1 in the CLI whatever that is) but won't do outgoing calls using call files

The card seems to be installed ok, but when i do ztcfg -vv it says 1 card TO configure, it doesn't say configured, what's the next step in configuring the channel?

The following is just stuff I've seen in the documentation, maybe something in it will give an answer that I can't see.

lspci -n | grep s191 gives:
01:04.0 Class 0200: d161:8005 Rev 11

modprobe wctdm24xxp gives:
finds the card, shows auto fxo in port 1, fcc mode
port 2,3 and 4 are empty and i don't have the echo cancellation

ztcfg -vv gives:
channel 01:  FXS Kewlstart (default) (Slaves: 01)
1 Channel to configure

zaptel.conf
loadzone=us
defaultzone=us
fxsks=1

zapata.conf
[channels]
signalling=fxs_ks
language=en
context => outgoing
channel => 1

extensions.conf
[outgoing]
exten => s,1,Wait(1)
exten => s,2,Playback(tt-weasels)
exten => s,3,Hangup( )
;will eventually use record() here

[incoming]
exten => s,1,Answer(1)
exten => s,2,Wait(1)
exten => s,3,Playback(tt-weasels)
exten => s,4,Hangup( )

thanks
scott_audioAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
MysidiaConnect With a Mentor Commented:
Based on the above, I would put
channel: Zap/g0
in the file for the outbound call.

Your zaptel.conf  looks proper for configuring a FXO port; you indeed want to use the FXS protocol, and KS (if available),  although in some rare cases fxsks hangup notification might not be there;  you could need fxls in zaptel.conf   and fxs_ls  in zapata.conf,  on the rare occasion you are connected to a telco provider that doesn't support  kewlstart.


To see your active zap channel numbers in Asterisk, do the following:
# rasterisk
asterisk> zap show channels
asterisk> exit

zapata.conf defines your channel groups. In yours you appear to have one group of channels defined, without a   group=  line before the matching channel=> line
so, that group number will be 0,

Therefore for outbound purposes, you should be Dialing Zap/g0
Or  the channel directly is  Zap/1

       zapata.conf
       [channels]
       signalling=fxs_ks
       language=en
       context => outgoing
       channel => 1
0
 
scott_audioAuthor Commented:
Mysidia:

Thank you for your clear concise answers - very helpful.

I added group=0 to zapata

After reloading, I do 'core show channels'  - it shows
0 active channels
0 of 1 Max active calls

Is that what it's supposed to say?

It won't answer incoming or do outgoing, but I had the incoming working before - I'm going to do a fresh install and setup again with the information you've given me, and see how that works, will post results, thanks again

scott
0
 
scott_audioAuthor Commented:
also did 'zap show channels' as told but in CLI it says that's not a valid command

when i do 'core show channeltypes', zap is not listed if that's helpful at all

listed are Agent, Local, IAX2, MGCP, Phone, SIP, Skinny and Console

0
 
scott_audioAuthor Commented:
ended up using DAHDI vs. Zap - I still don't understand completely, but it's working, so I'll do some more reading and learning, also OSS vs. ALSA was an issue.  You've been a big help, and I very much appreciate your taking time to respond.  -Scott
0
 
MysidiaCommented:
0 of 1 Max active calls
Is normal to see when there is not a call active, but you have 1 available channel device.

Apparently DAHDI is  a new name for the Zaptel project, which got changed due to trademark reasons (another company came up with a trademark to the Zaptel name),
and  Digium has renamed Zap to DAHDI  in some of the newest releases of Asterisk.
http://www.voip-info.org/wiki/view/DAHDI
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.