Mitel Forums - The Unofficial Source
Mitel Forums => Mitel Software Applications => Topic started by: donlou on October 16, 2015, 04:27:28 PM
-
Hello,
Does anyone know what needs to be done in the PBX/MBG to be able to capture MiNet calls?
I am able to capture SIP calls in MBG using Packet trace option under "Diagnostics" but not MiNet calls?
Please advise.
Thanks
-
You can do a TCPDUMP at the linux command prompt.
Ralph
-
Hi Ralph,
What is the full command for MiNet capture using TCPDUMP command in linux?
And how do you start/stop the capture?
-
what version? later version of MBG have a "running" capture that will capture sip and, recently, minet.
Though I am curious why you want to actually capture minet, the tug logs show plenty of minet information.
-
Here's the commands I'm familiar with:
tcpdump -i any -n -s0 -w wcs.cap udp
tcpdump -i any -n -s0 -C 20 -W 3 -Z root -w mitel.cap (Limits size of dump)
Ralph
-
I assume once those commands are entered, it will start capturing.
How do you stop the capture??
Thanks
-
what version? later version of MBG have a "running" capture that will capture sip and, recently, minet.
Though I am curious why you want to actually capture minet, the tug logs show plenty of minet information.
I am trying to troubleshoot no audio issue on both ends.
-
Plug a pc in the back of the phone and turn on the port mirror function this will give you enough to diagnose audio issues, Minet packets will go to the controller and will not be in readable form anyway
-
FYI... You can make the MiNet packets readable, although they might not make the most sense to a lay-person, go in the MCD System Options and turn of Audio Encryption (or something like that, do not have access to a system atm).
-
Even after disabling encryption you need to decode as RTP I believe.
-
Turning off Voice Encryption will only allow you to replay the voice stream it wont allow you to view Minet packets as these are proprietary, The only way to do this is to use the minet dissector if you can get hold of it, However there should be no need for this to diagnose voice streams.
Decoding the Minet will give you call control info like Call Put on Hold etc.
-
Just adding this for future reference.
At the prompt type > tcpdump -s0 -i any -w capturefile.pcap
To stop the trace type CTRL-C
The file 'capturefile.pcap' will now exist in the root directory
Fire up WinSCP and log into the MBG. WinSCP provides a file explorer type interface which you can use to get into the root directory and find the capturefile. Drag and drop it into your harddisk.
The file can now be opened in wireshark for analysis.
-
Just adding this for future reference.
At the prompt type > tcpdump -s0 -i any -w capturefile.pcap
To stop the trace type CTRL-C
A couple of things to consider when doing the tcpdump is that the folder that you are writing the dump to has write access. There are quite a few folders on MSL that don't have write access. I usually do the dumps to /tmp as that is a safe bet.
As Ralph previously mentioned in his post about limiting the size of the file, if you need to have the logs running for a while, say a couple of days to capture a problem, then rotating the files through when they reach a limit is handy as then you don't need to trawl through an excessively large file to find what you are after, and if you need to email it, or transfer it over the net back to the office, etc, then the files zip down pretty well. I usually set a 20MB rotation, and then that zips down to a few meg to transfer.
Using the -C xxx as a switch sets the file size to rotate through. So "-C 20" would set a 20MB file rotation
Likewise, if you know you only want to capture SIP traffic, then you can also specify the port so that the capture only contains the information you need. This saves capturing other traffic like HTTP/S or SSH, etc that isn't relevant to what you are looking for, and only serves to increase the amount of garbage in the capture. If you specify "port 5060" then the tcpdump will only capture SIP traffic on port 5060.
-
Thanks Martyn.
Very useful.
Ralph