Re: [asterisk-users] WARNING[21314]: chan_zap.c:8396 pri_dchannel: Ring requested on channel 0/1 already in use on span 1. Hanging up owner.
Hi Steve, I will try to make how you suggest...to use G instead of g but the problem remains inside Asterisk. If there is a dynamic channel allocation made by Asterisk, that message is non-sense.if telco sends a call on channel X and Asterisk has a free channel Y, Asterisk should use channel Y. Stop. Why showing that message? I do not know. If these message cannot be avoidedwell..I'll keep it, even if it is a bit strange to have a warning inside a system in general. Thank you Giorgio Incantalupo Steve Davies wrote: On 9/12/06, Steve Davies [EMAIL PROTECTED] wrote: On 9/12/06, Giorgio Incantalupo [EMAIL PROTECTED] wrote: Hi, I get many of these warnings inside Asterisk log: WARNING[21314]: chan_zap.c:8396 pri_dchannel: Ring requested on channel 0/1 already in use on span 1. Hanging up owner. What does they mean?? Can I assume then that 'resetinterval=never' did not make this problem go away? To expand on my interest this... We have a number of nearly identical installations of Asterisk. Same H/W, same Zaptel, and same Asterisk build etc etc - All of the PRI hardware is the same (Sangoma A101U), and a huge percentage of E1 lines in the UK are terminated by British Telecom. Even though there is this amount of comonality between them, we have exactly one customer who gets the already in use message seen above on a regular basis, and a second customer who had the error only once. The error tends to be fatal for inbound calls as it leaves the channel locked permanently and the telco continues to try to use it :( In almost every case there is an obvious SIP conversation on the box that has not cleared down fully, and which seems to be holding the Zap channel open in error. In the first company, they use a lot of WiFi phones, and in the 2nd company they used to use WiFi phones (different model), but don't anymore... I am assuming there is some kind of race condition going on, perhaps caused by slow or unreliable SIP phone responses to call closedown events. I looked at the zaptel code where this message is generated, in the hope that I could request a flush of the channel that incorrectly shows this channel open (if the telco is trying to put a call through, then the line is definitely meant to be clear!) but it was way beyond my ability to understand. I thought about Glare (someone else suggested that in another messsage), but the telco uses lowest-free channel, and we use Zap/1G, so use the highest free channel. Any thoughts or input are very welcome. Thanks Steve ___ --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
Re: [asterisk-users] WARNING[21314]: chan_zap.c:8396 pri_dchannel: Ring requested on channel 0/1 already in use on span 1. Hanging up owner.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Giorgio Incantalupo wrote: Hi Steve, I will try to make how you suggest...to use G instead of g but the problem remains inside Asterisk. If there is a dynamic channel allocation made by Asterisk, that message is non-sense.if telco sends a call on channel X and Asterisk has a free channel Y, Asterisk should use channel Y. Stop. Why showing that message? I do not know. If these message cannot be avoidedwell..I'll keep it, even if it is a bit strange to have a warning inside a system in general. Thank you Giorgio Incantalupo I have sometimes similar things happening, with a call coming in via SIP sometimes taking over one or more zap channels (wtf?). This is with a TDM400P -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5-ecc0.1.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFB8dcXqd/7Teiu2oRAgIGAJ0Y4cvFyCDYWdQOGgcWN7gPoiNIcQCeNENN Wxptm3Cs+5OeJQHLDSpa0tQ= =g6FU -END PGP SIGNATURE- ___ --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
[asterisk-users] WARNING[21314]: chan_zap.c:8396 pri_dchannel: Ring requested on channel 0/1 already in use on span 1. Hanging up owner.
Hi, I get many of these warnings inside Asterisk log: WARNING[21314]: chan_zap.c:8396 pri_dchannel: Ring requested on channel 0/1 already in use on span 1. Hanging up owner. What does they mean?? TIA Giorgio Incantalupo ___ --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
Re: [asterisk-users] WARNING[21314]: chan_zap.c:8396 pri_dchannel: Ring requested on channel 0/1 already in use on span 1. Hanging up owner.
On 9/12/06, Giorgio Incantalupo [EMAIL PROTECTED] wrote: Hi, I get many of these warnings inside Asterisk log: WARNING[21314]: chan_zap.c:8396 pri_dchannel: Ring requested on channel 0/1 already in use on span 1. Hanging up owner. What does they mean?? Can I assume then that 'resetinterval=never' did not make this problem go away? Cheers, Steve ___ --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
Re: [asterisk-users] WARNING[21314]: chan_zap.c:8396 pri_dchannel: Ring requested on channel 0/1 already in use on span 1. Hanging up owner.
On 9/12/06, Steve Davies [EMAIL PROTECTED] wrote: On 9/12/06, Giorgio Incantalupo [EMAIL PROTECTED] wrote: Hi, I get many of these warnings inside Asterisk log: WARNING[21314]: chan_zap.c:8396 pri_dchannel: Ring requested on channel 0/1 already in use on span 1. Hanging up owner. What does they mean?? Can I assume then that 'resetinterval=never' did not make this problem go away? To expand on my interest this... We have a number of nearly identical installations of Asterisk. Same H/W, same Zaptel, and same Asterisk build etc etc - All of the PRI hardware is the same (Sangoma A101U), and a huge percentage of E1 lines in the UK are terminated by British Telecom. Even though there is this amount of comonality between them, we have exactly one customer who gets the already in use message seen above on a regular basis, and a second customer who had the error only once. The error tends to be fatal for inbound calls as it leaves the channel locked permanently and the telco continues to try to use it :( In almost every case there is an obvious SIP conversation on the box that has not cleared down fully, and which seems to be holding the Zap channel open in error. In the first company, they use a lot of WiFi phones, and in the 2nd company they used to use WiFi phones (different model), but don't anymore... I am assuming there is some kind of race condition going on, perhaps caused by slow or unreliable SIP phone responses to call closedown events. I looked at the zaptel code where this message is generated, in the hope that I could request a flush of the channel that incorrectly shows this channel open (if the telco is trying to put a call through, then the line is definitely meant to be clear!) but it was way beyond my ability to understand. I thought about Glare (someone else suggested that in another messsage), but the telco uses lowest-free channel, and we use Zap/1G, so use the highest free channel. Any thoughts or input are very welcome. Thanks Steve ___ --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
