similar to: [ANNOUNCE] chan_capi-cm-0.5.4 release

If you're using StrictSubnets, you will still be fine. StrictSubnets means that A will only use B's key (which C does not know) to send packets to B's statically configured subnets. C cannot impersonate B (as in, take its node name) because it would have to know B's private key to do so, and it cannot impersonate B's subnets because A is using StrictSubnets. The worst that C

On 09/03/2016 10:56 AM, Etienne Dechamps wrote: > C will still need keys in order to establish metaconnections with A and B (as > well as a few other things). However there is no need for C to own any > "Subnets" at all. If somebody breaks into C, he could get access to the vpn network, right? Because the keys are there, it will be possible to use them to get access. Even if

On 09/02/2016 08:51 PM, Etienne Dechamps wrote: > What version of tinc are you using? tinc 1.1 already does what you want out of > the box: packets sent from node A to node B through node C will use a key that > A and B will negotiate between themselves. C doesn't have the key, and will > act as a blind relay. C will not be able to decipher the packets flowing > between A and B.

Hi all, A few days ago I found out with help of some of you guys how to set CLIR. (Calling line identification restriction) My first idea was to use the keypad protocol to set the CLIR with dialing *31* before the number but this was not possible. So thanks to Damon Estep I got it to work with executing 'SetCallerPres(prohib)' before the dial command. This works perfectly! But now

Hello! I just encountered a strange thing in my mysql cdr records. From a certain date on Asterisk (1.4.6) stopped to populate the CLIR and SCR flieds in the cdr table. As far as I know no changes happened to the system on that date and until then CLIR are recorded properly. The CLIR is still transmitted by the PRI and is shown in the console when a call comes in. But no traces of it in the CDR.

Hi Armin! I have problems on debian sarge with standard 2.6.8-2-386 kernel. I've installed the packages: kernel-headers-2.6.8-2 kernel-headers-2.6.8-2-386 kernel-image-2.6.8-2-386 kernel-kbuild-2.6-3 kernel-source-2.6.8 Then I unpacked the kernel sources into /usr/src/kernel-source-2.6.8 and made a symlink from /usr/src/linux --> kernel-source-2.6.8 Then I entered

I am trying to understand the difference between the divas4linux available from the Eicom/Dialogic website and the melware version. Am I right in thinking that the melware version is for Trixbox or Asterisk but the Dialogic version is for Asterisk only (i.e. will not work with Trixbox?). I've noticed that some of the things mentioned on the Dialogic web site as included with Divas e.g.

Hi, I am using: Asterisk 11.2.0 libpri 1.4.12 Dahdi: 2.6.1 Sangoma E1-Card with Wanpipe-Drivers 3.5.28 I call my asterisk box via SIP and connect the call to an AGI-Script. Within the script I do EXEC SetCallerPres prohib or EXEC SetCallerPres prohib_not_screened But I get the following error: ast*CLI> == Using SIP RTP CoS mark 5 -- Executing [100 at sip:1]

Hi (Armin?) ! Today I had a problem with Diva Server 4BRI-8M 2.0. Asterisk 1.2.12.1 chan_capi-cm-0.6.5 divas4linux-melware-3.0.f-106.622-1 Asterisk could not receive and make calls on the BRI ports, although the ports looked fine within Asterisk. I usually use "/usr/lib/divas/divactrl dchannel -c 1" to test line activity. This time there was no activity (cryptic log

hi I have a passive isdn port configured in modem.conf in extention.conf i use this two channel (ttyI0 and ttyI1) with the string: exten => _NXXXXXXXXX,1,Dial,Modem/g1:${EXTEN}|60|r how can i hide my msn? is it possible to activate the clir with the @ before the ${EXTEN}? thanks Cristian

When a user calling over the PSTN network calls one of our SIP users with a restricted number (CLIR), our PSTN gateway is sending us incoming calls with the following additional headers: Proxy-Require: privacy Anonymity: uri Remote-Party-ID: <sip:41781234567@192.168.0.100:4000>;privacy=uri as opposed to Remote-Party-ID: <sip:41781234567@192.168.0.100:4000>;privacy=off when CLIP

Michel Send me the same output for a dial string that only sends the *31* Is this an ISDN line? What type of card/signalling/switchtype are you using? It looks as if the PSTN switch accepts the *31* and then hangs up so you can make the NEXT call with the *31* feature enabled. If so I assume the *31* feature will be enabled for the next call on the ENTIRE SPAN if it is an ISDN trunk group. If

Hello, I have an issue getting the chan_capi module to load in asterisk cvs from today. Plain 2.4.20 kernel with melware patches for the Eicon Diva Server Bri card. I load the modules with: modprobe -v divas divacapi I load the firmware with: divactrl load -c 1 -f ETSI -vd6 Output in /var/log/messages is: Nov 9 19:26:26 voice kernel: Eicon DIVA - DIDD table (http://www.melware.net) Nov 9

C will still need keys in order to establish metaconnections with A and B (as well as a few other things). However there is no need for C to own any "Subnets" at all. On 3 September 2016 at 06:21, Armin <armin at melware.de> wrote: > On 09/02/2016 08:51 PM, Etienne Dechamps wrote: > > What version of tinc are you using? tinc 1.1 already does what you want > out of

I have installed Asterisk 1.2.18 am am trying to install chan_capi. The current RPM ftp://ftp.melware.net/Trixbox/chan_capi-1.0.1_1.2.14-1.i386.rpm installs but Asterisk dies on startup. The following appears in the log: May 27 03:28:18 asterisk1 kernel: divas: Diva Server V-4BRI-8 IRQ:7 SerNo:25290 May 27 03:28:18 asterisk1 kernel: divas: started with major 252 May 27 03:54:17 asterisk1 init:

Hi all, it took a while, but on sourceforge.net I added the new release 0.6 of chan_capi-cm driver. Note: dial string and capi.conf has changed. The main changes are: - added 'relaxdtmf'. - more BSD compatibility - correct PROGRESS handling - added verbose text for capi info/reason error messages. - use correct facility-selector for echo-cancel - added application capicommand() for CAPI

Hi, I'm trying to get an Eicon Diva Server4BRI card running under Ubuntu 6.06 - by downloading the v3 driver package from Melware and compiling everything. Yet, after activating the necessary modules (divas and divadidd) and interactively configuring the card (/usr/lib/divas/Config), starting up the adapter fails! The error "/usr/lib/divas/divactrl load -c 1 -Debug" produces

Hello, I am trying to use * to handle anonymous ISDN callers. Something like exten => 5150/0,1,Congestion should work but doesn't. Apparently because the ISDN CAPI doesn't use 0 for callers who don't send their number. Is there a way to make * identify ISDN callers who use CLIR? -Walter -- Walter Doerr =*= wd@infodn.rmi.de =*= FAX: +49 2421 962001

Dear Mailing List Members, the problem I've been grappling with für quite some time now is the following: I have a 100 rows x 200 columns matrix. data.set <- matrix(rnorm(20000, 100, 200)) Now I would like to get a vector of length 100 which collects the values from the following procedure: Take the sum of the minima of the two values from each row of columns 1 and 101, and divide it

Hi i use this into my extension : exten => _00339xxxxxxxx,1,Set(foo=${SIP_HEADER(To)}) exten => _00339xxxxxxxx,2,Set(cut1=${CUT(foo,:,2)}) exten => _00339xxxxxxxx,3,Set(CLI=${CUT(cut1,>,1)}) exten => _00339xxxxxxxx,4,Set(toexten=${CUT(CLI,@,1)}) exten => _00339xxxxxxxx,5,Noop(ORIGINAL NUMBER : [ ${toexten} ]) exten =>