Page 1 of 28
1 PREFACE
1.1 APPROVAL
Name
Adam Crisp
Title
Signature
Date
VoIP.co.uk Director
Description
Author
Release
Date
th
VoIP.co.uk technical
6 June 2008
1.3 DISTRIBUTION
Copy Number
Closed Distribution
Owner
Audience
VoIP.co.uk
System Integrators
Description
AAA
ACL
ALG
BGP
CAR
CDR
CBWFQ
COS
Class of Service
CPE
CQ
Custom Queuing
DHCP
DNS
IP
Internet Protocol
IPO
ISDN
ISP
LAN
MTU
NAT
Page 2 of 28
OSPF
PAT
PoP
Point-of-Presence
PPP
Point-to-Point Protocol
PQCBWFQ
PQ
Priority Queuing
QoS
Quality of Service
RADIUS
SIP
SLA
SNMP
SP
Service Provider
TACACS+
WAN
WFQ
WRED
1.5 REFERENCES
Reference Number
Document Title
Document Reference
2
1.1 APPROVAL.............................................................................................................................. 2
1.2 CHANGE CONTROL................................................................................................................... 2
1.3 DISTRIBUTION.......................................................................................................................... 2
1.4 GLOSSARY OF TERMS............................................................................................................... 2
1.5 REFERENCES........................................................................................................................... 3
1.6 TABLE OF CONTENTS................................................................................................................ 3
1.7 LIST OF FIGURES .................................................................................................................... 4
1.8 LIST OF TABLES....................................................................................................................... 4
2 INTRODUCTION
6
2.1 OBJECTIVES............................................................................................................................ 6
2.2 INTENDED USERS..................................................................................................................... 7
2.3 SCOPE.................................................................................................................................. 7
Page 3 of 28
Page 4 of 28
16
Page 5 of 28
2 INTRODUCTION
This document serves as best practice configuration guide for connecting Avaya IP office PBX systems to
VoIP.co.uk SIP Trunk call termination services.
The purpose of this document is to provide system integrators with the tools and notes necessary to deploy
Avaya IP office systems correctly, built for best performance and reliability.
2.1 OBJECTIVES
The main objective of this document is to provide information relating to the IP network connectivity and SIP
related configuration of the IP office 500 systems including:
IP connectivity routing
Access control
Unit IP configuration
DNS
Telephony settings
SIP LINE
Number reporting
Page 6 of 28
2.3 SCOPE
This document covers the tasks required to connect an Avaya IP office PBX to VoIP.co.uks SIP Trunking
network. This document is to be used in conjunction with documentation from the PBX vendor and is not a
complete PBX configuration guide
This document assumes that the reader has a working knowledge of IP networking systems and basic
configuration understanding of the PBX product.
Page 7 of 28
Physical Interface
Software reference
Default IP configuration
LAN
LAN1
192.168.42.1
WAN
LAN2
192.168.43.1
The out of the box configuration of the IPO includes a DHCP server enabled by default. It is recommended that
initial configuration is carried our on an isolated network segment to avoid potential disruption to a working IP
network.
The IPO supports a variety of devices including Analogue, Digital and IP telephones.
Configuration of the device is made using the Avaya IP Office Manager program. It is recommended that the
software running on the IPO is kept up to data. Is should be noted that IP telephones run a software program
internally and this software should also be maintained.
Page 8 of 28
4 IP CONNECTIVITY
This section is relevant to customers using the Public Internet for connectivity. Leased line and private network
customers should contact their account manager for further information.
4.1 NAT
Deploying VoIP systems behind NAT gateways is complex and is not always successful. The following items
needs to be taken into consideration.
RTP pin-holing
SIP signalling
VoIP.co.uk have implemented tools within the network to make operating behind NAT as successful as possible
however certain IPO features do not operate reliably in this configuration, specifically PBX based call forwarding
which can result in no-audio calls. In addition small network routers struggle to forward the vast quantity of small
Voice-data packets on a busy connection while performing NAT. For this reason VoIP.co.uk recommends that
IPOs are configured using a non-RFC 1918 address i.e. a publically routed IP address. VoIP.co.uk
recommend that an IPO is not used behind a NAT device where possible taking the network security issues into
consideration. An added benefit is that remote IP access from the PBX maintainer can be allowed.
Notes
It should be noted :
1. When a SIP device such as the IP office is configured with a publically routed real IP address, this
address should never pass through an additional device performing NAT.
2. If an IP office is deployed behind a NAT device, IP address in use must be RFC1918 compliant, i.e. a
private network address range, 10/8, 172.16/20, 192.168/16.
3. If an IP office is deployed behind a NAT device , any ALG running on the NAT device should be disabled
for SIP
4. Network Access control must be implemented for network security when using a real IP address. A
network device should be made available for this to be implemented.
Page 9 of 28
4.2 IP ROUTING
The IPO has two Ethernet Interfaces. The WAN port should be used to route traffic to the WAN. The LAN port
should be used to connect to an internal LAN used for the deployment of IP telephones. Single interface use is
possible in a behind NAT configuration. It is out of scope of this document to fully describe the IP networking
features of the IP office.
An ISP typically offers a single publically routed IP address. It is necessary to ensure that a /29 subnet is made
available by the ISP to enable the connection.
Example installations are shown below. For completeness an IP office is shown connected behind a NAT device,
however this is not recommended by VoIP.co.uk.
PSTN
Public
Internet
NAT Router
IP406 Office
IP500
E XPANSIO N PO RTS
1 2 3 4 5 6 1
ISDN P ORTS
3 4 5 6 7
W AN
1
LAN
UPLINK
8
Page 10 of 28
PSTN
Example IP PBX
configured with a real IP
address
Public
Internet
IP406 Office
IP500
E XPANSIO N PO RTS
1 2 3 4 5 6 1
ISDN P ORTS
3 4 5 6 7
W AN
1
LAN
LAN port
UPLINK
8
WAN port
IP SUBNET allocated by ISP
LAN
RFC 1918 address
Page 11 of 28
No NAT
PSTN
Example IP PBX
configured with a real IP
address
Public
Internet
IP406 Offic e
IP500
EXPANSION PORTS
ISDN PORTS
WAN
1 2 3 4 5 6 1 2 3 4 5 6 7 8 1
LAN
LAN port
UPLINK
8
No NAT
Page 12 of 28
Rule
Number
Description
Policy
Protocol
Port
Number
From
VoIP.co.uk
Allow
IP
n/a
193.203.210.0/23 Local
subnet
Both
PBX
maintainer
Allow
TCP
23
<maintainer IP>
Local
Subnet
Inbound
Remote
upgrade
Allow
UDP
69
Local subnet
<Maintainer Outbound
IP>
Deny All
Deny
Any
N/A
Any
Any
Page 13 of 28
To
Direction
Both
5 IP OFFICE CONFIGURATION
This section assumes that a real IP address is being configured on the IP office WAN port with onward routing to
the Public Internet. The LAN port is used for local access by IP telephones and system admin.
Configure System/Unit/LAN1/LAN Settings with the IP address required for the LAN Interface. A DHCP
server is available for automatic configuration of IP telephones, however this may need to be reviewed.
o
We assume that there is no requirement for the IP office to be an IP router, so ensure Enable
NAT is disabled and RIP mode is set to none.
Configure System/Unit/LAN2/LAN Settings with the IP address required for the WAN Interface.
A DHCP server is unlikely to be required, however this may need to be reviewed.
Ensure the Firewall profile is set to none. Avaya Documentation should be consulted if you
need to use the IP office as a network router.
Configure IP Route and configure the Default route for the PBX. In general the default route gateway IP
address should be set to the Network router on the WAN port (LAN2).
Page 14 of 28
Create A SIP line for VoIP.co.uk by clicking on Line and selecting create a new record SIP line
Complete the form with the following values:
Page 15 of 28
Line Number
ITSP IP Address
Registration Required
YES
In Service
YES
NO
NO
Re-Invite Supported
YES
Leave as default
Compression Mode
Automatic Select
Layer 4 Protocol
UDP
None
Send Port
6060 or 5060
Receive Port
6060 or 5060
Page 16 of 28
5.3.2
Click on the SIP URI tab of the new SIP Line previously created.
The IP Office uses Line Groups to identify inbound and outbound connections. The SIP URI settings are used to
create and map the Line Groups to VoIP.co.uk
5.3.2.1 Inbound connections (VoIP.co.uk to IP Office)
Identify your Inbound Line Group. We assume the default of zero 0 is used.
Click Add...
Page 17 of 28
Via
None
Local URI
Contact
Display Name
Registration
Primary
Incoming Group
0 or as required
Outgoing Group
Click OK and when the configuration is saved back, the IP office is now ready to receive calls.
Page 18 of 28
A Line group number that will be used the this part of the configuration, but will not be used elsewhere
on the system
For the purpose of this example, the outgoing line group number is 9 and we use 20 as the not used elsewhere
line group
Page 19 of 28
Click ADD on the SIP URI Tab to add a URI and configure as follows.
Table 5 - Outbound SIP Line Configuration
Via
<None>
Local URI
Contact
Display Name
Registration
Incoming Group
Outgoing Group
Page 20 of 28
5.4.1
BASIC ARS
50 (our example)
Route name
In Service
YES
Time Profile
N/A
N/A
Page 21 of 28
5.4.2
DIAL PLAN
Code
N;
Feature
Dial
Telephone number
N"@proxy.voip.co.uk;user=phone"
Line Group ID
9 (or as configured)
Local
<Blank>
Not ticked
Page 22 of 28
Once the Default dial plan entry has been configured it is possible to send calls to VoIP.co.uk. There will be a 5
second delay after the last digit is dialled unless the number is suffixed with a hash #.
To improve the dial plan and eliminate the dial delay, it is recommended that the dial plan is extended simply to
match common dialled numbers.
Create additional entry into the dial plan as follows
Table 8 - Improved Dial Plan
Code
01XXXXXXXXX
Feature
Dial
Telephone number
.@proxy.voip.co.uk;user=phone
Line group ID
Local
N/A
N/A
Add an entry into the dial plan to match simply the UK dial plan. A complete table is shown below
Page 23 of 28
01XXXXXXXXX
UK Fixed
02XXXXXXXXX
UK Fixed
03XXXXXXXXX
UK NGN
04XXXXXXXXX
Mixed
05XXXXXXXXX
Mixed
06XXXXXXXXX
Mixed
07XXXXXXXXX
Mainly UK Mobile
08XXXXXXXXX
Mixed
09XXXXXXXXX
Mixed
N;
Page 24 of 28
Withheld
6.1.1
The following parameters can be set as a company default policy for CLI
CLI withheld
CLI shown
o
Pilot number
Page 25 of 28
6.1.2
Build a table of PBX users, their SIP name and the CLI required.
Example
PBX USER
Required CLI
Ian Wilkinson
Extn201
02071411001
Bob Millar
Extn202
02071411002
Sarah Hills
MD
02071411003
Emily Bishop
emily
02071411004
Page 26 of 28
VoIP.co.uk in general generate Invoices monthly. A set of Call Data Records are summed into an Invoice line
item and Invoice notification set.
PBX user reports are available if the PBX user is setup on the https://my.voip.co.uk/FromMap website as
described within this document.
Click Call Records / Download for the CDRs and Call spend reports.
Page 27 of 28
Page 28 of 28