August 2001

Open Standards For Better Communication

BY Tom Keating

Of course, with Cisco's acquisition of Komodo, it made sense that Cisco would "productize" the Komodo FONE with the Cisco label. But why would Cisco send me another unit? The included letter named one of the Cisco contacts that I know very well, and who I was absolutely sure knew we recently reviewed their product. It is TMC Labs policy that we do not to review the same products in close proximity to each other so that we can give as much coverage to as many companies and products as possible. "Sorry, Cisco," I thought, "I'm going to have to stick you in the low priority review queue."

CISCO MEETS ENUM
But before I placed it on the back shelf, I decided to skim the press kit included with the package. It's a good thing I did! I discovered that Cisco didn't just stick a label on the Komodo FONE, or even just improve the aesthetics of the unit. In fact, they added some very interesting features.

The product is now called the Cisco ATA 186. The ATA 186 now supports two analog devices, each with their own independent phone number. Essentially, a service provider can provision two separate phone numbers. Now, two people can have simultaneous VoIP calls across a broadband connection. Or if you prefer, you can use the second analog port with a fax machine because the ATA 186 now supports G.711 fax pass-through capability. The new version also supports a Web admin interface. One of our "room for improvement" items when we reviewed the original Komodo FONE was support for ring-voltage generation so the unit would ring the connected analog device. Sure enough, they've taken our advice and added it to the product. The ATA 186 now supports both H.323 and SIP, which is great news for service providers since they can deploy enhanced services without worrying about buying obsolete hardware.

VOICENET
We've all heard that VoIP enhanced services are the wave of the future, but what about today? I learned that a company called VoiceNet is using Cisco's ATA product line for some interesting enhanced services. VoiceNet's digital telephone service (DTS) delivers additional phone lines and "local presence" numbers -- a virtual telephone number technology that provides remote numbers in hundreds of U.S. locations that ring your phone. Just what does this mean? Well, suppose you have a branch office in Los Angeles and another one in New York. Then, suppose you are telecommuting in Texas with a broadband connection. You can give out a different phone number to people who reside in California, and a different number for people who live near New York. Regardless of which phone number is dialed, the VoiceNet network will route the call across the Internet to wherever your Cisco ATA currently resides -- in this case, Texas. Of course, if you don't care about saving the caller money by dialing a local number, you can always give out just one phone number, and VoiceNet will still route the call.

Other features include the ability to call between VoiceNet DTS users for free, and rates as low as 3.5 cents per minute for calls in the continental United States. With VoiceNet's Web-based automated telephone manager, customers can change these virtual telephone numbers and manage features such as voice mail, call forwarding, and caller-ID. But I am most impressed with the ability to have several hundred local numbers that VoiceNet will route directly to my single Cisco ATA unit. It goes without saying that this opens up some interesting possibilities.

VoiceNet's ability to map PSTN numbers to your Cisco ATA's IP address reminded me of the recently proposed Enum standard which does the same thing. Enum (electronic numbering) is essentially the Internet's answer to the PSTN's unique telephone numbering scheme. For example, when you want to dial someone via the PSTN, you dial the phone number from memory, look in the phone book, dial directory assistance, or perhaps look it up on the Internet. On the other hand, if you wanted to dial from a phone to an IP-enabled device, or dial from an IP-enabled device to another IP-enabled device, how would you do it? You would need to know the unique IP address of that device, whether it's a PC, PDA, IP-enabled cell phone, etc. I have enough trouble remembering 1-800-FLOWERS for Mother's Day. I don't think I could remember an IP address such as 208.243.55.66! Trying to remember the IP address is difficult, not to mention that IP addresses often change, unlike phone numbers, which are static.

ENUM TO THE RESCUE!
That's where Enum comes into play. Essentially, it is a centralized registry that will contain a listing of phone numbers with the corresponding IP addresses for your PC, PDA, and other IP-enabled devices. There has been some contention as to which government agency will oversee it. For example, the E.164 standard, which defines the formatting of telephone numbers around the world, was defined by the ITU and overseen by the FCC. In the data world, within the United States, the Commerce Department oversees the Internet Domain Naming System (DNS). Since the Enum standard "touches" both the telecom and data worlds, it remains to be seen who will have final control. Another area of contention is whether more than one company can operate and store the Enum registry database to which all Enum queries are directed. Verisign, NeuStar, and NetNumber are all competing to be the main Enum database.

In my opinion, for Enum to be truly successful, cooperation and sharing of the Enum registry among all three will be necessary. Imagine dialing a phone number, but because you are using a small carrier, the Enum registries won't let your small carrier access their Enum database. Thus, you wouldn't be able to reach that person's PDA, PC, IP-enabled cell phone, etc. Cool applications such as instant messaging someone's PDA, PC-to-IP device phone call, or video conferencing would also be impossible without a 100 percent comprehensive and accessible Enum database.

Most likely "silo" databases that do not share information will not happen, since it defeats the purpose. I imagine it will be similar to the way it is with domain registrations. In the past, just one company, InterNIC, was allowed to accept registrations. Now there are several, yet everyone can reach the Web site via the DNS standard. Similarly, I expect even if there are three major Enum registries, they will have to synchronize their databases or provide some means of inter-access.

Their "value add" to compete with one another might be in adding privacy controls or even allowing you to define rules as to when an Enum query responds with the IP address to your PDA versus when it responds with the IP address to your PC. For example, when you are on vacation, you may not want work-related calls routed to your Compaq iPaq, Palm, or other type of PDA. If an Enum registrar allows you to define schedules or rules via a Web browser, offering those services could give it an edge. Thus, having three Enum companies competing against one another could help push for more advanced enhanced services.

MICROSOFT'S HAILSTORM/.NET STRATEGY
Microsoft is making a strong push for a unified communications platform in the next release of their operating system called Windows XP. Microsoft visited TMC to demo Windows XP and a core component of Windows XP: a software program called Windows Messenger. With Windows Messenger, users will have a single, unified way to participate in text chat, VoIP, and video communication, as well as data collaboration, including whiteboard and remote desktop sharing. The Windows Messenger technology also includes presence technology to notify users when their contacts are online.

Microsoft's Communications Push
Windows Messenger will utilize the Microsoft .NET Messenger Service via the Internet and work with the nearly 32 million MSN Messenger users. Windows Messenger also can utilize Microsoft .NET enterprise servers or be programmed to work with third-party SIP servers in corporate environments. Windows Messenger will be the centerpiece of Microsoft's plan for its new Internet services such as Passport and HailStorm. Microsoft's aim is to simplify Web surfing by giving people a single online identity and provide secure access to personal information such as credit card numbers with a single click.

This has stirred a lot of controversy, since many people do not want Microsoft having control over this information. But I should point out that this information need not be stored in Redmond. HailStorm gives service providers the tools necessary to offer enhanced services and own the confidential information themselves. For example, American Express, which uses Passport to authenticate some credit card purchases, utilizes MSN Messenger to warn customers of suspicious purchases. In addition, McAfee.com will use HailStorm to deliver online protection services and send virus warnings using Windows Messenger.

If You Build It, They Will Come
The VoIP and collaboration features of Windows Messenger sound a lot like Microsoft NetMeeting, so why reinvent the wheel? I suppose when Microsoft developed NetMeeting, they believed the "if you build it, they will come" philosophy. That is, Microsoft felt if they built a communications software platform (namely NetMeeting) for the mass market, people would eventually embrace it. Unfortunately, even though NetMeeting is bundled with Windows, the mass market never truly embraced it for various reasons. Most people probably don't even know where NetMeeting is located on their Start, Programs menu.

Time For Plan B
Rather than waiting for the mass market to come to Microsoft's communications software platform, Microsoft would instead bring a better communications software platform directly to the mass market using a program that was familiar to many people. With approximately 32 million MSN Messenger users, why not "bolt on" voice over IP capabilities, video, and remote desktop sharing in the next version of MSN Messenger, namely Windows Messenger?

NetMeeting's Achilles Heel
Of course there were other reasons why something better than Microsoft NetMeeting was necessary. As much as I like NetMeeting, the latency is terrible -- anywhere from 130 ms to 250 ms. It was also very difficult to locate people to talk to. In the past, you could log on to the now-defunct Microsoft ILS servers to chat or video conference with strangers, but it wasn't easy to chat with your friends or other known contacts.

Windows Messenger has just 70-80 ms of latency one-way, which is a vast improvement over NetMeeting. Also, they added a feature called "dynamic bandwidth allocation" which adjusts to the best codec according to the bandwidth available. If the bandwidth gets worse in the middle of the call, it can adjust the codec accordingly to the next logical one with more compression. If the bandwidth improves, it can switch back to a higher quality codec.

Another improvement they've made is through their usage of Polycom's (formerly PictureTel) acoustic echo cancellation technology. One of the main complaints about VoIP was that it required a headset to prevent echo feedback caused by the microphone picking up the sounds coming from your desktop speakers. Now, you can use a standard microphone and desktop speakers and not worry about echo. Windows Messenger will also support DirectX games, so online gamers can conduct VoIP conversations as they play. I thought of a really cool application that (in theory) would work, since Windows Messenger supports DirectX. Essentially, I asked Microsoft if you could simply double-click on an MP3 file or play music on the CD-ROM and then "stream" it to the remote caller via VoIP. They said it is on the "feature list" but probably won't make it into the final release.

The inclusion of Windows Messenger in Windows XP will undoubtedly raise the ire of AOL and other instant messaging competitors. It is this type of bundling of software applications in Windows (i.e., Internet Explorer) that caused antitrust litigation against Microsoft. Of course, Microsoft would argue that Windows Messenger is much more than just an instant messaging/chat client. Bill Gates was quoted as saying, "Windows XP offers an easy-to-use, real-time communication experience, enabling people to communicate and connect like never before." He continued, "With Windows Messenger, Windows XP will help make the world a more connected place by combining the power of the Internet with the innovation of the PC industry to make a real difference for users."

I've been using MSN Messenger since it first came out, and when Microsoft added VoIP capabilities to MSN Messenger using Net2Phone, I had a feeling that NetMeeting's days were numbered. Now I ask if AOL Instant Messenger's days are numbered. One of the biggest reasons for AOL's past success was it had the largest installed base of users who could instant message each other.

In fact, many people signed up for AOL for the sole reason that all their classmates or friends were on AOL and they wanted to be able to chat with them. I should point out, however, that the free AIM client can be downloaded and used by non-AOL subscribers. Now with Microsoft bundling an instant messaging client with Windows, AOL is crying foul.

Open Standards
Although picking the bad guy in this battle is like choosing the lesser of two evils, I have to side with Microsoft. Microsoft told me that they would be supporting the "open instant messaging" iMIP standard which as of yet AOL has refused to support. Yahoo! Instant Messenger is at least one other major IM client supporting iMIP, so this client will be able to interoperate with Windows Messenger. Why do I dare side with Microsoft on this issue when Microsoft often does not follow industry standards, or designs its own competing proprietary standards? Well, as someone with a programming background, I am always a strong proponent of open standards. In fact, in the May 2001 issue, I discussed the need for telephony boards to be more open.

Having an open IM standard opens the door to some interesting possibilities. For example, with PDAs becoming more prevalent, telematics in cars, and of course cell phones, wouldn't it be great if you could IM someone sitting in their car, to their cell phone, or their PDA? But I don't recommend typing while driving! I asked Microsoft if Windows CE and embedded Windows will support SIP and they assured me it would.

Would you like another reason why having an open IM standard is critical? OK. With AOL, you can currently search the AOL profiles for hobbies, location, and other criteria. Windows Messenger, Yahoo! Messenger, and other clients do not have access to search this information. For those with privacy concerns, this is probably a good thing. Then again, if someone puts something in their AOL profile, then they have already committed to the fact that they are offering information about themselves. If they don't want that information to be disclosed, they can enter no information at all.

Right now the instant messaging databases are fragmented, but with an instant messaging standard, you can query everyone's profile, regardless of which IM client they are using. But imagine for a minute that privacy controls were available to protect the user. Then imagine that every Internet user was able to define their hobbies, ZIP code, and other information. Let me give you a sample application. I have friends who are motorcycle fans -- many belong to motorcycle clubs. Using instant messaging technology, they can simple query their surrounding area (ZIP code) for the hobby "motorcycle enthusiast" and then shoot off an instant message to ask if that person wants to go for a cruise. With an open IM standard, your query will return many more results, since every single IM client's profile (privacy issues notwithstanding) on the Internet would be available. But one step at a time. First we need the IM clients to be able to chat with one another before we then take the next step of allowing each IM client access to each others database of user profiles.

Don't get me wrong; I realize the privacy implications that would exist. Fortunately, unlike AOL Instant Messenger, Windows Messenger allows you to block anyone except your personal or business contacts from instant messaging you. Anyone who uses AOL or ICQ knows all about the "IM spam" as I call it, where you usually get invited to visit porn sites.

Perhaps other privacy controls could be added to improve the experience? For example, maybe you can have two modes in your IM client: "privacy/business mode" and "personal/less restricted mode." The "less restricted" mode could in fact allow strangers to IM you with certain restrictions. Similar to Outlook's spam rules and filters, you could define rules that only allow users within 25 square miles of your ZIP code to IM you and they are of the opposite sex, within seven years of your age, and the instant message doesn't include a hyperlink to visit a Web site (spammers). This could make personals Web sites such as Match.com or AOL's search profile engine look pale in comparison! Other rules or criteria could also be defined, but you get the idea.

I brought up the personal use of this new Windows Messenger, but it has real-world business applications as well. Utilizing Windows Messenger, corporate enterprises can allow employees to interact with one another more easily. With presence detection, employees will know if the person they need to talk to is at their desk, which will certainly improve productivity. They can initiate a voice call simply by clicking on the person's name, rather than picking up the phone to dial an extension. Also, if the person is located in another state in a remote office, you save the expense of the long-distance call. You also avoid the possibility of reaching the person's voice mail and playing voice mail tag. In addition, Windows Messenger supports integration with Microsoft Exchange Server to easily setup, configure, and manage each employee's IM settings.

During my meeting with Microsoft, I inquired about security, since instant messaging can be a great business tool, but it can also be a security or productivity risk if employees are transmitting/receiving files or chatting all day long with friends. All of this can be managed from the server to allow or disallow internal and/or external communication. In addition to the SIP client (Windows Messenger), Windows XP also contains a SIP server registrar. With SIP support on Windows Messenger, Microsoft said that in addition to Net2Phone, they can now support other ITSPs. As an added security measure, IT management can define which ITSPs each employee must use. Another great application IT help desk personnel will enjoy is the remote desktop sharing feature, which will allow a help desk technician to remotely view the screen as well as control the mouse and keystrokes. This allows for remote troubleshooting without leaving their desk.

Another business application Windows Messenger could be used for is for e-commerce. When visiting a shopping Web site, a Web visitor with a question can simply click on a "Web call" button, which will spawn Windows Messenger and initiate a VoIP call to a call center agent. One might wonder if such a VoIP software client will kill competing VoIP software clients from Net2Phone, eStara, HearMe, or others. Well, most of these companies don't make any money on the VoIP client, except Net2Phone which does have banner ads. However most make the majority of their money on talk time or billable minutes. As long as the ITSP supports SIP, the Windows Messenger client can support it. Of course, some ITSPs currently only support H.323 and not SIP, so it is certainly possible that Windows Messenger could hurt these companies.

Communications is what this magazine is all about. Standards such as SIP, H.323, Enum, and iMIP can only further the cause for open communications, which in the end will benefit the consumer and business enterprise. I like what Cisco has done to enhance the former Komodo product and I'm very excited about Enum and its possibilities, as well as the mainstreaming of Internet telephony and collaboration capabilities to the masses that Windows Messenger will bring with the release of Windows XP. 

[ Return To The August 2001 Table Of Contents ]