-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
1 of 38
CTL-IPO101
Avaya Solution & Interoperability Test Lab
Application Notes for Configuring Centurylink SIP Trunk
Service with Avaya IP Office Release 10.1 using UDP/RTP -
Issue 1.0
Abstract
These Application Notes describe the procedures for configuring
Session Initiation Protocol
(SIP) Trunking between service provider Centurylink and Avaya IP
Office Release 10.1.
Centurylink SIP Trunk Service provides PSTN access via a SIP
trunk between the enterprise
and the Centurylink network as an alternative to legacy analog
or digital trunks. This approach
generally results in lower cost for the enterprise.
Readers should pay attention to Section 2, in particular the
scope of testing as outlined in
Section 2.1 as well as the observations noted in Section 2.2, to
ensure that their own use cases
are adequately covered by this scope and results.
Information in these Application Notes has been obtained through
DevConnect compliance
testing and additional technical discussions. Testing was
conducted via the DevConnect
Program at the Avaya Solution and Interoperability Test Lab.
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
2 of 38
CTL-IPO101
1. Introduction These Application Notes describe the procedures
for configuring Session Initiation Protocol (SIP)
Trunking between Centurylink and the Avaya IP Office solution.
In the sample configuration, the
Avaya IP Office solution consists Avaya IP Office 500 V2 Release
10.1, Avaya embedded
Voicemail, Avaya IP Office Application Server (with WebRTC and
one-X Portal services enabled),
Avaya Communicator for Windows (SIP mode), Avaya Communicator
for Web, Avaya H.323,
Avaya SIP, digital and analog endpoints. The enterprise solution
connects to the Centurylink
network.
The Centurylink referenced within these Application Notes is
designed for business customers. The
service enables local and long distance PSTN calling via
standards-based SIP trunks as an alternative
to legacy analog or digital trunks, without the need for
additional TDM enterprise gateways and the
associated maintenance costs.
2. General Test Approach and Test Results The general test
approach was to configure a simulated enterprise site using Avaya
IP Office
connecting to Centurylink.
This configuration (shown in Figure 1) was used to exercise the
features and functionality tests
listed in Section 2.1. Note: NAT devices added between Avaya IP
Office and the Centurylink
network should be transparent to the SIP signaling.
DevConnect Compliance Testing is conducted jointly by Avaya and
DevConnect members. The
jointly-defined test plan focuses on exercising APIs and/or
standards-based interfaces pertinent to
the interoperability of the tested products and their
functionalities. DevConnect Compliance Testing
is not intended to substitute full product performance or
feature testing performed by DevConnect
members, nor is it to be construed as an endorsement by Avaya of
the suitability or completeness of
a DevConnect member’s solution.
Avaya recommends our customers implement Avaya solutions using
appropriate security and
encryption capabilities enabled by our products. The testing
referenced in this DevConnect
Application Note included the enablement of supported encryption
capabilities in the Avaya
products. Readers should consult the appropriate Avaya product
documentation for further
information regarding security and encryption capabilities
supported by those Avaya products.
Support for these security and encryption capabilities in any
non-Avaya solution component is the
responsibility of each individual vendor. Readers should consult
the appropriate vendor-supplied
product documentation for more information regarding those
products.
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
3 of 38
CTL-IPO101
2.1. Interoperability Compliance Testing
A simulated enterprise site with Avaya IP Office was connected
to Centurylink. To verify SIP
trunking interoperability, the following features and
functionality were exercised during the
interoperability compliance test:
• Incoming PSTN calls to various phone types. Phone types
included Avaya H.323, Avaya SIP, digital, and analog telephones at
the enterprise. All inbound PSTN calls were routed to
the enterprise across the SIP trunk from the service
provider
• Outgoing PSTN calls from various phone types. Phone types
included Avaya H.323, Avaya SIP, digital, and analog telephones at
the enterprise. All outbound PSTN calls were routed
from the enterprise across the SIP trunk to the service
provider
• Inbound and outbound PSTN calls from/to the Avaya Communicator
for Windows (SIP mode)
• Inbound and outbound PSTN calls from/to the Avaya Communicator
for Web with basic telephony transfer feature
• Inbound and outbound long hold time call stability
• Various call types including: local; long distance; outbound
toll-free; local directory assistance 411; and emergency call 911
during the compliance testing
• SIP transport using UDP as supported by Centurylink
• Codec G.711A, G.711MU
• Caller number/ID presentation
• Privacy requests (i.e., caller anonymity) and Caller ID
restriction for inbound and outbound calls
• DTMF transmission using RFC 2833
• Voicemail navigation for inbound and outbound calls
• Telephony features such as hold and resume, transfer, and
conference
• Fax T.38 and G.711 pass-through modes
• Use Diversion header in off-net call forwarding
• Use SIP re-Invite and REFER in off-net call transfer
• Twinning to mobile phones on inbound calls
• Registration and Authentication
Item not supported by Centurylink LAB environment include the
following:
• TLS/SRTP
• Outbound call to Assisted Operator
• Inbound Toll- Free
• Outbound to International Call
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
4 of 38
CTL-IPO101
2.2. Test Results
Interoperability testing of Centurylink was completed with
successful results for all test cases with
the exception of the observation described below:
• CenturyLink does not support REFER for call forward:
CenturyLink supports REFER for call transfers to the PSTN, but does
not support REFER for call forward to the PSTN. The
call scenario in which CenturyLink does not support REFER is for
inbound calls from the
PSTN to Avaya IP Office which are then forwarded to another PSTN
endpoint. In this
scenario, if REFER is enabled, CenturyLink does not returns a
202 Accepted message as a
response to the REFER message sent by IP Office, causing IP
Office to send several REFER
messages to CenturyLink, the call eventually drops. This issue
was solved by enabling “No
REFER if using Diversion” on the IP Office SIP Line (See Section
5.6.2 - SIP advanced
configuration), which resulted in IP Office sending REFER during
call transfers to the PSTN
and not send it during call forwards to the PSTN.
• Disable Error Correction Mode (ECM) for T.38 fax: CenturyLink
does not support ECM for T.38; however, CenturyLink sets the ECM
bit in the facsimile control field describing its
capabilities in the T.30 signaling. Thus for interoperability,
ECM should be disabled on
Avaya IP Office so the resulting call will negotiate to not use
ECM (See Section 5.6.2 - T38
Fax configuration).
• SIP endpoints may indicate that a transfer failed even when it
is successful: Occasionally on performing a transfer operation,
Avaya IP Office SIP endpoints (Avaya 1100 Series
Deskphone and Avaya Communicator for Windows) may indicate on
the local call display
that the transfer failed even though it was successful. The
frequency of this behavior can be
reduced by enabling “Emulate Notify for REFER” on the IP Office
SIP Line (See Section
5.6.2 - SIP advanced configuration).
• SIP OPTION Messages: During the compliance test, CenturyLink
did not send SIP OPTION messages to IP Office, IP Office did send
SIP OPTION messages to CenturyLink, this was
sufficient to keep the SIP trunk up.
2.3. Support
For technical support on the Avaya products described in these
Application Notes visit:
http://support.avaya.com
For technical support on Centurylink SIP Trunking, contact
Centurylink at
http://www.centurylink.com
http://support.avaya.com/http://www.centurylink.com/
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
5 of 38
CTL-IPO101
3. Reference Configuration Figure 1 below illustrates the test
configuration. The test configuration shows an enterprise site
connected to Centurylink through the public IP network. For
confidentiality and privacy purposes,
actual public IP addresses used in this testing have been masked
out and replaced with fictitious IP
addresses throughout the document.
The Avaya components used to create the simulated customer site
included:
• Avaya IP Office 500 V2
• Avaya embedded Voicemail for IP Office
• Avaya Application Server (Enabled WebRTC and one-X Portal
services)
• Avaya 9600 Series IP Deskphones (H.323)
• Avaya 11x0 Series IP Deskphones (SIP)
• Avaya 1408 Digital phone
• Avaya Analog phone
• Avaya Communicator for Windows (SIP)
• Avaya Communicator for Web
Located at the enterprise site is an Avaya IP Office 500 V2 with
the MOD DGTL STA16 expansion
module which provides connections for 16 digital stations to the
PSTN, and the extension PHONE 8
card which provides connections for 8 analog stations to the
PSTN as well as 64-channel VCM
(Voice Compression Module) for supporting VoIP codecs. The
voicemail service is embedded on
Avaya IP Office. Endpoints include Avaya 9600 Series IP
Telephone (with H.323 firmware), Avaya
1100 Series IP Telephone (with SIP firmware), Avaya 1408D
Digital Telephone, Avaya Analog
Telephone, and Avaya Communicator for Windows. The LAN1 port of
Avaya IP Office is
connected to the enterprise LAN (private network) while the LAN2
port is connected to the public
network.
A separate Windows 10 Enterprise PC runs Avaya IP Office Manager
to configure and administer
the Avaya IP Office system.
Mobility Twinning is configured for some of the Avaya IP Office
users so that calls to these user’s
phones will also ring and can be answered at configured mobile
phones.
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
6 of 38
CTL-IPO101
Internet PSTN
DevConnect Test LAB
Enterprise site
Avaya IP Office 500 V2
Embedded Voicemail
Avaya 9600
Series IP
Deskphones
(H.323)
Analog
Phone
Digital
Phone
Digital Phone
10.10.98.X
Centurylink
Network
Oracle 6300 SBC/
Broadsoft Broadworks
FAX
FAX
Service Provider
10.10.97.X
IP Office
Manager
Mobile
twining
with Cell
.40
.14
.33
.1
.33
.44Avaya 1140E
IP Deskphone
(SIP)Avaya
Communicator
for Windows
(SIP)
Signaling Server IP address:
192.168.66.81
DID numbers: 4695557020,
4695557022, 4695557023
IP Office
Application
Server
Figure 1 - Test Configuration for Avaya IP Office with
Centurylink SIP Trunk Service
For the purposes of the compliance test, Avaya IP Office users
dialed a short code of 6 + N digits to
send digits across the SIP trunk to Centurylink. The short code
of 6 was stripped off by Avaya IP
Office but the remaining N digits were sent unaltered to the
Centurylink system. For calls within the
North American Numbering Plan (NANP), the user would dial 11 (1
+ 10) digits. Thus for these
NANP calls, Avaya IP Office would send 11 digits in the Request
URI and the To field of an
outbound SIP INVITE message. It was configured to send 10 digits
in the From field. For inbound
calls, Centurylink sent 10 digits in the Request URI and the To
field of inbound SIP INVITE
messages.
In an actual customer configuration, the enterprise site may
also include additional network
components between the service provider and the Avaya IP Office
such as a session border
controller or data firewall. A complete discussion of the
configuration of these devices is beyond the
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
7 of 38
CTL-IPO101
scope of these Application Notes. However, it should be noted
that SIP and RTP traffic between the
service provider and the Avaya IP Office must be allowed to pass
through these devices.
4. Equipment and Software Validated The following equipment and
software/firmware were used for the sample configuration
provided:
Avaya Telephony Components
Equipment Release
Avaya IP Office solution
Avaya IP Office 500V2 Embedded Voicemail Avaya Web RTC Gateway
Avaya one-X Portal Avaya IP Office Manager Avaya IP Office Analogue
PHONE 8 Avaya IP Office VCM64/PRID U Avaya IP Office DIG DCPx16
V2
10.1.0.0.0 build 237
10.1.0.0.0 build 237
10.1.0.0.0 build 237
10.1.0.0.0 build 305
10.1.0.0.0 build 237
10.1.0.0.0 build 237
10.1.0.0.0 build 237
10.1.0.0.0 build 237
Avaya 1140E IP Deskphone (SIP) 04.04.23
Avaya 9641G IP Deskphone 6.6.4.01
Avaya 9621G IP Deskphone 6.6.4.01
Avaya Communicator for Windows (SIP) 2.1.4.0 - 256
Avaya Communicator for Web 1.0.16.1718
Avaya 1408D Digital Deskphone R46
Avaya Analog Deskphone N/A
HP Officejet 4500 (fax) N/A
Centurylink Components
Equipment Release
Broadsoft BroadWorks
R21 service pack 1
Oracle 6300 SBC
SCZ7.3.0 MR-1 Patch 1
Note: Compliance Testing is applicable when the tested solution
is deployed with a standalone IP
Office 500V2 and also when deployed with IP Office Server
Edition in all configurations.
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
8 of 38
CTL-IPO101
5. Configure Avaya IP Office Solution This section describes the
Avaya IP Office solution configuration necessary to support
connectivity
to Centurylink. It is assumed that the initial installation and
provisioning of the Avaya IP Office
500V2 has been previously completed and therefore is not covered
in these Application Notes. For
information on these installation tasks refer to Additional
References Section 9.
This section describes the Avaya IP Office configuration
required to support connectivity to the
Centurylink. Avaya IP Office is configured through the Avaya IP
Office Manager PC application.
From a PC running the Avaya IP Office Manager application,
select Start Programs IP
Office Manager to launch the application. Navigate to File Open
Configuration, select the
proper Avaya IP Office system from the pop-up window and click
OK button. Log in using
appropriate credentials.
Figure 2 – Avaya IP Office Selection
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
9 of 38
CTL-IPO101
5.1. Licensing
The configuration and features described in these Application
Notes require the Avaya IP Office
system to be licensed appropriately. If a desired feature is not
enabled or there is insufficient
capacity, contact an authorized Avaya sales representative.
To verify that there is a SIP Trunk Channels license with
sufficient capacity, select IPOffice_1
License on the Navigation pane and SIP Trunk Channels in the
Group pane. Confirm that there is a
valid license with sufficient “Instances” (trunk channels) in
the Details pane.
Figure 3 – Avaya IP Office License
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
10 of 38
CTL-IPO101
5.2. System Tab
Navigate to System (1) under IPOffice_1 on the left pane and
select the System tab in the Details
pane. The Name field can be used to enter a descriptive name for
the system. In the reference
configuration, IPOffice_1 was used as the name in IP Office.
Figure 4 - Avaya IP Office System Configuration
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
11 of 38
CTL-IPO101
5.3. LAN2 Settings
In the sample configuration, LAN2 is used to connect the
enterprise network to Centurylink.
Note: The LAN1 port of Avaya IP Office connected to the
enterprise LAN (private network) is not
described in this document.
To configure the LAN2 settings on the IP Office, complete the
following steps. Navigate to
IPOffice_1 System (1) in the Navigation and Group panes and then
navigate to the LAN2
LAN Settings tab in the Details pane. Set the IP Address field
to the IP address assigned to the
Avaya IP Office LAN2 port. Set the IP Mask field to the mask
used on the private network. All
other parameters should be set according to customer
requirements. Click OK to submit the change.
Figure 5 - Avaya IP Office LAN2 Settings
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
12 of 38
CTL-IPO101
The VoIP tab as shown in the screenshot below was configured
with following settings:
• Check the SIP Trunks Enable to enable the configuration of SIP
Trunk connecting to Centurylink
• Verify Keepalives to select Scope as RTP-RTCP with Periodic
timeout 60 and select Initial keepalives as Enabled
• All other parameters should be set according to customer
requirements
• Click OK to submit the changes
Figure 6 - Avaya IP Office LAN2 VoIP
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
13 of 38
CTL-IPO101
5.4. System Telephony Settings
Navigate to IPOffice_1 System (1) in the Navigation and Group
Panes (not shown) and then
navigate to the Telephony Telephony tab in the Details pane.
Choose the Companding Law
typical for the enterprise location. For North America, U-Law is
used. Uncheck the Inhibit Off-
Switch Forward/Transfer box to allow call forwarding and call
transfers to the PSTN via the
service provider across the SIP trunk. Set Hold Timeout (sec) to
a valid number. Set Default Name
Priority to Favor Trunk. Defaults were used for all other
settings. Click OK to submit the changes.
Figure 7 - Avaya IP Office Telephony
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
14 of 38
CTL-IPO101
5.5. System VoIP Settings
Navigate to IPOffice_1 System (1) in the Navigation and Group
Panes and then navigate to the
VoIP tab in the Details pane. Leave the RFC2833 Default Payload
as default of 101. Select codec
G.729(a) 8K CS-ACELP, G.711 ULAW 64K which Centurylink supports.
Click OK to submit the
changes.
Figure 8 - Avaya IP Office VoIP
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
15 of 38
CTL-IPO101
5.6. Administer SIP Line
A SIP Line is needed to establish the SIP connection between
Avaya IP Office and Centurylink. The
recommended method for configuring a SIP Line is to use the
template associated with these
Application Notes. The template is an .xml file that can be used
by Avaya IP Office Manager to
create a SIP Line. Follow the steps in Section 5.6.1 to create
the SIP Line from the template.
Some items relevant to a specific customer environment are not
included in the template or may
need to be updated after the SIP Line is created. Examples
include the following:
• IP addresses
• SIP Credentials (if applicable)
• SIP URI entries
• Setting of the Use Network Topology Info field on the
Transport tab.
Therefore, it is important that the SIP Line configuration be
reviewed and updated if necessary after
the SIP Line is created via the template. The resulting SIP Line
data can be verified against the
manual configuration shown in Section 5.6.2.
Also, the following SIP Line settings are not supported on Basic
Edition:
• SIP Line – Originator number for forwarded and twinning
calls
• Transport – Second Explicit DNS Server
• SIP Credentials – Registration Required
• SIP Advanced Engineering.
Alternatively, a SIP Line can be created manually. To do so,
right-click Line in the Navigation Pane
and select New SIP Line. Then, follow the steps outlined in
Section 5.6.2.
For the compliance test, SIP Line 17 was used as trunk for both
outgoing and incoming calls.
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
16 of 38
CTL-IPO101
5.6.1. Create SIP Line from Template
This section describes the steps to create a SIP line from the
template as follows:
1. Create a new folder in computer where Avaya IP Office Manager
is installed (e.g. C:\Centurylink\Template). Copy the template file
to this folder. The template file for the
compliance test is CTL-IPO101.xml (for SIP Line 17).
2. Import the template into Avaya IP Office Manager: From Avaya
IP Office Manager, select Tools Import Templates in Manager. This
action will copy the template file from step 1
into the IP Office template directory.
Figure 9 – Import Template for SIP Line
In the pop-up window (not shown) that appears, select the folder
where the template file was
copied in step 1. After the import is complete, a final import
status pop-up window below
will appear stating success (or failure). Then click OK to
continue.
Figure 10 – Import Template for SIP Line successfully
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
17 of 38
CTL-IPO101
3. Create the SIP Trunk from the template: Right-click on Line
in the Navigation Pane, then navigate to New from Template Open
from file.
Figure 11 – Create SIP Line from Template
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
18 of 38
CTL-IPO101
4. Select the Template Files (*.xml) and select the imported
template from step 2 at IP Office template directory C:\Program
Files\Avaya\IP Office\Manager\Templates\. Click Open
button to create a SIP line from template.
Figure 12 – Create SIP Line from IP Office Template
directory
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
19 of 38
CTL-IPO101
A pop-up window below will appear stating success (or failure).
Then click OK to continue.
Figure 13 – Create SIP Line from Template successfully
5. Once the SIP Line is created, verify the configuration of the
SIP Lines with the configuration
shown in Section 5.6.2.
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
20 of 38
CTL-IPO101
5.6.2. Create SIP Line Manually
To create a SIP line, begin by navigating to Line in the left
Navigation Pane, then right-click in the
Group Pane and select New SIP Line (not shown).
On the SIP Line tab in the Details Pane, configure the
parameters as shown below:
• Select available Line Number: 17
• Set ITSP Domain Name to the Centurylink domain name. This
field is used to specify the default host part of the SIP URI in
the To, R-URI fields for outgoing calls
• Check the In Service and Check OOS boxes
• Set URI Type to SIP
• For Session Timers, set Refresh Method to Auto with Timer
(sec) to On Demand
• Set Name Priority to Favor Trunk. As described in Section 5.4,
the Default Name Priority parameter may retain the default Favor
Trunk setting, or can be configured to
Favor Directory. As shown below, the default Favor Trunk setting
was used in the
reference configuration
• For Redirect and Transfer, set Incoming Supervised REFER and
Outgoing Supervised REFER to Always. Note: Centurylink supported
either SIP re-Invite or SIP Refer for off-net
call transfer call during the compliance testing
• Default values may be used for all other parameters
• Click OK to commit then press Ctrl + S to save
Figure 14 – SIP Line Configuration
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
21 of 38
CTL-IPO101
On the Transport tab in the Details Pane, configure the
parameters as shown below:
• The ITSP Proxy Address was set to the IP address of
Centurylink signaling server: 192.168.66.81 as shown in Figure
1
• In the Network Configuration area, UDP was selected as the
Layer 4 Protocol and the Send Port was set to 5100
• The Use Network Topology Info parameter was set to None. The
Listen Port was set to 5100. Note: For the compliance testing, the
Use Network Topology Info field was set to
None, since no NAT was using in the test configuration. In
addition, it was not necessary to
configure the System LAN2 Network Topology tab for the purposes
of SIP trunking. If
a NAT is used between Avaya IP Office and the other end of the
trunk, then the Use Network
Topology Info field should be set to the LAN interface (LAN2)
used by the trunk and the
System LAN2 Network Topology tab needs to be configured with the
details of the
NAT device
• The Calls Route via Registrar was unchecked. In this
certification testing, Centurylink did not support the dynamic
Registration on the SIP Trunk
• Other parameters retain default values
• Click OK to commit then press Ctrl + S to save
Figure 15 – SIP Line Transport Configuration
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
22 of 38
CTL-IPO101
A SIP Credentials entry must be created for Digest
Authentication used by Centurylink to
authenticate calls from the enterprise to the PSTN. To create a
SIP Credentials entry, first select the
SIP Credentials tab. Click the Add button and the New SIP
Credentials area will appear at the
bottom of the pane. To edit an existing entry, click an entry in
the list at the top, and click the Edit…
button. In the bottom of the screen, the Edit SIP Credentials
area will be opened. In the example
screen below, a previously configured entry is edited. The entry
was created with the parameters
shown below:
• Set User name and Authentication Name to the value provided by
the service provider
• Set Password and Confirm Password to the value provided by the
service provider Expiration (mins) is set to 60
• Check the Registration required option. Centurylink requires
registration for Digest Authentication
Figure 16 – SIP Line SIP Credentials Configuration
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
23 of 38
CTL-IPO101
The SIP URI entry must be created to match any DID number
assigned to an Avaya IP Office user
and Avaya IP Office will route the calls on this SIP line.
Select the SIP URI tab; click the Add
button and the New Channel area will appear at the bottom of the
pane (not shown). To edit an
existing entry, click an entry in the list at the top, and click
Edit… button. In the example screen
below, a previously configured entry is edited.
A SIP URI entry was created that matched any DID number assigned
to an Avaya IP Office user.
The entry was created with the parameters shown below:
• Set Local URI, Contact, and Display Name to Use Internal Data.
This setting allows calls on this line whose SIP URI matches the
number set in the SIP tab of any User as shown in
Section 5.8
• For Identity, set Identity to Use Credentials User Name and
Header to P Asserted ID
• For Forwarding And Twinning, set Send Caller ID to Diversion
Header Note: When using the twinning feature, the calling party
number displayed on the twinned
phone is controlled by (but not necessarily extracted from) the
Send Caller ID parameter
• Leave Diversion Header to None by default
• Set Registration to 1: 4695557028
• Associate this line with an incoming line group in the
Incoming Group field and an outgoing line group in the Outgoing
Group field. This line group number will be used in
defining incoming and outgoing call routes for this line. For
the compliance test, a new line
group 17 was defined that only contains this line (line 17)
• Set Max Sessions to the number of simultaneous SIP calls that
are allowed using this SIP URI pattern
• Click OK to submit the changes
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
24 of 38
CTL-IPO101
Figure 17 – SIP Line SIP URI Configuration
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
25 of 38
CTL-IPO101
Select the VoIP tab to set the Voice over Internet Protocol
parameters of the SIP line. Set the
parameters as shown below:
• The Codec Selection can be selected by choosing Custom from
the pull-down menu, allowing an explicit ordered list of codecs to
be specified. The G.729(a) 8K CS –ACELP
and G.711 ULAW 64K codecs are selected. Avaya IP Office supports
these codecs, which
are sent to Centurylink, in the Session Description Protocol
(SDP) offer, in that order
• Check the Re-invite Supported box
• Set Fax Transport Support to T.38 or G.711 from the pull-down
menu. Note: Centurylink supported Fax T.38 and G.711 pass-through
modes during the compliance testing
• Set the DTMF Support to RFC2833 from the pull-down menu. This
directs Avaya IP Office to send DTMF tones using RTP events
messages as defined in RFC2833.
• Set Media Security as Disabled
• Default values may be used for all other parameters
• Click OK to submit the changes
Figure 18 – SIP Line VoIP Configuration
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
26 of 38
CTL-IPO101
Select the T38 Fax tab to set the Fax parameters. Set the
parameters as shown below:
• T38 Fax Version: 0
• Max Bit Rate (bps): 14400
• Check Disable T30 ECM option
• Default values may be used for all other parameters
• Click OK to submit the changes
Figure 19 – SIP Line Fax T.38 Configuration
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
27 of 38
CTL-IPO101
Select the SIP Advanced tab to set the SIP parameters. Set the
parameters as shown below:
• Check Use Domain for PAI option (Centurylink requires to use
the domain for PAI)
• Check Emulate NOTIFY for REFER option (See observation in
Section 2.2)
• Check No REFER if using Diversion option (See observation in
Section 2.2)
• Default values may be used for all other parameters
• Click OK to submit the changes
Figure 20 – SIP Line SIP Advanced Configuration
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
28 of 38
CTL-IPO101
5.7. Outgoing Call Routing
The following section describes the Short Code for outgoing
calls to Centurylink.
5.7.1. Short Code
Define a short code to route outbound traffic on the SIP line to
Centurylink. To create a short code,
select Short Code in the left Navigation Pane, then right-click
in the Group Pane and select New
(not shown). On the Short Code tab in the Details Pane,
configure the parameters for the new short
code to be created. The screen below shows the details of the
previously administered “6N;” short
code used in the test configuration.
• In the Code field, enter the dial string which will trigger
this short code, followed by a semi-colon. In this case, 6N;, this
short code will be invoked when the user dials 6 followed by
any number
• Set Feature to Dial. This is the action that the short code
will perform
• Set Telephone Number to N. The value N represents the number
dialed by the user.
• Set the Line Group ID to the Outgoing Group 17 defined on the
SIP URI tab on the SIP Line in Section 5.6.2. This short code will
use this line group when placing the outbound call
• Set the Locale to United States (US English)
• Default values may be used for all other parameters
• Click OK to submit the changes
Figure 21 – Short Code 6N
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
29 of 38
CTL-IPO101
The feature of incoming calls from mobility extension to
idle-appearance FNE (Feature Name
Extension) is hosted by Avaya IP Office. The Short Code FNE00
was configured with following
parameters:
• For Code field, enter FNE feature code as FNE00 for dial
tone
• Set Feature to FNE Service
• Set Telephone Number to 00
• Set Line Group ID to 0
• Set the Locale to United States (US English)
• Default values may be used for other parameters
• Click OK to submit the changes
Figure 22 – Short Code FNE
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
30 of 38
CTL-IPO101
5.8. User
Configure the SIP parameters for each user that will be placing
and receiving calls via the SIP Line
defined in Section 5.6. To configure these settings, first
select User in the left Navigation Pane, then
select the name of the user to be modified in the center Group
Pane. In the example below, the name
of the user is 7020. Select the SIP tab in the Details pane.
The values entered for the SIP Name and Contact fields are used
as the user part of the SIP URI in
the From and Contact headers accordingly for outgoing SIP trunk
calls. They also allow matching of
the SIP URI for incoming calls without having to enter this
number as an explicit SIP URI for the
SIP line. The example below shows the settings for user 7020.
The SIP Name and Contact are set to
one of the DID numbers assigned to the enterprise provided by
Centurylink. The SIP Display Name
(Alias) parameter can optionally be configured with a
descriptive name. If all calls involving this
user and a SIP Line should be considered private, then the
Anonymous box may be checked to
withhold the user’s information from the network.
Figure 23 – User Configuration
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
31 of 38
CTL-IPO101
One of the H.323 IP Deskphones at the enterprise site uses the
Mobile Twinning feature. The
following screen shows the Mobility tab for User 7020. The
Mobility Features and Mobile
Twinning boxes are checked. The Twinned Mobile Number field is
configured with the number to
dial to reach the twinned mobile telephone, in this case
61613XXX7497. Check Mobile Call
Control to allow incoming calls from mobility extension to
access FNE00 (defined in Section
5.7.1). Other options can be set according to customer
requirements.
Figure 24 – Mobility Configuration for User
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
32 of 38
CTL-IPO101
5.9. Incoming Call Route
An Incoming Call Route maps an inbound DID number on a specific
line to an internal extension.
This procedure should be repeated for each DID number provided
by service provider. To create an
incoming call route, select Incoming Call Route in the left
Navigation Pane, then right-click in the
center Group Pane and select New (not shown). On the Standard
tab of the Details Pane, enter the
parameters as shown below:
• Set the Bearer Capability to Any Voice.
• Set the Line Group ID to the Incoming Group 17 defined on the
SIP URI tab on the SIP Line in Section 5.6.2.
• Set the Incoming Number to the incoming DID number on which
this route should match.
• Default values can be used for all other fields.
Figure 25 – Incoming Call Route Configuration
On the Destination tab, select the destination extension from
the pull-down menu of the Destination
field. In this example, incoming calls to 4695557020 on line 17
are routed to Destination 7020 7020
as below screenshot:
Figure 26 – Incoming Call Route for Destination 7020
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
33 of 38
CTL-IPO101
For Feature Name Extension Service testing purpose, the incoming
calls to DID number
4695557022 were configured to access FNE00. The Destination was
appropriately defined as
FNE00 as below screenshot:
Figure 27 – Incoming Call Route for Destination FNE
For Voice Mail testing purpose, the incoming calls to DID number
4695557023 were configured to
access VoiceMail. The Destination was appropriately defined as
VoiceMail as below screenshot:
Figure 28 – Incoming Call Route for Destination VoiceMail
5.10. Save Configuration
Navigate to File Save Configuration in the menu bar at the top
of the screen to save the
configuration performed in the preceding section.
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
34 of 38
CTL-IPO101
6. Centurylink SIP Trunk Configuration Centurylink is
responsible for the configuration of Centurylink SIP Trunk Service.
The customer
must provide the IP address used to reach the Avaya IP Office
LAN2 port at the enterprise.
Centurylink will provide the customer necessary information to
configure the SIP connection
between Avaya IP Office and Centurylink. The provided
information from Centurylink includes:
• IP address and port number used for signaling or media servers
through any security devices
• DID numbers
• Centurylink SIP Trunk Specification (If applicable)
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
35 of 38
CTL-IPO101
7. Verification Steps The following steps may be used to verify
the configuration:
• Use the Avaya IP Office System Status application to verify
the state of the SIP connection. Launch the application from Start
Programs IP Office System Status on the PC
where Avaya IP Office Manager was installed. Select the SIP Line
of interest from the left
pane. On the Status tab in the right pane, verify the Current
State for each channel (The
following screen-shot shows 2 active calls at the present
time).
Figure 29 – SIP Trunk status
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
36 of 38
CTL-IPO101
• Use the Avaya IP Office System Status application to verify
that no alarms are active on the SIP line. Launch the application
from Start Programs IP Office System Status on
the PC where Avaya IP Office Manager was installed. Select Alarm
Trunks to verify that
no alarms are active on the SIP line.
Figure 30 – SIP Trunk alarm
• Verify that a phone connected to the PSTN can successfully
place a call to Avaya IP Office with two-way audio.
• Verify that a phone connected to Avaya IP Office can
successfully place a call to the PSTN with two-way audio.
• Use a network sniffing tool (e.g., Wireshark) to monitor the
SIP signaling between the enterprise and Centurylink. The sniffer
traces are captured at the LAN2 port interface of the
Avaya IP Office.
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
37 of 38
CTL-IPO101
8. Conclusion Centurylink passed compliance testing excepting
the limitation in Section . These Application
Notes describe the procedures required to configure the SIP
connections between Avaya IP Office
and the Centurylink system as shown in Figure 1.
9. Additional References
[1] Administering Avaya IP Office Platform with Manager, Release
10.1, 15-601011, Issue 14, July 2017.
[2] Deploying Avaya IP OfficeTM Platform IP500V2, Release 10.1,
15-601042, Issue 32d, May 2017.
[3] Avaya IP Office™ Platform Release 10.1 - Release Notes /
Technical Bulletin General Availability
Product documentation for Avaya products may be found at:
http://support.avaya.com. Additional IP
Office documentation can be found at:
http://marketingtools.avaya.com/knowledgebase/ipoffice/general/rss2html.php?XMLFILE=manuals.
xml&TEMPLATE=pdf_feed_template.html
Product documentation for Centurylink SIP Trunk may be found at:
http://www.centurylink.com
http://support.avaya.com/http://marketingtools.avaya.com/knowledgebase/ipoffice/general/rss2html.php?XMLFILE=manuals.xml&TEMPLATE=pdf_feed_template.htmlhttp://marketingtools.avaya.com/knowledgebase/ipoffice/general/rss2html.php?XMLFILE=manuals.xml&TEMPLATE=pdf_feed_template.htmlhttp://www.centurylink.com/
-
HV; Reviewed:
SPOC 8/30/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
38 of 38
CTL-IPO101
©2017 Avaya Inc. All Rights Reserved.
Avaya and the Avaya Logo are trademarks of Avaya Inc. All
trademarks identified by ®
and ™
are registered trademarks or trademarks, respectively, of Avaya
Inc. All other trademarks are the
property of their respective owners. The information provided in
these Application Notes is
subject to change without notice. The configurations, technical
data, and recommendations
provided in these Application Notes are believed to be accurate
and dependable, but are
presented without express or implied warranty. Users are
responsible for their application of any
products specified in these Application Notes.
Please e-mail any questions or comments pertaining to these
Application Notes along with the
full title name and filename, located in the lower right corner,
directly to the Avaya DevConnect
Program at [email protected].
SIPTrunk 20170809 enu voip.centurylink.com CallerIDNone true 1 1
false false true 1 SourceIP FavourTrunk UpdateAuto SIPURI false
false 192.168.66.81 SipUDP 5100 5100 0.0.0.0 0.0.0.0 false
AUTOSELECT true G.729(a) 8K CS-ACELP,G.711 ULAW 64K 4
DTMF_SUPPORT_RFC2833 false true FOIP_T38 false false false 0 UDPTL
0 0 Trans_TCF FaxRate_14400 2600 2300 false true true true false
false false false false 0 false false false false false true false
true false false false false false false true true CONNDISABLED
SipPEarlyMediaSuppNone false 5 486 0 60 true false false