SHARE
Follow this article on Twitter Facebook LinkedIn Bookmark and Share
Home >> Communications Infrastructure >> Network Devices

Adtran ships unified communications software

Adtran ships unified communications software

By:  Greg Meckbach  On: 05 Jan 2010 For: Network World Canada Creator
 

The NetVanta Enterprise Communications Server can support 2,000 users, includes fax, voicemail and works with telephony equipment from Avaya, Nortel and other vendors. A Yankee Group analyst was surprised Adtran is offering this capability

Adtran Inc. (NASDAQ:ADTN) of Huntsville, Ala. has announced three unified communications software products designed to combine voicemail, faxing and text-to-speech conversion for corporate users.

 

Although Adtran already makes private branch exchanges (PBXs), the Business Communications System and Enterprise Communications Server could work with hardware from other vendors, such as Nortel Networks Corp. and Avaya Inc., which has agreed to buy Nortel’s enterprise products.

 

“We can extend unified communications to existing PBXs,” said Jeff Wissing, Adtran’s senior product manager for unified communications. “We use integration hardware to connect to thing like a Nortel or Avaya PBX, things like ‘find me follow me’ and

inbound and outbound faxing.”

 

The NetVanta Business Communications System for small to mid-sized businesses can accommodate up to 100  users per server and can support Internet Protocol (IP) telephony. NetVanta Enterprise Communications Server can support more than 2,000 users per server. Both work only on Microsoft Corp.’s Windows operating system and also work with time division multiplexing (TDM) systems.

 

The NetVanta Business Application Server, which handles more than 200 concurrent calls, is designed to let non-technical staff customize their telecom processes.

 

“You don’t have to be a programmer to set up these applications and integrate these functions into your current systems and databases,” said Chris Thompson, Adtran’s senior product manager for voice.

 

Pricing depends on user configuration, but small firms could expect to pay US$29 per user for the Business Communications System software alone, not including the server. At the enterprise level, companies could expect to pay US$45 to US$56 per seat for Enterprise Communications Server, Wissing said.

 

The NetVanta UC products were originally made by ObjectWorld Communications Corp., an Ottawa firm Adtran acquired late last year.

 

“Since the acquisition, we rebranded it, we added some capabilities,” Wissing said. For example, users can go into their Microsoft Outlook contact list, find someone they want to call and initiate that call by clicking on the phone number.


Sign up for our Newsletters

 












Print |  Views: 4086   |   Rating:ononononoff  (1 votes)
Rate this article on a scale of
1 to 5 stars,5 being the best.




Greg Meckbach Greg Meckbach Greg Meckbach is editor of Network World Canada and has worked for ComputerWorld Canada, Communications & Networking and Computing Canada.

Recent Canadian IT Jobs




Related Content

How to make unified communications work for you
How to make unified communications work for you Here's how you can reduce the human latency that plagues unified communication and collaboration projects
Nortel picks up open source software PBX partner
Nortel picks up open source software PBX partnerNortel's purchase of Pingtel means it now owns an IP PBX it had been including in the SCS 500 bundle sold by IBM and Dell. Several analysts see merit in the deal, but one wonders what it means for Nortel's partnership with Microsoft
Can Microsoft speak reliably in the unified communications space?
would you buy a unified communications solution from microsoft corp.?if the product is anything like the operating system software the company sells, then most definitely not. unified communications (uc) isn’t something to invest in without some rock-solid guarantees of performance and reliability. there’s no, “we’ll work out the kinks as we go,” with this sort of application. it’s not windo
blog comments powered by Disqus