A lot of people are griping and moaning about this but their comments lie in completely unrelated email threads.
To understand sip signalling, one must understand that the internal components DO NOT show everything in a packet capture. Furthermore, running a packet capture manually on the interface can produce a very large file that has to be sifted through. sipx DOES have CLI commands, but requires the system to actually be properly functioning. It is also a good idea to ALWAYS have a realistically recent version to ask for help against. As of this email it would be (old) 4.0.4 and (new) 4.2.0. The wiki has exhaustive information on this, and it is not hard to do. It is only difficult is there is something "symptomatically wrong" with your build (i.e. your logs are not being written to the proper directory, etc.). There were discussions some time ago to see about moving the merge-logs and sipviewer into sipxconfig, but at the same time sipviewer was being updated for better handling of some dialogue. I would encourage people to discuss this IN A PROPER THREAD. Be it this one or another. The two things I could see realistically (to me anyway) are: *A. *Easier Logging to produce a merged.xml 1. Logging Quickset/Preset. A way to push an option that will change the logging for certain components so you can troubleshoot it. Ex: 1 - Registrations 2 - Presense 3 - Siptrunking 4 (etc, etc.) 9 - Revert all to normal 2. After that is done, make the call/process happen that you are having problems with. Especially handy with a "start" (logrotate) and "stop" (merge-logs). 3. Have the merged.xml ready for download in sipxconfig (nice, comments about what it is, storing it there for future reference) to display in viewer. *B. *Wireshark with "limited" capabilities from sipxconfig, because "a badly formed wireshark request" can be more problem than it is worth. Crippling a system because you said log all traffic indefinitely is NOT a good idea, sane limits should be imposed. 1. Wireshark Trace. Be able to click a few buttons (port 5060 users, port 5080 trunking, other port), default interface to listen on. How long and detailed to run it, making sure it doesn't run indefinitely. Giving you an option to download the pcap file. Of course, this would require wireshark to be installable and practically to be part of the ISO and REPO. What is NOT HELPFUL. Griping about what you wish you had in the way of diagnostics and having the discussion under a TOTALLY UNRELATED thread. If you keep commenting on why nothing is being done, it's because you don't (yes I mean you) have the discussion in a manner that makes it trackable and more easily discussed. Now, comment on the DIAGNOSTICS and keep it realistic, lets see about a JIRA improvment request. My old Sicilian Grandfather used to say, "If they don't ask for it, why give it to them." I miss him. -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: tgrazi...@voice.myitdepartment.net Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpd...@voice.myitdepartment.net Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
