[Home]

Summary:ASTERISK-15400: Conference Calls
Reporter:Tony Banks (shazzam-1)Labels:
Date Opened:2010-01-05 16:00:08.000-0600Date Closed:2011-06-07 14:07:49
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_zap
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:During our weekly conf calls(3hours), there are number of times when we have to hang up and dial back in due to another bridge overlapping noise on to our bridge.  Basically about 45-50 minutes in we would start hearing another conference call going on but they could not hear us.


Here is our config

Zapata.conf


[general]
echocancel=yes
echocancelwhenbridged=yes
echotraining=yes

[channels]
context=t1
language=en
switchtype = national
signalling = pri_net
group = 1
channel => 1-23

extension.conf

[xxx conference]
exten => s,1,NoOp(** Entering xxx Conferencing)
exten => s,n,Wait(1)
exten => s,n,Background(xxxconf/welcome)
exten => s,n(enterid),Read(CONFID,xxxconf/enterconfid,6,,2)
exten => s,n,GotoIf($[ 0${CONFID} < 100000 ]?noentry)
exten => s,n,Goto(xxx-conference,${CONFID},1)
exten => s,n,NoOp(*******************************NEXTLINE******************)
exten => s,n(noentry),Playback(xxxconf/goodbye)
exten => s,n,Hangup()

Please let me know if you need additional information.
Comments:By: Leif Madsen (lmadsen) 2010-01-06 08:44:57.000-0600

Marking this as related to issue ASTERISK-15368 as it seems similar, especially since you say you're using Zaptel.

Unfortunately, since you're using an older version of 1.4, and Zaptel, it could be that the issue is resolved by updating Zaptel to DAHDI as Zaptel is no longer supported.

I'd start with producing some logging files of when the issue happens, along with a more complete dialplan as the one you've provided does not appear to connect to a conference room at all.

Also, check with issue 16514 as well to see if any of the requested information there you could also provide.
By: Leif Madsen (lmadsen) 2010-03-23 09:44:22

I'm suspending this issue due to lack of feedback from the reporter. However, I'd suggest following up on the related issue and not necessary reopening this issue.