search for: dring2

Is it possible to allow distinctive rings work for FXS ports as well? I need a certain FXS extension to ring a distinctive double ring. I modified zapata.conf appropriately for dring1,dring2 and it just Seems to ignore my updates. Do distinctive rings only work for FXO ports? Paul Seniuk -------------- next part -------------- A non-text attachment was scrubbed... Name: Paul Seniuk.vcf Type: application/octet-stream Size: 2406 bytes Desc: not available Url : http://lists.digium...

...e ring to work on my PSTN with no luck. I can get 2 different ring codes but it skips the context assigned... here is my complete zapata.conf: [channels] signalling=fxs_ks usecallerid=yes rxgain=1.0 txgain=1.0 language=en context=default usedistinctiveringdetection=yes dring1=134,0,0 dring2=137,0,0 dring1context=internal2 dring2context=default channel => 1 here is the debug output: Aug 18 10:36:20 NOTICE[1112767280]: chan_zap.c:5053 ss_thread: Got event 2 (Ring/Answered)... -- Detected ring pattern: 137,0,0 -- Distinctive Ring matched context internal2 -- Executing Wai...

...They are are follows: 1. standard ring 2. short ring 3. long ring 4. short ring, long ring, short ring Based on the information I have been able to find, I have created the following entries in my zapata.conf file, to try and weed out some of the timings: dring1=95,0,0 dring1context=dist_ring1 dring2=95,325,95 dring2context=dist_ring2 dring3=325,0 dring3context=dist_ring3 ; If no pattern is matched here is where we go. context=dist_ring0 channel => 1 I am assuming that "95 ms" is a short ring and "325 ms" is a long ring. In my extensions.conf file, I have the followin...

...ich parameters in zapata.conf are global and which ones can be channel specific & nested. I have mucked around with it but I can't seem to make any effect on the gain levels on a per channel basis. dring1context=pbx } dring1=0,0,0 } obviously global because it sets conditions for dring2context=fax } all inbound calls dring2=387,321,0 } signalling=fxs_ks } is this the "lead" or should channel be the lead group=1 channel=1-2 rxgain=6 } can this go here to effect just chan 1-2? txgain=0 } signalling=fxo_ks group=2 mailbox=500 channel=3 rxgain=...

...es=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes canpark=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes rxgain=5.0 txgain=-7.0 group=1 callgroup=1 pickupgroup=1 immediate=no usedistinctiveringdetection=yes dring1=360,230,193 dring1context=from-intercom dring2=205,93,0 dring2context=from-zaptel dring3=0,0,0 dring3context=from-zaptel ;Sangoma A200 [slot:6 bus:1 span:1] context=from-zaptel group=0 signalling = fxs_ks channel => 1-4 zaptel.conf: # Autogenerated by /usr/local/sbin/sangoma/setup-sangoma -- do not hand edit # Zaptel Channels Configuration...

I know this subjeact has been beaten in here so much, but, here is my issue.<br /><br />I have a TDM400 with 2 ports tied into our telco lines. I have run fxotune on the lines, and have got the conf file in my /etc folder. I have fxotune loading in my startup right after the drivers load up, then asterisk loads up. <br /><br />Problem! When calling out, we get a horible

Hi All, I was wondering what the status of distinctive ring support in Asterisk is? I had a google search & read and Mark Spencer wrote some support for it. Is distinctive ring different in every country or is it pretty standard? And for my final question, does the Wildcard FXO card support distinctive ring? Essentially what I'm trying to do is route incoming calls with ring #1 to,

I tried implementing my * and it didn't pass the spouse factor at this time. I wanted to hook it up for outbound only at this point to get a better handle on the dial plans and the echo problem. I thought this might have been done before as a natural part of testing - but maybe not. In wcfxo.c I found this: if (!wc->offhook && !wc->ringdebounce) { if

...signalling = pri_net group = 1 channel => 1-23 ; ; Used for distintive ring support for x100p. ; You can see the dringX patterns is to set any one of the dringXcontext fields ; and they will be printed on the console when an inbound call comes in. ; ;dring1=95,0,0 ;dring1context=internal1 ;dring2=325,95,0 ;dring2context=internal2 ; If no pattern is matched here is where we go. ;context=default ;channel => 1

Hi, all I have installed TDM400 with 1 FXS and 1 FXP ports. Now I am goig through documentation on how to configure it. It mentions 3 protocols: Loopstart, Groundstart and Koolstart. Which one do I use? Can someone send me sample zaptel.conf file for Australia? This will save me some time and will be used as a working example. Thanks, Rudolf

...; ; Used for distintive ring support for x100p. ; You can see the dringX patterns is to set any one of the dringXcontext fields ; and they will be printed on the console when an inbound call comes in. ; ;dring1=95,0,0 ;dring1context=internal1 ;dring2=325,95,0 ;dring2context=internal2 ; If no pattern is matched here is where we go. ;context=default ;channel => 1 ----------------------------------------------------- zapata.conf: ----------------------------------------------------- loadzone = us #loadzone=fr #loadzone=de #loadzone=uk #loadz...

...alling = pri_cpe ; group = 2 ; channel => 1-23 ; ; Used for distintive ring support for x100p. ; You can see the dringX patterns is to set any one of the dringXcontext fields ; and they will be printed on the console when an inbound call comes in. ; ;dring1=95,0,0 ;dring1context=internal1 ;dring2=325,95,0 ;dring2context=internal2 ; If no pattern is matched here is where we go. ;context=default ;channel => 1 ; PSTN line for Will group=1 callgroup=1 pickupgroup=1 signalling=fxs_ks context=incoming-from-pstn-will callerid=Unknown call for Will's PSTN line <UNKNOWN> channel =&g...

...ri_cpe [ISDN PRI Switch Configuration] switchtype=national overlapdial=no pridialpan=unknown [Some Other Settings] language=en context=default [Multilink PPP Options] ;minunused=2 ;minidle=1 ;idledial=6999 ;idleext=6999@idle [Analog Trunk Features] usedistinctiveringdetection=no ;dring1=96,0,0 ;dring2=325,95,0 ;dring=367,0,0 ; ;dring1context= ;dring2context= ;dring3context= ; busydetect=yes busycount=8 callprogress=no pulse=no [Analog Handset Features] asdi=no immediate=no callwaiting=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes cancallforward=yes callreturn=yes ; ;group=1 ;call...

...g = pri_cpe ; group = 2 ; channel => 1-23 ; ; Used for distintive ring support for x100p. ; You can see the dringX patterns is to set any one of the dringXcontext fields ; and they will be printed on the console when an inbound call comes in. ; ;dring1=95,0,0 ;dring1context=internal1 ;dring2=325,95,0 ;dring2context=internal2 ; If no pattern is matched here is where we go. ;context=default ;channel => 1 -------------------------------------------------------------------------------- EXTENSIONS.CONF -----------------------------------------------------------------------------...

Hi All, Having searched the archives, I can see there has been much discussion at various points regarding capture of caller id information from good old BT. If I understand correctly, it seems that not only do the drivers not currently support it, but my X101P possibly/probably can't do it anyway due to hardware? So, that leaves me with the modem route, which seems more and more unlikely,