Siemens OpenScape Voice V7 SIP Connectivity with OpenScape SBC V7. to Integra SIP Service

Transcription

1 Siemens OpenScape Voice V7 SIP Connectivity with OpenScape SBC V7 to Integra SIP Service February 2013 Page 1 of 47

2 Document History Date Version / Issue Modified by Section(s) Affected High-Level Description Page 2 of 47

3 Table of Contents 1 Introduction OpenScape Voice Components Overview Capabilities Overview Siemens OpenScape Voice V5 / OpenScape SBC V1 - Integra Interoperability Test Results Tested Features and Capabilities Other Features and Capabilities Possible Issues and Limitations Tested SW Versions Configuration Guide Generate Route to the SBC Defining an EndPoint Profile Defining the OpenScape SBC Endpoint Create a Destination and Route Fail Over Timers Define the Call Routing Define Prefix Access Code Define Destination Code Create a Subscriber and enable the Subscriber Features Define a Subscriber Feature Profile Create Subscribers and assign a Feature Profile Configure the OpenScape SBC Creating a Service Provider Profile Creating a Remote Endpoint (of type SSP for SIP Service Provider) Configure Xpressions SIP settings Set IPApl SIP Streaming for G.729 and G Mediatrix 4102S Terminal Adapter Configuration Endpoint Configuration and Notes Troubleshooting Verify the Loaded SW Levels Verify Active Alarms and Alarm Log Network Verification Verify IP Addresses and Ports Capture SIP traffic between OpenScape Voice/SBC and SIP end-point Verify payload (RTP) Traffic Verify Call Detail Records Service / Support Contact Information Integra Contact Information... Error! Bookmark not defined. 8.2 Siemens Contact Information Siemens Level 1 Support Siemens Level 2 Support Page 3 of 47

4 1 Introduction This document highlights the capabilities of the Siemens OpenScape Voice V7 VoIP solution, and also describes the necessary steps to configure the system to connect to and to be used in conjunction with the Integra Telecom SIP Trunking service. The Siemens OpenScape Voice solution is comprised of various components. The core system is comprised of the OpenScape Voice Application Server, a Media Server for the delivery of tones and announcements, a Session Border Controller, and SIP endpoints. Additional capabilities and applications such as PSTN gateways, Unified Messaging, Contact Center, Accounting/Billing, User Management, etc., could be optionally incorporated to a customers deployment. This guide focuses on the relevant capabilities of the OpenScape Voice V7 and OpenScape SBC V7 platforms which interface/interact with the Integra s SIP Trunking service. The interface between the OpenScape Voice V7 solution is IP-based, and uses standard IETF SIP as the call control protocol and RTP as the protocol that transports the voice payload. In case of any questions or issues not covered in this guide please contact your local Integra or Siemens Service organization (See chapter 8 Service / Support Contact Information). Page 4 of 47

5 2 OpenScape Voice Components Overview The overview below depicts a typical OpenScape Voice deployment and its connections to the Integra Telecom SIP Trunking Service. Customer PSTN PSTN subscriber SIP Service Provider OpenScape Voice Subscriber PSTN Provider PSTN Gateway Customer LAN Provider SIP DMZ Openscape Voice SBC Internet Provider SIP Server The OpenScape Voice solution includes the following components: 1. OpenScape Voice Communication Server 2. OpenScape Voice Assistant Management 3. OpenScape Media Server 4. SIP End-Points 5. OpenScape Unified Messaging Application 6. OpenScape Session Border Controller Page 5 of 47

6 Optionally, a customer may also deploy various applications such as unified messaging, voice mail, presence manager, etc. 1. OpenScape Voice Communication Server The OpenScape Voice is the core of the solution. The OpenScape Voice is the registrar and the SIP server for the SIP end-points. The OpenScape Voice provides the functions, translations, and routing between the SIP end-points and the rest of the solution components such as the Media Server, Gateways (PSTN gateways or IP/IP gateways such as SBCs), Unified Messaging / Voic , and other applications. The OpenScape Voice only handles call control / signaling. Voice payloads are not directly handled by the OpenScape Voice; they are exchanged directly by the end-points or via the SBC. The OpenScape Voice provides a standard (IETF-based) SIP interface to the Integra SIP Trunking Service. 2. OpenScape Voice Assistant Management The OpenScape Voice Assistant Management provides the web based user interface to manage and configure the OpenScape Voice solution. 3. OpenScape Media Server The OpenScape Media Server provides tones, announcements and conference capabilities. 4. SIP End Points The SIP End Points are the end-user interface like SIP-phones, SIP-Soft-Client, and SIP- Terminal Adapters for analog fax machines, etc. 5. OpenScape Unified Messaging Application The OpenScape Unified Messaging server provides various UM features like Voice Mail capabilities, Presence Manager, Auto Attendant capabilities, fax server capabilities, etc. 6. OpenScape SBC OpenScape SBC delivers VoIP security and cost savings to OpenScape Voice customers. Designed specifically to address security and interoperability issues of SIP-based VoIP traffic, OpenScape SBC is architected for SIP trunking termination from multiple Service Providers, makes teleworker and contact center home agent deployment scenarios easy and cost-effective, and delivers secure connectivity from the enterprise data center to branch locations and hosted voice applications. Page 6 of 47

7 3 Capabilities Overview The OpenScape Voice, in conjunction with the other solution components (i.e. phones, gateways, application servers, etc.), can provide numerous capabilities and features to users. A complete listing of the features available with the OpenScape Voice solution is outside the scope of this document. However, a comprehensive list of features and capabilities can be found in the OpenScape Voice Feature Description Guide, which is provided to all customers. The interoperability tests of the OpenScape Voice with the Integra SIP Trunking Service are focused on features and capabilities that are relevant to the interaction between the two networks as used in the customer environment. 4 Siemens OpenScape Voice V5 / OpenScape SBC V1 Integra Interoperability Test Results 4.1 Tested Features and Capabilities The following list provides an overview of the capabilities that are supported by the OpenScape Voice solution and which have been confirmed to properly work with the Integra SIP service. PSTN Outbound Service (Hop Off) Calls from the CPE hosted by the OpenScape Voice through the Integra SIP serviceto the PSTN were tested. This included Local calls, as well as National and International LD calls. Toll Free calls were also tested and confirmed. Outbound service supports voice band calls using G.711 or G.729, as well as Fax calls using T.38 and G.711. PSTN Inbound Service (Hop On) Inbound voice calls from the PSTN to the OpenScape Voice, the CPE, were tested successfully using G.711 and G.729 compression. Fax transmissions from the PSTN were successfully tested using T.38 and G.711. Basic Inbound/Outbound Service (to/from Customer IP Trunk) Inbound/Outbound voice calls from OpenScape Voice to OpenScape Voice via the Integra network were tested successfully using G.729 and G.711. Fax transmissions to/from the OpenScape Voice were successfully tested using T.38 and G.711. Page 7 of 47

8 Features and Services The features that were tested in conjunction with the Integra SIP network are as follows: - G.729 Codec Support - G.711 Codec Support - RFC2833 DTMF Support - Calling Name Delivery - Calling Number Delivery - Calling Number Privacy - Three-Party conference - Attended Transfer - Unattended Transfer - Call Hold - Voice Mail - Call Forwarding (unconditional, no answer, busy) - Fax calling (T.38 and G.711) using G3 and super G3 devices - IP PBX 7-digit, N11 and international dialing & translation The OpenScape Voice solution supports many more features and services; this list includes the features that interact with the Integra SIP service and were included in the OpenScape Voice / SBC testing. Refer to the OpenScape Voice documentation for a description of all the available features. Page 8 of 47

9 4.2 Other Features and Capabilities The following lists shows OpenScape Voice capabilities that were tested using other external Siemens OpenScape voice servers CPE Voice Mail System An OpenScape Voice server does not include a voice mail system but supports various external voice mail systems like the Siemens OpenScape Xpressions/Unified Messaging. No interoperability issues were encountered related to voice mail system integration with the OpenScape Voice and the Integra SIP service. CPE based Meet-Me Conference An OpenScape Voice server does not include a meet-me conference system but support various external conference systems like the Siemens OpenScape Unified Communications. No interoperability issues were encountered related to conference system integration with the OpenScape Voice and Integra SIP service. Auto Attendant An OpenScape Voice server does not include an Auto Attendant system but supports various Auto Attendant systems like the Siemens Xpressions server or OpenScape Branch Auto Attendant. No interoperability issues were encountered related to Auto Attendant system integration with the OpenScape Voice and the Integra SIP service. 4.3 Possible Issues and Limitations 5 Tested SW Versions To ensure the Interoperability between the components at the customer premise (OpenScape Voice and SIP End Points) and the Integra SIP service with the PSTN- Gateways, the OpenScape Voice and OpenScape SBC should be on the SW level indicated below: OpenScape Voice:... V7 OpenScape SBC:... V7 The following components and SW levels were used during the OpenScape Voice V7 / SBC V7 Integra SIP service Inter-Operability tests: Siemens OpenStage 40 Phones:... V3 R Page 9 of 47

10 Mediatrix 4124 Terminal Adapter : V OpenScape Xpressions:... V6 Page 10 of 47

11 6 Configuration Guide The configuration of the OpenScape Voice is done through the web based Assistant. Following steps have to be taken to define and configure the Integra connectivity of an OpenScape Voice system: Generate Route to the Session Border Controller Defining an EndPoint Profile Defining the SBC EndPoint Create a Destination and Route Define Prefix Access Code Define Destination Enable End Point Features Define an End Point Profile Create Subscriber and assign End Point Profile Page 11 of 47

12 6.1 Generate Route to the SBC The OpenScape SBC is configured as an end point in the OpenScape Voice system Defining an EndPoint Profile Page 12 of 47

13 General Endpoint Parameters: Page 13 of 47

14 Endpoint Services: Page 14 of 47

15 6.1.2 Defining the OpenScape SBC Endpoint Define a SIP EndPoint for the Intrega IP trunk via the OpenScape SBC. In the example below the EndPoint to-att-via-csbc points to the SBC element. General Endpoint Parameters: Page 15 of 47

16 Endpoint SIP parameters: Page 16 of 47

17 Endpoint/Gateway Attributes: Page 17 of 47

18 Endpoint/Gateway Aliases: Add the IPaddress:IPport of the Endpoint as an Alias. Page 18 of 47

19 Page 19 of 47

20 6.1.3 Create a Destination and Route Define a destination to the Integra SIP service: Page 20 of 47

21 Define a route for the primary Integra border elements: Page 21 of 47

22 ! Number of digits to delete is set to Fail Over Timers Adjust the following Rerouting parameters if necessary: Srx/Sip/ReroutingTimerInvite The value for TimerInvite number of INVITE re-transmissions before rerouting default = 3 Srx/Sip/ReroutingTimerTrying The value for TimerTrying is the number of T1 timeouts before rerouting default = 30 Page 22 of 47

23 Page 23 of 47

24 6.2 Define the Call Routing Define Prefix Access Code The Prefix Access Code in this example is 9 (access code to the Integra network). Page 24 of 47

25 Page 25 of 47

26 6.2.2 Define Destination Code This example defines a Destination Code of 9 (national calls through the Integra network). Page 26 of 47

27 Page 27 of 47

28 6.3 Create a Subscriber and enable the Subscriber Features Define a Subscriber Feature Profile The subscriber features can be enabled / disabled through the Services tab in the Subscriber configuration or, To enable / disable features for multiple subscribers the features can be enabled / disabled in the subscriber Feature Profile. Page 28 of 47

29 Add / Remove the required features under Features : Note: Refer to the Configuration Documentation for a detailed description of all the parameters. Page 29 of 47

30 6.3.2 Create Subscribers and assign a Feature Profile Create the Subscriber: Page 30 of 47

31 Assign the Subscriber Feature Profile: Page 31 of 47

32 6.4 Configure the OpenScape SBC The following steps have to be taken to define and configure the Integra connectivity on the OpenScape SBC: Defining a Service Provider Profile for Integra Defining a Remote Endpoint that represents the Integra SIP Trunk This task can be accomplished via the Common Management Portal (CMP) interface (see below) or via the OpenScape SBC local GUI interface Creating a Service Provider Profile Page 32 of 47

33 Page 33 of 47

34 Page 34 of 47

35 6.4.2 Creating a Remote Endpoint (of type SSP for SIP Service Provider) Page 35 of 47

36 Page 36 of 47

37 6.5 Configure Xpressions SIP settings Set IPApl SIP Streaming for G.729 and G.711 Page 37 of 47

38 6.6 Mediatrix 4124 Terminal Adapter Configuration To ensure interoperability for fax calls between the Mediatrix 4124 Terminal Adapter and the Integra environment, the following parameters have to be set accordingly in addition to the regular Terminal Adapter configuration: The Unit Manager part: The T38 encoding should be set to itut38annexd Page 38 of 47

39 The Mediatrix web interface part: Enable/Disable T38 and/or G711 (hit edit for advanced setting)! Disable the VAD Page 39 of 47

40 T38 - advanced setting Page 40 of 47

41 Page 41 of 47

42 6.7 Endpoint Configuration and Notes Some calls during the testing of various endpoints were configured with a G.711 codec as first preference (as required in some test cases). However, most interoperability testing between OpenScape Voice/OpenScape SBC and Integra SIP service were performed using G.729 as the first preference. This is configurable in the endpoint/cpe. In order to use G.729 make sure that your endpoints are configured with G.729 as the first preference for the codec as shown below: All calls to the Xpressions voice mail used G.729 or G.711 for the testing performed. The Xpressions system can be configured to use either G.711 or G.729ab specifically. However, when both codecs are enabled Xpressions will use the codec with the higher voice quality. Page 42 of 47

43 7 Troubleshooting The following steps can be taken should any troubleshooting be required. 7.1 Verify the Loaded SW Levels See chapter Tested SW Versions for the SW levels that were tested to work with the Integra SIP Trunking service. 7.2 Verify Active Alarms and Alarm Log Verify the Active Alarms and the Alarm Log under Operation & Maintenance / Diagnostics. Contact Siemens Support in case of any severe Alarms. 7.3 Network Verification Verify that the end points (SIP phones, Endpoints, and IP Trunk) have connection to each other and IP packets are routed correctly. Page 43 of 47

44 7.4 Verify IP Addresses and Ports Verify that all IP addresses and Ports in the OpenScape Voice, OpenScape SBC and SIP end points are correct. 7.5 Capture SIP traffic between OpenScape Voice/SBC and SIP endpoint Capture the SIP traffic between the OpenScape Voice / OpenScape SBC and the involved SIP end points. Provide any suspicious captures to Siemens Support or Integra Telecom Support. 7.6 Verify payload (RTP) Traffic Capture the RTP/RTCP (& T38 exchange if applicable) traffic between the OpenScape Voice / OpenScape SBC and the involved SIP end points. Verify that IP traffic is routable between the SIP end points and the relevant servers. 7.7 Verify Call Detail Records Consult the Call Detail Records (CDRs). The CDRs can contain information related to unsuccessful call attempts. Page 44 of 47

45 8 Service / Support Contact Information 8.1 Integra SIP Support In case of any issues or questions with the Integra SIP Trunking service contact Integra Telecom support. Integra Telecom Support: (801) Siemens Contact Information In case of any issues or questions related to the Siemens components contact either the Siemens 1 st level support or open a ticket with the 2 nd level support according to your service contract Siemens Level 1 Support As the first-level customer interface, the Level 1 organization handles all customer support requests including performing remote service diagnostics and service repair, executing moves, adds, changes (MAC) activity on customer systems, providing consultation support, escalating potential product defects to the GCS center, providing vendor coordination support, and dispatching a customer request to the field offices. Siemens Level 1 Support: Siemens Level 2 Support The Technical Support Level 2 Center organization located in Irving, TX provides secondlevel support for all Siemens and Siemens Business Partner products. Siemens Level 2 Support: (automated system to open a trouble ticket) Prior to calling, please have the following information: Your security code CMR number of the site - You will only be prompted for this if needed Your callback number Page 45 of 47

46 This Customer Configuration Guide ("CCG") is offered as a convenience to Siemens and Integra customers. The specifications and information regarding the product in this CCG are subject to change without notice. All statements, information, and recommendations in this CCG are believed to be accurate but are presented without warranty of any kind, express or implied, and are provided AS IS. Users must take full responsibility for the application of the specifications and information in this CCG. In no event shall Siemens Enterprise Communications or its suppliers be liable for any indirect, special, consequential, or incidental damages, including, without limitation, lost profits or loss or damage arising out of the use or inability to use this Customer Configuration Guide. Page 46 of 47

47 End of Customer Configuration Guide Document Page 47 of 47