Microsoft Lync2013 integration with Sonus SBC1000 session border controller

Introduction

The Gigaset N720 does not have the Microsoft Lync implementation in the device, to be able to connect to Microsoft Lync additional hardware is needed. Sonus provides a solution with their SBC1000 that will be the interface to the Lync environment.

Sonus and Gigaset performed a series of tests to validate the connection of Gigaset N720 IP DECT Multicell System, through Sonus SBC1000, into the Microsoft Lync environment.

Under the described configuration the Gigaset DECT phones were validated to support the following features:

  • Basic Calls
  • Hold
  • Call Waiting
  • Forward
  • Transfer
  • Base Station Roaming

See below for a list of supported features when using Gigaset pro DECT systems and Microsoft Lync 2013 connected through an Sonus SBC1000

 

 

Feature                                       

     N720 Multi cell    

Firmware Version

70.073.00.000.00

Firmware Version Sonus SBC10003.0.0 v241

Basic Call

Calling line (CLIP)

Connected Line (COLP)

n/a

Anonymous call

n/a

Do Not Disturb (DND)

n/a

Message waiting

n/a

Call list/history

Voice mail deposit/retrieval

n/a

Call waiting

Call Hold / Toggle

Call forward (CFU)

Call forward (CFNR)

Call forward (CFB)

Call Transfer attended

Call Transfer unattended (blind)

n/a

Completion of Calls to Busy Subscriber (CCBS)

n/a

DTMF

Conference 3pty

n/a

BLF Busy / Idle indication

n/a

Call pick-up direct  ( * 8 extension)

n/a

Call pick-up group ( * 8 )

n/a

Call pick-up BLF

n/a

Session Audit

Call Completed Elsewhere

UDP / TCP protocol

(UDP tested)

Central Phonebook

n/a

Autoprovisioning

n/a

 

SBC 1000 (Formerly NET UX

The Sonus SBC 1000 Session Border Controller and Microsoft Qualified Survivable Branch Appliance

Sonus now brings session border controller (SBC) SIP communication capability to the enterprise branch and small and medium businesses. To further address deployment needs Sonus has also enabled branch survivability, Microsoft Lync primary / back-up server, and integrated analog ports all within the single Sonus SBC 1000 compact appliance.

  • Full SBC SIP security, demarcation, policy, and interworking functionality (including media interworking)
  • Microsoft Lync™ enhanced gateway/SBA (Survivable Branch Appliance) services for small to mid-size offices
  • Alternate SIP trunk(s) and/or TDM gateway for assured continuation of services
  • Analog ports for fax and low cost phones

The Sonus SBC 1000 is built from a common code base with the the Sonus SBC 2000. Miercom Performance Verified and Miercom Certified Secure Laboratory testing provided validation of the Sonus SBC 2000 Session Border Controller.

SBC offers optimized SIP Trunking

With an integrated enterprise SBC (Session Border Controller), the Sonus SBC 1000 offers enterprise branch and small and medium businesses optimized SIP Trunking services for Internet Telephony Service Provider ( ITSP) connectivity.

  • Complete enterprise/ ITSP demarcation point services, such as network topology hiding, transcoding, IP transport conversion (TCP <-> UDP),and signaling/media encryption (TCP<->TLS/RTP <->SRTP)
  • Multi-ITSP registration, with optimized routing, including cost or service quality / availability
  • Built-in Network Address Translation (NAT), prevention Denial of Service (DOS) and Distributed Denial of Service (DDOS) attacks
  • Call Admission Control (CAC) for quality of service and security

Branch Office Connectivity and Survivability for Microsoft Lync Server 2010

The Sonus SBC 1000 Survivable Branch Appliance (SBA) provides basic voice services to branch office users during a WAN outage. During a WAN outage, the SBA appliance manages the intra-branch voice calls and IM sessions as well as inter-branch communications and voice mail retrieval over PSTN. The Sonus SBC 1000 Benefits:

  • Multiservice Router and VoIP gateway with Branch office Survivability
  • Session Border Controller with NAT function, Network topology hiding, and Security
  • Continued branch office operations through WAN failure
  • Also configurable as a stand-alone office primary Lync server

Highly flexible connections for SIP, legacy PBX, analog, and PSTN

The Sonus SBC 1000 offers true “any-to-any” signaling translation and media interworking between SIP, analog, and TDM endpoints. The Sonus SBC 1000 can simultaneously connect to legacy TDM PBXs and the PSTN through 2 T1/E1 PRI ports and up to 24 FXO. In addition, up to 24FXS ports are available for fax and low cost analog phones. BRI ports are also supported, and may exist alongside the FXS, FXO, and PRI ports to provide complete analog/TDM device integration into a branch office’s Lync topology.

In parallel, the Sonus SBC 1000 also interconnects IP-based endpoints (i.e. IP-PBXs, non-Lync SIP clients) and public VoIP networks (e.g. ITSPs) to the Lync clients. And, with Sonus’ optional applications, there’s no need to replace your legacy non-Lync SIP clients; the Sonus SBC 1000 can report non-Lync SIP client user states (e.g. presence, user busy, etc.) to Lync clients.

Architecture and Modularity

The Sonus SBC 1000 can scale up to 100 simultaneous sessions.

The Sonus SBC 1000 provides interoperability with Sonus VX Series Voice Exchange and Quintum media gateway products while supporting the transparent “drop-in” installation methodology for the upstream deployment model that was pioneered by Sonus. Sonus platforms are specifically designed to support upstream deployments with advanced features that give customers the highest levels of flexibility, scalability, quality of experience (QoE) and investment protection.

The Sonus SBC 1000 offers powerful quality of experience features, industry leading voice quality, intelligent call routing, call forking, and comprehensive PBX interoperability. Directory-based call routing is built directly into the SBC platform. The SBC also features a multi-mode user interface that provides configuration and real-time management of SBC nodes. The web-based user interface is designed to simplify and accelerate installation using a “task” configuration mode.

 

  • No labels