I meant Stupid Mode = no Currently traveling and my own CONNECtS are poor M On Thu, Jul 15, 2010 at 5:04 PM, Thomas WALTHER <thomaswalther@xxxxxxxxxxx> wrote: > Hi Marvin, > well ... I do not quite understand your reply. > > - What is "shoty" negotiation. Cant find the word in dictionary. > - What do you mean with "Stupid Modem" ? I assume, you ment "without stupid > mode". Ok, but this is what I did, as described in my question. I tried with > stupid mode = yes and with stupid mode = no. In both cases dialing does not > work beside the single exeption, which I added a log from below. Dont know, > why it was running this one time. Did you missunderstand my question or > perhaps did I missunderstand your reply ? > > So here my question: Dialing-in does not work in Ubuntu (exept the one happy > accident), however dialing-in is running perfectly in WinVista with the same > Lap, the same USB-Modem and the same provider (WinVista Log below). Do you > have an idea what to do, to get dialing-in running in Ubuntu ? > Thanks Thomas > > ------------------------------------------------------------------------ > Am Donnerstag, 15. Juli 2010 16:17:36 schrieb Marvin Stodolsky: >> Thom, >> >> Please send to the List, not me , as I am rarely online. >> Try without Stupid Modem, as it cuts shoty negotiation between your >> modem and the IP. >> >> MarvS >> >> On Thu, Jul 15, 2010 at 5:54 AM, Thomas WALTHER >> >> <thomaswalther@xxxxxxxxxxx> wrote: >> > Hi Marvin, >> > thanks for quick response. >> > >> > I removed all the > and <. During 9 or 10 sudo wvdial attempts, one was >> > successful and I caught a log, which I added dowwn in this email. Firefox >> > was running successfuly. Wow, now I dare to hope, that a solution is >> > possible. >> > >> > After this one successful attempt all further attempts failed with "modem >> > not responding" after the program was "resending" something to the modem. >> > Changing stupid mode from yes to no didnot change anything. Could this be >> > a timing problem (modem does not answer quick enough or laptop doesnot >> > wait long enough) ? >> > Thanks in advance Thomas >> > ------------------------------------------------------------------------ >> > >> > Am Mittwoch, 14. Juli 2010 17:20:30 schrieb Marvin Stodolsky: >> >> Thomas, >> >> >> >> Remove the < > symbols within /etc/wvdial.conf. >> >> >> >> MarvS >> >> >> >> On Wed, Jul 14, 2010 at 10:03 AM, Thomas WALTHER >> >> >> >> <thomaswalther@xxxxxxxxxxx> wrote: >> >> > Hi, >> >> > tryig to get the above mentioned modem runing with wvdial , I got an >> >> > authentication error. Changing stupid moede to „no“ will change the >> >> > error to „carrier lost“, but no successful dial in. >> >> > >> >> > Dial in was successful with WinVista on the same laptop on the same >> >> > place with the same provider. I made a logfile with freeware >> >> > „ModemLog“ on Vista (sory, comments only in german, hope you can read >> >> > it). >> >> > >> >> > Can you tell me, how to change my wvdial.conf ? Thanks in advance >> >> > >> >> > >> >> > Btw: last try with Ubuntu 8: >> >> > http://linmodems.technion.ac.il/bigarch/archive- tenth/msg00490.html, >> >> > but did not work. >> >> > >> >> > What I added: (Contence) >> >> > 1. ScanModem: Modemdata.txt 1 >> >> > 2. wvdial.conf 6 >> >> > 3. Wvdial-log with success 6 >> >> > 4. WinVista Log of successfl dialing 10 >> >> >======================================= >> >> >======================================= >> >> > ScanModem: Modemdata.txt >> >> > Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List >> >> > Server, as HTML can contain viruses. Use as the email Subject Line: >> >> > YourName, YourCountry kernel 2.6.31-22-generic >> >> > With this Subject Line cogent experts will be alerted, and useful >> >> > case names left in the Archive. >> >> > YourCountry will enable Country specific guidance. Linux experts in >> >> > YourCountry >> >> > can be found through: http://www.linux.org/groups/index.html. >> >> > They will know your Country's modem code, which may be essential for >> >> > dialup service. >> >> > Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an >> >> > Internet Provider mail filters. >> >> > So in a day, also check the Archived responses at >> >> > http://www.linmodems.org -------------------------- System >> >> > information ---------------------------- CPU=i686, Ubuntu , >> >> > ALSA_version=1.0.20 Linux version 2.6.31-22-generic >> >> > (buildd@vernadsky) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) >> >> > #60-Ubuntu SMP Thu May 27 00:22:23 UTC 2010 scanModem update of: >> >> > 2010_05_29 >> >> > >> >> > Distrib_ID=Ubuntu >> >> > DistribCodeName=karmic >> >> > AptRepositoryStem=http://de.archive.ubuntu.com/ubuntu/ >> >> > >> >> > >> >> > Presently install your Linux Distributions dkms package. It provides >> >> > for automated driver updates, >> >> > following upgrade of your kernel. For details see >> >> > http://linux.dell.com/projects.shtml#dkms >> >> > >> >> > There are no blacklisted modem drivers in /etc/modprobe* files >> >> > >> >> > Potentially useful modem drivers now loaded are: >> >> > cdc_acm snd_hda_intel >> >> > >> >> > Attached USB devices are: >> >> > ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse >> >> > ID 0baf:0303 U.S. Robotics >> >> > ID 1aa6:0201 eFortune Technology Corp. >> >> > If a cellphone is not detected, see >> >> > http://ubuntuforums.org/archive/index.php/t-878554.html >> >> > A sample report is: http://linmodems.technion.ac.il/bigarch/archive- >> >> > nineth/msg00578.html >> >> > >> >> > If a USB modem or cellphone is attached and was not detected, please >> >> > provide available information in your request to discuss@xxxxxxxxxxxxx >> >> > >> >> > Candidate PCI devices with modem chips are: >> >> > 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio >> >> > Controller (rev 04) >> >> > High Definition Audio cards can host modem chips. >> >> > >> >> > For candidate card in slot 00:1b.0, firmware information and bootup >> >> > diagnostics are: >> >> > PCI slot PCI ID SubsystemID Name >> >> > ---------- --------- --------- -------------- >> >> > 00:1b.0 8086:284b 1462:2f81 Audio device: Intel >> >> > Corporation 82801H >> >> > >> >> > Modem interrupt assignment and sharing: >> >> > 21: 1980 1983 IO-APIC-fasteoi uhci_hcd:usb4, HDA >> >> > Intel --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >> >> > [ 0.797240] pci 0000:00:1b.0: reg 10 64bit mmio: >> >> > [0xfdcf8000-0xfdcfbfff] [ 0.797289] pci 0000:00:1b.0: PME# >> >> > supported from D0 D3hot D3cold [ 0.797293] pci 0000:00:1b.0: PME# >> >> > disabled [ 14.807196] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 21 >> >> > (level, low) -> IRQ 21 >> >> > [ 14.807238] HDA Intel 0000:00:1b.0: setting latency timer to 64 >> >> > [ 14.877491] input: HDA Digital PCBeep as >> >> > /devices/pci0000:00/0000:00:1b.0/input/input7 >> >> > >> >> > The PCI slot 00:1b.0 of the modem card may be disabled early in >> >> > a bootup process, but then enabled later. If modem drivers load >> >> > but the modem is not responsive, read DOCs/Bootup.txt about possible >> >> > fixes. Send dmesg.txt along with ModemData.txt to >> >> > discuss@xxxxxxxxxxxxx if help is needed. >> >> > >> >> > >> >> > >> >> > ===== Advanced Linux Sound Architecture (ALSA) diagnostics ===== >> >> > The ALSA packages provide audio support and also drivers for some >> >> > modems. ALSA diagnostics are written during bootup to /proc/asound/ >> >> > folders. >> >> > >> >> > The modem cards detected by "aplay -l" are: None >> >> > >> >> > >> >> > The /proc/asound/pcm file reports: >> >> > ----------------------- >> >> > 00-00: ALC888 Analog : ALC888 Analog : playback 1 : capture 1 >> >> > 00-01: ALC888 Digital : ALC888 Digital : playback 1 >> >> > 00-02: ALC888 Analog : ALC888 Analog : capture 1 >> >> > >> >> > about /proc/asound/cards: >> >> > ------------------------ >> >> > 0 [Intel ]: HDA-Intel - HDA Intel >> >> > HDA Intel at 0xfdcf8000 irq 21 >> >> > >> >> > PCI slot 00:1b.0 has a High Definition Audio Card >> >> > The drivers are in the kernel modules tree at: >> >> > /lib/modules/2.6.31-20-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> >> > /lib/modules/2.6.31-22-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> >> > /lib/modules/2.6.31-21-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> >> > /lib/modules/2.6.31-14-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> >> > /lib/modules/2.6.31-19-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> >> > >> >> > The HDA diagnostics did not recognize a modem chip on the audio >> >> > subsystem, though a Conexant chip modem might not be recognized. >> >> > >> >> > === Finished firmware and bootup diagnostics, next deducing cogent >> >> > software. === >> >> > >> >> > Predictive diagnostics for card in bus 002: >> >> > Modem chipset detected on >> >> > SLOT="Bus 002 Device 003:" >> >> > NAME="U.S. Robotics " >> >> > bus=002 >> >> > USBmodemID=0baf:0303 >> >> > IDENT=cdc_acm >> >> > Driver=cdc_acm >> >> > >> >> > For a detailed USB cellphone usage report, see >> >> > http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03240.html >> >> > For candidate modem in: 002 >> >> > U.S. Robotics >> >> > Primary device ID: 0baf:0303 >> >> > Support type needed or chipset: cdc_acm >> >> > >> >> > >> >> > >> >> > Writing DOCs/Intel.txt >> >> > >> >> > >> >> > Predictive diagnostics for card in bus 00:1b.0: >> >> > Modem chipset not detected on >> >> > NAME="Audio device: Intel Corporation 82801H " >> >> > CLASS=0403 >> >> > PCIDEV=8086:284b >> >> > SUBSYS=1462:2f81 >> >> > IRQ=21 >> >> > HDA2=00:1b.0 >> >> > SOFT=8086:284b.HDA >> >> > >> >> > For candidate modem in: 00:1b.0 >> >> > 0403 Audio device: Intel Corporation 82801H >> >> > Primary device ID: 8086:284b >> >> > Subsystem PCI_id 1462:2f81 >> >> > Softmodem codec or chipset from diagnostics: >> >> > from Archives: >> >> > >> >> > >> >> > >> >> > Support type needed or chipset: >> >> > >> >> > Support can likely be achieved through two mutually exclusive >> >> > alternatives: 1) The hsfmodem software for Conexant chipset modems: >> >> > Read DOCs/Conexant.txt The following ALSA alternative CANNOT work with >> >> > Conexant modems. >> >> > >> >> > 2) An ALSA modem driver plus slmodemd. Read DOCs/Smartlink.txt for >> >> > details, and >> >> > to test get the package SLMODEMD_gcc4.4_alsa1.0.20.tar.gz from: >> >> > http://linmodems.technion.ac.il/packages/smartlink/ >> >> > >> >> > >> >> > The base of the UDEV device file system is: /dev/.udev >> >> > >> >> > Versions adequately match for the compiler installed: 4.4.1 >> >> > and the compiler used in kernel assembly: 4.4.1 >> >> > >> >> > The patch utility is needed for compiling ALSA drivers, and possibly >> >> > others. >> >> > >> >> > >> >> > Minimal compiling resources appear complete: >> >> > make utility - /usr/bin/make >> >> > Compiler version 4.4 >> >> > linuc_headers base folder /lib/modules/2.6.31-22-generic/build >> >> > >> >> > However some compilations and executable functions may need >> >> > additional files, in the FileNames.h (so called kernel "h"eaders) >> >> > collection installed in /usr/include/ . >> >> > For martian_modem, additional required packages are needed. The also >> >> > required headers of package libc6 are commonly installed by default. >> >> > Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev >> >> > packages, for kernels 2.6.24 and later versions. >> >> > In not included on your install CD, search for them at >> >> > http://packages.ubuntu.com >> >> > or comparable Repository for other Linux distros. >> >> > When compiling ALSA drivers, the utility "patch" will also be needed. >> >> > >> >> > >> >> > >> >> > >> >> > If a driver compilation fails, with message including some lack of >> >> > some FileName.h (stdio.h for example), then >> >> > Some additional kernel-header files need installation to /usr/include. >> >> > The minimal additional packages are libc6-dev >> >> > and any of its dependents, under Ubuntu linux-libc-dev >> >> > >> >> > If an alternate ethernet connection is available, >> >> > $ apt-get update >> >> > $ apt-get -s install linux-kernel-devel >> >> > will install needed packages. >> >> > For Debian/Ubuntu related distributions, run the following command to >> >> > display the needed package list: >> >> > >> >> > Otherwise packages have to be found through http://packages.ubuntu.com >> >> > Once downloaded and transferred into a Linux partition, >> >> > they can be installed alltogether with: >> >> > $ sudo dpkg -i *.deb >> >> > >> >> > >> >> > Checking pppd properties: >> >> > -rwsr-xr-- 1 root dialout 277352 2009-02-20 18:25 >> >> > /usr/sbin/pppd >> >> > >> >> > In case of an "error 17" "serial loopback" problem, see: >> >> > >> >> > http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html >> >> > >> >> > To enable dialout without Root permission do: >> >> > $ su - root (not for Ubuntu) >> >> > sudo chmod a+x /usr/sbin/pppd >> >> > or under Ubuntu related Linuxes >> >> > sudo chmod a+x /usr/sbin/pppd >> >> > >> >> > Checking settings of: /etc/ppp/options >> >> > asyncmap 0 >> >> > noauth >> >> > crtscts >> >> > lock >> >> > hide-password >> >> > modem >> >> > proxyarp >> >> > lcp-echo-interval 30 >> >> > lcp-echo-failure 4 >> >> > noipx >> >> > >> >> > In case of a message like: >> >> > Warning: Could not modify /etc/ppp/pap-secrets: Permission denied >> >> > see >> >> > http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html >> >> > >> >> > For guidance on FAX usage, get from >> >> > http://linmodems.technion.ac.il/packages/ get faxing.tar.gz >> >> > It has samples for a modem using port /dev/ttySL0, which must be >> >> > changed to match your modem's port. >> >> > >> >> > Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 >> >> > ra0 Which can interfere with Browser naviagation. >> >> > >> >> > Don't worry about the following, it is for experts should trouble >> >> > shooting be necessary. >> >> > ========================================================== >> >> > >> >> > Checking for modem support lines: >> >> > -------------------------------------- >> >> > /device/modem symbolic link: >> >> > slmodemd created symbolic link /dev/ttySL0: >> >> > Within /etc/udev/ files: >> >> > /etc/udev/rules.d/usb_modeswitch.rules:# Beware: there are modem-only >> >> > variants around - no storage, >> >> > /etc/udev/rules.d/usb_modeswitch.rules:# To modem mode: >> >> > /etc/udev/rules.d/usb_modeswitch.rules:# Novatel U727 USB modem >> >> > /etc/udev/rules.d/usb_modeswitch.rules:# Novatel U760 USB modem >> >> > /etc/udev/rules.d/51-hso-udev.rules:SUBSYSTEM=="tty", >> >> > SUBSYSTEMS=="usb", ATTR{hsotype}=="Modem", SYMLINK+="wmodem0" >> >> > /etc/udev/rules.d/51-hso-udev.rules:SUBSYSTEM=="tty", >> >> > SYSFS{hsotype}=="Modem", SYMLINK+="wmodem0" >> >> > Within /etc/modprobe.conf files: >> >> > /etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in >> >> > order to blacklist unwanted modem drivers >> >> > /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem >> >> > /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem >> >> > /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2 >> >> > /etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2 >> >> > Within any ancient /etc/devfs files: >> >> > >> >> > Within ancient kernel 2.4.n /etc/module.conf files: >> >> > >> >> > --------- end modem support lines -------- >> >> > =============================================== >> >> > =============================================== >> >> > >> >> > >> >> > 2. wvdial.conf >> > >> > Init1 = ATZ >> > Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >> > Stupid Mode = yes >> > Modem Type = USB Modem >> > ISDN = 0 >> > Phone = 0191011 >> > New PPPD = yes >> > Modem = /dev/ttyACM0 >> > Username = ...................... >> > Password = ........ >> > Baud = 9600 >> > >> >> > =============================================== >> >> > =============================================== >> >> > >> >> > 3. Wvdial-log with success >> > >> > thomas@thomas-laptop:~$ exit sudo wvdial >> > --> WvDial: Internet dialer version 1.60 >> > --> Cannot get information for serial port. >> > --> Initializing modem. >> > --> Sending: ATZ >> > OK >> > --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >> > --> Sending: ATQ0 >> > ATQ0 >> > OK >> > --> Re-Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >> > --> Modem not responding. >> > thomas@thomas-laptop:~$ sudo wvdial >> > --> WvDial: Internet dialer version 1.60 >> > --> Cannot get information for serial port. >> > --> Initializing modem. >> > --> Sending: ATZ >> > --> Sending: ATQ0 >> > OK >> > --> Re-Sending: ATZ >> > --> Modem not responding. >> > thomas@thomas-laptop:~$ sudo wvdial >> > --> WvDial: Internet dialer version 1.60 >> > --> Cannot get information for serial port. >> > --> Initializing modem. >> > --> Sending: ATZ >> > --> Sending: ATQ0 >> > --> Re-Sending: ATZ >> > --> Modem not responding. >> > thomas@thomas-laptop:~$ sudo wvdial >> > --> WvDial: Internet dialer version 1.60 >> > --> Cannot get information for serial port. >> > --> Initializing modem. >> > --> Sending: ATZ >> > --> Sending: ATQ0 >> > OK >> > --> Re-Sending: ATZ >> > --> Modem not responding. >> > thomas@thomas-laptop:~$ sudo wvdial >> > --> WvDial: Internet dialer version 1.60 >> > --> Cannot get information for serial port. >> > --> Initializing modem. >> > --> Sending: ATZ >> > --> Sending: ATQ0 >> > OK >> > --> Re-Sending: ATZ >> > OK >> > --> Cannot get information for serial port. >> > --> Initializing modem. >> > --> Sending: ATZ >> > --> Sending: ATQ0 >> > OK >> > --> Re-Sending: ATZ >> > --> Modem not responding. >> > thomas@thomas-laptop:~$ sudo wvdial >> > --> WvDial: Internet dialer version 1.60 >> > --> Cannot get information for serial port. >> > --> Initializing modem. >> > --> Sending: ATZ >> > OK >> > --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >> > OK >> > --> Modem initialized. >> > --> Sending: ATDT0191011 >> > --> Waiting for carrier. >> > ATDT0191011 >> > CONNECT 50666/ARQ/V90/LAPM/V42BIS >> > --> Carrier detected. Starting PPP immediately. >> > --> Starting pppd at Thu Jul 15 10:49:21 2010 >> > --> Pid of pppd: 2930 >> > --> Using interface ppp0 >> > --> Authentication (PAP) started >> > --> Authentication (PAP) successful >> > --> local IP address 217.249.198.77 >> > --> remote IP address 193.158.131.189 >> > --> primary DNS address 217.0.43.161 >> > --> secondary DNS address 217.0.43.177 >> > --> Script /etc/ppp/ip-up run successful >> > --> Default route Ok. >> > --> Nameserver (DNS) Ok. >> > --> Connected... Press Ctrl-C to disconnect >> > exit >> > ^CCaught signal 2: Attempting to exit gracefully... >> > --> Terminating on signal 15 >> > --> Connect time 4.4 minutes. >> > --> Script /etc/ppp/ip-down started >> > --> Terminate Request (Message: "User request" ) >> > --> Disconnecting at Thu Jul 15 10:53:46 2010 >> > thomas@thomas-laptop:~$ exit >> > exit >> > >> > Script beendet: Do 15 Jul 2010 10:54:00 CEST >> > >> >> > ================================================ >> >> > ================================================ >> >> > >> >> > 4. WinVista Log of successful dial in >> >> > 07-14-2010 13:08:16.570 - TSP: Asynchroner Vorgang(0x00010302) wird >> >> > abgeschlossen, Status 0x00000000 >> >> > 07-14-2010 13:08:16.570 - TSP(0000): Anruf wird abgebrochen >> >> > 07-14-2010 13:08:16.570 - TSP: Asynchroner Vorgang(0x000102f1) wird >> >> > abgeschlossen, Status 0x00000000 >> >> > 07-14-2010 13:08:16.570 - TSP(0000): Anruf wird geschlossen >> >> > 07-14-2010 13:08:16.570 - DTR-Signal vor dem Beenden des Anschlusses >> >> > herabgesetzt. >> >> > 07-14-2010 13:08:16.680 - Sitzungsstatistik: >> >> > 07-14-2010 13:08:16.680 - Gelesen: 0 Bytes >> >> > 07-14-2010 13:08:16.680 - Geschrieben: 0 Bytes >> >> > 07-14-2010 13:10:18.750 - Datei: C:\Windows\system32\tapisrv.dll, >> >> > Version 6.0.6001 >> >> > 07-14-2010 13:10:18.750 - Datei: C:\Windows\system32\unimdm.tsp, >> >> > Version 6.0.6001 >> >> > 07-14-2010 13:10:18.750 - Datei: C:\Windows\system32\unimdmat.dll, >> >> > Version 6.0.6000 >> >> > 07-14-2010 13:10:18.750 - Datei: C:\Windows\system32\uniplat.dll, >> >> > Version 6.0.6000 >> >> > 07-14-2010 13:10:18.750 - Datei: >> >> > C:\Windows\system32\drivers\modem.sys, Version 6.0.6001 >> >> > 07-14-2010 13:10:18.750 - Datei: C:\Windows\system32\modemui.dll, >> >> > Version 6.0.6001 >> >> > 07-14-2010 13:10:18.750 - Datei: C:\Windows\system32\mdminst.dll, >> >> > Version 6.0.6001 >> >> > 07-14-2010 13:10:18.750 - Modemtyp: U.S. Robotics V.92 USB Modem >> >> > 07-14-2010 13:10:18.750 - Pfad für Modeminformationsdatei: oem31.inf >> >> > 07-14-2010 13:10:18.750 - Abschnitt in Modeminformationsdatei: >> >> > Modem_CV92_USB 07-14-2010 13:10:18.750 - Übereinstimmende >> >> > Hardwarekennung: >> >> > usb\vid_0baf&pid_0303 >> >> > 07-14-2010 13:10:18.750 - Opening Modem >> >> > 07-14-2010 13:10:18.750 - 115200,8,N,1, ctsfl=1, rtsctl=2 >> >> > 07-14-2010 13:10:18.765 - Modem initialisieren >> >> > 07-14-2010 13:10:18.781 - Senden: AT<cr> >> >> > 07-14-2010 13:10:18.781 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:10:18.781 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:10:18.781 - TSP(0000): Anruf wird durchgeführt >> >> > 07-14-2010 13:10:18.796 - Senden: AT&F1E0Q0V1&C1&D2S0=0<cr> >> >> > 07-14-2010 13:10:18.999 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:10:18.999 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:10:19.015 - Senden: ATS30=0L1M1&M4&K1&H1B0B15N1X4<cr> >> >> > 07-14-2010 13:10:19.030 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:10:19.030 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:10:19.030 - Auf Anruf warten >> >> > 07-14-2010 13:10:19.046 - Senden: AT+VCID=1<cr> >> >> > 07-14-2010 13:10:19.046 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:10:19.046 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:10:19.062 - Senden: ATS0=0<cr> >> >> > 07-14-2010 13:10:19.062 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:10:19.062 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:10:19.062 - 115200,8,N,1, ctsfl=1, rtsctl=2 >> >> > 07-14-2010 13:10:19.062 - Modem initialisieren >> >> > 07-14-2010 13:10:19.077 - Senden: AT<cr> >> >> > 07-14-2010 13:10:19.077 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:10:19.077 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:10:19.093 - Senden: AT&F1E0Q0V1&C1&D2S0=0<cr> >> >> > 07-14-2010 13:10:19.311 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:10:19.311 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:10:19.327 - Senden: ATS30=0L1M1&M4&K1&H1B0B15N1X4<cr> >> >> > 07-14-2010 13:10:19.327 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:10:19.327 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:10:19.327 - Wählen >> >> > 07-14-2010 13:10:19.327 - TSP: Asynchroner Vorgang(0x00010225) wird >> >> > abgeschlossen, Status 0x00000000 >> >> > 07-14-2010 13:10:19.327 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING >> >> > 07-14-2010 13:10:19.327 - TSP(0000): LINEEVENT: >> >> > LINECALLSTATE_PROCEEDING 07-14-2010 13:10:19.342 - Senden: >> >> > ATDT#######<cr> >> >> > 07-14-2010 13:10:51.993 - Empfangen: <cr><lf>CONNECT >> >> > 49333/ARQ/V90/LAPM/V42BIS<cr><lf> >> >> > 07-14-2010 13:10:51.993 - Interpretierte Antwort: Verbinden >> >> > 07-14-2010 13:10:51.993 - Verbindung wurde erstellt, aber das >> >> > CD-Signal war niedrig. Es wird gewartet bis das Signal sich erhöht. >> >> > 07-14-2010 13:10:52.024 - Das CD-Signal ist nach einer Wartezeit von >> >> > 20 ms immer noch niedrig. >> >> > 07-14-2010 13:10:52.056 - CD-Signal wurde heraufgesetzt. >> >> > 07-14-2010 13:10:52.056 - Verbindung hergestellt mit 49333 Bit/s >> >> > 07-14-2010 13:10:52.056 - Fehlerkontrolle an >> >> > 07-14-2010 13:10:52.056 - Datenkomprimierung an >> >> > 07-14-2010 13:10:52.056 - TSP(0000): LINEEVENT: >> >> > LINECALLSTATE_CONNECTED 07-14-2010 13:11:22.070 - Gelesen: Gesamt: 0, >> >> > Pro Sek.: 0, Geschrieben: Gesamt: 0, Pro Sek.: 0 >> >> > 07-14-2010 13:12:22.334 - TSP(0000): Anruf wird abgebrochen >> >> > 07-14-2010 13:12:22.334 - Modem aufhängen >> >> > 07-14-2010 13:12:22.334 - Modem hat nach DTR-Signal aufgehängt. >> >> > 07-14-2010 13:12:23.644 - CD-Signal wurde getrennt, da das DTR-Signal >> >> > herabgesetzt wurde. >> >> > 07-14-2010 13:12:23.644 - Empfangen: <cr><lf>NO CARRIER<cr><lf> >> >> > 07-14-2010 13:12:23.644 - Interpretierte Antwort: Kein Trägersignal >> >> > 07-14-2010 13:12:23.660 - Senden: ATH<cr> >> >> > 07-14-2010 13:12:24.783 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:12:24.783 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:12:24.799 - Senden: at#ud<cr> >> >> > 07-14-2010 13:12:24.830 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:12:24.830 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:12:24.830 - Empfangen: <2A4D3263 >> >> > 00=09 02=00 03=02 10=15 11=0C 12=2E><cr><lf> >> >> > 07-14-2010 13:12:24.830 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:12:24.830 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:12:24.830 - Empfangen: <2A4D3263 >> >> > 17=09 20=0C 21=0E 22=0C80 23=0C80><cr><lf> >> >> > 07-14-2010 13:12:24.830 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:12:24.830 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:12:24.830 - Empfangen: <2A4D3263 >> >> > 26=6720 27=C0B5 32=00 33=00><cr><lf> >> >> > 07-14-2010 13:12:24.830 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:12:24.830 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:12:24.830 - Empfangen: <2A4D3263 >> >> > 34=6720 35=B64A 40=01 41=80 42=00 43=01 44=01><cr><lf> >> >> > 07-14-2010 13:12:24.830 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:12:24.830 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:12:24.830 - Empfangen: <2A4D3263 >> >> > 50=02 51=02 52=FFFF201E 53=02CB82 54=00 55=00><cr><lf> >> >> > 07-14-2010 13:12:24.830 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:12:24.830 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:12:24.830 - Empfangen: <2A4D3263 >> >> > 56=040F 57=06BF 58=01 59=24><cr><lf> >> >> > 07-14-2010 13:12:24.830 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:12:24.830 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:12:24.830 - Empfangen: <2A4D3263 >> >> > 60=51 61=00><cr><lf> 07-14-2010 13:12:24.830 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:12:24.830 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:12:24.830 - Empfangen: <2A4D3263 >> >> > BA=0 BB=0 BC=0 BD=115200 BE=N BF=8><cr><lf> >> >> > 07-14-2010 13:12:24.830 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:12:24.830 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:12:24.830 - Empfangen: <2A4D3263 >> >> > FF="U.S. >> >> > ROBOTICS"><cr><lf> 07-14-2010 13:12:24.830 - Empfangen: >> >> > <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:12:24.830 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:12:24.830 - Diagnose >> >> > 07-14-2010 13:12:24.830 - Modemdiagnose: >> >> > 07-14-2010 13:12:24.830 - Verbindungsantwort: ..CONNECT >> >> > 49333/ARQ/V90/LAPM/V42BIS.. >> >> > 07-14-2010 13:12:24.830 - Version 0.9 >> >> > 07-14-2010 13:12:24.830 - Multimediamodus: Nur Daten >> >> > 07-14-2010 13:12:24.830 - DTE-DCE-Schnittstellenmodus: V.80 gerahmter >> >> > synchroner Modus >> >> > 07-14-2010 13:12:24.830 - Energiestand des Empfangssignals (in -dBm): >> >> > 21 07-14-2010 13:12:24.830 - Energiestand des Übertragungssignals (in >> >> > -dBm): 12 07-14-2010 13:12:24.830 - Geschätzter Geräuschpegel (in >> >> > -dBm): 46 07-14-2010 13:12:24.830 - Verzögerung: 9 ms >> >> > 07-14-2010 13:12:24.830 - Verhandlungsergebnis des >> >> > Übertragungsträgersignals: V.34 >> >> > 07-14-2010 13:12:24.830 - Verhandlungsergebnis des >> >> > Empfangsträgersignals: V.pcm (asymmetrisch) >> >> > 07-14-2010 13:12:24.830 - Symbolrate des Übertragungsträgersignals: >> >> > 3200 07-14-2010 13:12:24.830 - Symbolrate des Empfangsträgersignals: >> >> > 3200 07-14-2010 13:12:24.830 - Anfangsdatenrate des >> >> > Übertragungsträgersignals: 26400 >> >> > 07-14-2010 13:12:24.830 - Anfangsdatenrate des Empfangsträgersignals: >> >> > 49333 07-14-2010 13:12:24.830 - Angeforderte >> >> > erneuteTrägersignalübungen: 0 07-14-2010 13:12:24.830 - Zugelassene >> >> > erneuteTrägersignalübungen: 0 07-14-2010 13:12:24.830 - Endgültige >> >> > Übertragungsträgersignalrate: 26400 07-14-2010 13:12:24.830 - >> >> > Endgültige Empfangsträgersignalrate: 46666 07-14-2010 13:12:24.830 - >> >> > Protokollverhandlungsergebnis: V.42 LAPM 07-14-2010 13:12:24.830 - >> >> > Rahmengröße der Fehlersteuerung: 128 07-14-2010 13:12:24.830 - >> >> > Verbindungszeitlimits der Fehlersteuerung: 0 07-14-2010 13:12:24.830 - >> >> > Verbindungs-NAKs der Fehlersteuerung: 1 07-14-2010 13:12:24.830 - >> >> > Komprimierungverhandlungsergebnis: V.42bis 07-14-2010 13:12:24.830 - >> >> > Übertragungsflusssteuerung: V.24 ckt 106/133 07-14-2010 13:12:24.830 - >> >> > Empfangsflusssteuerung: V.24 ckt 106/133 07-14-2010 13:12:24.830 - Von >> >> > DTE gesendete übertragene Zeichen: -57314 07-14-2010 13:12:24.830 - An >> >> > DTE gesendete erhaltene Zeichen: 183170 07-14-2010 13:12:24.830 - >> >> > Verlorene übertragene Zeichen >> >> > (Datenüberlauffehler von DTE): 0 >> >> > 07-14-2010 13:12:24.830 - Verlorene empfangene Zeichen >> >> > (Datenüberlauffehler an DTE): 0 >> >> > 07-14-2010 13:12:24.830 - Übertragungsrahmenanzahl: 1039 >> >> > 07-14-2010 13:12:24.830 - Empfangsrahmenanzahl: 1727 >> >> > 07-14-2010 13:12:24.830 - Fehleranzahl übertragener Rahmen: 1 >> >> > 07-14-2010 13:12:24.830 - Fehleranzahl erhaltener Rahmen: 36 >> >> > 07-14-2010 13:12:24.830 - Abbruchursache: DTE-Auflegbefehl >> >> > 07-14-2010 13:12:24.830 - Ereignisanzahl wartender Anrufe: 0 >> >> > 07-14-2010 13:12:24.830 - Unbekanntes Format (0x000000ba, 0x00000000) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:12:24.830 - Unbekanntes Format (0x000000bb, 0x00000000) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:12:24.830 - Unbekanntes Format (0x000000bc, 0x00000000) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:12:24.830 - Unbekanntes Format (0x000000bd, 0x00115200) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:12:24.830 - Unbekanntes Format (0x000000bf, 0x00000008) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:12:24.830 - Unbekanntes Format (0x000000ff, 0x000002ca) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:12:24.830 - 115200,8,N,1, ctsfl=1, rtsctl=2 >> >> > 07-14-2010 13:12:24.830 - Modem initialisieren >> >> > 07-14-2010 13:12:24.845 - Senden: AT<cr> >> >> > 07-14-2010 13:12:24.845 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:12:24.845 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:12:24.861 - Senden: AT&F1E0Q0V1&C1&D2S0=0<cr> >> >> > 07-14-2010 13:12:25.064 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:12:25.064 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:12:25.079 - Senden: ATS30=0L1M1&M4&K1&H1B0B15N1X4<cr> >> >> > 07-14-2010 13:12:25.095 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:12:25.095 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:12:25.095 - Auf Anruf warten >> >> > 07-14-2010 13:12:25.111 - Senden: AT+VCID=1<cr> >> >> > 07-14-2010 13:12:25.111 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:12:25.111 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:12:25.126 - Senden: ATS0=0<cr> >> >> > 07-14-2010 13:12:25.126 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:12:25.126 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:12:25.126 - TSP(0000): LINEEVENT: >> >> > LINECALLSTATE_DISCONNECTED(0x1) >> >> > 07-14-2010 13:12:25.126 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE >> >> > 07-14-2010 13:12:25.126 - TSP: Asynchroner Vorgang(0x0001017b) wird >> >> > abgeschlossen, Status 0x00000000 >> >> > 07-14-2010 13:12:25.126 - TSP(0000): Anruf wird abgebrochen >> >> > 07-14-2010 13:12:25.126 - TSP: Asynchroner Vorgang(0x000100b0) wird >> >> > abgeschlossen, Status 0x00000000 >> >> > 07-14-2010 13:12:25.126 - TSP(0000): Anruf wird geschlossen >> >> > 07-14-2010 13:12:25.126 - DTR-Signal vor dem Beenden des Anschlusses >> >> > herabgesetzt. >> >> > 07-14-2010 13:12:25.235 - Sitzungsstatistik: >> >> > 07-14-2010 13:12:25.235 - Gelesen: 0 Bytes >> >> > 07-14-2010 13:12:25.235 - Geschrieben: 0 Bytes >> >> > 07-14-2010 13:34:46.544 - Datei: C:\Windows\system32\tapisrv.dll, >> >> > Version 6.0.6001 >> >> > 07-14-2010 13:34:46.544 - Datei: C:\Windows\system32\unimdm.tsp, >> >> > Version 6.0.6001 >> >> > 07-14-2010 13:34:46.544 - Datei: C:\Windows\system32\unimdmat.dll, >> >> > Version 6.0.6000 >> >> > 07-14-2010 13:34:46.544 - Datei: C:\Windows\system32\uniplat.dll, >> >> > Version 6.0.6000 >> >> > 07-14-2010 13:34:46.544 - Datei: >> >> > C:\Windows\system32\drivers\modem.sys, Version 6.0.6001 >> >> > 07-14-2010 13:34:46.544 - Datei: C:\Windows\system32\modemui.dll, >> >> > Version 6.0.6001 >> >> > 07-14-2010 13:34:46.544 - Datei: C:\Windows\system32\mdminst.dll, >> >> > Version 6.0.6001 >> >> > 07-14-2010 13:34:46.544 - Modemtyp: U.S. Robotics V.92 USB Modem >> >> > 07-14-2010 13:34:46.544 - Pfad für Modeminformationsdatei: oem31.inf >> >> > 07-14-2010 13:34:46.544 - Abschnitt in Modeminformationsdatei: >> >> > Modem_CV92_USB 07-14-2010 13:34:46.544 - Übereinstimmende >> >> > Hardwarekennung: >> >> > usb\vid_0baf&pid_0303 >> >> > 07-14-2010 13:34:46.544 - Opening Modem >> >> > 07-14-2010 13:34:46.544 - 115200,8,N,1, ctsfl=1, rtsctl=2 >> >> > 07-14-2010 13:34:46.544 - Modem initialisieren >> >> > 07-14-2010 13:34:46.575 - Senden: AT<cr> >> >> > 07-14-2010 13:34:46.575 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:34:46.575 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:34:46.575 - TSP(0000): Anruf wird durchgeführt >> >> > 07-14-2010 13:34:46.590 - Senden: AT&F1E0Q0V1&C1&D2S0=0<cr> >> >> > 07-14-2010 13:34:46.793 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:34:46.793 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:34:46.809 - Senden: ATS30=0L1M1&M4&K1&H1B0B15N1X4<cr> >> >> > 07-14-2010 13:34:46.824 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:34:46.824 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:34:46.824 - Auf Anruf warten >> >> > 07-14-2010 13:34:46.840 - Senden: AT+VCID=1<cr> >> >> > 07-14-2010 13:34:46.840 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:34:46.840 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:34:46.856 - Senden: ATS0=0<cr> >> >> > 07-14-2010 13:34:46.856 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:34:46.856 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:34:46.856 - 115200,8,N,1, ctsfl=1, rtsctl=2 >> >> > 07-14-2010 13:34:46.856 - Modem initialisieren >> >> > 07-14-2010 13:34:46.871 - Senden: AT<cr> >> >> > 07-14-2010 13:34:46.871 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:34:46.871 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:34:46.887 - Senden: AT&F1E0Q0V1&C1&D2S0=0<cr> >> >> > 07-14-2010 13:34:47.090 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:34:47.090 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:34:47.105 - Senden: ATS30=0L1M1&M4&K1&H1B0B15N1X4<cr> >> >> > 07-14-2010 13:34:47.121 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:34:47.121 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:34:47.121 - Wählen >> >> > 07-14-2010 13:34:47.121 - TSP: Asynchroner Vorgang(0x0001002e) wird >> >> > abgeschlossen, Status 0x00000000 >> >> > 07-14-2010 13:34:47.121 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING >> >> > 07-14-2010 13:34:47.121 - TSP(0000): LINEEVENT: >> >> > LINECALLSTATE_PROCEEDING 07-14-2010 13:34:47.136 - Senden: >> >> > ATDT#######<cr> >> >> > 07-14-2010 13:35:19.850 - Empfangen: <cr><lf>CONNECT >> >> > 50666/ARQ/V90/LAPM/V42BIS<cr><lf> >> >> > 07-14-2010 13:35:19.850 - Interpretierte Antwort: Verbinden >> >> > 07-14-2010 13:35:19.850 - Verbindung wurde erstellt, aber das >> >> > CD-Signal war niedrig. Es wird gewartet bis das Signal sich erhöht. >> >> > 07-14-2010 13:35:19.881 - Das CD-Signal ist nach einer Wartezeit von >> >> > 20 ms immer noch niedrig. >> >> > 07-14-2010 13:35:19.912 - Das CD-Signal ist nach einer Wartezeit von >> >> > 20 ms immer noch niedrig. >> >> > 07-14-2010 13:35:19.943 - CD-Signal wurde heraufgesetzt. >> >> > 07-14-2010 13:35:19.943 - Verbindung hergestellt mit 50666 Bit/s >> >> > 07-14-2010 13:35:19.943 - Fehlerkontrolle an >> >> > 07-14-2010 13:35:19.943 - Datenkomprimierung an >> >> > 07-14-2010 13:35:19.943 - TSP(0000): LINEEVENT: >> >> > LINECALLSTATE_CONNECTED 07-14-2010 13:35:49.958 - Gelesen: Gesamt: 0, >> >> > Pro Sek.: 0, Geschrieben: Gesamt: 0, Pro Sek.: 0 >> >> > 07-14-2010 13:36:11.080 - TSP(0000): Anruf wird abgebrochen >> >> > 07-14-2010 13:36:11.080 - Modem aufhängen >> >> > 07-14-2010 13:36:11.096 - Modem hat nach DTR-Signal aufgehängt. >> >> > 07-14-2010 13:36:13.451 - CD-Signal wurde getrennt, da das DTR-Signal >> >> > herabgesetzt wurde. >> >> > 07-14-2010 13:36:13.451 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:36:13.451 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:36:13.467 - Senden: ATH<cr> >> >> > 07-14-2010 13:36:13.935 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:36:13.935 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:36:13.950 - Senden: at#ud<cr> >> >> > 07-14-2010 13:36:13.982 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:36:13.982 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:36:13.982 - Empfangen: <2A4D3263 >> >> > 00=09 02=00 03=02 10=15 11=0C 12=2E><cr><lf> >> >> > 07-14-2010 13:36:13.982 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:36:13.982 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:36:13.982 - Empfangen: <2A4D3263 >> >> > 17=09 20=0C 21=0E 22=0C80 23=0C80><cr><lf> >> >> > 07-14-2010 13:36:13.982 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:36:13.982 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:36:13.982 - Empfangen: <2A4D3263 >> >> > 26=6720 27=C5EA 32=00 33=00><cr><lf> >> >> > 07-14-2010 13:36:13.982 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:36:13.982 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:36:13.982 - Empfangen: <2A4D3263 >> >> > 34=6720 35=B115 40=01 41=80 42=00 43=01 44=01><cr><lf> >> >> > 07-14-2010 13:36:13.982 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:36:13.982 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:36:13.982 - Empfangen: <2A4D3263 >> >> > 50=02 51=02 52=567B 53=01E957 54=00 55=00><cr><lf> >> >> > 07-14-2010 13:36:13.982 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:36:13.982 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:36:13.982 - Empfangen: <2A4D3263 >> >> > 56=0154 57=03F6 58=01 59=01><cr><lf> >> >> > 07-14-2010 13:36:13.982 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:36:13.982 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:36:13.982 - Empfangen: <2A4D3263 >> >> > 60=51 61=00><cr><lf> 07-14-2010 13:36:13.982 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:36:13.982 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:36:13.982 - Empfangen: <2A4D3263 >> >> > BA=0 BB=0 BC=0 BD=115200 BE=N BF=8><cr><lf> >> >> > 07-14-2010 13:36:13.982 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:36:13.982 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:36:13.982 - Empfangen: <2A4D3263 >> >> > FF="U.S. >> >> > ROBOTICS"><cr><lf> 07-14-2010 13:36:13.982 - Empfangen: >> >> > <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:36:13.982 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:36:13.982 - Diagnose >> >> > 07-14-2010 13:36:13.982 - Modemdiagnose: >> >> > 07-14-2010 13:36:13.982 - Verbindungsantwort: ..CONNECT >> >> > 50666/ARQ/V90/LAPM/V42BIS.. >> >> > 07-14-2010 13:36:13.982 - Version 0.9 >> >> > 07-14-2010 13:36:13.982 - Multimediamodus: Nur Daten >> >> > 07-14-2010 13:36:13.982 - DTE-DCE-Schnittstellenmodus: V.80 gerahmter >> >> > synchroner Modus >> >> > 07-14-2010 13:36:13.982 - Energiestand des Empfangssignals (in -dBm): >> >> > 21 07-14-2010 13:36:13.982 - Energiestand des Übertragungssignals (in >> >> > -dBm): 12 07-14-2010 13:36:13.982 - Geschätzter Geräuschpegel (in >> >> > -dBm): 46 07-14-2010 13:36:13.982 - Verzögerung: 9 ms >> >> > 07-14-2010 13:36:13.982 - Verhandlungsergebnis des >> >> > Übertragungsträgersignals: V.34 >> >> > 07-14-2010 13:36:13.982 - Verhandlungsergebnis des >> >> > Empfangsträgersignals: V.pcm (asymmetrisch) >> >> > 07-14-2010 13:36:13.982 - Symbolrate des Übertragungsträgersignals: >> >> > 3200 07-14-2010 13:36:13.982 - Symbolrate des Empfangsträgersignals: >> >> > 3200 07-14-2010 13:36:13.982 - Anfangsdatenrate des >> >> > Übertragungsträgersignals: 26400 >> >> > 07-14-2010 13:36:13.982 - Anfangsdatenrate des Empfangsträgersignals: >> >> > 50666 07-14-2010 13:36:13.982 - Angeforderte >> >> > erneuteTrägersignalübungen: 0 07-14-2010 13:36:13.982 - Zugelassene >> >> > erneuteTrägersignalübungen: 0 07-14-2010 13:36:13.982 - Endgültige >> >> > Übertragungsträgersignalrate: 26400 07-14-2010 13:36:13.982 - >> >> > Endgültige Empfangsträgersignalrate: 45333 07-14-2010 13:36:13.982 - >> >> > Protokollverhandlungsergebnis: V.42 LAPM 07-14-2010 13:36:13.982 - >> >> > Rahmengröße der Fehlersteuerung: 128 07-14-2010 13:36:13.982 - >> >> > Verbindungszeitlimits der Fehlersteuerung: 0 07-14-2010 13:36:13.982 - >> >> > Verbindungs-NAKs der Fehlersteuerung: 1 07-14-2010 13:36:13.982 - >> >> > Komprimierungverhandlungsergebnis: V.42bis 07-14-2010 13:36:13.982 - >> >> > Übertragungsflusssteuerung: V.24 ckt 106/133 07-14-2010 13:36:13.982 - >> >> > Empfangsflusssteuerung: V.24 ckt 106/133 07-14-2010 13:36:13.982 - Von >> >> > DTE gesendete übertragene Zeichen: 22139 07-14-2010 13:36:13.982 - An >> >> > DTE gesendete erhaltene Zeichen: 125271 07-14-2010 13:36:13.982 - >> >> > Verlorene übertragene Zeichen >> >> > (Datenüberlauffehler von DTE): 0 >> >> > 07-14-2010 13:36:13.982 - Verlorene empfangene Zeichen >> >> > (Datenüberlauffehler an DTE): 0 >> >> > 07-14-2010 13:36:13.982 - Übertragungsrahmenanzahl: 340 >> >> > 07-14-2010 13:36:13.982 - Empfangsrahmenanzahl: 1014 >> >> > 07-14-2010 13:36:13.982 - Fehleranzahl übertragener Rahmen: 1 >> >> > 07-14-2010 13:36:13.982 - Fehleranzahl erhaltener Rahmen: 1 >> >> > 07-14-2010 13:36:13.982 - Abbruchursache: DTE-Auflegbefehl >> >> > 07-14-2010 13:36:13.982 - Ereignisanzahl wartender Anrufe: 0 >> >> > 07-14-2010 13:36:13.982 - Unbekanntes Format (0x000000ba, 0x00000000) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:36:13.982 - Unbekanntes Format (0x000000bb, 0x00000000) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:36:13.982 - Unbekanntes Format (0x000000bc, 0x00000000) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:36:13.982 - Unbekanntes Format (0x000000bd, 0x00115200) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:36:13.982 - Unbekanntes Format (0x000000bf, 0x00000008) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:36:13.982 - Unbekanntes Format (0x000000ff, 0x000002ca) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:36:13.982 - 115200,8,N,1, ctsfl=1, rtsctl=2 >> >> > 07-14-2010 13:36:13.982 - Modem initialisieren >> >> > 07-14-2010 13:36:13.997 - Senden: AT<cr> >> >> > 07-14-2010 13:36:13.997 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:36:13.997 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:36:14.013 - Senden: AT&F1E0Q0V1&C1&D2S0=0<cr> >> >> > 07-14-2010 13:36:14.216 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:36:14.216 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:36:14.231 - Senden: ATS30=0L1M1&M4&K1&H1B0B15N1X4<cr> >> >> > 07-14-2010 13:36:14.247 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:36:14.247 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:36:14.247 - Auf Anruf warten >> >> > 07-14-2010 13:36:14.262 - Senden: AT+VCID=1<cr> >> >> > 07-14-2010 13:36:14.262 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:36:14.262 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:36:14.278 - Senden: ATS0=0<cr> >> >> > 07-14-2010 13:36:14.278 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:36:14.278 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:36:14.278 - TSP(0000): LINEEVENT: >> >> > LINECALLSTATE_DISCONNECTED(0x1) >> >> > 07-14-2010 13:36:14.278 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE >> >> > 07-14-2010 13:36:14.278 - TSP: Asynchroner Vorgang(0x000103cb) wird >> >> > abgeschlossen, Status 0x00000000 >> >> > 07-14-2010 13:36:14.278 - TSP(0000): Anruf wird abgebrochen >> >> > 07-14-2010 13:36:14.278 - TSP: Asynchroner Vorgang(0x00010265) wird >> >> > abgeschlossen, Status 0x00000000 >> >> > 07-14-2010 13:36:14.278 - TSP(0000): Anruf wird geschlossen >> >> > 07-14-2010 13:36:14.278 - DTR-Signal vor dem Beenden des Anschlusses >> >> > herabgesetzt. >> >> > 07-14-2010 13:36:14.387 - Sitzungsstatistik: >> >> > 07-14-2010 13:36:14.387 - Gelesen: 0 Bytes >> >> > 07-14-2010 13:36:14.387 - Geschrieben: 0 Bytes >> >> > 07-14-2010 13:44:06.072 - Datei: C:\Windows\system32\tapisrv.dll, >> >> > Version 6.0.6001 >> >> > 07-14-2010 13:44:06.072 - Datei: C:\Windows\system32\unimdm.tsp, >> >> > Version 6.0.6001 >> >> > 07-14-2010 13:44:06.072 - Datei: C:\Windows\system32\unimdmat.dll, >> >> > Version 6.0.6000 >> >> > 07-14-2010 13:44:06.072 - Datei: C:\Windows\system32\uniplat.dll, >> >> > Version 6.0.6000 >> >> > 07-14-2010 13:44:06.088 - Datei: >> >> > C:\Windows\system32\drivers\modem.sys, Version 6.0.6001 >> >> > 07-14-2010 13:44:06.088 - Datei: C:\Windows\system32\modemui.dll, >> >> > Version 6.0.6001 >> >> > 07-14-2010 13:44:06.088 - Datei: C:\Windows\system32\mdminst.dll, >> >> > Version 6.0.6001 >> >> > 07-14-2010 13:44:06.088 - Modemtyp: U.S. Robotics V.92 USB Modem >> >> > 07-14-2010 13:44:06.088 - Pfad für Modeminformationsdatei: oem31.inf >> >> > 07-14-2010 13:44:06.088 - Abschnitt in Modeminformationsdatei: >> >> > Modem_CV92_USB 07-14-2010 13:44:06.088 - Übereinstimmende >> >> > Hardwarekennung: >> >> > usb\vid_0baf&pid_0303 >> >> > 07-14-2010 13:44:06.088 - Opening Modem >> >> > 07-14-2010 13:44:06.088 - 115200,8,N,1, ctsfl=1, rtsctl=2 >> >> > 07-14-2010 13:44:06.088 - Modem initialisieren >> >> > 07-14-2010 13:44:06.104 - Senden: AT<cr> >> >> > 07-14-2010 13:44:06.104 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:44:06.104 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:44:06.104 - TSP(0000): Anruf wird durchgeführt >> >> > 07-14-2010 13:44:06.119 - Senden: AT&F1E0Q0V1&C1&D2S0=0<cr> >> >> > 07-14-2010 13:44:06.322 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:44:06.322 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:44:06.338 - Senden: ATS30=0L1M1&M4&K1&H1B0B15N1X4<cr> >> >> > 07-14-2010 13:44:06.353 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:44:06.353 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:44:06.353 - Auf Anruf warten >> >> > 07-14-2010 13:44:06.369 - Senden: AT+VCID=1<cr> >> >> > 07-14-2010 13:44:06.369 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:44:06.369 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:44:06.384 - Senden: ATS0=0<cr> >> >> > 07-14-2010 13:44:06.384 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:44:06.384 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:44:06.384 - 115200,8,N,1, ctsfl=1, rtsctl=2 >> >> > 07-14-2010 13:44:06.384 - Modem initialisieren >> >> > 07-14-2010 13:44:06.400 - Senden: AT<cr> >> >> > 07-14-2010 13:44:06.400 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:44:06.400 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:44:06.416 - Senden: AT&F1E0Q0V1&C1&D2S0=0<cr> >> >> > 07-14-2010 13:44:06.618 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:44:06.618 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:44:06.634 - Senden: ATS30=0L1M1&M4&K1&H1B0B15N1X4<cr> >> >> > 07-14-2010 13:44:06.650 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:44:06.650 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:44:06.650 - Wählen >> >> > 07-14-2010 13:44:06.650 - TSP: Asynchroner Vorgang(0x000103dc) wird >> >> > abgeschlossen, Status 0x00000000 >> >> > 07-14-2010 13:44:06.650 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING >> >> > 07-14-2010 13:44:06.650 - TSP(0000): LINEEVENT: >> >> > LINECALLSTATE_PROCEEDING 07-14-2010 13:44:06.665 - Senden: >> >> > ATDT#######<cr> >> >> > 07-14-2010 13:44:41.391 - Empfangen: <cr><lf>CONNECT >> >> > 49333/ARQ/V90/LAPM/V42BIS<cr><lf> >> >> > 07-14-2010 13:44:41.391 - Interpretierte Antwort: Verbinden >> >> > 07-14-2010 13:44:41.391 - Verbindung wurde erstellt, aber das >> >> > CD-Signal war niedrig. Es wird gewartet bis das Signal sich erhöht. >> >> > 07-14-2010 13:44:41.422 - Das CD-Signal ist nach einer Wartezeit von >> >> > 20 ms immer noch niedrig. >> >> > 07-14-2010 13:44:41.453 - CD-Signal wurde heraufgesetzt. >> >> > 07-14-2010 13:44:41.453 - Verbindung hergestellt mit 49333 Bit/s >> >> > 07-14-2010 13:44:41.453 - Fehlerkontrolle an >> >> > 07-14-2010 13:44:41.453 - Datenkomprimierung an >> >> > 07-14-2010 13:44:41.453 - TSP(0000): LINEEVENT: >> >> > LINECALLSTATE_CONNECTED 07-14-2010 13:45:11.469 - Gelesen: Gesamt: 0, >> >> > Pro Sek.: 0, Geschrieben: Gesamt: 0, Pro Sek.: 0 >> >> > 07-14-2010 13:45:59.283 - TSP(0000): Anruf wird abgebrochen >> >> > 07-14-2010 13:45:59.283 - Modem aufhängen >> >> > 07-14-2010 13:45:59.283 - Modem hat nach DTR-Signal aufgehängt. >> >> > 07-14-2010 13:46:01.623 - CD-Signal wurde getrennt, da das DTR-Signal >> >> > herabgesetzt wurde. >> >> > 07-14-2010 13:46:01.623 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:46:01.623 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:46:01.638 - Senden: ATH<cr> >> >> > 07-14-2010 13:46:02.137 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:46:02.137 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:46:02.153 - Senden: at#ud<cr> >> >> > 07-14-2010 13:46:02.169 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:46:02.169 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:46:02.184 - Empfangen: <2A4D3263 >> >> > 00=09 02=00 03=02 10=15 11=0C 12=2E><cr><lf> >> >> > 07-14-2010 13:46:02.184 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:46:02.184 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:46:02.184 - Empfangen: <2A4D3263 >> >> > 17=09 20=0C 21=0E 22=0C80 23=0C80><cr><lf> >> >> > 07-14-2010 13:46:02.184 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:46:02.184 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:46:02.184 - Empfangen: <2A4D3263 >> >> > 26=6720 27=C0B5 32=00 33=00><cr><lf> >> >> > 07-14-2010 13:46:02.184 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:46:02.184 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:46:02.184 - Empfangen: <2A4D3263 >> >> > 34=6720 35=B64A 40=01 41=80 42=00 43=02 44=01><cr><lf> >> >> > 07-14-2010 13:46:02.184 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:46:02.184 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:46:02.184 - Empfangen: <2A4D3263 >> >> > 50=02 51=02 52=FFFFE309 53=02B491 54=00 55=00><cr><lf> >> >> > 07-14-2010 13:46:02.184 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:46:02.184 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:46:02.184 - Empfangen: <2A4D3263 >> >> > 56=017E 57=06D9 58=02 59=31><cr><lf> >> >> > 07-14-2010 13:46:02.184 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:46:02.184 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:46:02.184 - Empfangen: <2A4D3263 >> >> > 60=51 61=00><cr><lf> 07-14-2010 13:46:02.184 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:46:02.184 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:46:02.184 - Empfangen: <2A4D3263 >> >> > BA=0 BB=0 BC=0 BD=115200 BE=N BF=8><cr><lf> >> >> > 07-14-2010 13:46:02.184 - Empfangen: <cr><lf>DIAG >> >> > 07-14-2010 13:46:02.184 - Interpretierte Antwort: >> >> > Diagnoseinformationen 07-14-2010 13:46:02.184 - Empfangen: <2A4D3263 >> >> > FF="U.S. >> >> > ROBOTICS"><cr><lf> 07-14-2010 13:46:02.184 - Empfangen: >> >> > <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:46:02.184 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:46:02.184 - Diagnose >> >> > 07-14-2010 13:46:02.184 - Modemdiagnose: >> >> > 07-14-2010 13:46:02.184 - Verbindungsantwort: ..CONNECT >> >> > 49333/ARQ/V90/LAPM/V42BIS.. >> >> > 07-14-2010 13:46:02.184 - Version 0.9 >> >> > 07-14-2010 13:46:02.184 - Multimediamodus: Nur Daten >> >> > 07-14-2010 13:46:02.184 - DTE-DCE-Schnittstellenmodus: V.80 gerahmter >> >> > synchroner Modus >> >> > 07-14-2010 13:46:02.184 - Energiestand des Empfangssignals (in -dBm): >> >> > 21 07-14-2010 13:46:02.184 - Energiestand des Übertragungssignals (in >> >> > -dBm): 12 07-14-2010 13:46:02.184 - Geschätzter Geräuschpegel (in >> >> > -dBm): 46 07-14-2010 13:46:02.184 - Verzögerung: 9 ms >> >> > 07-14-2010 13:46:02.184 - Verhandlungsergebnis des >> >> > Übertragungsträgersignals: V.34 >> >> > 07-14-2010 13:46:02.184 - Verhandlungsergebnis des >> >> > Empfangsträgersignals: V.pcm (asymmetrisch) >> >> > 07-14-2010 13:46:02.184 - Symbolrate des Übertragungsträgersignals: >> >> > 3200 07-14-2010 13:46:02.184 - Symbolrate des Empfangsträgersignals: >> >> > 3200 07-14-2010 13:46:02.184 - Anfangsdatenrate des >> >> > Übertragungsträgersignals: 26400 >> >> > 07-14-2010 13:46:02.184 - Anfangsdatenrate des Empfangsträgersignals: >> >> > 49333 07-14-2010 13:46:02.184 - Angeforderte >> >> > erneuteTrägersignalübungen: 0 07-14-2010 13:46:02.184 - Zugelassene >> >> > erneuteTrägersignalübungen: 0 07-14-2010 13:46:02.184 - Endgültige >> >> > Übertragungsträgersignalrate: 26400 07-14-2010 13:46:02.184 - >> >> > Endgültige Empfangsträgersignalrate: 46666 07-14-2010 13:46:02.184 - >> >> > Protokollverhandlungsergebnis: V.42 LAPM 07-14-2010 13:46:02.184 - >> >> > Rahmengröße der Fehlersteuerung: 128 07-14-2010 13:46:02.184 - >> >> > Verbindungszeitlimits der Fehlersteuerung: 0 07-14-2010 13:46:02.184 - >> >> > Verbindungs-NAKs der Fehlersteuerung: 2 07-14-2010 13:46:02.184 - >> >> > Komprimierungverhandlungsergebnis: V.42bis 07-14-2010 13:46:02.184 - >> >> > Übertragungsflusssteuerung: V.24 ckt 106/133 07-14-2010 13:46:02.184 - >> >> > Empfangsflusssteuerung: V.24 ckt 106/133 07-14-2010 13:46:02.184 - Von >> >> > DTE gesendete übertragene Zeichen: -7415 07-14-2010 13:46:02.184 - An >> >> > DTE gesendete erhaltene Zeichen: 177297 07-14-2010 13:46:02.184 - >> >> > Verlorene übertragene Zeichen >> >> > (Datenüberlauffehler von DTE): 0 >> >> > 07-14-2010 13:46:02.184 - Verlorene empfangene Zeichen >> >> > (Datenüberlauffehler an DTE): 0 >> >> > 07-14-2010 13:46:02.184 - Übertragungsrahmenanzahl: 382 >> >> > 07-14-2010 13:46:02.184 - Empfangsrahmenanzahl: 1753 >> >> > 07-14-2010 13:46:02.184 - Fehleranzahl übertragener Rahmen: 2 >> >> > 07-14-2010 13:46:02.184 - Fehleranzahl erhaltener Rahmen: 49 >> >> > 07-14-2010 13:46:02.184 - Abbruchursache: DTE-Auflegbefehl >> >> > 07-14-2010 13:46:02.184 - Ereignisanzahl wartender Anrufe: 0 >> >> > 07-14-2010 13:46:02.184 - Unbekanntes Format (0x000000ba, 0x00000000) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:46:02.184 - Unbekanntes Format (0x000000bb, 0x00000000) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:46:02.184 - Unbekanntes Format (0x000000bc, 0x00000000) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:46:02.184 - Unbekanntes Format (0x000000bd, 0x00115200) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:46:02.184 - Unbekanntes Format (0x000000bf, 0x00000008) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:46:02.184 - Unbekanntes Format (0x000000ff, 0x000002ca) >> >> > für Tag 0x2a4d3263 >> >> > 07-14-2010 13:46:02.184 - 115200,8,N,1, ctsfl=1, rtsctl=2 >> >> > 07-14-2010 13:46:02.184 - Modem initialisieren >> >> > 07-14-2010 13:46:02.200 - Senden: AT<cr> >> >> > 07-14-2010 13:46:02.200 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:46:02.200 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:46:02.215 - Senden: AT&F1E0Q0V1&C1&D2S0=0<cr> >> >> > 07-14-2010 13:46:02.418 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:46:02.418 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:46:02.434 - Senden: ATS30=0L1M1&M4&K1&H1B0B15N1X4<cr> >> >> > 07-14-2010 13:46:02.449 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:46:02.449 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:46:02.449 - Auf Anruf warten >> >> > 07-14-2010 13:46:02.465 - Senden: AT+VCID=1<cr> >> >> > 07-14-2010 13:46:02.465 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:46:02.465 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:46:02.481 - Senden: ATS0=0<cr> >> >> > 07-14-2010 13:46:02.481 - Empfangen: <cr><lf>OK<cr><lf> >> >> > 07-14-2010 13:46:02.481 - Interpretierte Antwort: OK >> >> > 07-14-2010 13:46:02.481 - TSP(0000): LINEEVENT: >> >> > LINECALLSTATE_DISCONNECTED(0x1) >> >> > 07-14-2010 13:46:02.481 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE >> >> > 07-14-2010 13:46:02.481 - TSP: Asynchroner Vorgang(0x000100a9) wird >> >> > abgeschlossen, Status 0x00000000 >> >> > 07-14-2010 13:46:02.481 - TSP(0000): Anruf wird abgebrochen >> >> > 07-14-2010 13:46:02.481 - TSP: Asynchroner Vorgang(0x000100bd) wird >> >> > abgeschlossen, Status 0x00000000 >> >> > 07-14-2010 13:46:02.481 - TSP(0000): Anruf wird geschlossen >> >> > 07-14-2010 13:46:02.481 - DTR-Signal vor dem Beenden des Anschlusses >> >> > herabgesetzt. >> >> > 07-14-2010 13:46:02.590 - Sitzungsstatistik: >> >> > 07-14-2010 13:46:02.590 - Gelesen: 0 Bytes >> >> > 07-14-2010 13:46:02.590 - Geschrieben: 0 Bytes >> >
