Page is loading ...
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
Page 2 of 33
IN STRICTEST CONFIDENCE
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.
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 3 of 33
IN STRICTEST CONFIDENCE
Document Revision History
Release
Version
Reason for Change
Date
Author
1
1.0
Document Created
22/08/2012
BTW Product Line
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 4 of 33
IN STRICTEST CONFIDENCE
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
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 5 of 33
IN STRICTEST CONFIDENCE
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
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 6 of 33
IN STRICTEST CONFIDENCE
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.
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 7 of 33
IN STRICTEST CONFIDENCE
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.
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 8 of 33
IN STRICTEST CONFIDENCE
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
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 9 of 33
IN STRICTEST CONFIDENCE
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.
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 10 of 33
IN STRICTEST CONFIDENCE
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.
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 11 of 33
IN STRICTEST CONFIDENCE
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
Line/port: 441234567891@<Network Defined Domain>
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
Line/port: 441234567892@<Network Defined Domain>
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
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 12 of 33
IN STRICTEST CONFIDENCE
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.
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 13 of 33
IN STRICTEST CONFIDENCE
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.
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 14 of 33
IN STRICTEST CONFIDENCE
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.
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 15 of 33
IN STRICTEST CONFIDENCE
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.
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 16 of 33
IN STRICTEST CONFIDENCE
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.
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 17 of 33
IN STRICTEST CONFIDENCE
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
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 18 of 33
IN STRICTEST CONFIDENCE
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.
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 19 of 33
IN STRICTEST CONFIDENCE
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
IN STRICTEST CONFIDENCE
BT Wholesale
Issue 1: 2012© British Telecommunications plc
Page 20 of 33
IN STRICTEST CONFIDENCE
/
