You wouldn't think that if you had a 3 year old Canadian MRE with the chocolate completely oxidated and its sugar separated from the Cocoa. So all you get is a WHITE bar of grainy milk chocolate that used to be brown and yummy
The upload limits of cable are there not because it's fun, but because of the limited frequency slices available for upload.
The Broadcom CMTS chip usually comes in a 8:1 flavour (8 upload channels for 1 download channels).
With existing cable infrastructure, it can be a challenge to find all the available upload bandwidth within 8 frequency slices, while the download channel is usually much higher up in the list, and it not a problem at all. Hence the single channel allowed to it for up to 27Mbps.
I'm sure that with a little fiddling, I can now use this in promiscuous (pun) mode on the Ethernet interface of my news server and save all PORN pictures to the hard drive.
This is incredible technology guys. Can it differentiated between blonde / brunettes? Cup size? *drool*
Actually, if you'd bothered to connect to the console port, you'll see that it runs VxWorks.
As much as I like linux, its telephony support is close to 0. In this case, using a proven RT OS like VxWorks by Windriver Systems is wise.
As for heavy network traffic degrading performance, that would be because you don't know how to integrate data-telephony
The NBX has Vlan Tagging and packet coloring support. We use it straight to our main switch on the same segments as the workstations and it works fine under quite some heavy load. When using IP Telephony, it becomes necessary to setup CoS and traffic prioritization.
As for having to move your phone around with you, that's one painful thing with the current NBX code.
Release code 2.5 will enable you to "login" to any phone and move your profile/configuration to it. That way, no need to move the phone around.
There was some other post saying NBX was only for intra-office. That's not quite true. You can use multiple NBX chassis with 1 having the Call Process module (NCP) and it will route calls across a WAN to multiple offices.
The current code versinon requires that you use an H.323 gateway to do inter-NBX communication, but the release of their hardware H.323 gateway blade will fix that.
I've had an horrible experience with Cisco's Selsius phones. The first strike is the call manager. Runs on NT and that is VERY far from the 5 9 (99.999%) availability that other PBX offers.
In a business environment, people can live without access to email for 5-10 minutes. But not to their phone system. Any system that bases their Call Manager and H.323 gateway around a NT solution is doomed. Cisco couldn't offer the reliability we were looking for
I don't really know why this IP Phone post is news, we've switched our own PBX to Selsius and then quickly took it out because of the unreliable call manager and the initial Selsius phone models were pretty bad.
We currently use 3Com's NBX100 product. It's worth checking out. It's been working great for us for the past year. Offers Layer2 and 3 telephony (why waste IP space when you're on a LAN).
Its Layer3 telephony has an "IP on the Fly" characteristic that assigns IP addresses on the fly to the phone only when it requires Layer3 addressing. This way, you don't waste an IP per phone, set up a minimal pool of addresses and they get assigned on the fly when required.
The actual "PBX" is a VxWorks powered box running an AMD Elan (x86 with integrated IO). It's got cards for analog lines, T1 lines, H.323 gateway and some more. It's offers CoS, ToS, Vlan tagging and all the things you'd expect from an IP telephony system.
There are also analog adapters, so you can plug any analog phone (we use it with cordless phones) to an end unit, which then let's you use your analog phone as an IP phone.
We've found the solution to be much more reliable than Cisco's, where you need to dedicate yet another NT box for your call manager and where the reliability just isn't there. The functionality of the Call Manager, though better now, has lacked trivial standard telephone options for a long time and just didn't cut it.
Another nicety of the NBX100 is that you can program/configure your phone through the NBX's web interface, check your voicemail through its integrated IMAP server. It's also TAPI compliant, so the Windows users can tie in their address book software with the phone system.
While the former can be dealt with by using SSL connections, the authentication part remains the most important security issue.
Using two factor authentication solves this problem quickly, and contrary to the poster's expectation, it doesn't set back projects 2-3 years. In fact, it usually accelerates them because all of the password management functionality is taken care of. No need to check for "easy" passwords, no need for "difficult" passwords.
If you look at RSA Security SecurID products, you'll see how it can be used to authenticate users with one time passphrases, making cracking tools, brute force and even sniffing attempts useless.
I've had the opportunity to install these servers in Banks and government agencies and know firsthand of the relief they have since they don't have to always worry about password exchange (most employees keep their password on sticky notes) between employees.
It has a policy based DHCP server and dynamic DNS functionality.
It basically allows the administrator to map a hostname to a MAC address, independent of the IP Address (hence the need for dynamicaly updating the hostname's IP). I can see only a few instances where this might be required. For 95% of the cases, why not just put a static IP in the DHCP server for a particular host. Saves lots of problems.
I guess Microsoft not only invented the internet, they pioneered DDNS with Windows 2000 as well! (*cough*) -- Let's not all suck at the same time please
Slashdot Mirror
Actually,there are 32 timezones in the world ,some are 30mins off and some 45mins .. so the answer is 64 for AM and PM.
Et Gaston la Gaffe!
Spielberg should try LaGaffe first.. then move on to Tintin!
You wouldn't think that if you had a 3 year old Canadian MRE with the chocolate completely oxidated and its sugar separated from the Cocoa. So all you get is a WHITE bar of grainy milk chocolate that used to be brown and yummy
Guitars are "DIGITAL", which means operated by fingers.
Their sound isn't yet DIGITIZED!
--
Let's not all suck at the same time please
The Broadcom CMTS chip usually comes in a 8:1 flavour (8 upload channels for 1 download channels).
With existing cable infrastructure, it can be a challenge to find all the available upload bandwidth within 8 frequency slices, while the download channel is usually much higher up in the list, and it not a problem at all. Hence the single channel allowed to it for up to 27Mbps.
--
Let's not all suck at the same time please
I don't think so !
--
Let's not all suck at the same time please
This is incredible technology guys. Can it differentiated between blonde / brunettes? Cup size? *drool*
--
Let's not all suck at the same time please
--
Let's not all suck at the same time please
--
Let's not all suck at the same time please
Learn how to spell.
--
Let's not all suck at the same time please
Good luck with your spell checker 2000!
--
Let's not all suck at the same time please
--
Let's not all suck at the same time please
Having so many typos, syntax and grammar errors make slashdot look so juvenile and unprofessional.
--
Let's not all suck at the same time please
--
Let's not all suck at the same time please
As much as I like linux, its telephony support is close to 0. In this case, using a proven RT OS like VxWorks by Windriver Systems is wise.
As for heavy network traffic degrading performance, that would be because you don't know how to integrate data-telephony
The NBX has Vlan Tagging and packet coloring support. We use it straight to our main switch on the same segments as the workstations and it works fine under quite some heavy load. When using IP Telephony, it becomes necessary to setup CoS and traffic prioritization.
As for having to move your phone around with you, that's one painful thing with the current NBX code.
Release code 2.5 will enable you to "login" to any phone and move your profile/configuration to it. That way, no need to move the phone around.
There was some other post saying NBX was only for intra-office. That's not quite true. You can use multiple NBX chassis with 1 having the Call Process module (NCP) and it will route calls across a WAN to multiple offices.
The current code versinon requires that you use an H.323 gateway to do inter-NBX communication, but the release of their hardware H.323 gateway blade will fix that.
--
Let's not all suck at the same time please
In a business environment, people can live without access to email for 5-10 minutes. But not to their phone system. Any system that bases their Call Manager and H.323 gateway around a NT solution is doomed. Cisco couldn't offer the reliability we were looking for
I don't really know why this IP Phone post is news, we've switched our own PBX to Selsius and then quickly took it out because of the unreliable call manager and the initial Selsius phone models were pretty bad.
We currently use 3Com's NBX100 product. It's worth checking out. It's been working great for us for the past year. Offers Layer2 and 3 telephony (why waste IP space when you're on a LAN).
Its Layer3 telephony has an "IP on the Fly" characteristic that assigns IP addresses on the fly to the phone only when it requires Layer3 addressing. This way, you don't waste an IP per phone, set up a minimal pool of addresses and they get assigned on the fly when required.
The actual "PBX" is a VxWorks powered box running an AMD Elan (x86 with integrated IO). It's got cards for analog lines, T1 lines, H.323 gateway and some more. It's offers CoS, ToS, Vlan tagging and all the things you'd expect from an IP telephony system.
There are also analog adapters, so you can plug any analog phone (we use it with cordless phones) to an end unit, which then let's you use your analog phone as an IP phone.
We've found the solution to be much more reliable than Cisco's, where you need to dedicate yet another NT box for your call manager and where the reliability just isn't there. The functionality of the Call Manager, though better now, has lacked trivial standard telephone options for a long time and just didn't cut it.
Another nicety of the NBX100 is that you can program/configure your phone through the NBX's web interface, check your voicemail through its integrated IMAP server. It's also TAPI compliant, so the Windows users can tie in their address book software with the phone system.
--
Let's not all suck at the same time please
- The security of the data during transmission
- The Authentication of the end-users
While the former can be dealt with by using SSL connections, the authentication part remains the most important security issue.Using two factor authentication solves this problem quickly, and contrary to the poster's expectation, it doesn't set back projects 2-3 years. In fact, it usually accelerates them because all of the password management functionality is taken care of. No need to check for "easy" passwords, no need for "difficult" passwords.
If you look at RSA Security SecurID products, you'll see how it can be used to authenticate users with one time passphrases, making cracking tools, brute force and even sniffing attempts useless.
I've had the opportunity to install these servers in Banks and government agencies and know firsthand of the relief they have since they don't have to always worry about password exchange (most employees keep their password on sticky notes) between employees.
--
Let's not all suck at the same time please
--
Let's not all suck at the same time please
--
Let's not all suck at the same time please
--
Let's not all suck at the same time please
Second Prediction: Jon Katz and other pseudo-journalists will suddenly realize that Millennium takes two Ns!!!!
I think the Millennium bug is really that people can't even spell the word right.
Makes you wonder how competent all the people behind the "MILLENIUM BUG" websites are!
--
Let's not all suck at the same time please
GO HABS GO! GO HABS GO!
--
Let's not all suck at the same time please
Cisco has had a DNS/DHCP server implementation for a long time
The new "Network Registrar" comes in Solaris and NT (4) flavours.
It has a policy based DHCP server and dynamic DNS functionality.
It basically allows the administrator to map a hostname to a MAC address, independent of the IP Address (hence the need for dynamicaly updating the hostname's IP). I can see only a few instances where this might be required. For 95% of the cases, why not just put a static IP in the DHCP server for a particular host. Saves lots of problems.
I guess Microsoft not only invented the internet, they pioneered DDNS with Windows 2000 as well! (*cough*)
--
Let's not all suck at the same time please
--
Let's not all suck at the same time please