 |
||
United States
UK
 |
||
       |
||
 |
||
OmniPeek Product Family
AiroPeek SE & NX
AiroPeek VX
EtherPeek SE & NX
Hardware
Other Products
|
Since all WildPackets products make use of the underlying Operating System for all time computations, no patch will be necessary for our products to operate correctly with the new Daylight Saving Time Change. Important Vista Note: Vista Operating System has a facility for dynamic Daylight Saving Time calculations that takes into account the fact that different years may have different DST dates. The next release of the OmniPeek Product Family (available end of Jan. 2007) will include the code to use this new operating system facility. The end result is that everything will work correctly with Vista, but if a user has XP with the DST hotfix installed, the duration of captures that span the actual time change in past years may be incorrect since XP does not have the facility to understand that different years may have different DST dates.
EtherPeek VX 2.1 will load and run on 64 bit operating systems in 32 bit compatibility mode and supports AMD and Intel x86 processors including the 64 bit capable Pentium and Xeon processors.
G.711 µ-law
No, at this time Windows Server 2003 is not supported with EtherPeek VX.
Configuration changes in the VoIP view do not take effect unless packets are reprocessed. Packets are reprocessed by using the Edit->Reprocess All Packets menu item or by hiding and then unhiding packets via the Edit menu while the Packets view is active.
EtherPeek VX can only playback a single media channel and cannot playback an entire call which usually comprises of 2 or more media channels. Since VoIP quality will be different in each media channel, it is important to isolate these streams for troubleshooting. The following audio compression formats are supported for playback: G.711, G.723, G.729, G.726, GSM-AMR, GSM-FR For more information, please look in the online help (F1) for the Playback feature.
EtherPeek VX can analyze real time calls and saved traces files. For real time analysis, the limit is 100 simultaneous open calls. For trace file analysis, the limit is 5000 calls (packet details) and unlimited for statistics.
Yes, open calls change to closed calls when you stop the capture. This is the way the product was designed; EtherPeek VXcloses all open calls when the capture stops. However, there is a color-code that indicates which calls closed normally and which were terminated due to capture stoppage.
Yes. To ignore signaling:
(Note: After this, you will not see signaling on the VoIP view.)
This is an expected result when you run EtherPeek VX after un-checking the "Detect media only according to signaling" option. Unselecting this option tells EtherPeek VX to ignore signaling and so will not have any information in the signaling section. Valid reasons to unselect this option are when the network is using encrypted and/or proprietary signaling methods.
The first column (No.) is only a row number and it has no other meaning. The color coding in this column does have meaning, corresponding to the color key at the top of the table. The call number is the sequence number of the call, assigned in the order in which the call was detected. The sequence always begins with call number zero (0). Calls retain their Call Number when they move from the Open Calls to the Closed Calls table. For example, imagine there are 3 calls: call 0, call 1, and call 2. (Call 0 started first, call 1 started second, and call 2 started third.) Call 2 closes first. In the closed calls, the order of calls will be:
This error can sometimes point to the amount of memory in your computer. Please be sure that your system meets the required specifications.
You will need to create a VoIP Analysis Module .ini file.
Example *.gst file
The expert threshold is based on jitter as reported by RTCP packets. The expert converts the value in each RTCP packet to milliseconds, based on the codec (G.711, G.729. etc) being used by the RTP stream.
Packet Loss is calculated by looking at the RTP and RTCP headers generated by the endpoints on each side of a VoIP conversation and examining the sequence numbers in those headers. Any differences between the sequence numbers from packet to packet are counted as lost Audio packets. For instance, let’s say EtherPeek VXis examining a sequence of 200 RTP packets as part of a Voice call and the sequence number starts with 1001. If EtherPeek VXsees a gap in sequence numbers, such as 1020, 1021, 1026, 1027, 1028, it would be noted that 4 packets (1022, 1023, 1024, and 1025) were lost. If these were the only missing packets out of the 200, then the percentage of lost packets 4/200 * 100% = 2%.
EtherPeek provides the ability to capture error packets only by installing one of the special drivers located in the "Driver" directory where you installed the program. To use these special drivers, you must have a compatible network adapter and a supported operating system configuration. Please refer to the "Readme.txt" file located in that directory. If you do not have a special driver installed, EtherPeek does not capture error packets but does provide the ability to report errors on your network if your NIC driver returns error statistics to EtherPeek. EtherPeek can provide statistics on these two error types: CRC error and Frame Alignment error (Runt and Oversize error packets are only available using the special driver). If your network adapter driver does not report error statistics, you may notice that error counts don't change in the Network Statistics window. You will find a list of all recommended error capture cards here: http://www.wildpackets.com/support/product_support/etherpeek/hardware_epc_other
The Profile tab lets you save Peer Map configurations settings into a single profile that controls the appearance and layout of the Peer Map. The Configuration tab lets you control what part of the traffic in the Capture window’s buffer is displayed in Peer Map. The Node Visibilities tab displays node counts, and nodes that are both shown and hidden in the Peer Map. For example, if this option is set to Always Hide, then all nodes that have not had their visibility assigned by the user will be hidden. This is useful if, during a live capture, the user doesn’t want new nodes to appear on the Peer Map as they are discovered.
EtherPeek VX does not support Hyper-Threading. If Hyper-Threading is enabled on your computer's processors, you may encounter program errors when capturing with EtherPeek VX.
The space shows you where protocol segments start and stop within conversations. This option is configurable by clicking the Options button. (Different from going to Tools -> Options).
This may be caused by a display DPI setting that is larger than 96 DPI. Confirm that the display's DPI setting is set to 96 DPI by checking the configuration for this setting in the Advanced Settings portion of the Display Control Panel.
Network analysis tools are powerful and must be protected from misuse. Data captured and sent across the network may be sensitive, so EtherPeek has been designed from the ground up to adhere to strict IT security requirements.
EtherPeek VX performance may degrade noticeably when more than one capture or packet file window is open. Additional captures may be performed if Voice Analysis is disabled in the Performance section of the Capture Options dialog. In the Capture/Monitor Options, select Performance. For peak performance, right click on one of the features and choose Disable All. This way, EtherPeek will function at peak performance, but the features are still available when needed. When you need a particular feature, you can always enable it. As you enable/disable individual features, the performance bar at the bottom of the Performance Options dialog will move to show you an estimate of the impact of each feature. Here are a few more tips to improve the performance of EtherPeek:
If you need one of the other features, you can enable it when you are actually viewing the capture file. Also if you're on a switched network, you can try using the switch's mirroring or monitoring capability to zero-in on the traffic you're looking for. Try only mirroring ports one by one to avoid overloading the analyzer with traffic. For more information, please see our White Paper: Applying EtherPeek to Switched and Gigabit Ethernet Network Management.
At this time, simultaneous voice playback for both directions is not supported.
To add custom ports to Peek VX, click on the VoIP tab.
Here is a snippet from RFC3611 that defines one-way delay: end system delay: 16 bits The most recently estimated end system delay, expressed in milliseconds. End system delay is defined as the sum of the total sample accumulation and encoding delay associated with the sending direction and the jitter buffer, decoding, and playout buffer delay associated with the receiving direction. This delay MAY be estimated or measured. This value SHOULD be provided in all VoIP metrics reports. If an implementation is unable to provide the data, the value 0 MUST be used. Note that the one way symmetric VoIP segment delay may be calculated from the round trip and end system delays is as follows; if the round trip delay is denoted, RTD and the end system delays associated with the two endpoints are ESD(A) and ESD(B) then: one way symmetric voice path delay = ( RTD + ESD(A) + ESD(B) ) / 2 " RT Delay is calculated in a couple of ways: 1) It can be calculated using RTCP SR/RR (if available) or 2) external means such as ping. Since RT delay is a component of one-way delay and if not available, then one-way delay may not be available also.
Although dual-direction playback is not supported within the application at this time, this can be accomplished by using one of the popular shareware audio programs available such as Awave or Audacity. The individual media steams can then be exported as .wav files into one of these programs for merging and adjacent playback. |
|
||||||
| COPYRIGHT © 2008 WILDPACKETS, INC — PRIVACY STATEMENT · CONTACT US | CORPORATE · PRODUCTS · SOLUTIONS · SERVICES · SUPPORT · PARTNERS · BUY NOW |
|
All registered and unregistered trademarks are the sole property of their respective owners |
|