hi, Just wanted to inform everyone, if you're using the latest bristuff's you might (depends on the country!) have hangup issues. The issue appears every time you dial an external number, and hangup after letting it ring for a few times. Then the remote party keeps ringing. In some situations (we only encountered this while dialing to other * servers) it keeps the line open on the telco-side. Meaning.. you pay for it! The cdr on the calling asterisk (with the bug) doesn't indicate a long connection time. However, the cdr on the called asterisk does.. (I've seen several durations of over 20 hours) A show channels doesn't indicate any active calls. A quick fix has been posted a while ago by Marcel van der Boom (in libpri/q931.c), this works. According to the release notes this should have been applied to the latest bristuff, but be careful, the problem still exists on bristuff-0.3.0-PRE-1q. I have emailed junghanns.net to let them know. Best regards, stoffell
2006/6/29, stoffell <stoffell@gmail.com>:> I have emailed junghanns.net to let them know. > > Did they acknowledge the issue ?"The issue appears every time you dial an external number, and hangup after letting it ring for a few times". Is it really every time ? Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060629/97ce9d8d/attachment.htm
> A quick fix has been posted a while ago by Marcel van der Boom (in > libpri/q931.c), this works.The fix works, but it creates another bug afaik. Once you apply the "q31.c ourcallstate/peercallstate patch" as I call it, the line gets hung up normally, but for some odd reason all the scripts in the hangup extension won't run. So be aware of that. Quote from Marcel: ----------- I've done a bit more testing and in our install the patch seems to cause an issue with the 'hangup' (h) extensions. We use this to convert incoming faxes to pdf and send them off through mail after the sending fax machine hangs up. The hangup extension is never reached so that bit of our dialplan didnt work anymore. Since both patched and unpatched dont work with that particular setup, there's no way (i know) to test out wether this is actually caused by the patch or not, but i thought i'd just mention it. ----------- Cheers, Jeroen Zwarts
I can also add that this happens on em_w lines as well. I've had issues where callers start getting dead air when dialing out. Talking with the phone company the lines were in an off-hook state even though Asterisk hung up the call. I done exactly as below where I hang up before the other party answers the call. I've also had where after I hang up the CLI shows the call hanging up and then another call starts, starting simple switch, as if the call was re-established but Asterisk doesn't know what to do with the call and executes the s,1,hangup() on the call. This does NOT however always hang up the call on the AT&T side. The T1 still shows the call as off-hook even though it's not in use. It seems random (at least I haven't figured out the pattern yet) as to when the channel gets hung up properly on AT&T's side and when it's not. -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of stoffell Sent: Thursday, June 29, 2006 3:44 AM To: asterisk-users@lists.digium.com Subject: [Asterisk-Users] bristuff hangup issue hi, Just wanted to inform everyone, if you're using the latest bristuff's you might (depends on the country!) have hangup issues. The issue appears every time you dial an external number, and hangup after letting it ring for a few times. Then the remote party keeps ringing. In some situations (we only encountered this while dialing to other * servers) it keeps the line open on the telco-side. Meaning.. you pay for it! The cdr on the calling asterisk (with the bug) doesn't indicate a long connection time. However, the cdr on the called asterisk does.. (I've seen several durations of over 20 hours) A show channels doesn't indicate any active calls. A quick fix has been posted a while ago by Marcel van der Boom (in libpri/q931.c), this works. According to the release notes this should have been applied to the latest bristuff, but be careful, the problem still exists on bristuff-0.3.0-PRE-1q. I have emailed junghanns.net to let them know. Best regards, stoffell _______________________________________________ --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
Seemingly Similar Threads
- Bristuffed Asterisk: Hangup problems
- IPcortex: ERROR[23444] chan_zap.c: You cannot use cause 17 number when in state 6
- FW: IPcortex: ERROR[23444] chan_zap.c: You cannot use cause 17 number when in state 6
- [patch] fix libpri problem in Q931_INFORMATION handling
- [kpj@junghanns.net: Re: [asterisk@frameweb.it: RE: Corrupt CDR records in Asterisk 1.2.x]]