Sonus Unified Communications SBC1000/2000 Series Enterprise Session Border Controller Configuration Guide

Transcription

1 Sonus Unified Communications SBC1000/2000 Series Enterprise Session Border Controller Configuration Guide For Use with Verizon s SIP Trunking Service And Microsoft Lync Server 2010 Sonus, Inc Paseo Padre Parkway Fremont, California Copyright 2011 Network Equipment Technologies, Inc., All rights reserved. This is a NET internal development document. It does not necessarily describe accurately the design or operation of any NET product or service and it does not create any express or implied warranty. NET s sole warranty is contained in its Product Warranty. The End User Documentation shipped with NET s products constitutes the sole Specifications referred to in the Product Warranty. NET assumes no responsibility for any use of the information contained in this document or for any infringement of patents or other rights of third parties that may result. Networking products cannot be tested in all possible uses, configurations or implementations, and interoperability with other products cannot be guaranteed. The customer is solely responsible for verifying the suitability of NET s products for use in its network. This document and NET s specifications are subject to change without notice.

2 Change History Author(s) Date Revision Comment SONUS May 11, Initial Version 2

3 Contents 1 INTRODUCTION 5 2 EQUIPMENT AND SOFTWARE REQUIREMENTS SBC1000/2000 Hardware and Software Microsoft Lync Hardware and Software 6 3 TOPOLOGY DESCRIPTION AND SONUSWORK DIAGRAM Component Descriptions Features Supported 10 4 VERIZON SIP TRUNK REQUIREMENTS 10 5 CONFIGURATION GUIDE Microsoft Lync 2010 Configuration Adding PSTN Gateway to Topology Associate the Mediation Pool to the PSTN Gateway Publish Updated Topology Configure Lync Route Configure Lync Dial Plan Configure Lync Voice Policy Enable Users for Enterprise Voice Enable Voice Mail in Exchange UM SONUS SBC1000 / SBC2000 Configuration SONUS SBC1000/2000 Prerequisites SBC1000/2000 Initial Configuration SBC1000/2000 SBC Lync 2010 Configuration Steps SBC1000/2000 Configuring Transformation Tables Call Route Table Configurations SBC1000/2000 Configuring SIP Server Tables Alternate Configuration Options Configuring SBC1000/2000 to Force Transcoding to G Using TCP instead of TLS between SBC1000/2000 and Lync 94 3

4 5.3.3 SBC1000/2000 Public EtherSonus Port and IP Addressing Error! Bookmark not defined. 6 SBC1000/2000 TROUBLESHOOTING Visual Analysis Viewing SBC2000 Debug Logs Sending SBC1000/2000 Debug Logs to a Syslog Collector VERIFYING SOFTWARE VERSION ON THE SBC1000/2000 SBC UPGRADING SBC1000/2000 SBC SOFTWARE SUPPORT INFORMATION SONUS Documentation and Support Information Documentation SONUS SBC1000/2000 Product Training SONUS SBC1000/2000 Technical Assistance Microsoft Documentation and Support Information Microsoft Lync Documentation Microsoft Lync Support 116 4

5 1 Introduction This document provides a configuration guide to assist administrators in connecting the Sonuswork Equipment Technologies (SONUS) SBC1000/2000 Session Border Controller (SBC) to work with Verizon s SIP Trunk Service. The SBC1000/2000 is an SBC that resides at the customer premise between the customer s Microsoft Lync Server 2010 deployment and the Verizon s SIP Trunk Service. Microsoft Lync 2010 combines Enterprise voice, instant messaging, enhanced presence, audiovideo conferencing, and into an integrated communications experience - A true unified communications. Enterprise voice is a Microsoft Lync server's fully featured VoIP solution, which includes connectivity with the telephony Sonuswork. For Enterprises wishing to fully utilize their deployed Microsoft Lync server and communicate outside the Enterprise, a connection to the traditional PSTN Sonuswork is required. An InterSonus Telephony Service Provider (ITSP), like Verizon Business Services, can provide a cost effective solution for connecting to the traditional PSTN Sonuswork, via their SIP Trunking service. The SBC1000/2000 SBC is required to provide the integration between the Microsoft Lync Servers to the Verizon SIP Trunking Service. The SBC1000/2000 Series SBC s offer true any-to-any signaling translation and media interworking between Lync and IP-based endpoints (i.e. IP-PBXs, non-lync SIP clients) and public VoIP Sonusworks (e.g. ITSPs) to the Lync clients. The SBC1000/2000 SBC s are architected to meet the demands of any size office; from the SBC1000/ scaling from 5 96 concurrent SIP Sessions to the SBC2000 scaling from 25 to 600 concurrent calls. The SBC1000/2000 also offers support for the Microsoft Survivable Branch Appliance (SBA) for customers who desire a higher level of resilience at remote offices. During a WAN outage, the SBA manages the intra-branch voice calls and IM sessions as well as inter-branch communications and voic retrieval over PSTN. SBC1000/2000 appliances offer extraordinary service integration of Unified communications to any size branch office. Businesses enjoy the benefit of deploying a single device for all Sonusworking and communication needs and save both capital and operational expenses. By supporting a variety of protocols, advanced security, codec transcoding,, and data services, the SBC1000/2000 enables a distributed enterprise to cost-effectively implement Unified communications across the enterprise. With an integrated Enterprise SBC, the SBC1000/2000 offers to Lync users optimized SIP Trunking services for ITSP connectivity. Complete enterprise / ITSP demarcation point services including: Sonuswork topology hiding Transcoding IP transport conversion (TCP <-> UDP> Signalling / media encryption conversion (TCP/RTP <-> TLS/SRTP) Multi-ITSP registration, with re-routing on excess cost or loss of service Built-in NAT(Sonuswork Address Translation) 5

6 Prevention of DDOS and DOS attacks 2 Equipment and Software Requirements 2.1 SBC1000/2000 Hardware and Software The follow tables provide information relating the hardware and software requirements of the SBC1000/2000 SBC s Software Version Solution Max Concurrent Sessions SBC v137 SIP 96 SBC v137 SIP 600 Build of Materials (BOM) used for the test equipment. Hardware SIP Licenses Concurrent Sessions SBC1000 UX1K-SBC-15 Included 15 SBC2000 SBC UX-SIP-25 (Qty-4) 100 The table below provides examples of the SONUS hardware and software that may be ordered for different customer requirements. For additional information please contact your SONUS Sales Representative or send requests to Sonus_sales@Sonus.com. Sessions SBC1000/2000 SBC Hardware SIP Licenses Required 15 SBC1000/ SBC1000/20001K- Included SBC SBC1000/ UX1K-SBC-30 Included 45 SBC1000 UX1K-SBC-45 Included 100 SBC2000 SBC UX-SIP-25 (Qty-4) 200 SBC2000 SBC UX-SIP-25 (Qty-8) 300 SBC2000 SBC UX-SIP-25 (Qty-12) 600 SBC2000 SBC UX-SIP-25 (Qty-24) Specification sheets for the SBC1000 and SBC2000 can be viewed at the links below. SBC1000 Data Sheet SBC2000 Data Sheet 2.2 Microsoft Lync Hardware and Software The follow tables provide information relating the hardware and software requirements of the Microsoft Lync components. 6

7 Software Solution Deployment Type Version Lync Server SIP Standard Edition Lync Mediation SIP Standard Edition Lync Client SIP Windows Version All Microsoft software components were hosted on an IBM X201 ThinkPad Computer. Details listed below. Lync Server Lync Mediation Server Lync Client Exchange Server Operating System Windows Server 2008 R2 Windows Server 2008 R2 Windows 7 Enterprise Windows Server 2008 R2 CPU Intel Core i5 Intel Core i5 Intel Core2 Duo Intel Core i5 RAM 2 GB 2 GB 4 GB 2 GB Hard Drive 40 GB 40 GB 80 GB 40 GB 32 / 64 bit Topology Description and Sonuswork Diagram This section provides an overview of how the SONUS SBC1000/2000 SBC is used to integrate the customer s Microsoft Lync Server 2010 with Verizon s SIP Trunking Service. 7

8 Admin Exchange NET UX2000/UX1000 SBC With Lync Server 2010 to Verizon SIP Trunk AD / DNS Server LyncDC.honig.net Lync Server / Lync Mediation Server LyncFE.honig.net Exchange Server Exchange.honig.net WAN/LAN Lync Hardphone Astra Lync Client Sonus SBC Uxsbc.honig.net Lync Client FAX UX2000 Unified Communications Verizon Managed Router Public IP Private IP Verizon SIP Network Figure 3.1 Topology Components 3.1 Component Descriptions The customer premises equipment may consist of the following components. Verizon Managed Router/NAT The Verizon managed router provides a termination point for the IP Link used to carry the SIP traffic to and from the customer location to the Verizon SIP Trunk Servers. It provides two interfaces, one which connects on the public IP Sonuswork and one which connects to the customers private IP Sonuswork. The router provides a Sonuswork Address Translation (NAT) function to pass IP traffic between the two IP Sonusworks. The router will be configured by Verizon to meet the specific customer location requirements. SONUS SBC2000 / SBC1000 Enterprise Session Border Controller Sonuswork Equipment Technologies SBC1000/2000 Series (SBC2000 &SBC1000) acts as an Enterprise Session Border Controller. The customer SBC1000/2000 SBC provides security, advanced signaling, routing and call control interworking between the customer s Microsoft Lync Server 2010 and Verizon SIP Trunk Service. The SBC1000/2000 SBC will be configured with a single EtherSonus Interface which will reside on the customer s private IP Sonuswork. SBC1000/2000 SBC to Verizon SIP Trunk 8

9 o The SBC1000/2000 SBC will be the termination point for the Verizon SIP Trunk and will use the SIP protocol to setup, manage, and tear down VoIP sessions. The transport protocol used on the Verizon SIP Trunk will be UDP and calls will be processed from the SBC1000/2000 SBC to the IP address and port of the Verizon Sip Trunk proxy server. This information will be provided by Verizon. Calls from the Verizon SIP Trunk proxy server will be sent to the IP address and port (typically 5060) on the SBC1000/2000 SBC. The VoIP codec will be G.711 in nearly all cases between these two end points. SBC1000/2000 SBC to Lync o The SBC1000/2000 SBC will interconnect to the Microsoft Lync environment via the Lync 2010 Mediation Server. The SBC1000/2000 SBC will use the SIP protocol to send calls to the Lync Server IP address and port (typically 5067 or 5068). The Microsoft Lync Mediation Server will use the SIP protocol to send calls to the SBC1000/2000 SBC IP address and port. The VoIP codec will be G.711 in all cases between these two end points. The SBC1000/2000 SBC will perform the UDP to TCP packet conversion between the Verizon SIP Trunk Proxy Server and the Microsoft Lync Server The SBC1000/2000 SBC can provide transcoding should this be a customer requirement. This functionality allows the customer to use the G.711 voice codec on the Microsoft Lync side of the SBC1000/2000 and another supported codec such as G.729 on the Verizon SIP Trunk side of the SBC1000/2000. This is desired in some cases where the IP bandwidth from the customer location to the Verizon IP Sonuswork is extremely limited. Microsoft Lync Server 2010 The customer Microsoft Lync Server 2010 provides Voice communication and Conferencing capabilities. Note that Microsoft Lync also provides Instant Messaging and Presence capabilities but these features are not relevant to the Verizon SIP Trunk Service and this configuration guide. Microsoft Lync Mediation Server 2010 The customer Microsoft Lync Mediation Server 2010 provides a transcoding feature to provide integration between Microsoft Lync clients and the SBC1000/2000 SBC. The Mediation Server is installed as part of the Lync installation and is not covered in this configuration guide. Microsoft Lync Client 2010 The customer Microsoft Lync Client 2010 provides the user interface into Microsoft Lync. The soft phone client allows the user to initiate, process, and terminate VoIP calls to and from other clients as well as the Public Switch Telephone Sonuswork (PSTN) via the Verizon SIP Trunk Service. From the client the user may enter a number to call or select from a list of contacts available through the interface. The Microsoft Lync Client allows provides the ability to Instant Message (IM), determine other client s presence, and initiate s, however these functions are outside the scope of this configuration guide. 9

10 Microsoft Exchange Server 2010 The customer Microsoft Exchange Server provides Voice Mail, Auto Attendant and Subscriber Access capabilities. The SBC1000/2000 SBC does not communicate directly to the Microsoft Exchange Server. The Microsoft Lync Server will process unanswered calls directly to the Microsoft Exchange Server. Aastra 6725ip Lync Hard Phone The Aastra 6725 Lync phone provides a desktop hardphone for the user to send and receive voice calls via the Lync Server. The Aastra works in much the same manor as the Lync Client, providing call features such as hold and transfer and also provides preence updates when the user is in a call with the hard phone. 3.2 Features Supported Virtual Telephone Number Support Calling Name Delivery Calling Number Privacy Call Hold and Resume Voice Mail Call Conference Attended Call Transfer Unattended Call Transfer Call Forward Unconditionally Auto Attendant Subscriber Access DTMF Relay (mid-call digits) Note: Microsoft Lync also provides Instant Messaging and Presence capabilities but these features are not relevant to the Verizon SIP Trunk Service and this Configuration Guide. 4 Verizon SIP Trunk requirements Below is the list of configuration details required from Verizon to complete the SIP Trunk side configuration on the SBC1000/2000 SBC. IP Address and Port for the Verizon SIP Trunk Proxy Server Verification of NAT configuration (If Applicable) o NAT Server IP Addresses Public Side Private Side 10

11 5 Configuration Guide This configuration guide provides a summary of the individual element settings that were used when testing with Verizon s SIP Trunk Service. The Sonuswork administrator configuring these elements should have prior knowledge and experience using each of these devices. Links to additional documentation and training are provided within this Configuration Guide. It is suggested that the Sonuswork administrator review these documents before performing an installation that can impact a live communication Sonuswork. 5.1 Microsoft Lync 2010 Configuration Lync Server 2010 will need to be configured to support the SBC1000/2000 SBC in order to communicate with the Verizon SIP Trunk Service. This section covers the addition of the SBC1000/2000 SBC into the Lync Server topology, adding the SBC1000/2000 SBC to the Lync Server 2010 routing, and configuring Verizon telephone numbers assigned to the Lync user accounts. Note: This section assumes that the Lync Server components have been installed along with Lync users. The user should be familiar with Lync Server Topology Builder, Lync Server Control Panel and Lync Server management Shell. This section does not cover the basic installation of Lync Server Adding PSTN Gateway to Topology The PSTN gateway must first be added to the Microsoft Lync topology using the topology builder tool. The Gateway device will be the interface to the Verizon SIP Trunk. Open Lync Server Topology builder and load the current topology. 11

12 Figure 5.1 Open Lync Topology Builder Select Download Topology From Existing Deployment Figure 5.2 Download Topology Provide a file name and save Lync topology when prompted. 12

13 Figure 5.3 Save Topology Expand the topology and click on the PSTN Gateways link in the left hand pane. Then Click on the link in the right hand pane New IP/PSTN Gateway. Populate the following into the dialog: Gateway FQDN or IP Address: Enter the FQDN of the SBC1000/2000 SBC (Ex. uxsbc.vx.sonus). Listening port for the IP/PSTN gateway: Enter TLS is going to be used between the Lync Server the SBC1000/2000 SBA. SIP Transport Protocol: Ensure the radio button for TLS is selected Once the dialog is complete click OK. 13

14 Figure 5.4 New PSTN Gateway Associate the Mediation Pool to the PSTN Gateway After the PSTN Gateway has been added, the gateway must be associated with the Mediation Pool. Click on the + sign next to the Mediation Pools to expand and the click on the configured Mediation Server. Click on the Edit Properties link in the right hand pane to open the edit dialog as shown below: Click on the gateway FQDN uxsbc.vx.sonus in the none associated gateway table. Once selected click the Add button. 14

15 Figure 5.5 Select Gateway FQDN This will move the uxsbc.vx.sonus FQDN to the bottom table for associated gateways. Click OK to complete the dialog. 15

16 Figure 5.6 Complete Gateway Association Publish Updated Topology Once the PSTN gateway has been added and correctly associated with the Lync Mediation Server, the new topology will need to be published to become active. 16

17 Select the Lync Server 2010 at the top left of the Topology Builder window and click on Publish Topology on the right side. Optionally, the topology can also be published by selecting the Action menu and then selecting Publish Topology. Figure 5.7 Publish Topology Click Next to continue the publishing of the topology. 17

18 Figure 5.8 Publish Topology Continued Once the topology completes the publishing process, click Finish to exit the dialogue box. Figure 5.9 Publish Topology Completion 18

19 5.1.4 Configure Lync Route The Lync route determines which media gateway will be used to pass the call to the PSTN. It can be viewed as a next hop for the call. In order for Lync Server 2010 to send calls to the Verizon SIP Trunk the SBC1000/2000 SBC will have to be added to the Lync routing. Launch the Lync Server Control Panel and provide login credentials if required. Figure 5.10 Open Lync Server Control Panel 19

20 Click on the Voice Routing link on the left hand pane. Click on the Route tab on top of the right hand pane. Once the screen loads, click New to add a new voice route entry. Figure 5.11 Select Voice Routing Complete the name and description fields, then click the add to add the + as the starting digit. 20

21 Name: Provide a name for the route. (ex. Verizon SIP Trunk) Description: Provide an optional description for the route. (Ex. Route to Verizon SIP Trunk) Figure 5.12 Configuring Route 21

22 For the Associated gateways field, click the Add button to select a PSTN Gateway. Figure 5.13 Associate PSTN Gateway with Route 22

23 Ensure the SBC1000/2000 SBC is highlighted in the dialog and click OK. Figure 5.14 Complete Route Configuration At this point Commit all changes to the topology Configure Lync Dial Plan The Lync dial plan controls the association of all the Lync voice components. 23

24 Select Dial Plan in the top right pane. After the screen loads select the New button to add a new dial plan. Figure 5.15 Create New Dial Plan Ensure the correct site is highlighted then click OK 24

25 Figure 5.16 Select Site 25

26 Under the Associated Normalization Rules click New to add a new normalization rule. Figure 5.17 Add 11 Digit Normalization Rule Complete the required fields then click OK. There are 2 screen captures below for this step. 26

27 Name: Provide a name for the rule. (Ex. 11 Digit Dial) Description: Provide an option description. (Ex. Normalize the number to E.164 when the user dials 11 digits) Starting Digits: Provide the starting digit for the rout to match. (Ex. 1; All US Long distance number start with 1) Length: Select the number of digits to match. (Ex. Exactly - 11) Digits to Remove: Leave at the 0 default value. Digits to Add: Leave at the 0 default value. Figure 5.18 Configure 11 Digit Normalization Rule 27

28 Figure 5.19 Configure 11 Digit Normalization Rule Continued 28

29 Under the Associated Normalization Rules click New to add a new normalization rule. Figure 5.20 Add 10 Digit Normalization Rule 29

30 Complete the required fields then click OK. There are 2 screen captures below for this step. Name: Provide a name for the rule. (Ex. 10 Digit Dial) Description: Provide an option description. (Ex. Normalize the number to E.164 when the user dials 10 digits) Starting Digits: Provide the starting digit for the rout to match. Leave blank as default. Length: Select the number of digits to match. (Ex. Exactly - 10) Digits to Remove: Leave at the 0 default value. Digits to Add: Leave at the 0 default value. Figure 5.21 Configure 10 Digit Normalization Rule 30

31 Figure 5.22 Configure 10 Digit Normalization Rule Continued 31

32 After completed the normalization rules, click OK to complete the dial plan configuration. Figure 5.23 Complete Dial Plan Configuration At this point Commit all changes to the topology. 32

33 5.1.6 Configure Lync Voice Policy The Lync Voice Policy associates the site with the route. Select the Voice Policy tab at the top of the right hand pane. Click the New drop down menu and select Site Policy. Figure 5.24 New Site Voice Policy Ensure that the correct site is highlighted and click OK. Figure 5.25 Site Selection 33

34 Select New under PSTN Usage. Figure 5.26 New PSTN Usage for Voice Policy Enter the name for the new PSTN Usage. (Ex. Fremont) Click Select to select an associated route. Figure 5.27 Associate Route with Voice Policy 34

35 Ensure the correct route is selected and click OK Figure 5.28 Select Route for Voice Policy Click OK to accept the new PSTN usage. Figure 5.29 Accept New PSTN Usage 35

36 Click OK to complete the voice policy configuration. Figure 5.30 Complete Voice Policy Configuration At this point Commit all changes to the topology. 36

37 5.1.7 Enable Users for Enterprise Voice In order for Lync users to be called directly from the PSTN, the Lync users will need to have the Verizon telephone numbers assigned to their user account. This is done in the User section of Lync Server Control Panel. Select Users in the right hand pane. Entry the name of the user being enabled for enterprise voice. Click the Find button. Figure 5.31 Ensure the correct user is highlighted, then click the Edit drop down menu and select Show Details. Figure

38 Select the Telephony drop down menu and select Enterprise Voice Figure 5.33 Enter the users telephone number in the Line URI field as an E.164 number. (Ex ) 38

39 Figure 5.34 Click Commit to complete the changes. Complete this task for all users that require enterprise voice via the Verizon SIP Trunk Enable Voice Mail in Exchange UM Exchange UM is the mechanism used by Microsoft Lync for voice mail. The following section provides steps in setting up a the Unified Message (UM) component of the Exchange Server. Note: This document does not cover the installation and configuration of the Microsoft Exchange Server(s). It assumes the server(s) are already functioning in the customer Sonuswork and integration with the Lync Servers has been completed. On the Exchange Server open the Exchange Management Console 39

40 Figure 5.35 Expand the left hand panel configuration tree and select Microsoft Exchange On- Premises/Organization Configuration/Unified Messaging. 40

41 Figure 5.36 On the far right hand pane select New UM Dial Plan 41

42 Populate the fields and click Next Name: Provide a name for the dial plan. (Ex. LyncUsers) Number of digits: Enter the number of digits for the user extensions. (Ex. 4, most common) URI Type: Select the URI type. (Ex. Telephone Extension) VoIP security: Select the type of security between Exchange and Lync. (Ex. SIP Secured) Country/Region code: Enter the country code for the location. (Ex. 1, USA) Figure 5.37 Select Add and ensure the correct Exchange Server is highlighted and click OK 42

43 Figure 5.38 Click New to continue the Dial Plan setup. Figure

44 Click Finish once the setup is complete. Figure

45 On the far right hand pane select New UM IP Gateway Populate the fields and click Browse to select a dial plan. Name: Provide a name for the gateway. (Ex. Lync Server) FQDN: Provide the FQDN of the gateway (Ex. lyncserver.vx.sonus) Figure

46 Ensure the correct dial plan is selected and click OK. Figure 5.42 Click New to continue adding the UM IP Gateway. Figure

47 Click Finish once the setup is complete. Figure

48 The next step is to enable users for Unified Messaging. On the left hand configuration tree select Microsoft Exchange On-Premises/Recipient Configuration/Mailbox. Once the users have loaded select the user who will be enabled for UM. Ensuring the correct user is highlighted, on the far right hand pane select Enable for Unified Messaging. Figure

49 Click Browse to select a UM Mailbox Policy. Figure 5.46 Ensure the correct policy is highlighted and click OK Figure

50 Click Next to continue. Figure 5.48 Click the radio button for Manually-entered mailbox extension and enter the users extension (Ex. 3531) and then click Next. Figure

51 Click Enable to complete the task. Figure 5.50 Once the task has completed click Finish. Figure

52 Perform this step for all users to be enabled for Unified Messaging. 5.2 SONUS SBC1000 / SBC2000 Configuration Configuring the SBC1000/2000 is done through the SBC1000/2000 s integrated web server (WEBUI). Access to the WEBUI is accomplished using one of the following browsers. InterSonus Explorer 8.0 or 9.0 Mozilla Firefox 3.6 or SONUS SBC1000/2000 Prerequisites The following will be required to complete the configuration of the SBC1000/2000 SIP Trunk task: Access to the Certificate Authority to download the root certificate and sign and download the user certificate for the proper TLS operation between the SBC1000/2000 and the Lync 2010 Server(s) FQDN of the Lync 2010 Mediation Server or Server pool IP Address(s) of the Verizon SIP proxy Server IP Address(s) for Private and Public side of NAT if applicable SBC1000/2000 Setup Information o Host Name o IP Domain o IP Address o Sonusmask o DNS IP Address o Default Gateway/Router o Username o Password SBC1000/2000 Initial Configuration The SBC1000/2000 SBC will need to be provided with an initial configuration in order to accessible from the IP Sonuswork. The SBC1000/2000 is shipped with a default IP address that can be accessed via one of the IP Ports. Note: Screen captures are displayed for both the SBC1000 and SBC2000 only in instances in which they vary. 52

53 SBC1000 There are 2 EtherSonus ports on the front of the SBC1000 SBC. Port 1 will be configured during the initial setup of the SBC1000 SBC and will normally be used for the company s internal IP Sonuswork. Port 2 will be used for the interface to the Verizon SIP Trunk Service. The initial configuration will be completed using port 1. Figure 5.52 SBC1000 EtherSonus Ports SBC2000 There are five EtherSonus ports on the front of the SBC2000 SBC. The far left (Admin) port is reserved for administrative use and configuration. The four other ports can be used for normal SIP signalling and media. Port 1 will be configured during the initial setup of the SBC2000 SBC and will normally be used for the company s internal IP Sonuswork. The Admin port will be used for the initial configuration. Figure 5.53 SBC2000 EtherSonus Ports 53

54 Using a PC with a supported web browser, connect an EtherSonus cable between the PC EtherSonus port and the appropriate port on the SBC1000/2000 SBC. Set the IP address on the PC to with a Sonusmask of Figure 5.54 Launch the web browser and connect to the SBC1000/2000 SBC default IP address Once connected you should see the screen below. This screen appears each time until a valid certificate is installed on the SBC1000/2000. Click Continue to this website to continue. 54

55 Figure 5.55 SBC1000/2000 SBC setup screen includes the following details: Host Name: SBC1000/2000 Host Name (Ex. SBC1000/2000SBC) InterSonus Domain Name: Provide the domain for the location. (Ex. vx.sonus) IPv4 Address: Provide the IP Address for the SBC1000/2000 SBC. (Ex ) Sonusmask: Provide the Sonusmask for the SBC1000/2000 SBC IP Address. (Ex ). DHCP Enabled: If SBA present select if to use DHCP. (Ex. No) IPv4 Address: Provide the IP Address for the SBA. (Ex ) Configure Default Route: Seclect Yes to configure a default route. Gateway: Provide the IP Address of the default gateway. (Ex ) Use primary DNS: Select Yes to configure a DNS Server. Primary Server IP: Provide the IP Address of the DNS Server. (Ex ) Use Secondary DNS: Select Yes to configure a secondary DNS Server. Secondary Server IP: Provide the IP Address of the secondary DNS Server. (Ex. N/A) User Name: Provide the user name that will be used to access the SBC1000/2000. (Ex. admin) Enter/Confirm Password: Provide the passowrd that will be used to access the SBC1000/2000. (Ex. admin) Complete all relavent fields for the specific customer siutation and click the ok button to continue. 55

56 Figure 5.56 Click OK to complete initial cofiguration. Figure 5.57 Once the SBC1000/2000 completes the setup configuration, disconnect from the Admin Port and continue the configuration using the assigned IP Address to Port 1. 56

57 5.2.3 SBC1000/2000 SBC Lync 2010 Configuration Steps The Lync 2010 setup is completed via a task configuration tool. This is a step by step process that will complete the configurations to position the SBC1000/2000 between Verizon SIP Trunk and Microsoft s Lync Server This task will install the necessary TLS certificates, create SIP components, and setup basic call routing. Connect to the SBC1000/2000 SBC using a supported web browser. Provide login credentials and click Login. Figure 5.58 Using the web browser navigate to the Tasks tab and click on the Microsoft UC Setup/Lync 2010 Setup link on the left pane. This will start the task to setup the SBC1000/2000 SBC to be configured between the Verizon SIP Trunk and the Lync Server

58 Figure SBC1000/2000 Installation of Root Certificate The page that loads will have 4 sub tabs located in the right configuration pane. Click on the Trusted CAs tab and then the left box with the red up arrow icon. This will prompt for the import of the Root CA Certificate. There are 2 options for the Certificate import method, Copy and Paste and File Upload. The Copy and Paste method is used to import a Certificate in ASCII Base64 format (PEM Privacy Enhanced Mail). To use the Copy and Paste method, first open the certificate file with a text editor such as Microsoft Notepad and then copy and paste into the text box as shown below. The File Upload method is used to import a Certificate in binary file format (DER Distinguished Encoding Rules). Figure

59 Figure 5.61 Importing Root CA Certificate in ASCII Base64 format Figure SBC1000/2000 Requesting Signed Certificate from CA 59

60 Click on the Generate CSR tab. Complete the dialog below with the minimum of the FQDN of the SBC1000/2000 in the Common Name field. Once the dialog is populated click OK. This will create the unsigned ASCII certificate that will have to be submitted to the appropriate Certificate Authority to be signed. This submission process varies per installation. Common Name: Provide the common name for the certificate. (Ex. uxsbc.vx.sonus) Address: Provide a contact address. (Ex. syost@vx.sonus) ISO Country: Select the appropriate country for the location. (Ex. United States) State/Province: Provide the State for the location. (Ex. Arizona) Locality: Provide the Locality for the location. (Ex. Phoenix) Organization: Provide the Organization name. (Ex. VX) Organizational Unit: Provide the Organization Unit. (Ex. Engineering) Key Length: Select the Key Length for the certificate. (Ex bits) Figure

61 Once the certificate request has completed copy and paste the output into a text file to provide to the Certificate Authority for processing. The Certificate Authority will return back to you a signed certificate to import into the SBC1000/2000 SBC. Figure

62 Once the certificate is signed from the Certificate Authority click on the SBC1000/2000 Certificate tab. Click on the green + sign. This will load a dialog similar to the root certificate import process. There are two options for the certificate import method, Copy and Paste and File Upload. Shown below is the Copy and Paste method to import the Certificate in ASCII Base64 format (PEM). Figure

63 Figure 5.66 When the certificate is successfully imported the relevant information will appear on the SBC1000/2000 as shown below. 63

64 Valid SBC1000/2000 Certificate Figure SBC1000/2000 SIP Signaling Endpoints Click on the last tab Lync 2010 Setup to configure the SIP Endpoints in SBC1000/2000. This process will setup the SBC1000/2000 to interface to the Verizon SIP Trunk and the Lync 2010 Server(s). The task will configure the SIP server tables and the SIP signaling groups associated with each entity along with the basic routing between each endpoint. Scenario Description: Provide a description that will associate to the setup of the SIP Trunk. Gateway Scenario: Select from the dropdown SIP Trunking No of Channels: Provide the total number of simultaneous calls you have purchased from Verizon. Server Pool Host: The FQDN of the Server or Server pool that the SBC1000/2000 will communicate with. Port Number: The IP Port that the Lync Server or Server pool listens on for SIP messages from the SBC1000/2000. Border Element Server: IP or FQDN Address of the Verizon SIP Proxy Server (Border Element) that the SBC1000/2000 will communicate with. 64

65 Protocol: Select from the dropdown UDP. Port Number: The IP Port that the Verizon SIP Proxy (Border Element) listens on for SIP messages from the SBC1000/2000. Use Secondary Border Element Server: Select Enabled from the dropdown if a secondary Verizon SIP Proxy (Border Element) will be configured. Secondary Border Element Server: IP or FQDN Address of the secondary Verizon SIP Proxy (Border Element) that the SBC1000/2000 will communicate with. Protocol: Select from the dropdown UDP. Port Number: The IP Port that the secondary Verizon SIP Proxy (Border Element) listens on for SIP messages from the SBC1000/2000. Once the page has been configured click Apply to finish the dialog. Figure 5.68 When the configuration is complete the following screen will appear. 65

66 Figure SBC1000/2000 Configuring Transformation Tables Transformation tables are used to modify the called and calling party information elements among other elements that are pertinent to proper call handling between the origination and destination servers. The basic transformations rely on the use of Regular Expressions as the numbers/names are changed from what is received to what is sent to the destination. Transformation tables can be configured as Optional or Mandatory to provide maximum flexibility in modification of signalling elements. The default routing on the SBC1000/2000 SBA is setup to pass through all calls between Microsoft Lync and the Verizon SIP Trunk. The following steps will adjust the manner in which called and calling numbers are handled in the SBC1000/2000 SBA. The following steps will provide the required number translations to integrate Microsoft Lync with the Verizon SIP Trunk. The Verizon SIP Trunk will typically provide a 10 digit called number to the SBC1000/2000 SBC. This number needs a +1 added to it in order to create the E.164 format that is used by Microsoft Lync. The same process will be completed on the Caller ID that is provided by the Verizon SIP Trunk. Microsoft Lync will provide an E.164 formatted number for both the called number and the Caller ID. The +1 needs to be removed from both these numbers then sent to the Verizon SIP Trunk 66

67 Under the Settings tab select Transformation in the right hand pane. Click the green + in the left hand pane to add a new transformation table. Figure 5.70 Enter the description for the new transformation table and click OK. (Ex. Lync to Verizon SIP Trunk) Figure

68 Under the Settings tab select Transformation in the right hand pane. Click the green + in the left hand pane to add a new transformation table. Figure 5.72 Enter the description for the new transformation table and click OK. (Ex. Verizon SIP Trunk to Lync) Figure

69 Once the new transformation tables are added, the line items need to be added with the number translations. Under the Settings tab select Transformation/Verizon SIP Trunk to Lync. Then click the green + to add a new entry. Figure

70 Populate the fields in the translation table entry and click OK. Description: Provide a description for the entry. (Ex. Add +1 to Called Number) Admin State: Determines if the entry will be active. (Ex. Enabled) Match Type: Determines if the entry must match in order to process the call. (Ex. Mandatory) Input Field Type: Identifies the number the SBC1000/2000 SBC will use to match this entry. (Ex. Called Address/Number) Value: RegEx entry for the number the SBC1000/2000 will be attempting to match. (Ex. (.*), match anything) Output Field Type: Identifies the number the SBC1000/2000 SBC will populate on the outbound call. (Ex. Called Address/Number) Value: RegEx entry for the number the SBC1000/2000 will populate on the outbound call. (Ex. +1\1, add the +1 to the call and include after that everything in brackets from the input field value) Figure

71 Under the Settings tab select Transformation/Verizon SIP Trunk to Lync. Then click the green + to add a new entry. Figure

72 Populate the fields in the translation table entry and click OK. Description: Provide a description for the entry. (Ex. Add +1 to Calling Number) Admin State: Determines if the entry will be active. (Ex. Enabled) Match Type: Determines if the entry must match in order to process the call. (Ex. Mandatory) Input Field Type: Identifies the number the SBC1000/2000 SBC will use to match this entry. (Ex. Calling Address/Number) Value: RegEx entry for the number the SBC1000/2000 will be attempting to match. (Ex. (.*), match anything) Output Field Type: Identifies the number the SBC1000/2000 SBC will populate on the outbound call. (Ex. Calling Address/Number) Value: RegEx entry for the number the SBC1000/2000 will populate on the outbound call. (Ex. +1\1, add the +1 to the call and include after that everything in brackets from the input field value) Figure

73 Completed view of the Verizon SIP Trunk to Microsoft Lync transformation table. Figure 5.78 Under the Settings tab select Transformation/Lync to Verizon SIP Trunk. Then click the green + to add a new entry. Figure

74 Populate the fields in the translation table entry and click OK. Description: Provide a description for the entry. (Ex. Pass Through Diversion Header) Admin State: Determines if the entry will be active. (Ex. Enabled) Match Type: Determines if the entry must match in order to process the call. (Ex. Mandatory) Input Field Type: Identifies the number the SBC1000/2000 SBC will use to match this entry. (Ex. Redirecting Number Type) Value: The Type of number that the SBC1000/2000 SBC will be attempting to match. (Ex. Any/Untranslated), match any type) Output Field Type: Identifies the number the SBC1000/2000 SBC will populate on the outbound call. (Ex. Redirecting Number Type) Value: The Type of number that the SBC1000/2000 SBC will populate on the outbound call. (Ex. H.323 ID or SIP. Figure

75 Under the Settings tab select Transformation/Lync to Verizon SIP Trunk. Then click the green + to add a new entry. Figure

76 Populate the fields in the translation table entry and click OK. Description: Provide a description for the entry. (Ex. Remove +1 from Diversion Header) Admin State: Determines if the entry will be active. (Ex. Enabled) Match Type: Determines if the entry must match in order to process the call. (Ex. Optional) Input Field Type: Identifies the number the SBC1000/2000 SBC will use to match this entry. (Ex. Redirecting Number) Value: RegEx entry for the number the SBC1000/2000 will be attempting to match. (Ex. \+1(.*), match +1 and any follow on digits) Output Field Type: Identifies the number the SBC1000/2000 SBC will populate on the outbound call. (Ex. Redirecting Number) Value: RegEx entry for the number the SBC1000/2000 will populate on the outbound call. (Ex. \1, include after that everything in brackets from the input field value) Figure

77 Under the Settings tab select Transformation/Lync to Verizon SIP Trunk. Then click the green + to add a new entry. Figure

78 Populate the fields in the translation table entry and click OK. Description: Provide a description for the entry. (Ex. Remove +1 from Called Number) Admin State: Determines if the entry will be active. (Ex. Enabled) Match Type: Determines if the entry must match in order to process the call. (Ex. Mandatory) Input Field Type: Identifies the number the SBC1000/2000 SBC will use to match this entry. (Ex. Called Address/Number) Value: RegEx entry for the number the SBC1000/2000 will be attempting to match. (Ex. \+1(.*), match +1 and any follow on digits) Output Field Type: Identifies the number the SBC1000/2000 SBC will populate on the outbound call. (Ex. Called Address/Number) Value: RegEx entry for the number the SBC1000/2000 will populate on the outbound call. (Ex. \1, include after that everything in brackets from the input field value) Figure

79 Under the Settings tab select Transformation/Lync to Verizon SIP Trunk. Then click the green + to add a new entry. Figure 5.85 Populate the fields in the translation table entry and click OK. Description: Provide a description for the entry. (Ex. Remove +1 from Calling Number) Admin State: Determines if the entry will be active. (Ex. Enabled) 79

80 Match Type: Determines if the entry must match in order to process the call. (Ex. Mandatory) Input Field Type: Identifies the number the SBC1000/2000 SBC will use to match this entry. (Ex. Calling Address/Number) Value: RegEx entry for the number the SBC1000/2000 will be attempting to match. (Ex. \+1(.*), match +1 and any follow on digits) Output Field Type: Identifies the number the SBC1000/2000 SBC will populate on the outbound call. (Ex. Calling Address/Number) Value: RegEx entry for the number the SBC1000/2000 will populate on the outbound call. (Ex. \1, include after that everything in brackets from the input field value) Figure

81 Completed view of the Microsoft Lync to Verizon SIP Trunk transformation table. Figure

82 5.2.5 Call Route Table Configurations The call route tables need to be updated to use the transformation tables created in the previous step. The follow steps provide details on making these changes. Under the Settings tab select the Call Routing Table/to Mediation Server route table. Click on the symbol to expand the entry in the right hand pane. Figure

83 Make the following changes and then click apply. (There are 2 screen captures for this step) Number/Name Transformation Table: Select the newly created Verizon SIP Trunk to Lync table via the drop down menu. Figure 5.89 Figure

84 Under the Settings tab select the Call Routing Table/to BE Server route table. Click on the symbol to expand the entry in the right hand pane. Figure

85 Make the following changes and then click apply. (There are 2 screen captures for this step) Number/Name Transformation Table: Select the newly created Lync to Verizon SIP Trunk table via the drop down menu. Figure 5.92 Figure

86 5.2.6 SBC1000/2000 Configuring SIP Server Tables The Verizon SIP Trunk will send calls to IP port 5060 on the SBC1000/2000 SBC. By default the SBC1000/2000 SBC set the listening port for the Verizon SIP Trunk to 5070, which is the IP Port that the SIP Trunk is listening on. The Signalling Group in the SBC1000/2000 SBC for the Verizon SIP Trunk needs to be updated to listen on port Under the Settings tab select Signaling Groups/SBC1000/2000 Border Element. Scroll to the bottom of the right hand pane and under the Listening Ports section check the box next to the 5070 port entry. Click on the red X to delete this entry. Figure

87 Once the entry is deleted click on the green + to add new SIP Listen Port Entry. Figure

88 Populate the fields with the new port information and click Apply Protocol: Enter the protocol via expected for SIP messages. (Ex. UDP, always UDP from Verizon SIP Trunk. Port: Enter the IP Listening port for SIP messages. (Ex. 5060) Figure

89 Click on Apply again in the bottom right corner to complete the SIP Signaling Group configuration. Figure

90 5.3 Alternate Configuration Options Configuring SBC1000/2000 to Force Transcoding to G.729 Lync 2010 does not support G.729. To save bandwidth, the SBC1000/2000 can be configured to Transcode all calls going over the link to Verizon SIP Trunk Service to G.729. This Transcoding is configured by removing the G.711 Codec from the Media List used within the Signaling Group facing Verizon. An example of the modified Media List is show below. Under the Settings tab select Media/Media Profiles. Click Add Voice Code Profile Figure

91 Populate the new codec profile fields and click OK. Description: Provide a description for this profile. (Ex. G.729) Codec: Select the codec for this profile. (Ex. G.729) Payload Size: Leave at the 20ms default. Figure

92 Under the Settings tab select Media/Media List/UC Media List, Highlight the existing Media Profile Lists one at a time and click Remove, remove the current G.711 entries. Figure Click Add to add a the new G.729 Media Profile created in the previous step. Figure

93 Select the G.729 Codec Profile and click Apply. Figure Scroll to the bottom of the right hand pane can click Apply to complete the media list change. Figure

94 5.3.2 Using TCP instead of TLS between SBC1000/2000 and Lync The Microsoft Lync Planning and Deployment Guides indicate All qualified gateways must support TLS, but can enable TCP as well. TCP is supported for gateways that do not support TLS. By default the SBC1000/2000 SBC Setup Wizard will use TLS (Transport Layer Security) with Microsoft Lync Server The following steps can be used to configure the SBC1000/2000 and Lync to use TCP (Transmission Control Protocol) instead of TLS. Lync Modifications In the Lync Server Topology Builder, change the SIP Transport Protocol to TCP as shown below. Expand the topology and select the PSTN Gateway (Ex.uxsbc.vx.Sonus) and click on Edit Properties in the far right pane. Figure

95 Populate the required fields and click OK. Listening Port: Change the listening port to the default port preferred by link for TCP port SIP Transport Protocol: Select the Radio button for TCP. Figure Publish the Topology as directed in Section Note: It may be necessary to reboot the Lync Server for the changes to become effective. 95

96 SBC1000/2000 Modifications Under the Settings tab select SIP/SIP Server Tables/Mediation Servers. Populate the fields listed below and click Apply Port: Enter the IP Port to use when sending SIP Calls to Lync (Ex. 5068, matching the Lync Server settings) Protocol: Enter the protocol to use when sending SIP Calls to Lync (Ex. TCP, matching the Lync Server settings) Figure

97 Under the Settings tab select Signaling Groups/UC Mediation Change the Media list option to the UC Media List. (No Crypto) Figure Scroll to the bottom of the right pane. Under the Listen Ports section, click the check box next to the port 5067 entry. Click the red X to remove the entry. Once removed click the green + to add the new listen port. Figure

98 Populate the fields with the new port information and click Apply Protocol: Enter the protocol via expected for SIP messages. (Ex. TCP) Port: Enter the IP Listening port for SIP messages. (Ex. 5068) Figure

99 Click Apply again at the bottom right of the right hand pane to complete the Signaling Group changes. Figure Under the Settings tab select Call Routing Table/to Mediation Server. Under the Media section change the Media List to the UC Media List (No Crypto) and click Apply Figure

100 6 SBC1000/2000 Troubleshooting The SBC1000/2000 provides various ways to troubleshoot call issues. The first is through visual analysis of configured systems and active and certain archived alarms through the Monitor page. And the SBC1000/2000 can generate debug logs to be viewed locally, downloaded to a text editor or the debug logs can be sent to a Syslog collector. 6.1 Visual Analysis Clicking on the Monitor tab will bring up a real time view of the current status of the configured Signalling Groups and their associated channels; including a real-time view of call status. If a Signalling Group is down the Signalling Group will be coloured Red as shown below for the Verizon Signalling Group. There are many reasons a Signalling Group may be down. The far end equipment may be off line, there could be a routing issue or there could be a configuration problem. The visual Monitor will provide a quick view on where to start trouble shooting. The current alarms will be shown in the Alarm View at the bottom of the screen. These alarms may also indicate problems which should be investigated. 100

101 Figure Viewing SBC2000 Debug Logs In order to gather information for the Debug logs, the required subsystem(s) need to be configured to send data to the debug log file. Under the Settings tab select Logging Configuration/Subsystems. Click the green + to add a new entry. 101

102 Figure 6.2 Populate the following fields and click OK. Subsystem Name: Select the subsystem required for troubleshooting (Ex. SIP Stack Service) Log Level: Select the desired log level. (Ex. Debug) Log Destination: Select the destination to send debug data. (Ex. Local Logs) Figure 6.3 Add additional subsystems as required for troubleshooting. The SBC2000 will continually record the last hour and 15 minutes of debug logs. These are split into 15 minute logs and can be viewed by clicking on the Logs tab as shown below: 102

103 Figure 6.4 The logs are ordered with the current log being written on top. When the current log reaches the end of the recording period it will be rotated down from the top and a new log will start to write. To view one of these logs click the blue box to the left of the file name. This will open a web based text box that can be scrolled through to find certain debug information. To download the log to either save or open in a text editor, click on the Download link to the right of the file information. This will open a dialog to either save to a file or open. Note: The SBC1000 does not locally create debug logs. The SBC1000 and SBC2000 can be configured to send debug information to a Syslog server as shown in the next section. 6.3 Sending SBC1000/2000 Debug Logs to a Syslog Collector Under the Settings tab select Logging Configuration/Remote Log Servers. Click the green + to add a new entry. 103

104 Figure 6.5 Populate the following fields and click OK. Global Log Level: Set the default log level for the information sent to the log server.(ex. Warning, this is the default) Log Destination: Enter the IP address for the destination to send data. (Ex ) Log Facility: Select the Facility to send the data.(ex. Local0, this is the default) Enabled: Select Yes to enable the entry and begin sending data to the log server Figure 6.6 In order to gather information for the log server, the required subsystem(s) need to be configured to send data to the debug log file. 104

105 Under the Settings tab select Logging Configuration/Subsystems. Click the green + to add a new entry. Figure 6.7 Populate the following fields and click OK. Subsystem Name: Select the subsystem required for troubleshooting (Ex. SIP Stack Service) Log Level: Select the desired log level. (Ex. Debug) 105

106 Log Destination: Select the destination to send debug data. (Ex. Remote Log: ) Figure 6.8 Add additional subsystems as required for troubleshooting. 7 Verifying Software Version on the SBC1000/2000 SBC Perform the following steps to verify the software version on the SBC1000/2000 SBC. 106

107 Connect to the SBC1000/2000 SBC using a supported web browser. Provide login credentials and click Login. Figure 7.1 The software version and build number are provided under the Overview tab. This screen also provides the SBC1000/2000 SBC. 107

108 Figure Upgrading SBC1000/2000 SBC Software The follow steps will be performed to update the software version on the SBC1000/2000 SBC. Note: Navigating away from a screen while an upgrade is in progress will cause the upgrade to stop. Downloading new software SBC1000/2000 SBC software can be downloaded by a registered user via the Website. Updating SBC1000/2000 Communications Service *Only performed on a SBC1000/2000 SBC with and ASM (SBA) module. 108

109 Connect to the SBC1000/2000 SBC using a supported web browser. Provide login credentials and click Login. Figure 8.1 Under the Task tab select Application Solution Module/Install ASM Update. Then click the Browse button. Figure

110 Locate and select the Setup.msi file for the SBC1000/2000 communications service. Click Open. Figure 8.3 Once the correct file is selected, click OK to start the update. Figure

111 Click OK to confirm the update. Figure 8.5 The current activity stats dialogue box will advise when the update is complete. Figure

112 Upgrading the SBC1000/2000 SBC Software Under the Task tab select System/Firmware Upgrade. Click on the Browse button. Figure 8.7 Locate and select the SBC1000/2000 SBC upgrade file. Note: The SBC2000 and the SBC1000 have specific upgrade files. Ensure the correct file is used for the SBC1000/2000 SBC being upgraded. Figure

113 Once the correct file is selected, click OK to start the upgrade. Figure 8.9 Click OK to confirm the upgrade. Figure

114 When the upgrade process has completed the SBC1000/2000 SBC will reboot and return to the login screen. Figure Support Information For support on any of the components identified in this configuration guide, follow the appropriate links in the table below. 9.1 SONUS Documentation and Support Information The following sections outline accessing documentation, training and support information for the SBC1000/2000 SBC Documentation The latest SBC1000/2000 documentation can be accessed via the SONUS support portal. The SBC1000/2000 documentation suite consists of a User s Guide, Installation Guide and Upgrade 114

115 Guide. It is suggested that the Sonuswork administrator installing the SBC1000/2000 be familiar with these documents. The documentation can be viewed online or downloaded as a PDF file. Web site: Figure SONUS SBC1000/2000 Product Training The SONUS. training services group offers cost-effective, educational programs that teach you how to install, administer, and use SBC1000/2000 products. For more Informational about SBC1000/2000 training, send to technical_training@sonus.com SONUS SBC1000/2000 Technical Assistance If there is a problem installing or using SONUS products, call the SONUS Technical Assistance Center (TAC) at the following numbers: For North America, call For International collect calls, use