similar to: script in perl or PGSQL to predictive dialing - progesive dialing.

Displaying 8 results from an estimated 8 matches similar to: "script in perl or PGSQL to predictive dialing - progesive dialing."

2003 Apr 14
1
libpri functionality
Does anyone have a document showing what all functionality libpri supports? I am trying to get the configuration set with Adelphia/now Telcove before they come out and drop a line that won't do what I want. Quick run down of what I want to accomplish. We are getting a PRI installed to our colocation provider. We will have 21 phone number assigned to the group. We wish to use 1 number for
2004 Feb 03
0
Interlazed video posibilities
I don´t found any patent around this but i ned help with the patents. I can´t found all patents for interlazed video and I only read the patents around MPEG , the optimization for field based video can be aplied without problem, this is compatible whih the progresive encoding and in a few scenarios they can be positive. <p>process: <p>common: -2 bits to indicate video type 0x
2004 Jan 27
1
RE: LARTC digest, Vol 1 #1558 - 9 msgs
Hi Roy, Strange. "kernel will resend then together with new ones" - this is interesting, since the firewall DOES know how to drop locally generated packets and the kernel doesn''t attempt to retry them. I am not an expert on this, but I think it might be interesting to check how the firewall does this. Another option would be to trick the kernel that the packet has been
2004 Jan 23
16
IMQ Stability
Hello all, I have been doing a lot of archive searching over the last week reading posts on IMQ and it''s apparent stability / instability. I have seen a number of posts about it not being maintained as well. Can anyone talk to me about IMQ''s stability in a heavy throughput environment (20 Mbps) and what was causing IMQ to fail if you know. Thanks, Mike
2010 Feb 24
4
Re: [Xen-changelog] [xen-3.4-testing] x86: Generalise BUGFRAME_dump mechanism to allow polled UART irq to
FYI, I see the following build error with this patch... MRJ ---- new warnings/errors for xen ---- keyhandler.c: In function `__dump_execstate'': keyhandler.c:96: warning: asm operand 1 probably doesn''t match constraints gmake[5]: *** [keyhandler.o] Error 1 gmake[4]: *** [/tank/ws/xvm-3.4.3/xen.hg/xen/common/built_in.o] Error 2 gmake[3]: *** [/tank/ws/xvm-3.4.3/xen.hg/xen/xen]
2005 Jul 04
0
Transfer and CDR's
Hello I have a problem with bad CDR's after transfer of call. This is an example: I've called from 616222820 to 616222821. Next I've called from 616668020 to 0600340000 and then I've transfered the call. I think, that I should received two CDR's where: in first CDR source=616222820 and destination=616222821 in second CDR source= 616222820 and destination=0600340000 but
2010 Mar 06
5
unstable 4.0 config file/ build error
Hi,   The unstable repository seems to be quite unstable even building the image... !! I see:   make[4]: Entering directory `/foo/xen-unstable.hg/tools/libxl'' gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD -MF .xl.o.d  -D_LARGEFILE_SOURCE
2010 Mar 06
5
unstable 4.0 config file/ build error
Hi,   The unstable repository seems to be quite unstable even building the image... !! I see:   make[4]: Entering directory `/foo/xen-unstable.hg/tools/libxl'' gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD -MF .xl.o.d  -D_LARGEFILE_SOURCE