Has anyone got distinctive ring detection working for PSTN lines in Australia. I am using the latest CVS and have got zapata.conf set up thus: but it appears that the chan_zap modules is not going anywhere near that piece of code and all it returns is the default 0,0,0 [channels] context = default signalling = fxs_ks echocancel = 128 echocancelwhenbridged = yes echotraining = yes relaxdtmf = yes pulsedial = no rxgain = +10% txgain = 0 immediate = no busydetect = yes busycount = 6 progzone = au musiconhold = default usecallerid = yes sendcalleridafter=2 callerid = asreceived usedistinctiveringdetection = yes dring1=0,0,0 dring1context=default dring2=296,235,146 dring2context=default dring3=296,275,266 dring3context=default useincomingcalleridonzaptransfer = yes faxdetect = both group = 1 channel => 4 -- Howard. LANNet Computing Associates - Your Linux people <http://lannet.com.au> -- When you just want a system that works, you choose Linux; When you want a system that works, just, you choose Microsoft. -- Flatter government, not fatter government; Get rid of the Australian states.
Howard Lowndes
2005-Nov-03 15:39 UTC
[Asterisk-Users] Why "n" & "s" priority in CVS but not in release?
I think one of the most important and flexible features of * is the ability to restructure the dial plan by using the "n" and "s" priorities. I cannot, for the life of me, see why they only exist in the CVS strand and not in the release strand; even the CVS of the release strand doesn't have these priorities. -- Howard. LANNet Computing Associates - Your Linux people <http://lannet.com.au> -- When you just want a system that works, you choose Linux; When you want a system that works, just, you choose Microsoft. -- Flatter government, not fatter government; Get rid of the Australian states.
Howard Lowndes
2005-Nov-03 18:19 UTC
[Asterisk-Users] Why "n" & "s" priority in CVS but not in release?
Great :) Kevin P. Fleming wrote:> Howard Lowndes wrote: > >> This implies that "n" & "s" priorities are "features" since they are >> not in 1.0.x. So, when do they cease to be "features" and become a >> standard part of the released version. I have certainly found them to >> be both essential and stable. > > > They become part of a released version when the branch containing them > becomes a release itself! > > We are currently beta testing 1.2 releases, which are made from the CVS > HEAD branch, which contains these features. That means that the first > actual release that will contain these features will be 1.2.0, scheduled > for release within the next two weeks. > _______________________________________________ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-- Howard. LANNet Computing Associates - Your Linux people <http://lannet.com.au> -- When you just want a system that works, you choose Linux; When you want a system that works, just, you choose Microsoft. -- Flatter government, not fatter government; Get rid of the Australian states.
Doug Meredith
2005-Nov-04 07:24 UTC
[Asterisk-Users] Re: Why "n" & "s" priority in CVS but not in release?
"Kevin P. Fleming" <kpfleming@digium.com> wrote:>actual release that will contain these features will be 1.2.0, scheduled >for release within the next two weeks.Oh my God! A Date! :) Doug -- Doug Meredith (doug.meredith@systemguard.com) SystemGuard - Oracle remote support 877-974-8273 (87-SYSGUARD) 506-854-7997 www.systemguard.com