search for: zap_bridge

...ing that call out to another number. Problem is that the call rings out but the moment the other party pickups both legs of the call are disconnected give Cause code 16. ********************************************************************************************************************* Dialplan: [zap_bridge] exten => s,1,answer() exten => s,n,Dial(ZAP/g0/4168889999) ********************************************************************************************************************* *****************************************************************************************************************...

...channels bridged, the call disconnects with cause 16 just exactly as Jay R. Ashworth shows in his CLI output. Bell Canada support RLT or know as 2BCT or TBCT to some but we have not requested that feature. However, we don't care to keep two channels tied up. Is this not possible through PRI? [zap_bridge] exten => s,1,answer exten => s,n,Dial(ZAP/g0/4167778888) If incoming leg of call is through PRI and outgoing leg is through SIP or analogue ZAP everything works just fine. But the moment Call comes in through PRI and goes out through PRI both channels drop. I should say that call rings the...

...legs of the call are disconnected give Cause code 16. >>> >>> >>> >>> >>> ********************************************************************************************************************* >>> >>> Dialplan: >>> >>> [zap_bridge] >>> >>> exten => s,1,answer() >>> >>> exten => s,n,Dial(ZAP/g0/4168889999) >>> >>> >>> ********************************************************************************************************************* >>> >>&gt...