search for: recroding

Hi All, I have a sample of data set show as below. tdat <- read.table(textConnection("stat year Y AL 2003 25 AL 2003 13 AL 2004 21 AL 2006 20 AL 2007 12 AL 2009 16 AL 2010 15 FL 2006 63 FL 2007 14 FL 2007 25 FL 2009 64 FL 2009 47 FL 2010 48 NY 2003 50 NY 2004 51 NY 2006 57 NY 2007 62 NY 2007 36 NY 2009 87 NY 2009 96 NY 2010

...server will be provided with 1 E1 card Questions are: 1- will those servers be able to handle that ammount of calls?' 2- the important issue is that they require call recording on all calls.. which means we will have to record ALL calls going out of the system .. which means we will need a call recroding.. will the four Asterisk servers handle the recording process or we will need external assistant? and if it was the second choice what is the best suggestion? is there a way to force an Asterisk server to record remote channels? -- AHD Tarek Sawah Integrated Digital Systems CCNA, MCSE, RHCE, Vo...

... and similar to Jim's suggestion but perhaps slightly simpler (or not!): > cross <- xtabs( Y ~ stat + year, data = tdat) > keep <- apply(cross, 1, all) > keep <- names(keep)[keep] > cross[keep,] year stat 2003 2004 2006 2007 2009 2010 AL 38 21 20 12 16 15 NY 50 51 57 98 183 230 > ## for counts just do: > xtabs( ~ stat + year, data

Thank you Bert and Jim, Jim, FYI , I have an error message generated as Error in allstates : object 'allstates' not found Bert, it is working. However, If I want to chose to include only mos years example, 2003,2004,2007 and continue the analysis as before. Where should I define the years to get as follow. 2003 2004 2007 AL 2 1 1 NY 1 1 2 Thank you

On Mon, 22 Apr 2002, Akos Maroy wrote: > Raúl Gutiérrez Segalés wrote: > > I have tried broadcasting from both SuSE Linux and Slackware and with > > various programs being the last one Tim`s Mixice (which is a perl > > script that works along with a program called catdsp). Looking at the > > source I saw that this programs, both of them, try to open /dev/dsp. >

>>> >>> Can I suggest that you do what I did, create your own small test >>> domain in VMs using Bind9 >> >> Yes, that is a good idea. However, from what I had read before, much >> of it on the Samba wiki, I was expecting Samba4 to just work with >> multiple DCs. I still wonder why no one ever seems to have tested or >> questioned that

Once both DC were rebooted, after the MS Windows was also rebooted (here I could have just wait I think) this MS Windows client is connecting on DC from its AD Site again. 2015-12-23 16:51 GMT+01:00 mathias dufresne <infractory at gmail.com>: > Hi all, > > Firs I apologize I did not manage to find time to reply earlier. > > The initial issue was about how Samba AD react when

Hi, my VoIP system uses speex with framesize = 160 samples(20 ms) at 8khz, sending and receiving paquets of 1600 samples(200 ms). When I receive a packet, I buffered it (I have also tried with speex_echo_playback) before sending to the speaker. When I capture from microphone, I fist remove DC offset (I saw in OPAL sources) and then I call speex_echo_cancellation for every one of the 10

Hi all, Firs I apologize I did not manage to find time to reply earlier. The initial issue was about how Samba AD react when one DC is out and more specifically about what happen when FSMO ower is unreachable (poweroff in Ole tests). This issue is solved using a correct AD Sites configuration. Here I kept 3 DCs in my domain. Sites: I set up a second site named "authentication" and

And for Ole, the OP, to solve its own failover issue: As there is 2 physical sites and only 2 DC. Let's say Site1 is 10.1.0.0/16 Site2 is 10.2.0.0/16 I would create 2 additional AD Sites : Site1 + Site2 To AD site "Site1" I would associate 10.1.0.0/16 and associate also DC1 To AD site "Site2" I would associate 10.2.0.0/16 and associate also DC2 To Default-First-Site-Name no

On 12/23/2015 12:39 PM, mathias dufresne wrote: > And for Ole, the OP, to solve its own failover issue: > As there is 2 physical sites and only 2 DC. > Let's say > Site1 is 10.1.0.0/16 > Site2 is 10.2.0.0/16 > I would create 2 additional AD Sites : Site1 + Site2 > To AD site "Site1" I would associate 10.1.0.0/16 and associate also DC1 > To AD site

Hi all, Wish you a happy new year altogether! Mathias, James, let me first say that I highly appreciate your help with all your testing and writing up your thoughts. Here are my responses: A. I have no different sites, no various subnets; so I don't really know what to do. B. I don't understand the purpose of setting my domain up with different sites with associated networks, if on

On 1/4/2016 12:23 PM, Ole Traupe wrote: > Hi all, > > Wish you a happy new year altogether! > > Mathias, James, let me first say that I highly appreciate your help > with all your testing and writing up your thoughts. > > Here are my responses: > > A. I have no different sites, no various subnets; so I don't really > know what to do. > > B. I don't

Hi James, First thanks for you detailed answer and the tests you did to be able to write this. Before reading your mail I was believing MS Windows keeps only one credentials, those for last connected account. This is why I did not pushed too far authentication process. Tomorrow I'm back to work and I'll redo this test, using some others users to test than some I have already used to

Hi James and everyone, There is a real issue with samba_dnsupdate and DNS records creation with Samba 4 as AD when it comes to AD Sites. Samba does not seems to create at all any Site relevant DNS record. As AD relies on DNS to find DC on the correct AD site, if no DNS entry is created related to AD Site, no usage of AD Sites. Here Win client ask for domain 11:37:28.671044 IP

Using ldbsearch we can find needed informations if we know AD Sites names list. Sites informations are stored in CN=CONFIGURATION,DC=SAMBA,DC=DOMAIN,DC=TLD. Here there is a CN=Sites which seems to contains Sites informations. Next using a search with -b 'CN=<site-name>,CN=Sites,CN=CONFIGURATION,DC=SAMBA,DC=DOMAIN,DC=TLD' we can list object related to <site-name>. And we

And to get mentioned entries list I used: "samba_dnsupdate --verbose --all-names | grep Default-First-Site-name" This list 8 DNS records related to Default Site. Next was to change Default-First... by the name of another AD Site (sed is still working :p) I was able to create DNS entries which were missing for one of my sites. Next, test: Back on one Windows on the network associated