similar to: Mailing list rollover

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, I have a simple question about incoming phone line rollovers. How are these usually done? Is this done at the phone company usually, or is this something that Asterisk or channel bank is capable of? I just need someone to give me a brief explanation how it usually works, and if someone was implementing an Asterisk system, how they would go

I was hoping that rolling over to the next trunk would be simple, but it doesn't appear to be so, especially for a newbie. So I'm looking for a simple way where if I get a busy on the first outgoing trunk, I can do something to get connected to the next one. Perhaps something like the big boys do and dial 9 first? I'm guessing a custom dial plan might do that but I haven't

Hello, I've got 2 analogue lines (from SBC) coming into a TDM22B. SBC have put rollover from the first to the second line. The rollover works fine when handsets are connected directly to the lines (ie when Asterisk is not involved), but when the lines are connected to Asterisk, the rollover fails: the caller just hears the line ringing, and the person on the first (busy) line hears call

I am trying to perform a "rollover" when the primary number is busy. This is coming from a POTS line. Apparently I need call waiting on the POTS line as I get immediate busy from the FXS if I don't have it. So my question is this. I have an Aastra 480I CT. The call forward when busy here seems pretty straight forward. Choose the mode as busy enter the extension in the forward number

Have a question about implementing Call Rollover with my current extensions.conf configuration. [macro-stdexten] exten => s,1,Dial(${ARG2},20) ; Ring the interface, 20 seconds maximum exten => s,2,Voicemail2(u${ARG1}) ; If unavailable, send to voicemail w/ unavail announce exten => s,3,Goto(default,s,1) ; If they press #, return to start exten =>

https://bugzilla.samba.org/show_bug.cgi?id=1529 Summary: 32bit rollover problem rsyncing files greater than 4GB in size Product: rsync Version: 2.6.2 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

My goal is to have only 1 primary phone number that can seamlessly "pool" multiple VoicePulse accounts. Let's say I have 3 accounts with VoicePulse Connect 212-555-1000 (primary) 212-555-1001 212-555-1002 When I receive inbound calls on 212-555-1000, I want to "forward" or "roll over" the connection to 212-555-1001 and 212-555-1002 so that the 212-555-1000

I have about 5 incoming USA SIP lines, but my provider does not have any sort of roll-over or huntgroup feature. Does anybody have an idea on how I can create a general number that will ring to the next available, non-busy SIP line that I have? Is there a provider out there that would do this? Any suggestions would be greatly welcome. Thank you. -------------- next part --------------

It appears that part of the problem could be that when logger rolls over the mongrel log file. There is a mutex synchronization issue where the various mongrel instances all try to write to the new log file and block each other. This keeps them in a continual Application 500 Error state. Has anyone run into this problem? With log rotation turned off the problem does not appear. - Jared Brown

I've been using tinc to do some high bandwidth VPNs between nodes in Amazon's EC2 environment (to work around some limitations there for effectively loadbalancing raw TCP connections while preserving the sources addresses, using Linux IPVS in NAT mode). The raw amount of traffic involved is probably making this a bit of a corner case for tinc. In the overall it has held up remarkably

https://bugzilla.samba.org/show_bug.cgi?id=1529 ------- Additional Comments From thomas@suse.de 2005-09-06 06:37 ------- Now when len is OFF_T is it possible that sum->count (which is size_t) in sum_sizes_sqroot() will rollover too at line: sum->count = (len + (blength - 1)) / blength; ? When we assume all variables have all bits set: 2^64 + (2^32 - 1) / 2^32 = 2^32 + 1

https://bugzilla.samba.org/show_bug.cgi?id=1529 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From wayned@samba.org 2004-07-14 09:55

It seems that tftpd-hpa is more suitable at serving arbitrarily large files (greater than 65535 blocks long; with pxelinux.0 using a default block size of 1408 this is 92,273,280 bytes) as atftpd will complain in the log stating "Requested file to big, increase BLKSIZE". I saw that a while back HPA mentioned that atftpd was probably more scalable (number of clients) while tftpd-hpa is

On Sat, Sep 30, 2017 at 08:53:09PM -0400, Gene Cumm wrote: > On Sep 30, 2017 8:47 PM, Bruce Ferrell wrote: > > > > I've recently seen something to the effect that the pxelinux.0 boot loader > > has some limit of 45MB. Is this correct or some misunderstanding? > > No, I've loaded 90MB files. The catch is often TFTP block number rollover. My first thought was:

...not that hypermail really helped much, but the mailing list archives for vorbis and vorbis-dev at xiph.org are now broken down by month. Hopefully the rollover automation even works :-) Search comes next... Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to

I am trying to implement a rollover of extensions. exten => 3000,1,GotoIf($[${line1} = Congestion]?3:2) exten => 3000,2,Dial(${line1},15,rt) exten => 3000,3,GotoIf($[${line2} = Congestion]?5:4) exten => 3000,4,Dial(${line2},15,rt) exten => 3000,5,GotoIf($[${line3} = Congestion]?7:6) exten => 3000,6,Dial(${line3},15,rt) exten => 3000,7,GotoIf($[${line4} = Congestion]?1:8)

Anyone experience ring oddities with extensions.conf rollovers? Let me summarize... One of my extensions.conf file is built to ring during the day, ring/go to voicemail after a certain time: [main-aa] exten => s,1,GotoIfTime(17:00-8:30|mon-fri|*|*|*?main-night-aa,s,1) exten => s,2,GotoIfTime(*|sat-sun|*|*|*?main-night-aa,s,1) exten => s,3,Dial(SIP/201,25,tr) exten =>

I previously wrote: > I have come across what appears to be a bug in __invalidate_buffers() > w.r.t. the change in ext3-0.0.6 using BH_JDirty instead of BH_Dirty > for buffers held in the journal. If invalidate_buffers() is called > on a device (LVM likes to do this a lot, for whatever reason), it yanks > JDirty buffers out from underneath the journal layer, and causes an > oops

Hi, The twist? We actually have far-end hangup detection working fine, and that seems to be where the problem lies for most people. Our problem seems to be with requesting a hangup from our end reliably. If we originate the call, we can hang it up. This suggests to me that the Sangoma A200D is sending the correct hangup signaling. This way round, it is 100% reliable. If we accept a call

TCP timestamps on some (but not all?) of our CentOs hosts are being reported as a vulnerability by OSSIM. I have looked into the matter briefly and cannot say that I consider this a serious security issue. The vulnerability seems limited to determining the uptime of the target host. The question therefore arises as to whether or not there is any way to reset the tcp timestamp present value to