stéphane plichon wrote: > stéphane plichon wrote: > >>Hi all, >> >>currently i running * 1.0.9 with chan_capi 0.3.5 >> >>my first problem is: >> >>in incoming call, when BCHAN is full in contr1 incoming call on contr2 >>are not answered with error : >> >>chan_capi.c:1953 in capi_handle_msg: received a call waiting CONNECT_IN >> >>but if use different msn in capi.conf incoming call works on both controler >> >> >> > > ok, now working, but i get only ring on third call >
always 2 sections, i'm going to upgrade ; ; CAPI config ; ; [general] nationalprefix=0 internationalprefix=00 rxgain=0.8 txgain=0.8 [interfaces] isdnmode=ptp ;msn=9881 incomingmsn=* ;9881,2942,2943,2944,2945,2946,2947,2948,2949 controller=1 group=1 deflect=0472529256 softdtmf=1 accountcode= context=capi-in devices=2 isdnmode=ptp ;msn=9881 incomingmsn=* ;9881,2942,2943,2944,2945,2946,2947,2948,2949 controller=2 deflect=0472529256 group=1 softdtmf=1 accountcode= context=capi-in devices=2 -- Stephane Plichon | HASGARD tel: +33 (0)472529881 fax: +33 (0)472177764 web: http://www.hasgard.net email: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] ~ _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
