« January 17, 2006 | Main | January 19, 2006 »
Asterisk Certification
Be sure to check out the Asterisk certification at Internet Telephony Conference & Expo next week. We are very proud to be expanding
------------------------
Open Source/Asterisk Certification Program Added to INTERNET TELEPHONY Conference & EXPO Program
Norwalk, CT, [January 18, 2006] - Technology Marketing Corporation (TMC) today announced that a special TMC University™ certification course covering Open Source and Asterisk, the open source PBX will be offered to attendees at next week’s INTERNET TELEPHONY Conference & EXPO East 2006 in Ft. Lauderdale, Florida.
The conference will be held January 24-27, 2006 at the Ft. Lauderdale/Broward County Convention Center in
Attendees of
According to TMC president and INTERNET TELEPHONY Conference Chairman, Rich Tehrani, open source technologies are revolutionizing PBX technology, replacing costly hardware with new, customizable software options.
“Open source is one of the fastest growing segments of VoIP. Adding these certification courses to the world’s largest VoIP conference is perfectly logical. Like with any emerging technology, there is a high demand for open source training as developers, service providers and enterprises evaluate the viability of open source as an alternative to other solutions,” said Tehrani.
The following topics are covered in
1. The Business Case for Open Source/Asterisk
2. Introduction to Asterisk Terminology and Jargon
3. Building and Installing Asterisk System
4. Building the First “Hello World” Application
5. Asterisk in the
Link this |
Email this |
Leave comment
Trackback URL: Asterisk Certification
Technorati
Del.icio.us
BoingBoing
Slashdot
Digg
Spurl
Furl
64 Bit Computing
Here is a great article from Microsoft that points out the benefits of 64 bit computing and how aside from the potential need to recompile, there are few problems with running 32-bit applications on 64-bit computers. The OS, Windows Server 2003 x64 is what makes this possible.
Here is a graph and and excerpt of the article:
There are two things of interest to note in the CPU utilization graphs. First, the average processor utilization of the x64 server is only about half that of the x86 server (34 percent versus 64 percent). Second, on the x86 server there are noticeable spikes where the CPU was running at 100 percent capacity for a sustained period of time. This was due to one or more app pools recycling because they had run out of virtual memory. On the x64 server these spikes don’t occur because the app pools don’t run out of memory.
The impact of this on the rest of the server is huge. Application response times improve and content is delivered to the clients much more quickly. Using the Microsoft® Server Performance Advisor, it becomes obvious that this is the case when you look at the response times of the different components of our site (see Figure 6).
The Server Performance Advisor (SPA) used to generate these numbers is available free at Microsoft Windows Server 2003 Performance Advisor.
All in all, the key things to remember from this migration include the significantly improved application response times thanks to larger virtual memory space on the x64 platform, the significant drop in CPU utilization due to less frequent recycling, and the server consolidation made possible by better performance on each server.
Lessons Learned
As with any platform migration there are sure to be hiccups or unexpected scenarios while validating the new platform. Take a lesson from our experience and remember to always verify and ensure that any third-party dependencies are compatible with the x64 operating system. Also ensure that any component that requires a kernel-mode driver has an x64 compatible driver, because x86 drivers cannot be used on the x64 operating system.
In addition, MSCOM had to verify the compatibility of third-party products like antivirus software, backup software, imaging and deployment software, and common administration tools that use filter drivers (such as filemon, regmon, and so on). So when you consider migration, keep these dependencies in mind.
Be sure to fully understand any third-party dependencies and the availability of x64 compatible versions. Become familiar with the WoW64 redirection behaviors that occur in both the registry and file system, and understand script dependencies so you know which script host to run it with, as explained in the sidebar "Redirection Behaviors and Dependencies."
Future Directions
After transitioning to the x64 OS, the memory limitations that MSCOM struggled with for years suddenly were eliminated. At the time of this writing, Microsoft.com is running the 32-bit version of IIS and ASP.NET running on Windows Server 2003 x64 Edition, and enjoying all the benefits.
The ongoing transition to the x64 platform in our environment is easier because the hardware and software migration is easier. The migration steps outlined here allow for a phased approach that enables proper testing, while letting you capitalize on the x64 hardware investment immediately.
This migration is merely a stepping stone in a transition to running in a native 64-bit x64 environment. Still, this configuration has already yielded tremendous results. In addition, as we migrate to the newly released ASP.NET 2.0, we will be able to run certain applications in a full native 64-bit IIS worker process, increasing available virtual memory from 4GB to 8TB. I think we’ve only seen the beginning of what the x64 platform has to offer!
Link this |
Email this |
Leave comment
Trackback URL: 64 Bit Computing
Technorati
Del.icio.us
BoingBoing
Slashdot
Digg
Spurl
Furl
Silver Peak
I received this whitepaper from Silver Peak. I haven’t heard of the company previously and I thought this was an interesting paper and worth posting. I think VoIP quality is a hidden problem the industry needs to do a better job of addressing. This paper is a bit commercial but still worth a read:
---------------
Many of you are aware of "server sprawl" - the proliferation of servers and storage in branch and remote offices. This occurs when applications run poorly over the WAN and local servers are required in the branch office to achieve acceptable performance for branch office workers.
Following are unique VoIP challenges that we have seen as companies begin to consolidate branch office servers:
-The Branch Office Problem
-Special VoIP Challenges
-How to Measure VoIP Quality
-Fixing VoIP on the WAN
-Additional Resources
The Branch Office Problem
--------------------------
When most people think of server sprawl, they think about conventional branch office applications, such as email, file and web. Every time a new branch office is opened, a rack of networking equipment is required to support these functions. To combat this, companies have begun to strategically move towards a model of server centralization.
As fixed or declining budgets have intersected with new regulatory standards such as Sarbanes Oxley, the environment has become ripe for this type of change. (More information on the security and compliance issues that come from server sprawl can be found at:
http://www.silver-peak.com/html/security_compliance.htm
As branch office infrastructure is centralized, applications are subject to the inherent limitations of WAN technology. Originally, compression, QoS and other optimization techniques were sufficient to support basic branch office application needs. The emergence of web acceleration technology gave rise to an alternative solution, caching, which was later extended to address file services and email.
Unfortunately, they are not enough to support today's complex branch office application needs.
Special VoIP Challenges
-----------------------
Of special interest is the effect that server centralization in the branch office is having on VoIP. According to a recent ComputerWorld survey, VoIP deployments will grow faster in the next 18 months than any other category of enterprise applications. As VoIP (and Video) becomes more prevalent throughout the enterprise, IT staff are being forced to address the unique requirements of delivering voice to branch office and remote users. At the same time, to keep user performance acceptable for the newly centralized applications, they must accelerate other business critical applications over the WAN, which have very different delivery requirements from voice, video, and other real-time applications.
VoIP, for example, is based on UDP, which is highly sensitive to WAN traffic quality - jitter, latency and packet loss. As a result, companies considering VoIP and consolidation projects will require an acceleration platform that is specifically architected to support UDP, including advanced QoS capabilities to minimize jitter, latency, and packet loss.
Sidebar: How to Measure VoIP Quality
------------------------------------
Voice quality is measured in the telecom industry using the 'Mean Opinion Score', or MOS. The MOS score is a number between 1 and 5 used to quantitatively express the subjective quality of speech in communications systems. A "MOS score" of 4.0 is considered toll quality voice - the quality you would hear on a wired land-line from your local telephone company. A "typical" cell phone call might achieve a MOS score of 3.0 to 3.5, give or take.
Running VoIP with the current generation of IP PBX equipment and a G.711 codec will achieve a MOS score of 4.0 ~ 4.4 on a clean LAN. On a WAN link however, the impact of jitter, latency and packet loss can drop the voice quality to that of an old analog cell phone - a MOS of under 3.0.
Fixing VoIP on the WAN
----------------------
To maintain toll quality over an impaired WAN, application acceleration devices need to use advanced Quality of Service (QoS) techniques, jitter and latency mitigation, loss mitigation, and real-time data reduction. But the typical network link between the branch office and headquarters is carrying more than VoIP: web traffic, file sharing Citrix and other traffic is mixed in with VoIP traffic.
Here's the problem: most acceleration products today do not handle all traffic types. Some accelerate only web (HTTP) traffic while others provide packet shaping or file acceleration only. More recent acceleration products accelerate only TCP traffic (VoIP and video are UDP traffic and are either passed through the acceleration appliance, or are 'stepped on', which doesn't do much to improve VoIP quality).
Does voice matter? There is enormous overlap between companies undergoing branch office server centralization initiatives and those implementing VoIP. As many application acceleration platforms ignore VoIP, or hamper voice performance by adding latency and/or jitter, these two initiatives are likely to be on a collision path. Proper planning can ease this transition, as - there are application acceleration solutions that support voice traffic in conjunction with traditional data applications.
Net/net: If you are considering acceleration appliances as a means to reduce server sprawl in the branch office, be sure your vendor can in fact accelerate and manage all traffic types: TCP, UDP, streaming traffic (VoIP and video) and even real time traffic.
Additional Resources
--------------------
Below are various white papers and resources with additional insights into the VoIP/centralization challenge (no registration required):
Independent VoIP performance report
This test report, completed by Miercom, which shows the effect that WAN latency and jitter can have on VoIP, and how a proper acceleration solution can attain toll quality MOS (note - this report also demonstrates the performance you can expect when accelerating file services, NFS and Citrix)
VoIP application brief
This one describes in more detail unique requirements for delivering VoIP and other traffic types to remote and branch offices.
ComputerWorld Survey
A CIO survey conducted by Computerworld that shows how voice, video, and other real-time applications are the fastest growing traffic in today's enterprise.
"The Future of Application Delivery"
A whitepaper by industry veteran Robin Layland that addresses different techniques for application acceleration across the WAN, including advanced data reduction techniques, such as "Network Memory."
Link this |
Email this |
Leave comment
Trackback URL: Silver Peak
Technorati
Del.icio.us
BoingBoing
Slashdot
Digg
Spurl
Furl
ITEXPO Don't Miss Luncheon
Vonexus, an Interactive Intelligence are hosting a "New Rules of Business Communications" luncheon at Internet Telephony Conference & Expo next week.
This luncheon includes a keynote from Interactive Intelligence founder, president, and CEO, Dr. Donald E. Brown, who will provide an educational and entertaining look at the latest in best practices for deploying business communications systems, including IP telephony solutions for the enterprise and contact center. I understand this event will be very exciting and not a standard industry function. I have heard rumors about what the company is planning and it sounds like you don't want to miss it.
The luncheon will take place Wednesday, Jan. 25, 12noon - 1 p.m. There is no advance registration and attendance is limited so please arrive early. Food will only be provided to those people who receive food as part of their expo plan such as paid conferees, analysts and members of the press. Others are welcome to come and hear Dr. Brown speak.
Link this |
Email this |
Leave comment
Trackback URL: ITEXPO Don't Miss Luncheon
Technorati
Del.icio.us
BoingBoing
Slashdot
Digg
Spurl
Furl
Google as Ad Agency
You know I think it is time to call a spade a spade. Google doesn’t want to be called an agency and past interviews with company execs categorically deny the company is an agency or has any intention to become an agency. I have read that Google treasures ad agencies and considers them important partners in their mutual success.
This is all true. Many agencies do in fact place ads on Google and sites displaying Google ads. However, it is important to note that Google is getting more and more into the center of the ad placing relationship between media companies and buyers. If they are not becoming an ad agency then at least they have become a placement agency. Placement agencies may not design creative but instead they help companies decide where and when ads should run.
Typically placement agencies crunch numbers and tell companies where they think their ad dollars are best spent. There are a whole host of metrics these agencies use to make suggestions. Google is currently using automation to do the exact same thing online. For example they help decide where ads go. Will the ad be on the top of a page, as the fifth link down, etc.
Perhaps your ad is best to be placed on partner pages where related editorial lives. To further muddy the waters the issue of creative comes into play. If you have multiple ads the search giant uses its algorithms to determine which ad does best in what place. They may even take into consideration the time of day and whether weekends and holidays affect the click through results.
Certainly Google can be considered a placement agency in the online world. It seems now, Google wants to bring its expertise at helping companies place ads into the world of radio as well. The company recently purchased dMarc Broadcasting, a company that runs an online system allowing advertisers to buy radio airtime. It further connects the ads with the computer systems that help run radio stations for eventual broadcasting.
Google says they have access to many smaller advertisers that would not typically run ads on radio and their involvement in the business is good for radio advertising. I tend to agree. Many advertisers have done well with Google web-based ads and these companies are a no brainer to try new media such as radio. The next stop is television it seems as industry rumors point in the direction of Google purchasing a company doing something similar in the TV world as well.
If you have been waiting for the VoIP tie-in, here it is. Google is going to potentially figure out how to generate revenue from pay per call advertising. If the radio and TV markets are indeed going to be struggling more and more to make money, they may be amenable to getting paid per phone call instead of not at all.
This isn’t so far fetched as many TV stations routinely deliver deep discounts on their ads – especially when they can’t find advertisers for certain time slots.
I would imagine that pay per call ad programs will work well for some networks and advertisers. I am sure it is not perfect for every business. Still if there are 5,000 companies – a number I pulled out of a hat, that can benefit from such a program and these companies wouldn’t think of using TV or radio today, then this is a win/win for Google, TV and radio. Of course Google’s customers too will win.
If there has to be a loser it may become the placement agencies as Google’s automation could eventually render some of these agencies obsolete. But in a world that is increasingly becoming more automated and subsequently more efficient, Google’s automation of the advertising world may be welcome.
Link this |
Email this |
Leave comment
Trackback URL: Google as Ad Agency
Technorati
Del.icio.us
BoingBoing
Slashdot
Digg
Spurl
Furl