Microsoft Serious About VoIP
VoIPluvr writes "Microsoft, is quietly turning into a voice-over-IP powerhouse. It all started with the launch of its Microsoft Live Communication Server. Bill Gates says, 'Communicating in a better way has a huge impact for business,' and he states that he wants Microsoft to marry the PC, the cell phone and the desk phone. Recently, Microsoft teamed up with VoIP companies like Sylantro to offer hosted IP-PBX services, and now is rumored to have bought Teleo, a small VoIP company based in San Francisco. Microsoft's dominance on the desktop is helping the company extend its reach into the fast growing VoIP business, thus putting it in direct competition with the likes of Cisco. Teleo, for instance could help the company compete more effectively with the likes of Yahoo and Skype."
Prepare for the blue screech of death when you pick up the phone!
Sorry...
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
Great now my cellphone, home phone and PC can all crash at once.. thanks Micrsofot for being the leader in innovation!!
-=Linsys=-
http://www.intrusionsec.com
a true "core" product?
everyone else seems to be seeking out one specific segment of the market, is MS finally realizing specializing in everything means you specialize in nothing?
i think they are good and bad, but they seem to have lost the wind in their sails...
Microsoft makes a PDF-like format, Microsoft takes over municipal water works, Microsoft creates new ice-cream cone. My god, can't Microsoft leave anything alone? This is what is going to kill MS; they are doing too many things and fighting too many wars on too many fronts in an effort to maintain market dominance. You would think large companies would ditch MS wholesale simply because MS may one day use the revenue to compete with them.
-_-
I wonder how this is going to play with the Telco's. I worked a long time at one of the Telco's and we did much/most of our work on IBM mainframes and Unix servers. Then our high level management and Microsoft marketers got very cozy and all of a sudden many of our critical applications began shifting to the Windows 2000, SQLServer, IIS platform. This was all very much with heavy opposition from technical staff, but their input wasn't wanted. In the course of five to ten years I saw us (them?) become very heavily vested in Microsoft platforms (including the public facing web site (which was nothing but problematic rolling out on the MS platform)).
And now, Microsoft wants to enter the market of the telcos? I know everyone is jumping in on this, and I for one have little empathy/sympathy for the PHB's who've made their beds with Microsoft, but I wonder how much they like Microsoft now?
It seems to me like any new sector or industry comes along and people start making money microsoft goes AAHHH we don't control that! So they buy a bunch of companies and produce some buggy vaporware and spend a bunch of money. Is it possible for them to be happy with that they got or at least not branch out so much and focus on goods they can produce and produce them well.
----
Go canucks, habs, and sens!
I agree with you for the most part.. however if you start implementing VoIP PBX solutions for your customers and it crashed regularly yes, you are gonna make a bit of cash off your customer, but it's also going to make you look like a CRAPPY consultant..
I believe in a mix of Unix, Linux and MS solutions for my customers.. I don't look so bad when PCs crash, but when their mail server or web server is down because IIS got doss attacked it makes me look horible(or probably would, I NEVER would implement an IIS Solution...).
I have implemented many asterisk solutions for customers who are very happy with the realiability, price, and quality of the product.. I would hate to get calls from customers all the time saying they can't call out becasue of SpyWare.
-=Linsys=-
http://www.intrusionsec.com
The submitter, VoIPluvr, must be using the Yale comma style and not the more popular Harvard style.
So letsee... in order to go from traditional PBX to VOIP you could either a) deploy a brand new separate IP network to directly replace your PBX or B) Upgrade your existing IP network including all of your ethernet switches so that they support PoE (Power over Ethernet).
You may need to implement QOS (you don't want some FTP transfer blocking time sensitive voice traffic.
You may need to redesign your core routers, backbone etc for this increase in traffic.
Also, if the CallManager (the computer that sets up the connection between the two telephones) goes down, you're not making phone calls. Do you really want to trust this to Windows? Yes, I realize that Cisco's CallManager runs on Windows, but rumor has it they are making a linux version.
So the question remains, with all the changes to your network that are required I doubt this will go far.. unless of course MSFT buys Juniper, Nortel...
Method for outputting a crashdump as a series of audio tones.
bill: hey steve, can you hear me now!!
steve bummer: what WHAT!!!
bill: GOOOOOOODDDD...
I will gladly loose all of life's battles.. in order to win the war..
I wonder when that little pop-up will start appearing on computer screens during incoming VoIP calls. I can think of a million ways MS could embrace-and-extend VoIP to add features that only work/ "work best" with MS software. Makers of VoIP add-ons will then test their widgets with MS only and not support "non-standard" operating systems.
Two wrongs don't make a right, but three lefts do.
I'd love to see something like VoIP take off. It just seems like IP is the wrong protocol to do the job.
If you don't want crime to pay, let the government run it.
See also:
Hotmail
WebTV
X-Box
MSN
MSNBC
Etc.
Lawrence Person (lawrencepersonh@gmailh.com (remove all "h"s to mail)
http://www.lawrenceperson.com/
Now they also want to marry it to my cell phone and my desk phone?
Already done.
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
That third link is a redirect to Tubgirl, way to mod that up to Interesting mods...
You're talking Windows here, so your comment should read " EVERTHING you open or look at is logged into temp files or stored in user.reg files."
If you don't want crime to pay, let the government run it.
Avaya built one of their switches based on Windows. They tried to sell it at the same price as their *nix switches. They lost money on it big time. What was interesting was that the switch had to have double the CPU and double the ram. Even with that, it still crashed and could not carry the same load. Finally, the support cost were enormous.
I prefer the "u" in honour as it seems to be missing these days.
Damnit! Don't they get it? I just want a simple phone that works, not lots of gadets. How am I supposed to fit my PC, my cellphone and my desk phone in a shirt pocket?
Besides, I find this whole thing unnatural and sick. We should pass a Constitutional amendment prohibiting the marrying of objects. Just because Bill Gates has a sexual fetish for devices, doesn't mean I want it shoved in my face. Respect the sanctity of human marriage!
... and then they built the supercollider.
he states that he wants Microsoft to marry the PC, the cell phone and the desk phone, Why? Has anyone thought of that? Integration is nice but sometimes it's pointless and harmful. For example, my Motorola v600 is Java powered. That's great except sometimes I can punch things in faster than it can handle. The battery life is poor. My older StarTac was perfect for me. No java or camera but it go the job done right. I never had to reboot a cellphone until I got this new one. Oh, let's not forget how the battery life is kind of mediocre. Let me count the number of times I've taken advantage of the Java and camera features: 5. Those 5 times, I could have done without them anyways. MS needs to take a lesson fron Apple and even *nix. Do one thing and do it well. Then make all those things play together well. God I wish Apply made cellphones.
EvilCON - Made Famous by
Skype seems to be the only product making cross-platform solutions.
as for video -- it doesn't seem like ANYONE is looking for cross-platform compatibility. iChat doesn't work with netmeeting or gnomemeeting (and the tiny AIM video screen sucks). video4skype only works in windows (though it is great in windows.)
i use linux, but i have recently had to reinstall (dual-boot) windows so I can use AIM's video chat with my girlfriend (who uses iChat.) It's the only solution that easily works through odd connections (firewalls,etc.) And, unfortunately, xmeeting just doesn't work that easily for the non tech savvy (like her.)
why hasn't there been movement to make cross-platform video solutions?
What comes first, finding a teacher or becoming a student?
Where I work, we have a saying. "There are only two things that need to be up and running 24x7 without a hitch. Ever: phone and e-mail". Until Microsoft can provide an OS with this kind of reliability that doesn't cost the farm (like Windows Data Center on Unisys) they will not be chosen as a serious contender for carrier grade mail or phone. How many large ISPs out there use Exchange for mail? None. An for people like me... I want carrier grade quality in everything even for my own home use. That's why I use *nix for anything serious.
-"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
Avaya also has a windows-based eIVR product, which they will sell you for a minimum $50k plus custom programming rates of $20k-$50k if you actually want to run anything on it. (Custom programmed in VBScript, and they won't bother to test it with any database other than Sql Server.)
Or you could spend $5k on hardware, install Linux, Asterisk PBX software, spend an afternoon hacking, and have the same thing.
Lots of people mention Skype and similar services. But I want to know how the new MS offering will stack up against Asterisk?
Microsoft have tied all their systems nicely together. I don't know much about Microsoft products but once or twice every year I see problems that brings down every Microsoft based problems.
Whenever we need different MS systems to talk to each other, they pretty much needs to be on the same network or at least have so many open network ports between them that firewalling them in different security zones becomes useless.
I'd prefer different systems with clearly defined boundries, communicating trough standard protocols instead. Moving everything to a big consolidated MS monster, might have helped bring down some of the expenses of having different systems. But I have yet to see it bring better stability.
I see some signs of people not any longer want everything to be tied in to a MS system after have had problems with one vendor to rule them all.
but sadly the management in a lot of places does not understand why they don't get the stability they had on the mainframe after moving it all to MS.
The IP multimedia subsystem (IMS) which is coming out of 3GPP (GMS) and 3GPP2 (CDMA) will establish a solid footing for VoIP where it can match the quality of current PSTN.
IMS will allow Quality of Service (QOS) on the network, between carriers.
IMS will also support much more security than available now with VoIP. Especially between carriers.
IMS will allow roaming, because the network you are on will probably not give you QOS otherwise.
Best of all, IMS is based on SIP and other IETF standards. It will allow much more rapid development of multimedia applications for both wireless and wireline applications.
The downside is that while the standards are open, this will be a big player game. While there will be much more intelligence on the End User device compared to PSTN, the network will still maintain control. It has to for QOS. Peer-to-peer VoIP will never match the quality of PSTN. Ultimately the big carriers do not want to be commoditized dumb pipes
Truth be told, most people are not savvy enough for peer-to-peer and putting enough intelligence in our software is still a long-long way off. Especially if it's being developed by Microsoft.
Note: I work for a telecommunications equipment vendor. I am heavily into and biased for IMS.
Peace,
Vudu Child
If you had my real name, you'd use an alias too.
What type of call processing system were you running? Separate VLAN's for data and voice? I've rolled out Cisco phone systems in some pretty dodgy network scenarios, and voice quality has never really been an issue.