Getting started with the 8378 DECT IP-xBS solution
on OXO
8AL90357ENAAed01
26
/
37
OXO DHCP server configuration could be modified here:
⇒
OMC
→
Hardware and Limits
→
LAN / IP Configuration
→
DHCP
8.3 TFTP
The embedded TFTP servers must be used to take benefit of the auto-discovery feature.
The TFTP server address is given to the xBS by the DHCP server.
It is not possible to use any external TFTP server.
8.4 VLAN
A network can be segmented with VLANs. VLANS (defined by IEEE 802.1q) must be used
at switch level:
•
to identify and prioritize voice flows (with QoS mechanisms),
•
to reduce the broadcast domain for the ports belonging to the VLAN and/or
•
to carry the prioritization and VLAN identifications between switches
Generally, a VLAN policy is already implemented throughout the customer network and it is
based on port, MAC address, IP sub-net, etc.
VoIP deployment must either follow the existing VLAN policy rules or if any, a Voice
VLAN(s) must be configured. The use of VLAN for VoIP is recommended to separate RTP
and associated SIG traffics from the data traffic (from data broadcast traffic for ex.). It is
generally called “Voice VLAN”. The Call Server embedded DHCP server will send to the
xBS the Voice
“VLAN id” to use.
VLAN can also be configured via the switch using the LLDP protocol or using the WBM or
via DHCP option 43 sub-option 58.
In case of one VLAN for all xBS, the network infrastructure products must be sized and
configured in terms of:
•
Bandwidth: infrastructure network equipment must be able to handle the traffic
generated by xBS especially during their initialization.
•
ARP table: the ARP table of the infrastructure network equipment must be sized to
handle the xBS ARP requests.
xBS VLAN tagging (through the WBM) is not necessary because contrary to an IP phone
there is no PC connected behind the xBS. The VLAN assigned to the xBS will be done by
the switch itself. The switches must
be “managed” switches to support VLAN.
