This section provides configuration and diagnostics information for the TAP paging protocol. Consider the following items:
Note: ATI3 is the modem driver version and ATI6 is the chipset type. Modems listed with an init string require that the string be set for a successful connection.
ATI3: V2.05C-V34_ACF_DS1
ATI6: RC336DPFSP Rev. 44BC
Init string: AT&F&C1&D2&G0-C0%C0%E2\N391=13
ATI3: V1.000-V34_DS
ATI6: RC288DPi Rev 04BC
Init string: ATQ0E1F1N1W1\K5S37=11S82=128S95=47X4
ATI3: V1.120HY-K56-DLS
ATI6: RC56DPF L8570A Rev 35.0/34.0
ATI3: LASAT Safire 288 V1.43C
ATI6: RCV288DPi Rev 05BA
ATI3: LT V.90 Data+Fax Modem Version 6.00
ATI6: 6.00,0,19,11C1,0448,1668,2400
ATI3: Cisco MICA Hex Modem Module Product Information
ATI6: Returns error, instead looked at ATI4
ATI4: Cisco Mica V.90/K56FLEX/FAX/V.110
ATI3: V1.301-V34_DP
ATI6: RC288Dpi Rev 05BA
Note: The modem works fine on UNIX/Linux. On Windows it works fine when the TAP protocol uses TAPI, but has problems when TAP uses the COM port directly. Direct COM port access works only when previous use of the modem worked with TAPI, but stops working when the modem is reset.
ATI3: Zoom ACF3_V1.801A-V92 -C Z201
ATI6: RCV56DPF-PLL L8571A Rev 50.02/34.00
Init string: ATZ&F~AT+IBC=0,0,0,,,,,0;+PCW=2;+PMH=1;+PIG=1~ATE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2~ATS7=60S30=0L1M0+ES=3,0,2;+DS=3;+IFC=2,2;BX4
Note: The init string was taken from the modem's Windows driver init string. This init string and no init string provided successful connections most of the time, but not always. The ~ character represents a carriage return.
|
Copyright © 2010 CA.
All rights reserved.
|
|