Who decides the fate of Linux when Linus is retired or otherwise? Does that person get the decision because they hold a position in a foundation or will it be a committee? How would someone get in this position? An election of some sort? I can see the corruption coming.
I have a macbook and I used the alternate cd. Alot of things work: cd eject, sound buttons. But somethings don't: airport (will with a hack, but I got a belkin wireless G usb adapter that works out of the box).
I just deployed an Asterisk phone system powering ~140 wired Polycom phones and ~70 wireless phones covering 31 acres. Here are some tips from what I learned in this process:
1. Pick a capable vendor for each job you outsource. I looked at Asterisk and decided it is too technical for a Asterisk newbie to build a production system, so I called Digium and they referred me to a dCAP certified Asterisk consultant in my area. Knowing Asterisk is one thing, but knowing how to pull off a great install is more than that. Our vendor developed a workbook that covers many parts of a successful deployment, such as reviewing the network (gear, configs, wiring plant), getting the users (names, current extentions, locations ..), getting the users to think about the dial plan and having them understand their satisfaction with the results is directly related to trying to get it right. When we distributed the phones to each desk, the boxes were labeled and sorted on the pallet this helped save a huge amount of time and allowed us to have the furniture installers help setup phones if we wanted too. Staging the phones: pre-configuring them, having the boxes labeled and sorted on the pallet was well worth doing. The wireless phones we signed out to the employees with some other stuff like work shirts. Having the right vendor to walk us through the process was critical.
2. Pilot your install before you deploy it. The environment I was choosing Asterisk for is an automall. Phones are a big part of the business (as with many) and setting expectations is important. We formed a phone users group to have them decide how we wanted to route calls (dial plan), the idea was to get them involved because it is really theirs to use. Some departments were easy and some were not. Sales was essentially create a call groups for the differnt brands we sell and have the operators transfer them to the appropriate group. Service was much more complicated, but having live operators helps a ton. Parts was easy as well, but all of that needs some serious consideration. Knowing you will get it wrong and tweaking it on the fly will happen, do it and move on.
3. We picked Polycom phones and that turned out to be a great choice, the 601's have six "programmable" buttons and great sound quality (handset and speakerphone). The Polycoms have a two port switch built-in and will trunk with the network switch which means the second port on the phone can be a differnt vlan than the phone. So we have them plugged in/wired like this: [network-switch]---[phone]---[computer]. The phones run Cisco CDP, when the switch detects the phone (via CDP) it assigns the phone as a trunk device and allows you to choose what vlan the phone will be on and what vlan the computer port on the phone will be on. Also you can have a differnet vlan if you were to plug the PC directly into the switch. The setup works well and I could go on and on about QoS, edge marking of traffic and PoE issues but I will stop.
4. The FOP (Flash Operator Panel) is a cool thing, but we had to do some customizing for our needs. We looked at Fonalitys HUD, but FOP works great. You can see which phones are ringing, have voice mail (whether it is new or old), transfer calls by drag and drop, monitor the inbound queues and really not have to touch the phone to work the system as an operator. Nicholas, the guy that wrote FOP is an invaluable resource. He was willing to help and has done a great job. I am asking our vendor and am going to make sure he gets paid in some way.
5. Wireless WiFi phones (OUCH): We chose the Hitachi IPC-5000 and Meru Networks for the AP's. Okay I was getting a little cutting edge here, but hey why not?! Lessons:
Meru Networks ROCKS!! They figured out the roaming WiFi thing for sure!
Hitachi IPC-5000's to be determined: it look like either the phones have a high failure rate or we have a bad batch or something. Also it looks like they aren't nearly as durable as say a cell phone/mobile phone (which is VER
I don't know if you have posted like that before or even how to know who you are, but you ROCK. I have seen posts like this before and they were good too. Keep up the good work!!
www.asterisk.org - I haven't looked to see is it has the ability to do the toll by-pass you are asking for, but I know a couple of Cisco routers can do it. Software PBX, analog/digital/VOIP phones mix and a toll by-pass link between the two sites with a dial plan should do it.
Actually there are no ports listening and doesn't have to be, until the knock. THen it could turn on any service for any range of IP to gain access. This will be HUGE!!!! I bet every forewall will support this within this year.
Routing is the solution. Anyone that runs a layer two network beyond one switch should be fired. Routing convergence is much faster than spanning-tree (even with the Cisco tweaks). Why would I want layer two when layer routers are capable of wire-speed routing?!
Slashdot Mirror
Who decides the fate of Linux when Linus is retired or otherwise? Does that person get the decision because they hold a position in a foundation or will it be a committee? How would someone get in this position? An election of some sort? I can see the corruption coming.
I have a macbook and I used the alternate cd. Alot of things work: cd eject, sound buttons. But somethings don't: airport (will with a hack, but I got a belkin wireless G usb adapter that works out of the box).
I just deployed an Asterisk phone system powering ~140 wired Polycom phones and ~70 wireless phones covering 31 acres. Here are some tips from what I learned in this process:
.), getting the users to think about the dial plan and having them understand their satisfaction with the results is directly related to trying to get it right. When we distributed the phones to each desk, the boxes were labeled and sorted on the pallet this helped save a huge amount of time and allowed us to have the furniture installers help setup phones if we wanted too. Staging the phones: pre-configuring them, having the boxes labeled and sorted on the pallet was well worth doing. The wireless phones we signed out to the employees with some other stuff like work shirts. Having the right vendor to walk us through the process was critical.
1. Pick a capable vendor for each job you outsource. I looked at Asterisk and decided it is too technical for a Asterisk newbie to build a production system, so I called Digium and they referred me to a dCAP certified Asterisk consultant in my area. Knowing Asterisk is one thing, but knowing how to pull off a great install is more than that. Our vendor developed a workbook that covers many parts of a successful deployment, such as reviewing the network (gear, configs, wiring plant), getting the users (names, current extentions, locations .
2. Pilot your install before you deploy it. The environment I was choosing Asterisk for is an automall. Phones are a big part of the business (as with many) and setting expectations is important. We formed a phone users group to have them decide how we wanted to route calls (dial plan), the idea was to get them involved because it is really theirs to use. Some departments were easy and some were not. Sales was essentially create a call groups for the differnt brands we sell and have the operators transfer them to the appropriate group. Service was much more complicated, but having live operators helps a ton. Parts was easy as well, but all of that needs some serious consideration. Knowing you will get it wrong and tweaking it on the fly will happen, do it and move on.
3. We picked Polycom phones and that turned out to be a great choice, the 601's have six "programmable" buttons and great sound quality (handset and speakerphone). The Polycoms have a two port switch built-in and will trunk with the network switch which means the second port on the phone can be a differnt vlan than the phone. So we have them plugged in/wired like this: [network-switch]---[phone]---[computer]. The phones run Cisco CDP, when the switch detects the phone (via CDP) it assigns the phone as a trunk device and allows you to choose what vlan the phone will be on and what vlan the computer port on the phone will be on. Also you can have a differnet vlan if you were to plug the PC directly into the switch. The setup works well and I could go on and on about QoS, edge marking of traffic and PoE issues but I will stop.
4. The FOP (Flash Operator Panel) is a cool thing, but we had to do some customizing for our needs. We looked at Fonalitys HUD, but FOP works great. You can see which phones are ringing, have voice mail (whether it is new or old), transfer calls by drag and drop, monitor the inbound queues and really not have to touch the phone to work the system as an operator. Nicholas, the guy that wrote FOP is an invaluable resource. He was willing to help and has done a great job. I am asking our vendor and am going to make sure he gets paid in some way.
5. Wireless WiFi phones (OUCH): We chose the Hitachi IPC-5000 and Meru Networks for the AP's. Okay I was getting a little cutting edge here, but hey why not?! Lessons:
Meru Networks ROCKS!! They figured out the roaming WiFi thing for sure!
Hitachi IPC-5000's to be determined: it look like either the phones have a high failure rate or we have a bad batch or something. Also it looks like they aren't nearly as durable as say a cell phone/mobile phone (which is VER
I love these posts!!!
I don't know if you have posted like that before or even how to know who you are, but you ROCK. I have seen posts like this before and they were good too. Keep up the good work!!
How do you post so fast?
www.asterisk.org - I haven't looked to see is it has the ability to do the toll by-pass you are asking for, but I know a couple of Cisco routers can do it. Software PBX, analog/digital/VOIP phones mix and a toll by-pass link between the two sites with a dial plan should do it.
You prolly meant AXIM and SDIO. Is there one that has CF?! Maybe an add-on board for CF?
Sony will . . . http://www.dynamism.com/u70/ if this isn't what you are looking for, it is getting close.
Actually there are no ports listening and doesn't have to be, until the knock. THen it could turn on any service for any range of IP to gain access. This will be HUGE!!!! I bet every forewall will support this within this year.
Routing is the solution. Anyone that runs a layer two network beyond one switch should be fired. Routing convergence is much faster than spanning-tree (even with the Cisco tweaks). Why would I want layer two when layer routers are capable of wire-speed routing?!