Problem resolved with setting transfer=no in zapata.conf.<br><br><div class="gmail_quote">On Mon, Apr 12, 2010 at 9:14 PM, bruce bruce <span dir="ltr"><<a href="mailto:bruceb444@gmail.com">bruceb444@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Guys,<div><br></div><div>I am sorry if my issue is not related to this but I think it is.</div><div><br></div><div>
I have a PRI with Bell Canada and when I dial in and have the call transfered to a context to dial out and then have those two 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? </div>
<div><br></div><div>[zap_bridge]</div><div>exten => s,1,answer</div><div>exten => s,n,Dial(ZAP/g0/4167778888)</div><div><br></div><div>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 2nd party and 2nd party sees Caller ID info and when they press Talk then there is the busy signal. I can post all the debug and bore you with it but maybe someone already knows the answer.</div>
<div><br></div><div>I have been looking for this for couple of days now and I don't seem to get anywhere with answers.</div><div><br></div><div>Input is much appreciated.</div><div>Bruce</div>
</blockquote></div><br>