Displaying 20 results from an estimated 1334 matches for "unreliant".
Did you mean:
reliant
2003 Jun 26
3
Request for option for use on an unreliable connection
I have been using rsync for the last year or so. Generally I am very
pleased with the performance and features, but I am forced to use a
rather unreliable link to one of my mirrors. Consequentially rsync often
bails out with a protocol error in the middle of a large session due to
transient misbehaviour on the link. This appears to abort the whole
transfer. One solution would appear to be an
2005 Jun 21
1
GSM ISDN gateway to quadbri NT port under bristuffed Asterisk - where to set gain (I have unreliable inband dtmf recognition )?
Hi,
I'm getting unreliable dtmf recognition (it works fine for 4-5 digits,
errors (duplicates) on more), when transferred inband from gsm gateway to NT
port of quadbri under bristuffed Asterisk.....
Since Asterisk is claimed to have good dtmf recognizer, I suspect there are
some settings to workarouned... I've tried dtmf relax, but didn't help, so I
suspect gain settings....
Is
2006 Jan 31
1
Asterisk 1.2.1 + TDM400P + fax machine unreliable ?
Hi,
I have a running asterisk 1.2.1 (bristuffed) with a TDM400 Board. Connected
to 1 port is am ordanary Fax Machine. Everything 'seems' to work,
however receiving faxes is very unreliable.
Sometimes I receive a normal page, without problems. Sometimes
half of a page and the rest is scrambled, but most often, I receive
nothing and the other site reports a Fax error...
The Fax machine
2004 Jan 07
1
[PATCH] Unreliable network connections with 3.0.1
A lot of people have complained about unreliable connections to W2K and XP
machines. The folowing patch solved the problems for us. I have no idea
why it works, but after this patch we had no more problems connecting to
workstations in the domain.
--- samba-3.0.2pre1/source/rpc_parse/parse_net.c 2004-01-06 22:08:41.000000000 +0100
+++ samba-3.0.2pre1/source/rpc_parse/parse_net.c 2004-01-07
2004 Feb 04
1
[PATCH] Unreliable network connections with 3.0.1 - need advice
Hi
I saw your post about bug in Samba 3.0.1:
Quote:
????A lot of people have complained about unreliable connections to W2K
and XP machines. The folowing patch solved the problems for us. I have
no idea why it works, but after this patch we had no more problems
connecting to workstations in the domain.
--- samba-3.0.2pre1/source/rpc_parse/parse_net.c 2004-01-06
22:08:41.000000000 +0100 +++
2002 Jun 17
1
O_EXCL unreliable?
Hi all,
I fear I can't rely on "open (path, O_CREAT | O_EXCL)" behaviour
on samba share.
The libc's doc says:
If both `O_CREAT' and `O_EXCL' are set, then `open' fails
if the specified file already exists. This is guaranteed
to never clobber an existing file.
But this isn't probably true on network filesystems. When I run
this tiny program on
2005 Jun 21
4
voip-info.org unreliable lately?
Anyone have any insight as to why voip-info.org has been up and down all
day, and more importantly unreliable for the last month?
I assume the bandwidth is being donated or something, but surely someone
would be willing to donate reliable bandwidth as the knowledge hosted on
the site (which is also donated!) is worth way more than the bandwidth.
There is no doubt it is the best
2005 Apr 26
4
docecot and procmail?
Is dovecot still considered unreliable when combined with NFS?
Is this true for mbox only, or Maildir as well?
If dovecot Is still considered unreliable with NFS, how about having a
dovecot mode that would chain into procmail for delivery, so that dovecot
doesn't (necessarily) have to reinvent that wheel?
Thanks!
2010 Apr 24
1
Update on "non-dying" nx connections over unreliable network
Dear Sirs & Madams:
Thank you so much for your help. To remind, my situation is a wireless connection that is unreliable, where:
(a) upon disconnect, !M's nxclient does not recognize connection death
(b) after I manually kill nxssh and reconnect, reconnection takes some time.
My idea:
intercept myself in between NX client and server - detect connection drop, and reconnect. This is
2014 Nov 25
0
Dealing with an unreliable remote
(until a better answer comes along)
The killed rsync process should leave a temporary file .<file-name>.<random>
If you rename the temporary to the real file name, rsync should continue
from about where it left off.
-----Original Message-----
From: rsync-bounces at lists.samba.org [mailto:rsync-bounces at lists.samba.org]
On Behalf Of net.rsync at io7m.com
Sent: Tuesday, November 25,
2008 Jul 10
0
callerid_get_dtmf: Couldn't detect start-character. CID parsing might be unreliable
Hi list,
My caller ID is not working anymore on my TDM11B (TDM400P) cards and i get
this error message on the asterisk console:
== Starting post polarity CID detection on channel 4
-- Starting simple switch on 'Zap/4-1'
[Jul 8 11:58:55] WARNING[9539]: callerid.c:219 callerid_get_dtmf:
Couldn't detect start-character. CID parsing might be unreliable
A long time ago my
2004 Mar 06
0
Samba 3.0.2a + Win2K clients: unreliable share access
After upgrading from 3.0.1 to 3.0.2a, accessing a shared folder has become unreliable: after being able to access my shares for some time I get an error message "No domain contoller was available" (actually, I'm paraphrasing that one, I unfortunately did not record it verbatim). Host linux log contains the following error message for each access:
Mar 5 20:07:08 sharesmb01
2014 Nov 25
0
Dealing with an unreliable remote
On 25.11.2014 15:02, net.rsync at io7m.com wrote:
> 'Lo.
>
> I've run into a frustrating issue when trying to synchronize a
> directory hierarchy over a reliable (but slow) connection to an
> unreliable remote. Basically, I have the following:
>
> http://mvn-repository.io7m.com/com/io7m/
>
> This is a set of nested directories containing binaries and
2015 Jun 23
0
RHEL/CentOS 7.x KVM kernel instability & unreliability
Hello,
I'm managing smaller private virtualization infrastructure, currently based
on CentOS 7.x. In the past we were running mostly on Debian 7 (kernel
3.2.x) and CentOS 6.x without problems.
After we have upgraded to CentOS 7.x, I have experienced occasional
physical host crashes when I did e.g. suspend or resume more virtual
machines OR random virtual machine checkpoint was invalid and VM
2019 Feb 02
0
linux rsync <-> SSHDroid has started becoming unreliable after an upgrade of Fedora 28 to 29
On Sun 03 Feb 2019, Philip Rhoades via rsync wrote:
>
> For some years I have been using rsync quite happily to send / retrieve
> files to / from SSHDroid Pro but recently I have started having a problem
> when transferring large numbers of file - I am pretty sure it started after
> upgrading from Fedora x86_64 28 to 29 - but I am not 100% sure. Below is
[...]
> Corrupted MAC
2005 Jun 01
1
Unreliable DTMF detection with DISA on incoming Zap channel on bristuffed * and GSM gateway
Hi,
I'm getting unusable DTMF detection with DISA on incoming ZAP channel
(bristuffed *) on quadbri from GSM gateway. DTMF detection works ok in
normal ISDN incoming line.
How can I check what's going on ? What settings to check ?
Anyone with more experience on such scenarios ?
Thanks in advance,
regards,
Rob.
2006 Jan 19
0
AudioCodes Unreliable DTMF Detection
We're trying to use some AudioCodes MP104 FXO units as gateways to
Asterisk but cannot get them to reliably detect DTMF. Some landline
calls get most digits but some are duplicated. Some cell phone calls get
0% DTMF recognition.
Anyone with experience with these units have any suggestions? ABP
Technical Support has been unable to diagnose the problem and is now
sending random guesses and
2007 Apr 26
0
IAX channel unreliable with multiple hops
Hi,
My problem is related to a bug in the Asterisk bug database:
(Bug 2773) http://bugs.digium.com/view.php?id=2773
Essentially, when one has a call going over more than one IAX legs,
the audio is not transferred *sometimes*. This is quite randomly
observed. With "notransfer=yes", the problem goes away.
In my situation, the IAX channels originate from 2 Asterisk servers
themselves -
2009 Feb 17
0
Swift - detection of multiple digits unreliable on my system
Hi all,
I just installed Cepstral and app_swift version 1.4.2 on my Asterisk
1.4.22.1 box. It seems to work great with one exception.
If I play a test message with instructions to collect a maximum of 5
digits, it collects those 5 digits correctly if the user waits for the
message to complete before entering them. But if the user barges in
with digits before the message completes, the detected
2007 May 14
1
round(#, digits=x) unreliable for x=2 (PR#9682)
Full_Name: Scott Wilkinson
Version: 2.3.1
OS: WinXP Pro
Submission from: (NULL) (140.253.203.4)
In the example below round() does not report to the specified number of digits
when the last digit to be reported is zero: Compare behaviour for 0.897575 and
0.946251. Ditto for signif(). The number of sigfigs is ambiguous unless the
reader knows this behaviour. Is this a bug or intended behaviour? Is