76 System description

Fallback in IP Trunk3.01 (and later)

In QoS monitoring, the local node queries the remote node and gets a
response; the remote node queries the local node and gets a response.
If the remote node cannot query the local node, QoS monitoring is not
available. When an IP Trunk 3.01 (and later) node uses a Gatekeeper to
resolve an address, IP Trunk3.01 (and later) cannot monitor QoS and
provide fallback. This function resides with the device resolving the address.
As a result, for all calls going to the Gatekeeper, such as in IP Peer
Networking, no fallback can occur. The call either goes through with
possibly a lower QoS, or the call clears instead of falling back. All QoS
control is in the hands of the Gatekeeper.
However,for calls using the ATPM static address tables, the IP Trunk 3.01
(and later) Leader retains awareness of network status and can cause
fallback to the PBX, if needed.
The full QoS fallback function is availablefor locally provisioned addresses.

IP Peer and Qos

The IP Peer Networking nodes do not support QoS monitoring. The
capability must be enabled for both sides in order forit to work, but it
cannot be enabled for IP PeerNetworking. Therefore, do not enable QoS
monitoring for any numbers terminating on an IP PeerNetworking node. If
this is done, the IP Peer Networking node is unreachablefor that IP Trunk
3.01 (and later) node.
IP Trunk3.01 (and later) nodes can perform QoS monitoring only on remote
IP Trunk3.01 (and later) nodes provisioned locally with SL1, SL1 with ESN5
node capabilities.

Return to the IP network

Unless the DCH is down and all trunks appear busy to the system, outgoing
calls are introduced to the IP Trunk3.01 (and later) node. Eachcall is tested
against the outgoing address translation and Quality of Service (QoS)
for the destination node. After the QoS returns to an acceptable level,
all new outgoing calls are again routed through the IP network. The call
connections that were established under the fallback to alternate facilities
condition are not affected.
Type of Service
The IP packet handler has a byte of data forType of Service (ToS). This
byte allows the user to indicate a packet’sprior ity so that routers can more
efficiently handle data packets. For example, a router can decide to queue
low priority data while immediately passing packets marked as high priority.
Nortel Communication Server 1000
IP TrunkFundamentals
NN43001-563 02.01 Standard
Release 5.5 21 December 2007
Copyright© 2007, Nor tel Networks
.