[Asterisk-Dev] More Zaptel/BRI questions

[Matthew Fredrickson]

On Jan 6, 2006, at 8:38 AM, <kpj at junghanns.net> wrote:

>>>
>>
>> Zaptel likes to just have the raw B-channel data.  If you are trying 
>> to
>> also interface the D-channel with zaptel and you can pull your
>> HDLC-unstuffed messages from the BRI controller, you can use the
>> software API for zaptel for basically passing D-channel messages into
>> the zaptel buffers the way the userland apps expect it (without having
>> to go through the HDLC and other code).  If you look at bug note 5120
>> (IIRC) the most recent version of the patch against zaptel can be
>> found.
>>
>> Due to the timing difference, (16kbps as opposed to 64kbps) this is 
>> the
>> approach you'll probably want to take for the D-channel, unless you 
>> can
>> think of a really clever way to pass the raw data into zaptel.
>>
>
> Check out the minimal zaptel patch included in BRIstuff. It basically 
> only
> adds support to send/receive raw data (where HDLC is en-/decoded by the
> hardware).
> It's also quite useful if you want to interface zaptel to some other 
> kind
> of hardware (e.g. we are using it to interface with serial interfaces 
> on
> our multiGSM PCI card).
>

Yeah, I just realized right after I sent that email that you could 
probably even do a raw 16kbit/sec HDLC encoded pipe to a zap channel 
without problems.  The timing is pretty much only crucial for audio 
purposes anyway.

Matthew Fredrickson