Removed complete bchannel handling from chan_lcr The remote application interface does not allow any bchannel to be exported or imported. Audio traffic via socket interface is used instead. The joinremote instance became obsolete and is removed. The remote action (routing) became obsolete, use interface.conf instead. The handling of loopback device became obsolete and was removed The chan_lcr does not rely on mISDN anymore, that means: - can be used with GSM and without mISDN at all. - chan_lcr can be used as internal extension of LCR (e.g. SIP phone) (chan_lcr can be handled as any other interface) - no loopback device to be used anymore.
Adding simple bridge application to forward calls without PBX app. Call received on an interface can directly be forwarded to a given destination interface, instead of routing the call through PBX application. This way calls can be forwarded without going through route.conf. Currently only SIP and GSM destinations are supported. Also there are no tones generated, if one side provides no tones, but the other wants to receive them. The keyword "bridge <output interface>" in interface.conf is used. Without that keyword, incomming calls are handled as usual.
Replaced polling loop for LCR and chan_lcr with select based event loop. Now LCR and chan_lcr will not use any CPU until there is work to do.
changed long to int (64 bit system's compatibilty)
unified socket application interface (for asterisk and maybe other apps) bugfixes
alpha phase is open, this means: it compiles! it runs! it calls without known bug yet! comments to jolly@eversberg.eu