User's Manual
Table Of Contents
- About This Manual
- Contents
- Figures
- Tables
- Chapter 1 - System Description
- 1.1 Introducing BreezeMAX
- 1.2 Base Station Equipment
- 1.3 Networking Equipment
- 1.4 Management Systems
- 1.5 Specifications
- 1.5.1 Radio
- 1.5.2 Base Station 2.X GHz Antennas (Optional)
- 1.5.3 Base Station 3.x GHz Antennas (Optional)
- 1.5.4 ˘AU-IDU to AU-ODU Communication
- 1.5.5 Data Communication (Ethernet Ports)
- 1.5.6 Configuration and Management
- 1.5.7 Environmental
- 1.5.8 Standards Compliance, General
- 1.5.9 Services
- 1.5.10 Physical and Electrical
- Chapter 2 - Installation Guidelines
- 2.1 Installing the AU-ODU
- 2.2 Installing the Base Station Equipment
- 2.2.1 BST Installation Requirements
- 2.2.2 BMAX-BST-SH Chassis Slot Assignments
- 2.2.3 Power Requirements
- 2.2.4 HOT SWAP Support
- 2.2.5 Power Interface Unit (PIU)
- 2.2.6 Power Supply Unit (PSU)
- 2.2.7 Access Unit Indoor Module (AU-IDU)
- 2.2.8 Network Processing Unit (NPU)
- 2.2.9 Using the Hot Swap Injector/Ejector Handles
- 2.2.10 Installing the Base Station Chassis and Modules
- 2.2.11 Air Ventilation Unit (AVU)
- 2.2.12 Replacing Base Station Components
- 2.3 Installing the ODU Power Feeder
- 2.4 Installing the GPS Adapter
- Chapter 3 - Commissioning
- Chapter 4 - Operation and Administration
- 4.1 BreezeMAX System Management
- 4.2 The Monitor Program
- 4.3 IP Addresses Configuration
- 4.4 ˘The NPU's Main Menu
- 4.5 Base Station Menu
- 4.5.1 Show
- 4.5.2 Configuration
- 4.5.3 Alarms and Traps
- 4.5.4 RADIUS
- 4.5.5 ˘˘˘Licenses
- 4.6 ˘NPU Menu
- 4.7 Radio Cluster Menu
- 4.8 ODU Menu
- 4.9 AU Menu
- 4.9.1 Show Summary
- 4.9.2 Upgrading AU’s SW
- 4.9.3 SW Files in NPU
- 4.9.4 Select
- 4.9.5 AU Slot # Menu
- 4.9.6 Performance Monitoring
- 4.10 SU Menu
- 4.10.1 Show Summary
- 4.10.2 Show Summary by AU
- 4.10.3 Upgrading SU’s SW
- 4.10.4 ˘SW Files in NPU
- 4.10.5 Select by Name
- 4.10.6 Select by MAC Address
- 4.10.7 SU # Menu
- 4.10.7.1 Show
- 4.10.7.2 Unit Control
- 4.10.7.3 Configuration
- 4.10.7.3.1 Registration Parameters
- 4.10.7.3.2 MAC (Standard FDD) Parameters
- 4.10.7.3.3 Phy (Standard FDD) Parameters
- 4.10.7.3.4 Multirate and ATPC Parameters
- 4.10.7.3.5 Voice/Networking Gateways
- 4.10.7.3.6 Ethernet Port
- 4.10.7.3.7 Installer Password
- 4.10.7.3.8 ˘Bridging Parameters
- 4.10.7.3.9 License
- 4.10.7.3.10 Best BST/AU (Advanced Si)
- 4.10.7.3.11 Radio Parameters (Advanced Si)
- 4.10.7.4 Performance Monitoring
- 4.10.7.5 Show MAC Addresses Behind SU
- 4.10.7.6 Delete
- 4.10.8 Add New SU
- 4.10.9 Clear All Configured SU SW Files
- 4.11 Services Menu
- 4.11.1 Introduction to Services
- 4.11.2 Introduction to Filtering Features
- 4.11.3 Common Operations in Services Menu
- 4.11.4 The Services Menu
- 4.11.4.1 General
- 4.11.4.2 Subscribers
- 4.11.4.3 Services
- 4.11.4.4 Service Profiles
- 4.11.4.4.1 Service Profile Name
- 4.11.4.4.2 Service Type
- 4.11.4.4.3 VLAN Transparency Mode
- 4.11.4.4.4 VPL ID
- 4.11.4.4.5 Priority Marking Mode
- 4.11.4.4.6 Priority Marking Value
- 4.11.4.4.7 Forwarding Rule
- 4.11.4.4.8 Priority Classifier (L2 and PPPoE Service Type)
- 4.11.4.4.9 Maximum Number of Voice Calls (L2 and VoIP Service Type)
- 4.11.4.4.10 Service Profile Class
- 4.11.4.5 Forwarding Rules
- 4.11.4.6 Priority Classifiers
- 4.11.4.7 QoS Profiles
- 4.11.4.8 Filtering Rules
- 4.11.4.9 Interface Filtering
- 4.11.4.10 Filtering Examples
- 4.11.4.11 MAC Addresses Deny List
- 4.11.5 Defining Service Profiles
- 4.11.6 Defining Local (Permanent) Services
- 4.11.7 Defining RADIUS Based Services
- 4.11.8 Pre-configured Profiles
- 4.12 NPU Parameters Summary
- Appendix A - Software Upgrade
- Appendix B - Defining Service Profiles for Generic VoIP Gateways
- Glossary
- Index
266 BreezeMAX Modular Base Station System Manual
Appendix B - Defining Service Profiles for Generic VoIP Gateways
B.1 Introduction
This section describes the method used for defining the pre-configured Service
Profiles for Generic (3rd party) VoIP devices that do not use the DRAP protocol.
The same principles can be used for modifying the pre-configured profiles or
creating new ones for VoIP services that have different characteristics.
B.1.1 Priority Marking
We distinguish between two types of Service Profiles for Generic VoIP devices:
Marking is not used: This scenario is applicable when the VoIP device behind
the SU does not support either DSCP or 802.1p marking to distinguish
between different VoIP related traffic types, or when such marking is not used
for any reason. The implication is that a single Continuous Grant connection
should be used for all VoIP traffic.
Marking is used: This scenario is applicable when the VoIP device is capable
of marking the different VoIP related traffic types. The assumption is that 3
different priority marks are used: One for RTP traffic, the second for RTCP and
VoIP Signaling, and a third one for Data (Device Management).
B.1.2 General Assumptions
Protocol Header: 18 bytes for Ethernet L2 header (including 4 bytes for
VLAN), plus 40 bytes of IP/UDP/RTP headers. A total of 58 bytes.
RTCP bandwidth: RFC 3556, Session Description Protocol (SDP) Bandwidth
Modifiers for RTP Control Protocol (RTCP) Bandwidth, states that normally, the
amount of bandwidth allocated to RTCP in an RTP session is 5% of the session
bandwidth. To be on the safe side allocate 10% of the RTP bandwidth to RTCP.
VoIP Signaling: Cisco states that its IP Phones generate approximately 150
bps signaling traffic (without L2 overhead). To be on the safe side assume 2
Kbps of VoIP Signaling traffic for each POTS interface.
Fax: Fax services are assumed to be based on T.38 Fax Relay. Protocol Header
is assumed to be 58 bytes (same as for RTP).
Data: Data traffic may include ARP, DHCP, TFTP, SNMP, HTTP and other
management protocols. The recommended default bandwidth value is up to 64