Alan, A document I've seen describes a tool used by Lucent internally, a Perl script that is capable of generating reporting information from logging entries or directly from the system console. This snippet of information comes from the documentation, and explains a little about gathering AT&V2 information from modems... <snip> .modemdiag Modemdiag is a debug command, implemented on all the modem cards used with the TNT, APX, and Max platforms. This command causes a modem, in the process of hanging up from a call, to display some diagnostic information about that call. Modemdiag causes an extra command, AT&V2 to be sent to the modem after a modem is disconnected from a call. Historically, this causes Conexant-based modem chipsets (the MADD, while not Conexant-based, emulates AT&V2) to output an encoded set of statistics, about the call just ended, that look similar to the following: BEGINaa25ab25ac25ba12bb12bc12ca77cb67cc202da4ea0eb0fa88fb88fc89ga10gb1ha41hb 35hc45hd0he43hf173hg0hh0hi0hj35hk40hl36hm42hn45ho39hp43hq42hr40hs39ia23ib23i c23ja0jb0jc0jd0ka1kb1kc0kd1ke16kf16kg0kh0ki38kj0kk0kl30km33kn255la101lb103lc 101ld103ma0mb0m35na0nb0oa0ob0oc0pa1pb0qa12qb1ra34rb148rc129rd129re33rf151rg2 55sa255sb255END These statistics include information such as minimum and maximum transmit and receive speeds; the modem modulation negotiated; the modem's reason for disconnection; and line quality over the last 10 seconds of the connection. Radulator's interpretation of modemdiag is based on Conexant's supplied documentation, version 42. </snip> Also of interest may be: <snip> GATHERING MODEMDIAG NOTE: enabling modemdiag increases the time (up to 5 seconds) that Conexant-based devices require to reset between calls. On busy systems, where the access server is near capacity, this may mean that callers will receive busy signals as the resetting modems will not yet be able to take calls. The MADD is not subject to this delay. Modemdiag is toggled on or off by typing modemdiag in debug mode. On the TNT, a modem card's debug mode must be accessed from the console, with the "open" command, first. On the Max, debug mode can be accessed from the LCD with CTRL-D, D. Typically, modemdiag can be captured by using the "start logging" option in Windows telnet, after enabling modemdiag on the access server. On a Unix system, you could pipe the output of telnet to "tee <filename>." In either case, the raw log is directly acceptable to Radulator. No pre-processing is required. By itself, modemdiag does not identify the remote users' username or caller ID. Naturally, this makes it impossible to identify a given user. However, modemdiag can be combined with the output of other debug toggle commands, such as routmgr, and tntcall -t 3. Both these of these commands display the users caller ID, if available (tntcall -t 3 requires DNIS or CLID authentication to be enabled, in the access server's ANSWER configuration profile). MADDTELEM Maddtelem, the MADD modem telemetry-gathering tool (available at ftp://ftp.ascend.com/pub/Software-Releases/maddtelem/) has a feature to gather routmgr and modemdiag together, automatically, along with MADD telemetry (logged separately, which is not yet parsable by Radulator). Each line is time and date stamped with the local time of the Unix host on which Maddtelem was running. This feature can be enabled by setting $dologdebug = 1 in maddtelem.conf. </snip> I'm currently investigating some modem compatibility issues myself... Hope this information helps in some way. It would seem that Lucent would to well to consider making this tool available to the users on this list, does anyone know where it can be obtained. I may attempt to find out if I can obtain a copy through the ISP team in the UK... Regards, - Matt Matthew Watkins Technical Consultant Knowware UK Ltd Mobile: 07968 755807 Home Office: +44 (0)1223 300917 Fax: +44 (0)1223 301280 Email: matt at knowware.co.uk http://www.knowware.co.uk -----Original Message----- From: owner-ascend-users at max.bungi.com [mailto:owner-ascend-users at max.bungi.com]On Behalf Of Alan Martin Sent: 14 November 2000 15:42 To: Troy Settle; ascend-users Subject: Re: (ASCEND) test Well, Troy. I asked the group last week if anyone knew of any way to get more detailed modem stats out of the MAX. No answer. Looking for mibs or ANY other way to get stats such as : SNR Modulation error correction After an analog call terminates. Also do you or anyone know how to get &V2 stats from the modem after an analog call? Thanks Alan ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com To get FAQ'd: <http://www.nealis.net/ascend/faq>