search for: frimwar

Displaying 8 results from an estimated 8 matches for "frimwar".

Did you mean: frimware
2005 Jul 12
0
Cisco SIP Frimware for 7940/7960 v7.5
Hello list, is there anyone out there that could grab the new SIP firmware 7.5 for the 7940/7960 from Cisco's Site and mail it to me (r.zagler@fog.at)? i already ordered a support contract but did not get my access data yet! Thanks, Roland
2006 Feb 23
5
Cisco 79xx and SIP 7.5 Problems
...een all three of them. Since then I have had only constant problems, mainly that after 3 calls on a phone, if they try to xfer or do any ohter things (sometimes just answer the 4th call) the phone freezes, they have had this happen to them throughout the week. Until yesterday I decided it must be a frimware problem, so I downgraded them to 7.1. Since then (around 5PM EST yesteday) it didn't happen *yet*. So I'm assuming it has to do with the firmware. So my question is, is anybody else using 7.5 firmware? If yes, do you have all the line buttons configured to the same SIP account? If yes, do...
2018 Jan 22
2
/lib/firmware/microcode.dat update on CentOS 6
...about washing hands, lawsuits, or soeoen else's stuff. It is about broken microcode updates. The code from intel was broken .. causing several CPUs not to boot after update. That (and only that) is why they were pulled. Users MUST individually QA the microcode for their individual CPUs, OEM Frimware, chipset etc. The issue here is that the microcode broke peoples machines .. therefore it had to be rolled back. All the other discussion is full and total BS. It is likely ONCE all the microcode updates are tested and completely working that Red Hat will again include it in the microcode_ctl R...
2018 Jan 22
0
/lib/firmware/microcode.dat update on CentOS 6
...oeoen else's stuff. It is > about broken microcode updates. > > The code from intel was broken .. causing several CPUs not to boot after > update. That (and only that) is why they were pulled. > > Users MUST individually QA the microcode for their individual CPUs, OEM > Frimware, chipset etc. > > The issue here is that the microcode broke peoples machines .. therefore > it had to be rolled back. All the other discussion is full and total BS. > > It is likely ONCE all the microcode updates are tested and completely > working that Red Hat will again inc...
2003 Apr 12
2
asterisk / channel bank
I have two loop-start phone lines connected to an Adtran TA 750 channel bank. When a call comes into asterisk thru the first phone line and the call is redirect (in transit) back thru the second phone line, the channel bank will leave one or both lines opened (ie hangup with spawn a connection again). does any body have a suggestion: 1) I checked the cables into the channel bank from both phone
2003 Nov 23
1
Phone compatibility list
Hello! Is there a phone compatibility list anywhere? I know Asterisk is supposed to be compatible with IP phones that support SIP, h.232, and IAX, but a list of phone known to be supported would be a nice addition to the documentation. I need a buisiness phone, and the Cisco is _EXPENSIVE_ I like the 3com 1102, but it is NBX phone, and I can find no documentation of this phone working
2018 Jan 23
3
/lib/firmware/microcode.dat update on CentOS 6
...t is >> about broken microcode updates. >> >> The code from intel was broken .. causing several CPUs not to boot after >> update.? That (and only that) is why they were pulled. >> >> Users MUST individually QA the microcode for their individual CPUs, OEM >> Frimware, chipset etc. >> >> The issue here is that the microcode broke peoples machines .. therefore >> it had to be rolled back.? All the other discussion is full and total BS. >> >> It is likely ONCE all the microcode updates are tested and completely >> working that...
2018 Jan 18
5
/lib/firmware/microcode.dat update on CentOS 6
> Look at: > > https://t.co/6fT61xgtGH > > Get the latest microcode.dat file from here: > > https://t.co/zPwagbeJFY > > See how to update the microcode from the links at the bottom of this page: > > https://t.co/EOgclWdHCw > > An before anyone asks .. I have no idea why Red Hat chose this path, > they did. It doesn't matter if I (or anyone else)