Installation guide

SHOW ACLI COMMANDS N - Z
Version S-C6.1.0 Oracle Communications Session Border Controller ACLI Reference Guide 83
This command displays Local Routing Table (LRT) statistics on the Net-Net SBC.
Arguments <route-entry> Display a specific entry in the LRT
<stats> Display all LRT statistics
Example ACMEPACKET# show lrt stats
show mbcd
Syntax show mbcd <mbcd-stats>
The show mbcd command displays MBCD statistics for your Net-Net SBC.
Arguments <mbcd-stats> The following is a list of all mbcd-stats:
Values • statistics—Display information related media flows
established by the MBCD task. The following is a list of the
MBCD statistics displayed when you enter this command:
–Client Sessions—Number of media sessions established by
application clients of the MBCD task. Clients of MBCD
include all signaling protocol tasks (SIP, MGCP, and H.323).
–Client Trans—Number of MBCD transactions in the
application clients to create, modify and remove flows
–Contexts—Number of Contexts in the MBCD task. A
Context represents the MBCD Server side of a media session.
It contains all flows for the media session.
–Flows—Number of unidirectional flows established in
MBCD. This includes both static flows defined by the
signaling configuration, and dynamic flows for media
sessions.
–Flow-Port—Number of "anchor" ports established by
MBCD. MBCD maintains a mapping of the RTP steering port
allocated for a flow so it can recognize flows that hairpin or
spiral through the SD. This statistic reflects the number of
entries in that table.
–Flow-NAT—Number of entries in the MBCD table that
maps CAM entry indexes to flows. An entry is added to this
table when a NAT entry is added to the CAM for a flow.
–Flow-RTCP—Number of special NAT table entries for
RTCP. For Hosted NAT Traversal (HNT), the RTP and RTCP
flows must be treated separately because the source port of
the RTCP cannot be predicted.
–Flow-Hairpin—Number of hairpined/spiraled flows
recognized by MBCD. This occurs when the signaling
originates in an access realm, goes into a backbone realm, and
then back into the same access realm, or another access realm
on the same network interface.