Upcoming Events

Cloud Connect
Santa Clara
Feb 13-16, 2012

Cloud Connect brings together the entire cloud eco-system to better understand the transformation we're experiencing and promises to be the defining event of the cloud computing industry. Learn about the latest cloud technologies and platforms from thought leaders in Cloud Connect’s comprehensive conference.

Register Now!

R E V I E W

Polycom KOs Proprietary VoIP Woes

August 21, 2003
By Peter Morrissey

>> continued from previous page

How We Tested

	Issue TOC
	Print full article
	Print this page
	Download as PDF
	E-Mail this URL
	Discuss this article
	Flame the author

	In this article
	Introduction
	It's All Good
	Just Managing
	Polycom SoundPoint IP 600
	Mitel Networks Corp. 5055 SIP Phone 2.0
	Siemens optiPoint 400 standard SIP 2.2
	Zultys Technologies ZIP 4x4
	Snom Technology Snom200 VoIP phone
	ipDialog SipTone
	How We Tested
	SIP and NAT: Not So Perfect Together
	Web Links
	Report Card

For our phone-to-phone call testing, we used BroadSoft's BroadWorks product for the SIP infrastructure. First, we called every phone from every other phone. We also tested interoperability with Microsoft clients.

For our three-party conference test, we made a call from the PSTN through BroadSoft's gateway, and attempted to transfer the call to every other phone.

How We Tested

click to enlarge

For our message waiting indicator test, we left voicemail messages and then read them to see if the indicator turned on and off correctly. We also tested each phone's ability to check BroadSoft's voice-mail product.

Finally, for our call-pickup test, we put all the phones in a "call pickup group" using BroadSoft's Web-based provisioning software. We then called one phone in the group and attempted to pick up the call from each of the other phones by dialing the associated call-pickup *98 feature code.