TELUS SIP Trunk Configuration Guide

Interactive Intelligence

CIC 2016 R1 Patch5Configuration Guide
over MPLS

March 2016

Performed By

tekVizion PVS, Inc.

Contact: 214-242-5900

Copyright © 2016 by tekVizion PVS, Inc.

All Rights Reserved.

Confidential Information

The information contained in this document is confidential and proprietary to tekVizion PVS, Inc. Its purpose is to communicate the overall strategy of an Interoperability Test Plan used by tekVizion Labs.

This document is the property of, and is proprietary to tekVizion. It is not to be disclosed in whole or in part without the express written authorization of tekVizion, shall not be duplicated or used, in whole or in part, for any purpose other than to evaluate the proposed scope of testing under contemplation.

TEKVIZION, TEKVIZION PVS, AND TEKVIZION LABS ARE TRADEMARKS OF TEKVIZION PVS, INC.

Document Revision History

Version / Reason for Change / Date / Created/Updated by
1.0 / Initial Draft / 2/29/2016 / Pradeep Gali
1.1 / Customer requested revision and document proofing / 3/23/2016 / Rachel Jerome

Table of Contents

1Introduction

2Validation Environment

2.1Network Topology

2.2Hardware Components

2.3Software Requirements

2.4TELUS Equipment

2.5Features

2.5.1Features Supported

2.5.2Features Not Supported

3Summary of Test Results

3.1Declaration

3.1.1Purpose

3.2Passed

3.3Not Tested / Not Supported

3.4Known Limitations and Restrictions

3.5Test Plan

4CIC Server Trunk Configuration

4.1Trunk (Line) Configuration

4.1.1Set Server IP Address

4.1.2Line Configuration

4.1.3Line Groups

4.1.4Dial Plan Configuration

5Outbound call with Restricted Caller ID

5.1Procedure to add Privacy Header

6Allow UPDATE from Carrier

Table of Figures

Figure 1: Network Topology

Figure 2: Server IP Address

Figure 3: Line Configuration

Figure 4: Lines Configuration – Cont.

Figure 5: Line Configuration – Cont.

Figure 6: Line Configuration – Cont.

Figure 7: Line Configuration – Identity (In)

Figure 8: Line Configuration – Identity (Out)

Figure 9: Line Configuration - Identity (Out) – Cont.

Figure 10: Line Configuration - Identity (Out) - Cont.

Figure 11: Line Configuration – Audio

Figure 12: Line Configuration - Transport

Figure 13: Line Configuration - Transport – Cont.

Figure 14: Line Configuration - Session

Figure 15: Line Configuration - Authentication

Figure 16: Line Configuration - Proxy

Figure 17: Line Configuration – Registrar

Figure 18: Line Configuration - Headers

Figure 19: Line Configuration – Access

Figure 20: Line Configuration - Region

Figure 21: Line Configuration - Recorder

Figure 22: Line Configuration – Call Putback

Figure 23: Line Configuration – Custom Attributes

Figure 24: Line Groups

Figure 25: Line Groups - Cont.

Figure 26: Line Groups - Members

Figure 27: Dial Plan

Figure 28: Privacy Header

Figure 29: Privacy Header - Cont.

Figure 30: Privacy Header - Cont.

Figure 31: Allow UPDATE

Figure 32: Allow UPDATE - Cont.

Figure 33: Allow UPDATE – Cont.

1Introduction

This configuration guide describes how to configure an ININ CIC 2016 R1 SERVERwith a TELUSIP Trunk. The deployment model covered in this application note is an ININ CIC 2016 R1 SERVER witha TELUSIP Trunkconnected to the PSTN.

The configuration of the ININ CIC 2016 R1 SERVER detailed in this document is based on a lab environment with a simple dial-plan used to ensure proper interoperability between the TELUSIP Trunk and the PSTN network. Testing with TELUS BVOIP and Wireless service were not included in this test plan and will be covered in different document. Please use the TELUS provided configuration guide for configuring TELUS IP Trunking R2 services.

Testing was performed by tekVizion Labs, an independent testing and certification facility, in accordance to ININ Certification Test Plan. Key features verified are:

•New services install processes

•Call capabilities (various features, basic call operations, local calling, domestic long distance calling and international calling)

•FAX

•Out-of-band DTMF

•Conference Calls

The configuration described in this document details the critical commands to have enabled for interoperability to be successful.

This Application Note details the configuration used for connectivity to the tekVizion PSTN network. This document serves as guidance for the integration, but does not guarantee interoperability for every use case or release combinations.

2Validation Environment

2.1Network Topology

Figure 1: Network Topology

2.2Hardware Components

  • ININ CIC Media Server
  • ININ CIC2016Servers
  • Polycom IP 550 and IP 650 Phones

2.3Software Requirements

  • ININ CIC 2016 Release1 Patch5

2.4TELUS Equipment

  • Oracle AP6300 Session Border Controller 7.2
  • Genband EXPERiUS Application Server MCP-17.0.22.15
  • Genband C20 Call Session Controller CVM17

2.5Features

2.5.1Features Supported

  • Voice calls using G.711 codec
  • RFC 3261 support
  • Calling number presentation / restriction
  • Call conferencing
  • Call transfer (attended,unattended & blind transfer)
  • Call hold and resume
  • Call forwarding
  • CIC Server Switchover

2.5.2Features Not Supported

  • Multiple Ports: TELUSdoes not support Multiple Ports
  • TCP SIP Messaging: TCP SIP can be supported by TELUS, but this is not the usual way TELUS is configured
  • WAN Phones: TELUS does not support provisioning the WAN phones

3Summary of Test Results

3.1Declaration

tekVizion has tested the ININ CIC 2016 R1 Patch5 with the TELUSIP Trunk and has certified its use as Service Provider.

3.1.1Purpose

This document serves to provide other areas of ININ CIC 2016 R1 Patch5 Certification test review of the TELUSIP Trunk. Uses of this product outside that of public voice call termination/origination to the TELUSIP Trunk host falls outside the scope of this certification.

3.2Passed

All test cases that were executed have been marked as ‘Pass’

3.3Not Tested / Not Supported

The following test cases were marked as ‘Not Supported’

# / TC# / Title / Results / Notes
34 / 6113 / Multiple Ports / N/S / TELUS does not support Multiple Ports on UDP
36 / 6115 / Support for TCP SIP Messaging / N/S / TCP SIP can be supported by TELUS, but this is not usual way TELUS is configured
40 / FS-1422 / WAN Phones Setup / N/S / TELUS does not support provisioning the WAN phones

3.4Known Limitations and Restrictions

  • None identified

3.5Test Plan

  • Device Under Test (DUT) –TELUSIP Trunk
  • DUT - Customer Interface Type - IP TRUNK
  • WAN Transport – MPLS VPN Connectivity

# / TC# / Title / Results
1 / 4906 / Configure SIP Carrier to Route Calls to IC / Pass
2 / 11403 / Configure SIP Carrier Line / Pass
3 / 11402 / Configure & Provision Managed IP Phones / Pass
4 / 11406 / Configure Dial Plan for Outgoing Calls / Pass
5 / 11411 / Out-of-band DTMF / Pass
6 / 11416 / G.711 Through Carrier / Pass
7 / 4898 / Inbound call with ANI / Pass
8 / 4899 / Inbound Call without ANI / Pass
9 / 4900 / Outbound Call with ANI / Pass
10 / 8700 / Early Media / Pass / Call made to Early media number "9725980147" to test early media call. Can hear the announcement from Carrier before the call was answered.
11 / 5553 / Transfer - Blind (Internal) / Pass
12 / 4877 / Transfer – Consult (Internal) / Pass
13 / 4878 / Transfer – Blind (External) / Pass / Made configuration change in IC Server to send PAI instead of DIVERSION Header in forwarded INVITE as per Carrier’s Requirement
14 / 4879 / Transfer – Consult (External) / Pass
# / TC# / Title / Results
15 / 4884 / Hold Support – Re-Invite to 0.0.0.0 / Pass / No Re-INVITE from IC Server when placed the call on Hold. MOH is sent in RTP
16 / 4885 / Forward Incoming Call - from Carrier to Carrier / Pass / Made configuration change in IC Server to send PAI instead of DIVERSION Header in forwarded INVITE as per Carrier’s Requirement
17 / 4886 / 3 Party Conference / Pass / Even after the 1st user client disconnects the call, the other 2 legs are still in the call
18 / 4887 / Fax - G.711 Pass-through / Pass / 10 out of 10 inbound and outbound FAX calls are successful
19 / 14094 / Always In Audio / Pass
20 / 4908 / Service Unavailable – 503 response from carrier / Pass / Made changes in DUT to generate 503 response
21 / 4915 / Power Failure / N/A / Not Applicable for SIP Trunk Testing
22 / 14127 / Switchover Support / Pass
23 / 14128 / WAN Failure / Pass / Deleted the VPN credentials and added again
24 / 14311 / Latency SIP Outbound / Pass / Latency is measured as 190ms
25 / 14150 / Outbound Call with RESTRICTED ANI / Pass
26 / 4880 / Putback (Release Link) Transfer (Blind) / Pass
27 / 4881 / Putback (Release Link) Transfer (Consult) / Pass
28 / 4888 / Fax - T.38 (Inbound) / Pass / 10 out of 10 FAX calls are successful
29 / 4889 / Fax - T.38 (Outbound) / Pass / 10 out of 10 FAX calls are successful
30 / 4890 / Dynamic Audio / Pass
31 / 4894 / SIP Authentication Support / N/T / SIP authentication cannot be tested with the current VPN setup with TELUS
# / TC# / Title / Results
32 / 6001 / QoS tagging of RTP is preserved / N/A / Not Applicable for SIP Trunk Testing
33 / 6002 / QoS tagging of SIP Signaling is preserved / N/A / Not Applicable for SIP Trunk Testing
Optional Test Cases –FS 1259
34 / 6113 / Multiple Ports / N/S / TELUS does not support Multiple Ports on UDP
35 / 6114 / SIP to SIP call support / Pass
36 / 6115 / Support for TCP SIP Messaging / N/S / TCP can only be supported by TELUS only when configured the trunk to TLC
37 / 6655 / Support for sRTP / N/A / Not Applicable for SIP Trunk Testing
38 / 6722 / Support for TLS / N/A / Not Applicable for SIP Trunk Testing
WAN Managed Phone Test Cases – FS 1422
# / TC# / Title / Results / Notes
40 / 14179 / Provision WAN Managed Phone / N/S / No Supported by TELUS
41 / 14183 / WAN Phone Intercom Calls / N/S / No Supported by TELUS
42 / 14184 / WAN Phone External Calls / N/S / No Supported by TELUS
43 / 14185 / WAN Phone Transfer (Blind) / N/S / No Supported by TELUS
44 / 14186 / WAN Phone Transfer (Consult) / N/S / No Supported by TELUS
45 / 14187 / WAN Phone Conference / N/S / No Supported by TELUS
46 / 14188 / WAN Phone Switchover / N/S / No Supported by TELUS

4CIC Server Trunk Configuration

4.1Trunk (Line)Configuration

4.1.1Set Server IP Address

  1. Navigate Start > Control Panel > Network and Internet > View Network Status and Tasks>Change Adapter Settings > Ethernet> Ethernet Status > Properties > Internet Protocol Version 4(TCP/IP4) > Properties
  2. Use the Following IP Address: Selected
  3. Set IP Address: Enter the IP address assigned for the ININ CIC 2016 server. 10.70.65.2 is used in this example.
  4. Set Subnet Mask: 255.255.255.0 is given for this example
  5. Set Default Gateway: 10.70.65.1 is used for this example
  6. Set Preferred DNS Server: 10.85.0.12 is used for this example. The computer is placed in this domain for this example.
  7. Set Alternate DNS Server: 10.85.0.232 is used for this example. This is the DNS server for Enterprise network.
  8. Click OK

Figure 2: Server IP Address

4.1.2Line Configuration

  1. In Interaction Administrator: Navigate to INISERVER1(Name of IC Server) – 2016 R1Lines
  2. Right Click on Lines and click New
  3. Set Line Name: TELUS is given for this example

Figure 3: Line Configuration

4.1.2.1Line
  1. Select theSIP Line Configurationtab
  2. In left navigation pane, select Line
  3. Set Line Usage: General Purpose is selected from the drop down menu
  4. Set Domain Name: Enterthe FQDN of the server provided at the domain controller. INISERVER1.tekvizionlabs.com is given for this example.
  5. Set Fax Protocol: T38 then T30 were selected for this example
  6. Check Enable Fax Detection. It supports both Fax Protocols T38 & T30. This can be changed based on the carrier requirement.
  7. All the other values are set to default values

Figure 4: Lines Configuration–Cont.

Figure 5: Line Configuration –Cont.

Figure 6: Line Configuration–Cont.

4.1.2.2Identity (In)
  1. In left navigation pane, click Identity (In)
  2. All the values are set to default values as shown in the figure below

Figure 7: Line Configuration –Identity (In)

4.1.2.3Identity (Out)
  1. In left navigation pane, selectIdentity (Out)
  2. Set Line Value 1
  3. Set Name: TELUS is given for this example
  4. Set Address: Enter the pilot number of the DID range assigned by ITSP
  5. Click OK
  6. All the other values are set to default values as shown in the figures below

Figure 8: Line Configuration–Identity (Out)

Figure 9: Line Configuration - Identity (Out)–Cont.

TELUS network expects to have P-Asserted-Identity(PAI) in any INVITE going out from IC server. By default, IC server sends Diversion header for call forward all and Blind transfer calls. Below are the changes required to send the PAI instead of diversion header.

  1. Set ‘P-Asserted-Identity’ Address: Use diverted valueis selected from the drop down menu
  2. Set ‘P-Asserted-Identity’ Name: Use diverted value
  3. Set Diverted Header Address: None
  4. Click Apply

Figure 10: Line Configuration - Identity (Out) - Cont.

4.1.2.4Audio
  1. In left navigation pane, select Audio
  2. Set Audio Path: Always Inis selected from the dropdown menu. This disables the Media Bypass.
  3. Set DTMF Type: RFC2833 if supported, otherwise inband
  4. Set DTMF Payload: 101 is selected for this example
  5. All the values are set to default values as shown in the figure below

Figure 11: Line Configuration –Audio

4.1.2.5Transport
  1. In left navigation pane, selectTransport
  2. All the values are set to default values as shown in the figures below

Figure 12: Line Configuration - Transport

Figure 13: Line Configuration - Transport–Cont.

4.1.2.6Session
  1. In left navigation pane, selectSession
  2. All the values are set to default values as shown in the figure below

Figure 14: Line Configuration -Session

4.1.2.7Authentication
  1. In left navigation pane, selectAuthentication
  2. All the values are set to default values as shown in the figure below

Figure 15: Line Configuration -Authentication

4.1.2.8Proxy
  1. In left navigation pane, selectProxy
  2. Click Add
  3. Set Address: Enter the Address of the next hop (i.e. TELUS SIP Trunk LAN IP Address)
  4. Set Port Number: 5060 is given for this example
  5. Click OK

Figure 16: Line Configuration -Proxy

4.1.2.9Registrar
  1. In left navigation pane, selectRegistrar
  2. All the values are set to default values as shown in the figure below

Figure 17: Line Configuration–Registrar

4.1.2.10Headers
  1. In left navigation pane, selectHeaders
  2. All the values are set to default values as shown in the figure below

Figure 18: Line Configuration -Headers

4.1.2.11Access
  1. In left navigation pane, selectAccess
  2. Under All Computers will be:Check Denied Access
  3. Click Add
  4. Set Address: Enter the Address of the next hop (i.e. TELUS SIP Trunk IP Address)

Figure 19: Line Configuration–Access

4.1.2.12Region
  1. In left navigation pane, selectRegion
  2. All the values are set to default values as shown in the figure below

Figure 20: Line Configuration - Region

4.1.2.13Recorder
  1. In left navigation pane, selectRecorder
  2. All the values are set to default values as shown in the figure below

Figure 21: Line Configuration - Recorder

4.1.2.14Call Putback
4.1.2.14.1Sending SIP REFER Messages Disabled
  1. Select theCall Putback tab
  2. Enable sending SIP REFER messages is unchecked for Internal (Blind & Consultative) Transfers as per Test cases

Figure 22: Line Configuration–Call Putback

4.1.2.15CustomAttributes
  1. Select theCustom Attributes tab
  2. All the values are set to default values as shown in the figure below

Figure 23: Line Configuration–Custom Attributes

4.1.3Line Groups

  1. Navigate to Line Groups
  2. Right Click and select New
  3. Set Enter the Group Name: TELUS Group is given for this example
  4. Click OK

Figure 24: Line Groups

4.1.3.1Line Group Configuration

  1. Use for Reporting: Checked
  2. Use as Dial Group: Checked
  3. Under Hunt Selection Method: Select Descending Sequential
  4. Click Apply

Figure 25: Line Groups -Cont.

4.1.3.2Members

  1. Select theMembers tab
  2. From Available Lines: Select TELUSand Click Add
  3. The TELUS Line should be moved to “Currently Selected Lines” as shown below
  4. Click Apply

Figure 26: Line Groups -Members

4.1.4Dial Plan Configuration

  1. Navigate to system Configuration > Phone numbers > Configuration
  2. Under Regional Dial Plan: Click Dial Plan
  3. To route the 10 digit outbound call out from IC Server to Carrier, the Dial plan needs to be configured as shown below. To use this dial plan, dial the access code (9) followed by PSTN number.
  4. Click Add Group and add the Line Group added in Section 4.1.3

Figure 27: Dial Plan

5Outbound call with Restricted Caller ID

  1. To Make an outbound call with restricted caller ID to PSTN, “Privacy Header” needs to be added in the in the initial INVITE going out from IC Server
  2. To add privacy header to the line, a new line and a new line group needs to be created using the same configuration steps from Section 4.1.2 and Section 4.1.3
  3. Configure the dial plan with a new access code (8) and add the line group to access the Line with Privacy ID

5.1Procedure to add Privacy Header

  1. In IC server, navigate toStart > Run > dsedit.exe
  2. In dsedit, navigate to your CustomerSite > IC Server using > Lines
  3. Select the line configured for Restricted Caller ID
  4. Navigate to Attribute Add Attribute

Figure 28: Privacy Header

  1. To add the Privacy Header, two attributes need to be added as shown in the figure below
  • Billing Header: Privacy
  • Billing Account Number: id

Figure 29: Privacy Header - Cont.

Figure 30: Privacy Header - Cont.

6Allow UPDATE from Carrier

By default IC server block the “UPDATE” packets coming from the carrier. To allow “UPDATE” packets coming from the carrier, a server parameter needs to be added.

  1. In left navigation pane, select Server Parameters
  2. Right-click on any of the parameters as shown below and click New

Figure 31: Allow UPDATE

  1. Set EnterParameter Name: AllowUpdateInd
  2. Click OK

Figure 32: Allow UPDATE - Cont.

  1. Set Parameter Value: True
  2. Click Apply

Figure 33: Allow UPDATE– Cont.

Page 1 of 32

TEKVIZION PVS, INC. CONFIDENTIAL