I am finding that with the combination above, the zap channel will hang up, though the call has hung up. I am make all changes in my zapata.conf file that I can find on the internet with nothing fixing this issue. I have added busydetect=yes, busycount=6, and made sure that the signalling is set for fxs_ks these setting worked fine with zaptel 1.2 but not with the newest zaptel drivers. Is there something i can do or change or check (besides getting rid of the x100p) that can fix this annoying issue? Thanks in advance. Mark
Tzafrir Cohen
2008-Jan-21 15:27 UTC
[asterisk-users] x100p & Asterisk 1.4.17 and Zaptel 1.4.7
On Tue, Jan 22, 2008 at 01:12:56AM +1100, Mark Huff wrote:> I am finding that with the combination above, the zap channel will hang > up, though the call has hung up.There seems to be a typo in the above line.> > I am make all changes in my zapata.conf file that I can find on the > internet with nothing fixing this issue. > > I have added > busydetect=yes, busycount=6, and made sure that the signalling is set > for fxs_ksWhere are you from?> > these setting worked fine with zaptel 1.2 but not with the newest zaptel > drivers. Is there something i can do or change or check (besides > getting rid of the x100p) that can fix this annoying issue?busydetect could be further tuned. KNowing where you're from can help. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir