Bridge Traffic Analyzer free download, Bridge Traffic Analyzer download on software download

The Bridge Traffic Analyzer application was designed to be a tool that allows administrators to obtain traffic data on their Cisco Bridge units to determine: · total size of messages sent · number of messages sent · which servers messages have come from or gone to · how long it takes for messages to arrive at their destinations · how many analog ports are in use for message transport · How many failures were there sending and receiving messages between various nodes Main features: Message Queue Activity Report: The Message Queue Activity report shows how many messages and how much data is passing through the inbound and outbound message queues on the Bridge server. Inbound messages are those traveling from Octel nodes to the Bridge via analog lines and then to the Cisco Unity servers via IP; outbound messages are those traveling from Cisco Unity to the Bridge via IP and then to Octel nodes via analog lines. Outbound message traffic is the more interesting item to analyze, because this is where bottlenecks may occur. Cisco Unity can quickly route messages to and from the Bridge via IP. It is the ability of the Bridge to get messages out of the queue and to the Octel nodes that may be a problem. Therefore, it is not likely that the inbound message queue will grow very large, but the outbound message queue can back up if port resources are not sufficient to handle the load. Port Availability Report: The Port Availability report does not take any parameters; instead, it processes analog port activity on the log for the entire day. The purpose of this report is to show how many analog ports on the Bridge are being used to communicate to Octel nodes at any given time of the day. The report shows a bar for each minute of the day, indicating how many ports are in use and/or how many ports are available to take calls. You can choose to show busy ports, ports available to take calls, or both, by checking the checkboxes at the top of the report form. The Port Availability report can show the entire day, or you can use the Zoom menu to show a 12-hour, 4-hour, or 1-hour chunk of the day. The following screen shot shows an hour of port activity from 6:15 pm to 7:15 pm (all times are shown in 24-hour clock format). The report was set up with the default mode of showing the number of analog ports available to take or make calls on the Bridge server. Note that as the bars get closer to 0, the number of ports available for processing new messages goes to 0. This report format makes it easier to see when port resources are getting critically low. The Bridge does contain logic to terminate message delivery calls in order to free up analog ports when the number of available ports approaches 0, therefore making sure that ports are available to handle inbound calls from Octel nodes. However, heavy inbound message traffic from Octel nodes through to Unity nodes can chew through all the available ports. Message Latency Report: The Message Latency report is designed to allow you to see how long messages sit in the outbound queue before they are delivered to the Octel nodes via the analog lines on the Bridge. This report shows only the outbound messages because inbound messages that arrive on the Bridge are delivered to Cisco Unity via IP, and therefore the total time in the queue is very short. Outbound messages, on the other hand, arrive from Cisco Unity via IP, enter the queue, and then are delivered via analog lines to the target Octel node. If port resources are limited on the Bridge unit, messages can wait in queue for delivery for a long time and thus create a bottleneck. The Message Latency report allows you to select a time range (the default is a full 24 hours for the log selected) and which nodes to include in the report (the default is all nodes in the log selected). In the following screen shot, the report is set to show messages going from a particular Cisco Unity node to a specific Octel node. The Limit Report Data to Messages Involving These Specific Nodes check box is checked, as are the applicable Unity node and Octel node check boxes. You must select at least one Octel and one Unity node in order to run this report. Node Message Traffic Report: The Node Message Traffic report shows how many messages and how much data is passing between different Unity and Octel nodes. For example, this report can show which Octel nodes a specific Cisco Unity node messages with most heavily. As with the Message Latency report, you can select one or more Unity nodes, one or more Octel nodes, and a time range to run the report against. In the following screen shot, one Unity node was selected (node ID 80100), and all the Octel nodes that showed up in the log were selected (nodes 80200 and 80300). The report shows inbound traffic from Octel to Cisco Unity as a factor of message size (shown in megabytes). It is immediately apparent that Cisco Unity is getting far more data from node 80200 than from the other node. Non-delivery Notifications Report: The Non-delivery Notifications (NDN) report shows which nodes received or sent failure messages as a result of messages that were rejected for whatever reason (full mailbox, destination not valid, transmission error etc…). Inbound NDNs are those that Unity gets in response to a message it was sending that got rejected by the remote Octel node for whatever reason. An Outbound NDN is a message that Unity sends in response to rejecting an inbound message for whatever reason.

Bridge Traffic Analyzer Related Software