sip trunking · the sip trunking provisioning admin guide details how to provision sip trunk...

SIP TRUNKING NEC SL1100/SV8100: ADMINSTRATOR GUIDE 1.0

Author: BTW Product Line

Date: 22/08/2012

IN STRICTEST CONFIDENCE

BT Wholesale

Issue 1: 2012© British Telecommunications plc

of 33


Confidentiality

All information in this document is provided in confidence as per your terms and conditions

with BT and shall not be published or disclosed wholly or in part to any other party without BT’s prior permission in writing and shall be held in safe custody. These obligations shall not apply to information which is published or becomes known legitimately from some source other than BT.


BT Wholesale


of 33


Document Revision History

Release Version Reason for Change Date Author

1 1.0 Document Created 22/08/2012 BTW Product Line


BT Wholesale


of 33


CONTENTS

DOCUMENT REVISION HISTORY ................................................................................................ 3

1 INTRODUCTION ................................................................................................................ 6

2 IPVS SOURCE NUMBERING REQUIREMENTS ........................................................................ 7

3 DEVICE CAPABILITIES AND KNOWN INTEROPERABILITY ISSUES ........................................... 8

3.1 Caveats ..................................................................................................................................................... 9 Forwarding ................................................................................................................................................................ 9 Toolbar Hold and Call Control ..................................................................................................................................... 9 Off System Hold ......................................................................................................................................................... 9 Codec Profiles ............................................................................................................................................................ 9 T.38 Negotiation ....................................................................................................................................................... 9 Double Hold .............................................................................................................................................................. 9 Blind Transfer .......................................................................................................................................................... 10

4 SOLUTION CONFIGURATION ............................................................................................ 11

5 CONNECTING TO THE NEC SL1100/SV8100 ....................................................................... 12

6 PROVISIONING ............................................................................................................... 13

7 CONNECTIVITY SPECIFIC CONFIGURATION ........................................................................ 14

8 NEC IP-PBX CONFIGURATION .......................................................................................... 15

8.1 SL1100/SV8100 Security ......................................................................................................................... 16

8.2 SIP Networking ........................................................................................................................................ 17 System Information Setup ........................................................................................................................................ 17 SIP Server Setup ...................................................................................................................................................... 17 Authentication Information ...................................................................................................................................... 18 Codec Setup ............................................................................................................................................................ 19 Incoming Type – VoIP .............................................................................................................................................. 21 Calling Party Number for Extensions ......................................................................................................................... 22

8.3 DDI Routing Table .................................................................................................................................... 23

8.4 IP Addressing .......................................................................................................................................... 24 CCPU IP Network Setup ............................................................................................................................................ 24 VoIP Resource IP Address ......................................................................................................................................... 25


BT Wholesale


of 33


8.5 COS ......................................................................................................................................................... 27

8.6 Trunk to Trunk Routing - Optional ............................................................................................................. 28 Trunk to Trunk Transfer ............................................................................................................................................ 28 External Call Forward -COS....................................................................................................................................... 28 Trunk to Trunk Options ............................................................................................................................................ 28

8.7 Dialing Plan ............................................................................................................................................. 29

9 TROUBLESHOOTING AND USEFUL INFORMATION ............................................................. 30

9.1 Checking SIP Messaging To/From the PBX .................................................................................................. 30

9.2 Device Fails to Register ............................................................................................................................ 31

9.3 Outbound Calls Fail .................................................................................................................................. 32

9.4 Inbound Calls Fail ..................................................................................................................................... 33


BT Wholesale


of 33


1 INTRODUCTION

This document describes the configuration procedures required for the NEC SL1100 and SV8100 IP-

PBX ranges to make full use of the capabilities of IPVS SIP Trunking. These NEC IP-PBX’s are come of the many access products that interoperate with IPVS. They use the Session Initiation Protocol (SIP) to communicate with IPVS for call control.

This guide describes the specific configuration items that are important for use with IPVS. It does not describe the purpose and use of all configuration items on the SL1100 and SV8100, for those details, see the relevant NEC documentation.

Interoperability testing validates that the device interfaces properly with IPVS via the SIP interface.

Qualitative aspects of the device or device capabilities not affecting the SIP interface such as display

features, functionality and performance are not covered by interoperability testing. Requests for

information and/or issues regarding these aspects should be directed to manufacturer.


BT Wholesale


of 33


2 IPVS Source Numbering Requirements Please note that the following prerequisites must be satisfied for successful deployment: Any SIP call must present a number with a current registration on the IPVS platform in one or more of

the following headers of the SIP message transmitted by the IP-PBX (listed in order of significance): 1. Diversion 2. P-Asserted-Identity 3. Remote-Party-Id

4. From If you see a 604 SIP message back from IPVS then the device is not presenting the correct CLI to the IPVS platform or the account is not present on the IPVS platform.

SIP Trunking DDI Users must have an active Public Number (DDI) on the IPVS Platform. Legacy PBX users/extensions (who do not have a SIP Trunking User account provisioned) must present the SIP Trunk Group number or ‘Bearer Number’ as their outbound CLI for calls to be able to traverse the IPVS platform.


BT Wholesale


of 33


3 DEVICE CAPABILITIES AND KNOWN INTEROPERABILITY ISSUES

Comments

Device Type IP-PBX

Verified Revisions SL1100 - v2.0 with VOIPDB card

SV8100 - v7.0 with IPL card

Route Using TO Header Yes

SIP Connect Yes

Registration Capable Yes

Codecs G711u/G711a/G729a See Caveats

RFC 2833 DTMF Yes

T.38 Fax Yes

Call Control

- Hold

- Call Waiting - Blind Transfer

- Consultive Transfer

- Three Way Call

Yes Yes

Yes

Yes Yes

See Caveats

Call Services

- PBX Redirect

- IPVS CLI Blocking - IPVS Call Pickup

Partial Yes

Yes

See Caveats

Redirect by PBX to IPVS Voicemail is not supported

IPVS Enhanced Features

IPVS Voicemail / Local Voicemail Both

Voicemail MWI No Use IPVS Voicemail to Email or

Email Notification (Call Notify)

SIP Trunk Mobility User Features

- Call Forward Always

- Call Forward Busy

- Call Forward No Ans - Call Forward Unreach

- Call Notify

- Intercept User - SIM Ring

- Remote Office

Yes

Yes Yes

Yes

Yes Yes

Yes

Yes

Set via Customisable Feature Access Codes, Business Portal or

Toolbar

Toolbar

- Click-to-Dial

- Call Control

- Services

Partial

Yes

Partial Yes

See Caveats


BT Wholesale


of 33


3.1 Caveats

Forwarding

When a call is forwarded by a SL1100/SV8100 user/device regardless of whether it has a specific CLID setup the default CLID for the system is always used in this scenario and therefore is what will be seen by the destination of the forward.

Toolbar Hold and Call Control

Hold on PBX handset and Toolbar must be used together.

Off System Hold

When a hold request is sent from the IPVS platform to the SL1100/SV8100 and is not followed by an

update for Music On Hold the system will play its own hold music to the local user.

Codec Profiles

The codec profiles offered by the SL1100/SV8100 are predefined meaning the following:

The SL1100/SV8100 only offers one G711 type per profile so we recommend that this is set to A-law. The G.729_PT profile will offer and therefore allow the use of G711 and G722 meaning that while G729 is the primary codec it may not be used in all call scenarios. The G.729_Fix profile will only offer G729 and therefore this will always be used.

T.38 Negotiation

Due to limitations with the current firmware the SL1100/SV8100 is unable initiate the renegotiation of T.38 for a fax call. If the other party initiates the renegotiation the SL1100/SV8100 will accept this and T.38 will be used. Where the SL1100/SV8100 attempts to renegotiate to T.38 the fax will progress using G.711a pass-through with this associated limitations of this method.

Double Hold

Due to limitations with the current firmware if an external party is placed on hold by the SL1100/SV8100 that party is then unable to in turn place the SL1100/SV8100 user on hold. This means that any flows involving the SL1100/SV8100 user being placed on hold which include transferring will fail.


BT Wholesale


of 33


Blind Transfer

Please note that when blind transfering to a CO party users should press the hash (#) key at the end of the dialled digit string for the destination before pressing transfer so that the IP-PBX is instructed that the dialling has ended and can setup the call.


BT Wholesale


of 33


4 SOLUTION CONFIGURATION

The following diagram shows an example of a typical deployment configuration with the NEC SL1100/SV8100. Typically, the SL1100/SV8100 is placed at the customer premises with either Analogue to IP handset connected/registered to it.

The SL1100/SV8100 registers the main line (or Trunk Group number) with the Trunk Group configured on IPVS. This enables all PBX users to be implicitly registered with IPVS via the trunk group number registration.

IP Network

NEC SL1100/

SV8100

Trunk Group Number

441234567890@<Network Defined Domain>

Trunk Group Profile Data:

Device Type: NEC SL1100/NEC SV8100

Trunk Group Number Profile Data:

Line/port: 441234567890@<Network Defined Domain>

Authentication Username: 441234567890

Authentication Password: password

DDI: 01234 567890

PBX User 1:

User Type: Business Trunking User

Feature Package: SIP Trunk User / SIP Mobility User etc

Add-ons: Toolbar, Voicemail etc

Device Type: Trunk Group


DDI: 01234 567891

PBX User 2:

User Type: Business Trunking User

Feature Package: SIP Trunk User / SIP Mobility User etc

Add-ons: Toolbar, Voicemail etc

Device Type: Trunk Group


DDI: 01234 567892

SIP Registra/Proxy Data:

FQDN: <Network Defined Domain>

Port: 5060

Outbound Proxy Data:

FQDN: <Network Defined Domain>

Port: 5060

Router / IP

access

PBX User 1

01234 567891

PBX User 2

01234 567892


BT Wholesale


of 33


5 CONNECTING TO THE NEC SL1100/SV8100

To connect to the NEC SL1100/SV8100 install the manufacturer recommended PCPro management application, for details please follow the associated manufacturer documentation.


BT Wholesale


of 33


6 PROVISIONING

Before reading and using this Admin Guide you must read the SIP Trunking Provisioning Administrator Guide that can be found on the Support Centre: Support Centre >> Downloads >> SIP Trunking >> SIP Trunking Provisioning Admin Guide

NOTE:

The SIP Trunking Provisioning Admin guide details how to provision SIP Trunk Groups, SIP Trunk Users and SIP Trunk Mobility Users. This guide assumes that you have read this guide and the required provisioning has

been completed. When provisioning please select the appropriate Shared Device Type:

NEC SL1100 or NEC SV8100

Note: If you do not have this device type available in your service offering please contact your Account Manager who will be happy to arrange its addition for you. We would also recommend reading the SIP Trunking Overview Guide that can be found on our

Support Centre for background on the messaging that a SIP Trunking device should present to the IPVS platform to be able to successfully make calls.


BT Wholesale


of 33


7 CONNECTIVITY SPECIFIC CONFIGURATION

The below table discusses the different Access Network products that the SL1100/SV8100 can be used with and in each case the SIP FQDN that should be configured on the SL1100/SV8100. Access Network SIP FQDN

BT Wholesale Ethernet uk.dc.sipconnect.hipcom.co.uk

BT IP Clear uk.dc.sipconnect.hipcom.co.uk

Bring Your Own Network (BYON) uk.dc.sipconnect.hipcom.co.uk

All other products uk.ic.sipconnect.hipcom.co.uk

This document is written based on a connection to IPVS that transits the Public Internet meaning that uk.ic.sipconnect.hipcom.co.uk is used, wherever you see this string substitute it for the correct SIP

FQDN based on your Access Network product.


BT Wholesale


of 33


8 NEC IP-PBX CONFIGURATION

The following steps show how to program a NEC SL1100/SV8100 to interconnect with IPVS using SIP Trunking. The steps in this section assume that you are connected to the SL1100/SV8100 with the relevant

privileges using NEC’s PCPro application and at the Advanced Programming Level. They also assume that you have prior knowledge of PCPro and the setup of a NEC PBX using it. For more details on the PCPro application and configuration of a SL1100/SV8100 PBX please consult the relevant NEC documentation.

NOTE:

Before installing and configuring the NEC SL1100/SV8100, ensure that you read the NEC Safety and Compliance Information and any other related NEC documentation.

The configuration steps discussed in this section have been taken from an example configuration of a NEC SV8100. The steps are applicable to all SL1100 and SV8100 PBX’s discussed in the Device Capabilities and Known Interoperability Issues section of this document.

It is assumed that the fundamental configuration of the SL1100/SV8100 has already been carried out.


BT Wholesale


of 33


8.1 SL1100/SV8100 Security

For public access network configurations IPVS recommends that the SL1100/SV8100 is placed behind a router/firewall for security reasons. This is particularly important in situations where the SL1100/SV8100 is issued a public IP making it easily accessible from the internet; in these cases we recommend that the SL1100/SV8100’s position

is hardened to reflect this public accessibility as per standard industry practices. In private access network configurations traversing a IPVS private solution i.e. BYON, though it is not expected that the SL1100/SV8100 will be publically accessible we still recommend that steps are taken to prevent unauthorised access to it.


BT Wholesale


of 33


8.2 SIP Networking

Advanced Items > VoIP > Networking > SIP Networking This section assumes that you have installed and enabled the IPL card that is installed in your SL1100/SV8100.

The settings under SIP Networking define all of the necessary parameters for enabling SIP communication between the SL1100/SV8100 and the IPVS platform.

System Information Setup

Under the System Information Setup page the following values should be set. Domain Name hipcom.co.uk

Host Name This should be the first part of the FQDN discussed in the Network

Specific Configuration section of this document, the portion of the

string prior to ‘.hipcom.co.uk’ i.e. uk.ic.sipconnect. This should be the FQDN that is relevant to the access network that will be used.

Transport Protocol UDP

User ID This is the DDI of the Trunk Group as configured in the Business

Portal i.e. 441234567890.

Domain Assignment Domain Name

IP Trunk Port Binding Unchecked

SIP Server Setup

Under the SIP Server Setup page the following values should be set. If a value is not discussed then this should be left as default unless advised otherwise.

Default Proxy IP Address 0.0.0.0


BT Wholesale


of 33


Register Mode Manual

Registrar IP Address 0.0.0.0

DNS Mode Checked

DNS IP Address The IP of the DNS server used on the LAN that the SL1100/SV8100 will be placed on.

Registrar Domain Name This should be the FQDN discussed in the Network Specific Configuration section of this document that is relevant to the access

network that will be used.

Proxy Domain Name This should have no value.

Proxy Host Name This should have no value.

SIP Carrier Choice The value selected here must be Carrier L

Register Sub Mode Unchecked

Authentication Information

Under the Authentication Information Setup page the following values should be set. User Name This should match the Authentication Username value given to the

Trunk Group when it was created in the Business Portal.

Password This should match the Password value given to the Trunk Group

when it was created in the Business Portal.


BT Wholesale


of 33


Codec Setup

Under the Codec Setup page the following values should be set. If a value is not discussed then this should be left as default unless advised otherwise.

Audio Capability Priority The default value here is G.711_PT and where WAN bandwidth is

not an issue we recommend that this is left.

If you have a requirement to use G.729 as the preferred codec then

the G.729_PT or G.729_Fix profiles should be considered. The G.729_PT profile will place G729 as the first choice codec in a

list of possible options meaning that G729 should be negotiation in

most call scenarios but is not guaranteed, this profile offers the best compatibility with other SIP devices.

The G.729_Fix profile will only allow the use of G729 for calls but

reduces the systems compatibility with other SIP devices that do not support G729.

DTMF Payload Number 101

DTMF Relay Mode RFC2833

G.722 Maximum Audio Frame Size 20ms

Fax Relay Mode Checked

T.38 Protocol Mode UDPTL/RTP


BT Wholesale


of 33



BT Wholesale


of 33


Incoming Type – VoIP

For the trunks that you have identified for use with the IPVS SIP Trunking service we recommend that

DID mode is used for incoming call routing. The below image is taken from our example deployment where trunks 5 to 12 are set as SIP Trunks and used for the IPVS service.


BT Wholesale


of 33


Calling Party Number for Extensions

By default the SL1100/SV8100 will present the Trunk DDI which is the User ID setup previously for all

outbound calls. If you wish for some/all extensions to display different User DDI(s) we recommend that you set a DDI for each extension on this page. The below image shows our example deployment where SIP Trunk User 1 is Extension 210 and User 2 Extensions 211.


BT Wholesale


of 33


8.3 DDI Routing Table

DDI > DDI Routing Table The DDI Routing Table is what was used to route inbound calls for our example deployment.

For each DDI configured on the IPVS platform either as the Trunk Group or and associated Trunk User an equivalent DDI Translation Table Entry was used. The matching was done on the last 6 digits of the inbound number which was entered in the Received

Number field while the destination for the call was set in the Target 1 field.

The below image shows the values taken from our example deployment.


BT Wholesale


of 33


8.4 IP Addressing

Advanced Items > VoIP > General Settings > IP Addressing The settings in the IP Addressing section are used to control the settings used by the VoIP card in the SL1100/SV8100.

The following details have been included for reference but are specific to your SL1100/SV8100 network setup.

CCPU IP Network Setup

On this page the following details are important.

IP Address This value is not influential to deployments where an IPL card

(VOIP) is not installed, so give this a dummy value.

Subnet Mask Give this a value to match the previous dummy value.

Default Gateway Enter the IP Address of the router/gateway for the network that the

SL1100/SV8100 will be placed on.

Time Zone Select the appropriate Time Zone for the location of the

SL1100/SV8100.

IPL IP Address This is the IP that the SL1100/SV8100 will use for sending and

receiving of all SIP signalling and is also used for management, this

supersedes the previous IP Address value.

IPL Subnet Mask Enter the subnet mask for the network the SL1100/SV8100 is

placed on.

DNS Primary/Secondary Enter the IP Addresses for DNS’s available to the SL1100/SV8100.

As a DNS value is also entered for the SIP Networking configuration

these settings aren’t crucial to the working of the SL1100/SV8100.

The below image is taken from our example deployment.


BT Wholesale


of 33


VoIP Resource IP Address

This page defines the IP Addresses used for media termination on the SL1100/SV8100. SV8100

There are two VoIP cards available for the SV8100, the IPLA and newer IPLB. With the IPLA card an IP address is assigned to handle 16 DSP resources. So if I have a 32IPLA you will need 2 IP addresses to be able to use all 32 resources (2 x 16), a 64IPLA (4 x 16) would need 4 IP addresses assigned, and a 128IPLA (8 x 16) would need 8 IP addresses assigned.

The newer IPLB card whether you have a 32, 64 or 128 DSP card you only need 1 IP address for all these media resources. With regards to the port addressing these are dynamically issued in pairs based from the initial values

that you specify. The below image is taken from our example deployment using an IPLA card where two sets of 16 DSP’s have been assigned valid IP and port ranges allowing up to 32 calls.


BT Wholesale


of 33


Whilst only a single RTP and RTCP Port have been specified in each case these signify the starting point for the allocation of RTP/RTCP port pairs for that resource.

To elaborate the OSO will issue the first port pair 10020 and 10021 to the first call then the second logical pair 10022 and 10023 to the second call, it will continue to do this for all 16 DSP’s which in the case provisioned above would use the ports up to 10051 which is why 10052 is the first assigned to the second resource.

SL1100

The NEC SL1100 uses a different VOIPDB card that works using the same configuration as discussed for the SV8100 but has a maximum capacity of 16 SIP Trunk connections.


BT Wholesale


of 33


8.5 COS

COS The SL1100/SV8100 use the COS settings to define what the associated extensions and features are allowed to do.

Most of the settings within these tabs are dependent on the setup and usage situation of the PBX; the values that we recommend changing within the COS are listed below. Second Call for DDI/DISA/DIL/E&M Enabled

Call Forward Off-premise Enabled

Trunk to Trunk Transfer Restriction Disabled

Trunk to Trunk Transfer Restriction Disabled

Trunk Port Disable Disabled


BT Wholesale


of 33


8.6 Trunk to Trunk Routing - Optional

Trunks > Trunk to Trunk Routing There are several settings under the Trunk to Trunk Routing section of the configuration that you may choose to set for trunk to trunk forwarding and transfer to work as required.

Where the SL1100/SV8100 has been connected to an ISDN previously these will likely have be configured. When trunk to trunk forwarding is enabled access to the setting of this functionality for users should

be restricted where possible as unauthorised configuration of these settings creates a potential security vulnerability on any PBX system.

Trunk to Trunk Transfer

Enable the Trunk to Trunk transfer settings for all required trunks.

External Call Forward -COS

Enable the Call Forward Off-premise setting for the required COS.

Trunk to Trunk Options

If you have enabled Trunk to Trunk transfer previously change the settings for warning tone and

disconnect time to meet your requirements. You may wish to configure a Conversation Continue Code to increase the security of transferred calls.


BT Wholesale


of 33


8.7 Dialing Plan

System Numbering Plan The dial plan that you enter is relative to your local area and the calls that you want to allow you r users to make. We recommend that you consider the following dialling options:

Feature Access Codes International Calls 6 / 7 Digit Local Calls National Calls

118 Enquiries Calls 999 Emergency Calls 112 Emergency Calls 123 Speaking Clock


BT Wholesale


of 33


9 TROUBLESHOOTING AND USEFUL INFORMATION

9.1 Checking SIP Messaging To/From the PBX

When debugging a SIP Trunking issue with a PBX it is extremely useful to be able to capture the SIP messaging sent to/from it.

For the SL1100/SV8100 we recommend that you capture the SIP messaging sent over its connection to the LAN/WAN using an appropriate mirroring device and a PC with wireshark installed.


BT Wholesale


of 33


9.2 Device Fails to Register

By carrying out a SIP trace as discussed previously check that the PBX is sending SIP registration messages and whether it is receiving a response from the IPVS platform.

Check that the device has connectivity to the Internet by conducting a Ping from the same LAN/WAN segment.

Check that the SIP ports are not being blocked by a firewall on the network. Details of the ports can be found in the Security Guide under Support Centre » Downloads » General Help & Information.

Make sure the details entered in SIP Networking section, particularly for Authentication Information match those set for the Trunk Group in the Business Portal.

If you can find no problems with the configuration and setup based on the above steps please raise a ticket with Support with any SIP Protocol Traces you have taken attached.


BT Wholesale


of 33


9.3 Outbound Calls Fail

Check that the Device is registered as above.

Check that the SIP/RTP ports are not being blocked by a firewall on the network. Details of the

ports can be found in the Security Guide under Support Centre » Downloads » General Help & Information.

Check whether any calls can be made between extensions on the PBX; if not they the issue is likely to be local to the PBX.

Check that the device is sending out SIP messaging for calls by taking a SIP Protocol Trace and looking for outbound INVITES within this.

Check that the INVITE’s are not being continually challenged by the Registrar with 401

responses; if they are then check the SIP Networking Authentication Information details are the same as those set in the Business Portal.

Check that the expected outbound CLI of either the Trunk Group or the Trunk User is being presented in either the From or the P-Asserted-Identity in the outbound SIP INVITE.

If the Trunk Group or Trunk User DDI’s are being sent out in the INVITE make sure that they are in the correct format i.e. 441234567890.

If none of the above points highlight the cause please take a SIP trace of a call failing where possible and raise a ticket with Support.


BT Wholesale


of 33


9.4 Inbound Calls Fail

Check that the Device is registered as above.

Check that the SIP/RTP ports are not being blocked by a firewall on the network. Details of the

ports can be found in the Security Guide under Support Centre » Downloads » General Help & Information.

Check whether any calls can be made between extensions on the PBX; if not they the issue is likely to be local to the PBX.

Check that the device is receiving SIP messaging for calls by taking a SIP Protocol Trace and looking for inbound INVITES within this.

Check that the expected outbound CLI of either the Trunk Group or the Trunk User is being

presented in the TO header of the inbound SIP INVITE.

If the Trunk Group or Trunk User DDI’s are being received make sure that they match the

format of the numbers in your DDI / DID Table i.e. 441234567890.

If the DDI / DID Table is correct for the inbound INVITE make sure that the destination for the

call is available to other extensions on the PBX.

If none of the above points highlight the cause please take a SIP trace of a call failing where

possible and raise a ticket with Support.

sip trunking · the sip trunking provisioning admin guide details how to provision sip trunk...

Documents