are you in the Toronto area Tom, and are you using Bell for your telco? The busydetect setting doesn't make a difference for me.
I just spoke to a tech support person at Sangoma and they told me that a few other people have run into this same problem and that they're currently trying to find some way to fix it. It seems the problem _is_ with the card, since the wanpipemon program shows the registers of the actual hardware card, regardless of what asterisk is doing, and the status of the registers isn't changing for about 10 seconds after a call is disconnected, which means the card is not detecting a disconnect properly. I also posted the same question on the asterisk-users digium mailing list, and a few people reported back that they're using the Sangoma A200 card with absolutely no problems in the US. So it looks like it's a problem between Bell Canada and the Sangoma card. Interesting considering that Sangoma is a local Canadian company based in Markham - you'd think that having their cards functioning properly in the Canadian market would be their first priority. So for any other Sangoma A200 owners that are having problems, let Sangoma know about it! The more they hear about this issue, the faster we'll have a solution. Thanks, Mike On 4/25/06, TOM BACEVICIUS <[EMAIL PROTECTED]> wrote: > In my testing I found I needed to have this parameter set in order for > Asterisk to hang up without reaching the default timeout. I tested this by > setting my timeout value (in extensions.conf) to a number I was sure would > be long enough > > example: exten = s,2,Set(TIMEOUT(response)=30) > > I'm pretty sure you need to restart Asterisk after making any changes to > zapata.conf (I don't think there is a way to "reload" changes made to this > file - please correct me if I'm wrong anyone). You can reload changes made > to extensions.conf by using the "extensions reload" command from the > Asterisk console. > > As far as I know the only potential downside to having this parameter set is > that it is possible for Asterisk to mistake a random noise (like a cat > meowing or something) as a busy signal. To compensate for this you can set > the "busycount=" parameter to some number that works for you. I believe the > current default for this value is 3. > > > > On 4/24/06, Mike Garey <[EMAIL PROTECTED]> wrote: > > Hi Tom, I just tried setting busydetect=yes in zapata.conf, but I > > can't see any noticeable difference. When you made this change, did > > asterisk immediately start recognizing when a call had become > > disconnected? Also, what are the downsides to using busydetect, if it > > solves the problem? Thanks, > > > > Mike > > > > On 4/24/06, TOM BACEVICIUS <[EMAIL PROTECTED]> wrote: > > > Hi Mike, > > > > > > I am having the exact same problem and was given the exact same advice > from > > > Sangoma. What I've found is that Asterisk does not detect a hangup until > it > > > hears the fast-busy signal about 10-15 seconds later. I needed to add > > > "busydetect=yes" to zapata.conf in order for this to work, otherwise the > > > default timeout would end the call. > > > > > > Hopefully a better solution can be found... If you find something, > please > > > keep us posted. > > > > > > Tom > > > > > > > > > On 4/24/06, Mike Garey < [EMAIL PROTECTED]> wrote: > > > > well, I just spoke to someone at Sangoma and they had me execute the > > > > following command after dialing into one of my channels: > > > > > > > > wanpipemon -i w1g1 -c aregdump -m <channel number> > > > > > > > > which gives the following output: > > > > > > > > ------- Direct registers (FXO,port 0) ------- > > > > > > > > 0. 00 1. 00 2. 03 3. 00 4. E9 5. 09 6. 00 7. 00 > > > > > > > > and when the phone has been disconnected, I get the following: > > > > > > > > 0. 00 1. 00 2. 03 3. 00 4. E9 5. 08 6. 00 7. 00 > > > > > > > > (the entries are listed by byte, in the above example, byte 5 has > > > > changed from 09 [channel is connected] to 08 [channel is not > > > > connected]) > > > > > > > > Anyways, after I hung up the line, the status wouldn't change for > > > > about 15 or so seconds. Now I'm not sure if this indicates a problem > > > > with the Sangoma card, or if it may just confirm that Asterisk is > > > > holding onto the channel. The Sangoma tech support person said they'd > > > > write up a support ticket and have someone else contact me regarding > > > > this.. > > > > > > > > If anyone else has run into the same problem, please let me know. > Thanks, > > > > > > > > Mike > > > > > > > > On 4/24/06, Andrew Kohlsmith < [EMAIL PROTECTED]> wrote: > > > > > On Monday 24 April 2006 14:20, Mike Garey wrote: > > > > > > We're having some problems on our asterisk box where a user calls > in > > > > > > through a PSTN line, gets to voicemail, but hangs up before > leaving a > > > > > > message, yet asterisk doesn't realize the phone has been > disconnected > > > > > > and starts recording an empty message, which of course can become > very > > > > > > annoying. I also notice that when calling from a PSTN line and > > > > > > ringing an extension, then immediately hanging up, the SIP phone > on > > > > > > the other end will continue ringing about 4 or 5 times before > Asterisk > > > > > > realizes the call has hung up. > > > > > > > > > > Bell Canada does indeed provide CPD, but I don't think it's in a > form > > > that the > > > > > analog cards are happy with. > > > > > > > > > > If you use your cellphone to call your landline, have a short > > > conversation > > > > > with yourself and then hang up the cellphone, the landline will go > > > > > completely, totally dead for about 300-500ms before you get another > > > dialtone. > > > > > That's Bell's CPD: Battery removal. If you have a VOM you can > place it > > > > > across the tip&ring and see the ~5V drop to 0 briefly before going > back > > > to > > > > > ~5V when this happens. > > > > > > > > > > You *might* be able to get away with callprogress=yes but that's > also > > > crappy > > > > > and can cause random disconnects. > > > > > > > > > > -A. > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > >
