Site Survey Avaya SBCE

Download as pdf or txt
Download as pdf or txt
You are on page 1of 9

SBCE Survey

Avaya Professional Services


Instructions

This form requires Adobe Reader 7.0 or higher to be interactive. Please use the interactive feature to
fill out ALL the fields to the best of your knowledge. Change the color of the square to indicate a yes
for the statement or question.

Avaya Project Information

E-project Number
Sold-To #
SAP #
Project Manager
Phone E-mail

Customer Location Deployment Information

Customer Company Name


Customer Contact (full name)
Customer Contact e-mail address
Customer Contact telephone number
State/Province (if US or Canada) Zip
Country

Date of service provider install

Checklist
❑❑ A current network diagram has been provided by the customer.
❑❑ Automatic Registration Tool (ART). (Not required if IPO install)
❑❑ SAL registration is completed. (Not required if IPO install)
❑❑ GRT (Global Registration Tool) is completed. (Install base record)
❑❑ SSL/VPN On boarding completed. (Technical registration)
❑❑ PLDS licensing is completed.

Other Important Information

***This SBCE project has been installed, tested, and completed on this date

Avaya Inc. – Proprietary & Confidential.


1 Use pursuant to the terms of your signed agreement or Avaya policy.
V2.7
Please select all that apply
❑❑ Standalone SBCE Combo
❑❑ Standalone SBCE with separate EMS Server
❑❑ High Availability Pair
❑❑ IP Office
❑❑ Service Provider Trunking
❑❑ Remote Worker
❑❑ Recording (Forking)
❑❑ Video
❑❑ Refer handling

***These passwords can be changed at any time after the installation is complete.

Password Rules
Sipera Console password - Must be a minimum of 8 characters long, must contain at least two (2)
uppercase characters, not including the first character of the password, 1 lower case, 1 special, must
contain at least two (2) digits, not including the last character of the password.

EMS GUI password - Must be a minimum of 8 characters long, must contain a mix of an upper and
lower case, 1 special character and 1 number.

Password Information
Please enter a password of mixed case which is eight or more characters long and contains at least
one special character and one number.
IPCS (Console)
ROOT (Avaya)
UCSEC (EMS GUI)

Customer Network Information


Specify the location (enterprise management network of SIP trunk provider network) and IP address.
You can specify more than one DNS IP Address. Some networks separate the management DNS from
the applications DNS. An NTP provided timeserver is preferred, specify the IP address, otherwise
time synchronization will be performed by the EMS.

DNS Server IP
NTP Server IP

***If the enterprise wants to integrate the SBCE with other systems, those must be specified.

SNMP (Optional)
Trap Server IP
Community String ❑❑ v2 ❑❑ v3

Avaya Inc. – Proprietary & Confidential.


2 Use pursuant to the terms of your signed agreement or Avaya policy.
V2.7
Radius (Optional)
❑❑ Radius will be used for SBCE GUI login authentication.
Radius Server IP Login

Syslog (Optional)
Server IP
Recording Server Model/Release
MAC ❑❑ QR ❑❑ CCR ❑❑ CCR w/ RMR
Other

SFTP Server automatic database backups (Optional)


IP Port
User Name Password
File repository

Customer Server Connection Information


Hardware
Server IP
Port ❑❑ UDP ❑❑ TCP ❑❑ TLS
Release
Domain
FQDN
Media Ports

Notes:

Service Provider Connection Information


Vendor Name
Provider IP
Port ❑❑ UDP ❑❑ TCP ❑❑ TLS
Domain
FQDN
Media Ports
❑❑ Registration or Authentication is required from SBC
User Name URI
SIP Method ❑❑ Register ❑❑ Other
Authentication

The SBCE appliance can be deployed in a one-wire or two-wire deployment. In a one-wire configu-
ration, one Ethernet port (internal/external interfaces) is used with two IP addresses in the same
subnet. In a two-wire configuration, two Ethernet ports are used with two IP addresses in different
subnets. (Two wire is more typical)

❑❑ One-Wire ❑❑ Two-Wire

Avaya Inc. – Proprietary & Confidential.


3 Use pursuant to the terms of your signed agreement or Avaya policy.
V2.7
***The Management (M1) interface IP must be on a separate subnet from the A1/B1 interfaces.
Please keep that in mind when filling out the network information.

EMS Server Server Serial Numbers


Appliance Name EMS
IP Address 1 SBC1
Network Mask SBC2
Gateway
Ethernet M1 (Primary) Ethernet M1 (HA Standby)
Appliance Name Appliance Name
IP Address 1 IP Address 1
Network Mask Network Mask
Gateway Gateway

Trunking
When using HA the A1 (internal) interface needs to be on separate Vlan from the customer media
resources so that the switch will handle GARP unless you have a switch capable of handling GARP
with the SBC on same Vlan as the Media gateway. If on the same Vlan you can see one-way audio
due to the Media Gateway not supporting GARP. The recommendation is to place the M1 interface
on the same subnet as the PBX keeping A1 interface on a separate subnet. This means that a mini-
mum of 3 subnets or vlans will be utilized for this installation.

Ethernet A1 (Trunking) Ethernet B1 (Trunking)


IP Address 1 IP Address 1
Network Mask Network Mask
Gateway Gateway

Remote Worker
If using SBC remote worker you will need one IP for A1 and two for B1. This is to have one external
IP set for file serving to the hard phones the other is for SIP, PPM (Personal Profile Management) and
Presence. These are separate from any trunk interface IP’s that may be needed as well.
Ethernet Internal A1 (Remote Worker) Ethernet External B1 (Remote Worker)
IP Address 1 IP Address 1
IP Address 2
Network Mask Network Mask
Gateway Gateway

Please indicate set types to be used with the Remote Worker feature:

Avaya Inc. – Proprietary & Confidential.


4 Use pursuant to the terms of your signed agreement or Avaya policy.
V2.7
Interworking
Provide information about any inter working required to be done on the SBC for PBX and Trunk side.
For complex header manipulation needs, please describe in the space provided.

Inside (PBX)
Media / Signaling QoS: ❑❑ Yes ❑❑ No
Fax: ❑❑ T.38 ❑❑ Other
Topology Hiding: ❑❑ None ❑❑ Auto ❑❑ Overwrite

Outside (PSTN)
Media / Signaling QoS: ❑❑ Yes ❑❑ No
Fax: ❑❑ T.38 ❑❑ Other
Topology Hiding: ❑❑ None ❑❑ Auto ❑❑ Overwrite

If there are any custom items such as header manipulation, early media, or DTMF interworking,
please indicate these option settings in the interworking notes section below.

Interworking Notes:

Sessions

Concurrent sessions required


❑❑ TLS encryption required
❑❑ SRTP encryption required

Please indicate lower and upper UDP port range if required. SBC default is 35000-40000.
UDP Port Min: (2048)
UDP Port Max: (65535)

Avaya Inc. – Proprietary & Confidential.


5 Use pursuant to the terms of your signed agreement or Avaya policy.
V2.7
DMZ Security

Some enterprises require a data firewall for all external connections – even for SIP trunks. This is rare
though. If firewalls exist, please note if they are performing any NAT / PAT and ALG functions. If
NAT is being used, provide the routable IP address on the pbx side and the routable IP address on the
provider side.

There is a firewall between the SBCE and the PBX.


❑❑ No ❑❑ Yes ❑❑ NAT/PAT ❑❑ ALG
If NAT’d, provide routable IP of SBCE

There is a firewall between the SBCE and the Provider.


❑❑ No ❑❑ Yes ❑❑ NAT/PAT ❑❑ ALG
If NAT’d, provide routable IP of SBCE

Avaya Inc. – Proprietary & Confidential.


6 Use pursuant to the terms of your signed agreement or Avaya policy.
V2.7
Port Information

Internal – Between one or more SBCs and the EMS


1. SSH TCP-222
2. HTTPS TCP-443
3. OpenVPN UDP-1194
4. Syslog TCP/UDP-514
5. NTP UDP-123

External – Between the EMS and SBCs and an external device


1. SSH TCP-222
2. HTTPS TCP-443
3. Syslog TCP/UDP-514
4. NTP UDP-123
5. DNS TCP/UDP-53 (for DNS and the signaling and media ports)
6. SNMP (Ver. 2 / 3) UDP-161 + 162 The SNMP agent receives requests on UDP port 161, and the
SNMP manager receives notifications (Traps and InformRequests) on port 162.

DNS server
If your DNS server is not in the DMZ, open UDP port 53 on the SBCs via the EMS GUI so the
SBCs can access the DNS server.

SNMP
If you have your own SNMP, open the SNMP UDP ports 161 and 162 on the SBCs via the EMS GUI so
the SBCs can access the SNMP from the DMZ.

Syslog
If you have your own Syslog, open the Syslog UDP port 514 on the SBCs via the EMS GUI so
the SBCs can access the Syslog from the DMZ.

Media ports
The default media port range is 35000 to 40000, but other media port ranges can be configured, if a
different media port range is required.

SIP signaling ports


The ports listed below are defaults. Other ports may be configured.
1. TCP/UDP 5060
2. TLS 5061

HTTP/HTTPS ports
These ports are used for Personal Profile Management (PPM) communications, configuration files
and firmware downloads. Configure these ports on the SBCs via the EMS GUI so the phones can
login and download configuration files from the Avaya HTTP server or HTTPS server.
1. HTTP port 8080 or port 80
2. HTTPS port 443

Avaya Inc. – Proprietary & Confidential.


7 Use pursuant to the terms of your signed agreement or Avaya policy.
V2.7
Reference Standalone Connectivity
**Different servers have different labeling.

B2 B1 A2 A1
M2 M1
Serial VGA

CLI

Public Private
DMZ
Firewall Firewall

Reference HA Connectivity
**Different servers have different labeling

Eth1 Eth2 EMS

B2 B1 A2 A1
M2 M1 SBC2
Serial VGA

B2 B1 A2 A1
M2 M1 SBC1
Serial VGA

CLI

Public Private
DMZ
Firewall Firewall

Avaya Inc. – Proprietary & Confidential.


8 Use pursuant to the terms of your signed agreement or Avaya policy.
V2.7
Program trunking reference diagram only

B1-Interface IP PSTN Network Configuration Enterprise A1-Interface IP

Device ports 35K-40K Media Interface Media Interface ports 35K-40K


Specific
Settings udp,tcp.tls Signal Interface Signal Interface udp,tcp.tls

Global Server Interworking Server Interworking


Profile T38 T38
Manipulation Manipulation

Server Configuration Server Configuration


type, transport type, transport
Advanced Advanced

Next HOP Routing Routing Next HOP


Auto Topology Hiding To,From,Request
Topology Hiding
line (if req'd)
Domain Application Rules Application Rules
Policy Video, Sessions Video, Sessions
Endpoint Policy Endpoint Policy
Group Group
Device Server Flows Server Flows
Specific
Settings Server Conf Server Conf
Recv Interface Recv Interface
Sig Interface Sig Interface
Media Interface Media Interface
Endpt Policy Endpt Policy
Route Profile Route Profile
Topology Hiding Topology Hiding
Tue Dec 11 2012

Avaya Inc. – Proprietary & Confidential.


9 Use pursuant to the terms of your signed agreement or Avaya policy.
V2.7

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy