waitfordialtone=yes on chan_dahdi.conf is supposed to be the perfect solution, but does it work on on UK lines?
Kelvin Chua On Fri, Aug 26, 2011 at 4:44 PM, Kelvin Chua <kel...@gmail.com> wrote: > i am comparing the experience of using an analog span to a T1 for example: > if i have a 3 quad port t1 card, with the initial view of dahdi_tool, i can > easily tell if a line is not working > now supposed i have a system with 3 24port cards, with just watching the > main view of dahdi_tool, > i cannot do that, i still need to go into each one, and look at the stats > > maybe it's just me but i think it's making things easier for everyone if > there is some sort of an indication > there like > please-take-a-look-at-this-as-i-have-a-port-here-without-a-battery (not > really yellow, perhaps orange? :D) > > > using callprogress is *experimental* > ; This feature can also easily detect false hangups. The symptoms of this > is > ; being disconnected in the middle of a call for no reason. > it's actually ok for me, but for other zones, it might not be adviseable. > for example, calling a mobile phone and a > landline would give you a different tone and cadence for the ringback thus > billing apps will be completely screwed. > (unless already anticipated by the billing software) > > what i have in mind is just plain simple. when the fxo port goes offhook, > it waits for the dial tone (based on tonezone) > after that, nothing more so as to avoid detection of false hangups. i think > this is not too hard as Newman Ventures implemented > something like this before. > > Kelvin Chua > > > > On Fri, Aug 26, 2011 at 11:51 AM, Shaun Ruffell <sruff...@digium.com>wrote: > >> On Fri, Aug 26, 2011 at 10:58:10AM +0800, Kelvin Chua wrote: >> > I should clarify on my post, i can see a red alarm on cat /proc/dahdi/1 >> but >> > never when using dahdi_tool >> > >> > in cat /proc/dahdi/1: >> > Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER) >> > >> > 1 WCTDM/4/0 FXSKS (In use) RED(SWEC: OSLEC) >> > 2 WCTDM/4/1 FXSKS (In use) RED(SWEC: OSLEC) >> > 3 WCTDM/4/2 FXSKS (In use) RED(SWEC: OSLEC) >> > 4 WCTDM/4/3 FXSKS (In use) RED(SWEC: OSLEC) >> > >> > In dahdi_tool: >> > Tx/Rx Levels: 0/ 0 >> > Total/Conf/Act: 4/ 4/ 0 >> > >> > but the behavior status alarm is OK >> > a little bit misleading, what i am thinking is adding a sort of "yellow" >> > alarm or something if one of the configured fxo lines >> > goes down? >> >> I understand now. Yes, dahdi_tool is showing the alarm status for >> the entire span, and for analog cards, the entire span is always >> essentially green. It's the individual channels that can go into red >> alarm unlike on digital spans. >> >> Why do you want to add a yellow status? What are you trying to >> accomplish that you cannot with the way things are now? >> >> > another thing, what if 1 of the configured lines' battery is up, but >> there >> > is no dial tone? outbound calls will try to go through >> > and the caller will hear dead air. >> >> 'callprogress=yes' in chan_dahdi.conf won't help you here? It may be >> able to detect dialtone before attempting to dial out. >> >> -- >> Shaun Ruffell >> Digium, Inc. | Linux Kernel Developer >> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA >> Check us out at: www.digium.com & www.asterisk.org >> >> -- >> _____________________________________________________________________ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> New to Asterisk? Join us for a live introductory webinar every Thurs: >> http://www.asterisk.org/hello >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users >> > >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users