Yes, you are using POTS, and there is no way for asterisk (or any other pbx) to know that there is an incoming call if the actual ring hasn't been detected yet. How all the other PBXs work around this is that you make sure to plug in the lines in one direction while dialing out in the other direction. That doesn't realy get rid of the problem, it just works around it. In asterisk you do that by (assuming you have a 4 port FXO Digium card, and that you have more than one line, if you only have one then get anohter one): 1. Find out which line is always the first one for incoming in you hunt group. 2. Plug that in to the first port on the Digum card. 3. Repeat steps 1 and 2 for the next line 4. Set up your zapata.conf to have channel 1-4 as one group. 5. In extensions.conf make sure that you use dial(zap/G1) and not dial(zap/g1) that will make sure that it always tries 4 first.
On 1/12/06, Dan Elder <[EMAIL PROTECTED]> wrote: > Hey all, been noticing some oddness on a new AAH install... occasionally an > incoming zap line with automatically connect with an outgoing extension, > even though the incoming line hasn't specified what extension it's aiming > for (i.e. haven't tapped in the ext # yet)... so someone's trying to call > out from inside the office & are automatically connected with an incoming > line. Anyone seen this or know what might be causing it? > > _______________________________________________ > --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 > _______________________________________________ --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
