[Asterisk-Users] hint on Zap channels

[Francesco Peeters (Asterisk)]

On Fri, December 16, 2005 20:44, Kevin P. Fleming said:
> Francesco Peeters (Asterisk) wrote:
>
>> I personally think this is a fault in (*). (Or rather Zaptel)
>
> You are certainly welcome to your opinion, but thinking that Asterisk
> should understand the concept of 'remote endpoints' as native devices is
> by no means a 'fault'. If nobody has wanted this enough before to be
> able to code it up and submit it, then it's just a lack of functionality.

OK, Maybe fault wasn't the right word here... Lacking is probably better...

I'd love to look in to it and code it, but I simply haven't got the time
to investigate and code it...

>> Because there is such a thing as ISDN, I think it should be able to
>> recognize separate channels for DIDs...
>> Both internal and external ZAP channels should be able to recognise the
>> different DID/CID/CLID as separate identifiable endpoints. That way you
>> can chose a 'channel' and have (*) use the correct CID/CLID.
>
> And how would Asterisk know when these endpoints communicate directly
> with each other to keep trace of device state?

Because it would either be the device in NT mode, and therefore initiate
the connection, and be able to see the data flows. Or it would be TE mode,
but still on the same bus (which means it'll still see the data)

> It would certainly be possible to do what you want, but it would need to
> be implemented by the Zaptel driver that is communicating with that ISDN
> interface, so it can present distinct 'channels' to chan_zap for each
> device on the ISDN bus.

That's why I said 'Or rather Zaptel' in my original comment...

-- 
F Peeters
  PIII 450 - 1 GB - * 1.2 - BRIstuff 0.3.0 Pre 1 - Florz patch
  2 Sweex HFC-PCI modes=2 sync_slave=2 timer_card=0
    Cologne HFC-S pins #52, #54, #55 connected in parallel for synching.