Correlating Important Events › Understanding Configuration Manager › Configuration and Diagnostics › Page - TAP Protocol Issues

Page - TAP Protocol Issues

This section provides configuration and diagnostics information for the TAP paging protocol. Consider the following items:

• Because TAP is modem-based, it has to operate with the different modems available now, and may require special Hayes AT initialization strings to operate correctly. When to use an initialization string depends mainly on the quality of the phone line, baud rate, and how well the modem handles the phone service (with its current settings). A modem may work fine on one phone line with no initialization string but not on another. The higher the baud rate the greater the chance an initialization string is required.
• For modem parity the TAP specification recommends 7 bits, even parity, 1 stop bit (7E1), however the specification also notes that not all providers adhere to this. The most likely alternative is 8 bits, no parity, 1 stop bit (8N1). The TAP specification does not give average numbers, but the most likely maximum message length ranges from 80 to 256 characters. We recommend that you check with the provider.
• The following US providers have been tested with Notification Services TAP:
  • SkyTel
  • Arch
• The following modems have been tested with Notification Services TAP:

  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.

  • Boca Modem 33.6

    ATI3: V2.05C-V34_ACF_DS1

    ATI6: RC336DPFSP Rev. 44BC

    Init string: AT&F&C1&D2&G0-C0%C0%E2\N391=13

  • Boca Modem v.34 28.8

    ATI3: V1.000-V34_DS

    ATI6: RC288DPi Rev 04BC

    Init string: ATQ0E1F1N1W1\K5S37=11S82=128S95=47X4

  • Hayes Accura 56K + FAX

    ATI3: V1.120HY-K56-DLS

    ATI6: RC56DPF L8570A Rev 35.0/34.0

  • LASAT SAFIRE 288

    ATI3: LASAT Safire 288 V1.43C

    ATI6: RCV288DPi Rev 05BA

  • Lucent LT Winmodem

    ATI3: LT V.90 Data+Fax Modem Version 6.00

    ATI6: 6.00,0,19,11C1,0448,1668,2400

  • MICA (V.90/K56FLEX/FAX/V.110) Hex Modem Module (installed in a Cisco AS5300 series router)

    ATI3: Cisco MICA Hex Modem Module Product Information

    • Country Code 001
      V.90, K56FLEX 1.1, V.34+, V.32terbo, V.22bis, V.42, MNP2-4, V.42bis, MNP5,
      Fax, V.110, SS7_COT, TRACE, VOICE
    • HEX modem index 00
      CP code revision 2.7.2.0
      CP revision date May 30 2000
    • SP code revision 2.7.2.0
      SP revision date 05/30/2000 (MM/DD/YYYY)

    ATI6: Returns error, instead looked at ATI4

    ATI4: Cisco Mica V.90/K56FLEX/FAX/V.110

  • Unknown name internal modem

    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.

  • ZOOM V.92 External Modem (3049)

    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.

Troubleshooting

• If the protocol driver reports a timeout error while dialing or after connection, specify a modem initialization string. If the initialization string does not resolve the problem, or if no string is available, lower the baud rate. A higher baud rate may cause handshake problems and more sensitivity to line noise.
• If an error occurs during modem initialization, make sure the modem is connected properly and detected by the operating system:
  • On Windows, choose Control Panel, Phone and Modem Options. On the Modems tab, highlight the modem being used and click Properties. On the Diagnostics tab, click the Query Modem button. The modem should respond with response codes and not return an error. If it returns an error, the modem needs to be configured properly on Windows before it can be used with the protocol driver.
  • On UNIX/Linux, open a terminal program such as minicom. When the program has access to the modem device being used, enter the command ATQ0 and press Enter. The modem should respond with OK. If it does not return anything, the modem needs to be configured properly on UNIX/Linux before it can be used with the protocol driver.
• If your phone network requires a prefix number to dial out, the phone number used in the connection information must begin with this number and a comma. For example, if the dial-out prefix is 9, the phone number would be: 9,18005555555.

More information:

Configuration and Diagnostics