Справочник Пользователя для Nortel Networks Recording Equipment 1
Voice over Wireless LAN Solution Guide
v1.0
December 2005
______________________________________________________________________________________________________
Page 46
0x00 to 0x30 (110000) corresponding to the CS6 class. All other DSCP/ToS values are left
untouched. Note that this assumes that the WSS 2300 is not connected to the ERS through a
one-arm connection such that CAPP and regular (unencapsulated) user traffic are on the same
port.
untouched. Note that this assumes that the WSS 2300 is not connected to the ERS through a
one-arm connection such that CAPP and regular (unencapsulated) user traffic are on the same
port.
An ERS 8300 port connected to an AP2330 at Interface A would be configured to mark all traffic
with DSCP value of 0x2e (101110) corresponding to the EF class. The easiest way to accomplish
this is with a port level QoS setting.
with DSCP value of 0x2e (101110) corresponding to the EF class. The easiest way to accomplish
this is with a port level QoS setting.
2.5.4.2 Prioritizing/marking
interswitch (WSS 2300) traffic
The classification techniques for an ERS 8300/8600 at Interface B do not differ from the ES. The
marking behavior is also as described for the ES.
marking behavior is also as described for the ES.
2.5.4.3 Prioritizing/marking
SVP
Because the ERS 8300/8600 has the same restriction on user-defined IP protocol numbers as
the ES family, the recommended filtering criteria at Interface C is the same as for an ES at
Interface C. As in the ES case, the filter on a port connected to a WSS 2300 matches the
destination IP address field against the node address of the WTM 2245 and marks the DSCP
value as 0x2e.
the ES family, the recommended filtering criteria at Interface C is the same as for an ES at
Interface C. As in the ES case, the filter on a port connected to a WSS 2300 matches the
destination IP address field against the node address of the WTM 2245 and marks the DSCP
value as 0x2e.
A port connected to the WTM 2245 can be configured to simply trust the markings set by the
WTM 2245.The WTM 2245 should also be set to mark traffic with a DSCP value of 0x2e.
WTM 2245.The WTM 2245 should also be set to mark traffic with a DSCP value of 0x2e.
2.5.4.4
Prioritizing/marking native VoIP traffic
As noted previously, it is assumed for purposes of this discussion that remote VoIP telephones,
call servers, and LAN switching equipment are properly marking and classifying traffic. Locally as
the VoIP packets leave the WTM 2245, they will be classified properly if the ERS 8300/8600 is
set to trust markings.
call servers, and LAN switching equipment are properly marking and classifying traffic. Locally as
the VoIP packets leave the WTM 2245, they will be classified properly if the ERS 8300/8600 is
set to trust markings.
2.5.5 QoS
summary
Regardless of the switch model at any of the interfaces described in this section, there are many
general requirements that can be summarized on a per-interface basis. At Interface A, the main
need is to prioritize CAPP. Interface B needs to prioritize CAPP as well as interswitch
authentication and roaming traffic. Lastly, Interface C will be forwarding both native voice and
SVP, though you should implement Interface C as a trusted port because the WTM 2245 can
mark its own traffic.
general requirements that can be summarized on a per-interface basis. At Interface A, the main
need is to prioritize CAPP. Interface B needs to prioritize CAPP as well as interswitch
authentication and roaming traffic. Lastly, Interface C will be forwarding both native voice and
SVP, though you should implement Interface C as a trusted port because the WTM 2245 can
mark its own traffic.
2.6 WLAN Handset 2210/11/12, IP Softphone 2050, MVC
2050, and MCS Client support on the same network
It is a relatively easy task to design a WLAN and LAN for one type of VoWLAN device, such as
WLAN Handsets 2210/11/12. However, many customers may want a comprehensive VoWLAN
implementation, including soft phones on PCs and PDAs in addition to dedicated handset
devices. Designing a network to adequately support all types simultaneously is much more
challenging because of the different QoS implementations and auxiliary devices used.
WLAN Handsets 2210/11/12. However, many customers may want a comprehensive VoWLAN
implementation, including soft phones on PCs and PDAs in addition to dedicated handset
devices. Designing a network to adequately support all types simultaneously is much more
challenging because of the different QoS implementations and auxiliary devices used.
2.6.1 Issues
Most of these challenges relate to the fact that the soft clients do not use SVP while the handsets
do. Having two different QoS solutions implemented side by side creates a number of problems
that must be resolved. Note that there is currently no perfect solution that does not require
compromise in some key areas. You may need to make difficult decisions in order to support both
do. Having two different QoS solutions implemented side by side creates a number of problems
that must be resolved. Note that there is currently no perfect solution that does not require
compromise in some key areas. You may need to make difficult decisions in order to support both