You can find sipXecs snapshot file at following link: https://docs.google.com/uc?id=0B7frGZobn9jyN2YyNmNhMTAtZjU4My00NGY1LWExNzctM2IxN2ZiNGRlMzgz&export=download&authkey=CN2omfwN&hl=en You can find captured packets at following link: https://docs.google.com/uc?id=0B7frGZobn9jyNzkxZWNiNWYtMGI5Yy00ZmJjLWFhODAtNjk0ODc1ODMyNjEz&export=download&authkey=CILQqOcE&hl=en Problem Call-ID is: OGMyOGUxODExMGVjZTY1NDRjMTY3NDE1YzU1ODg2NDk.
-- Sincerely yours, Alexey Kanukhin On Thu, Aug 26, 2010 at 7:09 PM, Worley, Dale R (Dale) <[email protected]> wrote: > ________________________________________ > From: Alexey Kanukhin [[email protected]] > I captured a voice mail session by the Wireshark tool. The captured > packets are in the attached file. > ________________________________________ > > I want to see a sipXecs *snapshot*, which captures far more information than > Wireshark and makes diagnosis much easier. > > Also, unfortunately, I can't see e-mail attachments with this account, so > you'll have to put the snapshot some place where I can retrieve it. > > Dale > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
