search for: aroudn

Well because I had sooo may problems with chan_agent.c I wrote this. I'm releasing it under LGPL but if you use it or anything please let me know. It'd be interesting if anyone finds this more useful than just a pile of junk. I've included a (working) example extensions file. SIP phones are assumed to have the same identifier as their extension number, but it'd be trivial to

This version contains a fix to mbr.asm, plus a version of Murali's menu system, but ported to gcc. Although gcc produces much bigger 16-bit code (since it's really 32-bit code with prefixes) I figured it would be much easier for people to deal with since it requires the configuration to be compiled in. That being said, it's a *very* powerful menu system, partially *because*

Hi, We are starting a new project, and are trying to decide the best way to proceed. We want to setup a LAMP configuration using Centos, something we have been doing in the past with great success. The question is load balancing. We antisipate the potential for the system to receive 500,000 requests/ day with in the next year. We want to plan for that extra load now as we start the

...y example) in from-sip,s,1 which equates to default,s,1 but they have ALL the internal extensions and dial plan. Why? Heck if I know. Somehow the C code loses track of who I'm dialling and in 1.0.1 chan_park can't find the origianl extension in the event of a timeout. Yup you could code aroudn this in the dial plan logic by leaving some sort of hint, but I don't get why it's missing. Also don't put a /n at the end of the Dial(Local...) stuff in the AgentCallBack macro, it will cause zombies, lots of them, and weird behaviour of 7940 and 7960 SIP phones. Why? Again, don'...

I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB