You could use Eric's solution to minimize glare, but in my experience having the circuit set to CO Yields causes a ton of problems. This is only from my experience with a couple of my customers and also my old PRI at the office. Just about the time I figured out the problem with my circuit was glare we ended up moving to Level(3)'s hosted product and disconnected the circuit. Once 3tone went away we ended up getting a PRI through a different provider and I made it a point to double and triple check the glare setting with the provisioner.
We experienced "All Circuits Busy" messages on people calling into the office. We never had more than 8-10 calls going at one time when we were receiving this message so there were plenty of channels available, but since the CO was yielding to the CPE (CO Yields) it would immediately give that "All Circuits Busy" message when it collided with our equipment. I just wanted to make it clear that these problems were with a different phone system, not Asterisk. I really suggest you have the phone company switch you to CPE Yields and implement what Eric suggests as that is good practice anyway. On 11/27/06, Matt <[EMAIL PROTECTED]> wrote:
Can I set the yield option on asterisk? The telco confirmed it is set to CO Yields... which to me doesn't make a whole lot of sence... On 11/22/06, Rob McKrill <[EMAIL PROTECTED]> wrote: > Check with your telco on the "Glare" setting. They probably have Glare set > to "CO Yields" which tells their switch to 'yield' to your switch/pbx when > negotiating which channel to use. We ran into this problem with our PRI and > an older phone system that did not give nearly the amount of insight (logs) > as to what the problem might be. > > It sounds like you probably want them to set it to "CPE Yields". > > > On 11/21/06, Matt <[EMAIL PROTECTED]> wrote: > > > > We are doing PRIs into T4XXP cards. When I call out things are > > fine... however tonight sometimes on inbound calls I'd get: > > > > chan_zap.c: Duplicate setup requested on channel 0/1 already in use on > span 1 > > > > in the full debug log followed by a fast busy signal on the calling > parties end. > > > > Anyone know what would cause that? > > _______________________________________________ > > --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 > > > _______________________________________________ --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
