[asterisk-dev] Zaptel drivers Part 2

[Steven Critchfield]

On Thu, 2006-08-10 at 10:16 -0500, Tim Johnson - Eclipse Electronic
Systems wrote:
> Okay, so after taking Steven Crutchfield's advice and looking into the 
> libpri stuff, I decided to mostly use code from pridump.c to start 
> experimenting with.  First complaint the code made was in trying to open 
> the /dev/zap/1 file while the interface was in signaling 128 mode.  So I 
> changed my /etc/zaptel.conf to make all channels dchan, (see below). 
> 
> When I do this, operations on the device sort of seem to work as far as 
> opening and doing a ZT_GETEVENT.  However when I do a select() on the 
> device file, nothing appears to happen.  select() just continues to 
> wait, long after data is flowing in.  When I check my syslog, I get 
> multiple instances of:

D channels are for signalling data, and not for audio. D roughly stands
for data, and B channels are bearer channels. You need bearer channels
to actually transfer your audio.

You need to step back and use the signalling layer to setup and tear
down a call, then you can use the b channel to pass the audio.

You would probably do well to actually read the code that is around to
use zapata drivers such as the asterisk chan_zap, or
http://linuxgazette.net/120/smith.html but this doesn't use libpri.

You will probably have to do a lot of reading before you will have
enough knowledge to do anything interesting with an E1 circuit. If you
are doing a T1 circuit from zapata to zapata, you could use CAS and
ignore libpri for now.
-- 
Steven Critchfield <critch at basesys.com>