Paging Software for Wireless Messaging to PCS phones, Alphanumeric Pagers, and PDA's InfoRad's FAQs 
InfoRad Text Messaging When a failure to communicate is not an option.®

Categories :  | FAQs | Interactive | ServicesAndReceivers | ErrorHandling | Users_Manuals |



Search

Found 78 total topics.


FAQs



1. I have a High Speed Internet (cable modem/DSL line/LAN) connection, Do I Need to be Online to Send Text Messages with InfoRad Wireless software?


It is up to your paging or cellular company as to whether or not they support Dialup Text Messaging (using a Dialup Modem connected to your PC - Show Me). Therefore, if your Paging or Cellular company supports Dialup Text Messaging (via TAP), then you do not need to be online to send text messages. However, you do need a Dialup Modem. If your Paging or Cellular company supports Internet Text Messaging (using your High Speed DSL or Cable Internet connection), then you do need to be online to send text messages.
  • View a List of Dialup Messaging Services
  • List All Messaging Services








  • 2. Do you have a Dialup Modem Access Number for my Local Paging Company?


    Local Modem access numbers are available through your Messaging Service. Please call your local Paging Representative for a local access number in your area, then refer to our Interactive Demos for a walkthrough for setting up your InfoRad software. We have a List of Nationwide Access Numbers







    3. If you Receive a Winpage.exe error


    Possible issues:

    1) Turn off any Windows Compatibility settings (Shortcut Icon - Properties or Winpage.exe file - Properties)
    2) On the InfoRad Wireless program folder, grant 'Users' group Full Control under Security permissions
    3) If using a MODEM for dial-up paging/texting, power cycle the PC - and the MODEM if external
    4) Verify that Telephony (TAPI) service is running on the PC (Administrative Tools - Services - Telephony). The Telephony service should be listed and Started)
    5) If you have been using Scheduled Messages, rename the 'SCHEDPGS.IRT' file in the InfoRad Wireless program folder and see if that resolves the issue.

    If none of the above help resolve the issue Please Contact InfoRad Tech Support (techsupport@inforad.com)






    4. Alternative Messaging Services - A Family Tree Approach


    The following is a list of Alternative Messaging Services that you might be able to use within the InfoRad software:



    USA Mobility Alternatives

    American Messaging Alternatives

    Verizon PCS - Internet SMTP (However, we do not necessarily recommend connecting directly to Verizon's email servers)

    There are two email servers with Verizon - smtp-bb.vtext.com and smtp-sl.vtext.com. They are interchangeable.

    Verizon also supports Dialup TAP.

    AT&T Wireless / Cingular PCS - Internet SMTP

    There are various email addresses for AT&T Wireless / Cingular phones. Therefore, you may want to contact an AT&T Wireless representative for that particular cell phone if you are not certain. Otherwise, start at the top and work your way down:

    AT&T Wireless / Cingular's Enterprise Paging for cell phones is a different plan and would use a different email address from the ones above:

    However, AT&T Wireless / Cingular's Enterprise Paging also supports the Internet Paging Protocols - SNPP and WCTP - as well as Dialup TAP, unlike the standard text messaging email addresses listed above.

     

    You can also refer to Brad Dye's website for a nice look at the Family Tree of Paging Companies.







    5. Telus Mobility - Dialup TAP


    Please contact your Telus representative for the local Telus Dial-up TAP MODEM phone number.






    ServicesAndReceivers



    6. ATT Wireless - Dialup TAP

    Website: www.wireless.att.com
    Messaging Service: (800) 909-4602 : N/A
    Receiver ID: 10-digit-phone-number

    Show Me






    7. ATT Wireless Enterprise Paging 1 - Dialup TAP

    Website: www.enterprisepaging.com/faq.jsp#01
    Messaging Service: (888) 298-3562 : N/A
    Receiver ID: 10-digit-phone-number

    Show Me






    8. ATT Wireless Enterprise Paging 2 - Dialup TAP

    Website: www.enterprisepaging.com/faq.jsp#01
    Messaging Service: (408) 961-2819 : N/A
    Receiver ID: 10-digit-phone-number

    Show Me






    9. American Messaging 1 (Nationwide) Paging - Dialup TAP

    Website: www.americanmessaging.net/modemnumbers.html
    Messaging Service: (888) 206-7243 : N/A
    Receiver ID: 10-digit-phone-number

    Show Me






    10. American Messaging 2 (Nationwide) Paging - Dialup TAP

    Website: www.americanmessaging.net/modemnumbers.html
    Messaging Service: (888) 592-7564 : N/A
    Receiver ID: 10-digit-phone-number

    Show Me






    11. Arch Wireless (2400) Paging - Dialup TAP

    Website: www.archwireless.com
    Messaging Service: (800) 946-4644 : N/A
    Receiver ID: 10-digit-pager-number

    Show Me






    12. Arch Wireless (33.6) Paging - Dialup TAP

    Website: www.archwireless.com
    Messaging Service: (800) 250-6325 : N/A
    Receiver ID: 10-digit-pager-number

    Show Me






    13. Baileys Comm Paging - Dialup TAP

    Website: www.baileyspaging.com
    Messaging Service: (706) 771-1792 : N/A
    Receiver ID: 7-digit-PIN-number

    Show Me






    14. Banner Communications Paging - Dialup TAP

    Website: bannercom.com
    Messaging Service: (530) 265-7799 : N/A
    Receiver ID: 7-digit-pager-number

    Show Me






    15. Bell Mobility Ca (800) PCS - Dialup TAP

    Website: www.bell.ca
    Messaging Service: (800) 331-6352 : N/A
    Receiver ID: 10-digit-pager-number

    Show Me






    16. CellularPage (423) - Dial-up TAP

    Website: pager.cellularpage.net
    Messaging Service: (423) 714-1591 : N/A
    Receiver ID: 7-digit-phone-number

    Show Me






    17. Electronic Engineering Paging - Dialup TAP

    Website: www.connectingyou.com
    Messaging Service: (515) 234-0999 : N/A
    Receiver ID: 7-digit-pager-number

    Show Me






    18. First Page Paging - Dial-up TAP

    Website: www.firstpage.net
    Messaging Service: (843) 764-6990 : N/A
    Receiver ID: 7-digit-pager-number

    Show Me






    19. Heartland Communications Paging - Dialup TAP

    Website: www.heartlandcommunications.com/alpha.html
    Messaging Service: (815) 965-2184 : N/A
    Receiver ID: 10-digit-pager-number

    Show Me






    20. Metrocall (559) Paging - Dialup TAP

    Website: www.metrocall.com
    Messaging Service: (559) 261-7099 : N/A
    Receiver ID: 7-digit-pager-number

    Show Me






    21. Metrocall (775) Paging - Dialup TAP

    Website: www.metrocall.com
    Messaging Service: (775) 328-2169 : N/A
    Receiver ID: 7-digit-pager-number

    Show Me






    22. Midwest Paging northern area TAP

    Website: www.midwestpaging.com
    Messaging Service: (800) 946-2024 : N/A
    Receiver ID: 7-digit-pager-number

    Show Me






    23. Midwest Paging southern area TAP

    Website: www.midwestpaging.com
    Messaging Service: (800) 433-7662 : N/A
    Receiver ID: 7-digit-pager-number

    Show Me






    24. Mobilfone Paging - Dialup TAP

    Website: www.mobilfone.com
    Messaging Service: (816) 864-7000 : N/A
    Receiver ID: 7-digit-pager-number

    Show Me






    25. Morris Wireless Paging (803) - Dialup TAP

    Website: www.morriswireless.com
    Messaging Service: (706) 731-9764 : N/A
    Receiver ID: 7-digit-pager-number

    Show Me






    26. Nextel PCS - Dialup TAP

    Website: www.nextel.com
    Messaging Service: (aaa) xxx-6683 -- aaa = areacode; xxx = Exchange number (typically the same as your Nextel phone number unless your number has been transferred from another carrier) : N/A
    Receiver ID: 10-digit-phone-number

    Show Me






    27. PortaPhone Paging - Internet SNPP

    Website: www.graylink.com
    Messaging Service: epage.graylink.com : 444
    Receiver ID: 10-digit-pager-number

    Show Me






    28. Radio Comm Paging - Dialup TAP

    Website: www.radiocommpaging.com
    Messaging Service: (636) 818-0888 : N/A
    Receiver ID: 7-digit-pager-number

    Show Me






    29. Ram-Page Paging - Dialup TAP

    Website: www.ram-page.com
    Messaging Service: (606) 327-9936 : N/A
    Receiver ID: 10-digit-phone-number

    Show Me






    30. Range Paging - Dail-up TAP

    Website: http://www.rangepaging.com/
    Messaging Service: (218) 279-4600 : N/A
    Receiver ID: 7-digit-phone-number

    Show Me






    31. Rogers Two-Way Paging - Dialup TAP

    Website: www.rogerstwoway.com
    Messaging Service: (218) 759-3828 : N/A
    Receiver ID: 7-digit-pager-number

    Show Me






    32. Rogers Wireless Canada - Dialup TAP 1

    Website: www.rogers.ca
    Messaging Service: (416) 402-1250 : N/A
    Receiver ID: 10-digit-phone-number

    Show Me






    33. Rogers Wireless Canada - Dialup TAP 2

    Website: www.rogers.ca
    Messaging Service: (800) 665-1644 : N/A
    Receiver ID: 10-digit-phone-number

    Show Me






    34. Salisbury Comm Paging - Dialup TAP

    Website: www.sbycomm.com
    Messaging Service: (410) 270-1702 : N/A
    Receiver ID: 7-digit-pager-number

    Show Me






    35. Satellink Paging - Dialup TAP

    Website: www.satellink.net
    Messaging Service: (888) 237-5293 : N/A
    Receiver ID: 10-digit-pager-number

    Show Me






    36. Sharp (AllPage) Paging - Dialup TAP

    Website: www.sharpcom.com/pager/software/index.htm
    Messaging Service: (256) 517-5624 : N/A
    Receiver ID: 10-digit-pager-number

    Show Me






    37. Skytel Paging - Dialup TAP

    Website: www.skytel.com
    Messaging Service: (800) 679-2778 : N/A
    Receiver ID: 10-digit-pager-number

    Show Me






    38. Southern LINC Paging - Dialup TAP

    Website: www.southernlinc.com/pagesoftware.asp
    Messaging Service: (800) 557-6747 : N/A
    Receiver ID: 10-digit-phone-number

    Show Me






    39. Sprint PCS - Dialup TAP

    Website: www.sprintpcs.com
    Messaging Service: (888) 656-1727 : N/A
    Receiver ID: 10-digit-phone-number

    Show Me






    40. Telecator Paging - Dialup TAP

    Website: www.telecator.com
    Messaging Service: (705) 876-5928 : N/A
    Receiver ID: 7-digit-PIN-number

    Show Me






    41. Teletouch Paging - Dialup TAP

    Website: www.teletouchpaging.com
    Messaging Service: (800) 844-9811 : N/A
    Receiver ID: 10-digit-pager-number

    Show Me






    42. Telus Mobility - Dialup TAP

    Website: www.telusmobility.com/pdf/tap_telus_doc.pdf
    Messaging Service: (250) 319-6820 : N/A
    Receiver ID: 1XXX5551212

    Show Me






    43. Telus Mobility - Dialup TAP

    Website: www.telusmobility.com/pdf/tap_telus_doc.pdf
    Messaging Service: (XXX) 555-1212 : NULL
    Receiver ID: 1XXX5551212

    Show Me






    44. US Cellular PCS - Dialup TAP

    Website: www.uscc.com
    Messaging Service: (866) 559-8398 :
    Receiver ID: 10-digit-phone-number

    Show Me






    45. USA Mobility Paging - Dialup TAP (2400)

    Website: www.usamobility.net
    Messaging Service: (800) 946-4644 : N/A
    Receiver ID: 10-digit-pager-number

    Show Me






    46. USA Mobility Paging - Dialup TAP (33.6)

    Website: www.usamobility.net
    Messaging Service: (800) 250-6325 : N/A
    Receiver ID: 10-digit-pager-number

    Show Me






    47. Unity (304) Paging - Dialup TAP

    Website: www.ram-page.com
    Messaging Service: (304) 540-2880 : N/A
    Receiver ID: 7-digit-pager-number

    Show Me






    48. Verizon (CA) Paging - Dialup TAP

    Website: www.inforad.com/techsupport/MessagingServices/Verizon/
    Messaging Service: (416) 462-6700 : N/A
    Receiver ID: 10-digit-pager-number

    Show Me






    49. Verizon (CLEV) Paging - Dialup TAP

    Website: www.inforad.com/techsupport/MessagingServices/Verizon/TAP%20Phone%20Numbers.htm
    Messaging Service: (216) 549-2471 : N/A
    Receiver ID: 10-digit-pager-number

    Show Me






    50. Verizon PCS - Dialup TAP

    Website: www.verizonwireless.com
    Messaging Service: (866) 823-0501 : N/A
    Receiver ID: 10-digit-phone-number

    Show Me






    51. Weblink 2-way Paging - Dialup TAP

    Website: www.weblinkwireless.com
    Messaging Service: (800) 557-8081 : N/A
    Receiver ID: 10-digit-pager-number

    Show Me






    ErrorHandling



    52. (1104) Local Error: Could not access modem

    • The first question to ask: "Do you not have a high speed Internet connection or does your paging company not support text messaging via the Internet?" If you have a high speed Internet connection and your paging or cellular company supports Internet text messaging, then change your Receiver (under Edit, Receivers) to use an Internet Messaging Service (WCTP, SNPP, or SMTP). If you are unsure whether or not your paging company supports text messaging via the Internet, then call your local paging representative to find out for sure. Most, if not all, cellular companies support text messaging via Internet email (Show Me) or via the Internet SNPP (Show Me).

      Otherwise, if you know that you do need to dialup to your paging company, then here is another question: "Does InfoRad software show a name of a modem under Setup, Communications?" This error indicates that your InfoRad software is not communicating properly with the modem, no modem exists on the Com Port, your modem is not properly connected to your PC, or the modem is not powered up.

    • Restart the PC. This could be because the port that the Modem uses could not be opened (port was busy, or it does not exist, etc.) or because the Modem itself did not respond (Modem is turned off, or is using another port, etc.). So make sure that the Modem is working properly and is not being used by another program. Many times, it is helpful just to restart the PC, especially after new updates have been installed.

    If it is an external Modem, it’s more obvious that the Modem is turned on and working properly. Make sure the lights are working as they should and make sure that the Modem’s serial cable is properly seated at both ends (at the Modem itself and at the PC). Also, make sure that the phone line is plugged into the Line side of the Modem and that (if a phone is plugged into the Modem) the phone is plugged into the Phone side of the Modem.

    If all this checks out ok, then continue on below.

    • Reinstall the InfoRad software (Walk Me Through). During the installation, make sure to choose to "Keep the existing files/paging database" and when prompted, "Override the system's modem configuration..." and click on Create to make sure that the InfoRad software is able to communicate with the Modem. If a string is generated, the test is complete, click it back to "Use the system's modem configuration..." Click OK to finish the installation. Try sending another test page.

    • Reinstall or Upgrade the Modem's driver. Make sure to restart the computer if the Modem's driver installation program requires. You may also want to reinstall the InfoRad software again as directed above and see if the software is able to communicate with the Modem during the installation as described.

    • Get/Try another Modem. This is the last resort that no one really wants to hear. However, getting a new Modem or trying a different Modem may be the easiest way to resolve this issue at this point. InfoRad Tech Supports recommends any type of Modem with a “Conexant” chipset or any US Robotics Modem (Internal PCI or External Serial – not USB. We do not recommend USB Modems because of their Win-modem resemblance).

    • Registered Users - Contact InfoRad Tech Support. If you are beyond the point of frustration after exhausting all efforts above, the please contact us so that we can help. techsupport@inforad.com







    53. (1105) Local Error: Line is not available
    This means that the line device selected for sending pages is unavailable to the system. Usually this means that the line is in use by some other application.
    • Make sure that the phone line is plugged into the Line side of the Modem and that (if a phone is plugged into the Modem) the phone is plugged into the Phone side of the Modem.



    • Connect a phone to the modem's phone port so that you can listen in on the call made by the InfoRad software. Make sure that there is a dial tone prior to sending a message.







    54. (1201) Remote Error: Could not handshake with service
    InfoRad Wireless software was able to CONNECT to the answering modem, but is receiving no further response from the messaging service.
    • Check to ensure the messaging service modem access number is correct. Note that it may also be called the Terminal phone number, AlphaPort phone number, or Access number.

    • Check the messaging service communication parameters – Baud Rate, Data Bits, Parity, and Stop Bit. (Note: Most wireless messaging services are 1200 Baud, sometimes 2400 or 300; and are almostalways 7 data bits, even parity, 1 stop bit.)

    • Check the modem selection in the Communications Setup.

    • Select Override in the ModemConfiguration dialog, and then click on the Create button to build a unique initialization string for your modem.

    • Reference your modem manual (reference AT command section) to construct a modem initialization string for your modem.

    • Check with your modem manufacturer to ensure that your modem supports the wireless messaging service Baud Rate and data settings (Ex: 1200, 7, even 1). Note: Modems that are known to not work with numerous paging companies are Intel 53X Modems and USB Modems. However, this does not mean that these modems will not work for you. It does mean that InfoRad Tech Support might not be able to get your modem to communicate properly with the paging company. Tech Support may recommend that you purchase another modem, which may save time and money.







    55. (1202) Remote Error: Service did not respond to message
    The wireless messaging service did not return any response code after the InfoRad Wireless software sent a data block; generally a result of a poor connection, or can be a problem at the messaging service. Sometimes this error may be returned from the paging system (or paging company) if an incorrect pager ID is entered. Make sure that you are using the proper code or phone number, normally the seven or ten-digit phone number of the pager. Do not use dashes, spaces, or parentheses.
    • Verify the Receiver ID (Under Edit, Receivers)

    • Retry sending the message(s).

    • If received when sending multiple messages, check with your wireless messaging service for any limit on the number of messages that can be sent in a single dial-upsession.







    56. (1203) Remote Error: Message was not acknowledged
    The messaging service responded to a data block with the NAK code.
    • Retry sending the message.
    • Try Removing the area code from the wireless receiver ID number (text pagers). NOTE: The Receiver's ID (under Edit, Receivers) is normally the seven or ten-digit phone number of the pager. Do not use dashes, spaces, or parentheses.
    • Verify that the proper seven or ten-digit wireless receiver ID number (or phone number) is entered.
    • Use the wireless receiver’s PIN number.
    • Check the maximum message length, lower the message length - setting to 80 characters - and retry. You can change the Maximum Message Length under Edit, Messaging Services. Select the appropriate Messaging Service being used by the affected Receiver(s) and click the Edit button.







    57. (1204) Remote Error: Forced to abandon by service
    It is most likely that either the Receiver ID is entered incorrectly or the pager is not setup for "UVB" with your paging company

    Possible Cause #1:

    Enter the correct ten-digit phone number of the pager, do not use dashes, spaces, or parentheses.

    Possible Cause #2:

    If you have Arch (USA Mobility) pagers and you know that you have entered the correct phone number, then call your local Arch representative and verify that the pager(s) are setup for UVB.








    58. (1205) Remote Error: Service forced a disconnect
    The wireless messaging service sent the InfoRad Wireless software a disconnect code. This can happen when the service does not accept InfoRad Wireless software response to the login prompt.
    • Check that any password is valid in the Wireless Messaging Service setup advanced properties. (Note that most wireless messaging services do not require a password.)
    • A [P in error messages in the Failed Messages error screen indicates that the wireless receiver ID # is incorrect—try and use the PIN number and not the wireless receiver phone number in the receiver’s ID Number field. Double-check the receiver ID to make sure it was correctly entered.
    • Some messaging companies will reject messages if the message is too long. Try sending a short message. If it successfully sends, verify the allowable message length with your messaging company, and then set the message size in the wireless messaging service.
    • Make sure the wireless receiver has been activated or not disconnected by the messaging company. Optionally, try messaging it from your phone as a numeric pager.
    • Verify that you are dialing the correct access number for your receiver—wireless messaging services sometimes have multiple systems, and your wireless receiver number must be valid on the system to which you are connecting.







    59. (1206) Remote Error: Invalid reply to login
    The messaging service did not properly respond after the InfoRad Wireless software’s login.
    • Retry sending the message.
    • Check the data bits and parity settings (Messaging Service Advanced Settings).
    • Check that any password is valid. Remove the password if it is not required by the messaging service.
    • Try changing the baud rate (Messaging Service Advanced Settings).
    • Check the modem selection in the Communications Setup to ensure that the proper modem is selected.
    • Select Override in the modem configuration, and click on the Create button to build a custom initialization string for your modem.
    • Reference the ‘Using High Speed and Fax modems’ section of the manual or on-line Help and your modem’s manual (reference AT command section) to construct a modem initialization string for your modem.
    • Check with your modem manufacturer to insure your modem supports the messaging service Baud Rate and data settings (Ex: 1200, 7, even, 1).







    60. (1301) Communications Error: Could not connect with remote modem

    This appears when the phone was successfully dialed, but no CONNECT message was received. Common causes are bad service phone numbers, bad modem initialization strings, bad modems (on either end), incorrectly installed modems (no dial tone) and so on.
    • Verify that you correctly entered your messaging service phone number and parameters such as baud rate, data parity, and stop bits. You should always hear a high-pitched modem connection tone when dialing the correct number.
    • Verify your modem selection or custom init string. If you are using a Fax or high-speed modem disable the data compression and error correction features; see Using High Speed and Fax Modems section for more information.
    • Verify that you are dialing the correct service number for your wireless receiver—messaging services sometimes have multiple service numbers, and your wireless receiver number must be valid on the number you are dialing.
    • Verify your dialing location settings and selection.
    • Check if the messaging service requires a password, and if so, verify that password (normally, messaging services don’t use a password).
    • Double-check the custom modem initialization string, if the override option was used during modem setup.
    • Make sure the modem isn’t attempting to connect to a fax number.
    • The wireless messaging system may be experiencing technical difficulties. Check with your messaging service.







    61. (1303) Communications Error: There was no dial tone on the dialing line

    This appears when the local modem could not detect a dial tone, and so could not begin dialing.
    • If you are using a USB modem, then our first recommendation would be to try using another modem. We recommend either any Internal PCI modem with a Conexant chipset, or an External Serial US Robotics modem.
    • Verify the modem is correctly installed.
    • Check to see if the phone line is in use or is working properly.
    • Verify that your modem has power, that you have dial tone at your modem, and that your phone line is plugged into the modem jack labeled line.
    • Verify that your dialing location and options are correct (Windows Telephony or Modems control panels).
    • Verify your modem selection. If you have a digital phone system, you may need to use a special jack to access an analog phone line. Plugging your modem directly into a digital phone system will not work, and may damage the modem or the phone system.







    62. (1304) Communications Error: The called number was busy

    This appears when the program has already redialed the service provider the specified number of times, and received a busy signal every time.
    • This error may appear if you need to dial an 8 or 9 to get an outside line (for long distance) but do not have the software setup to do so. If you are familiar with adding this as a rule to the Dialing Properties, do so. Otherwise, you can "hard code" this into the phone number of the Messaging Service. Under Edit, Messaging Services, select the appropriate Messaging Service and click Edit. Uncheck the option to "Use Area Code, Country Code, ..." and enter the appropriate Dialing String to the Phone Number (Ie. 8, 1-800-555-1212).
    • Verify the messaging service access number is correct.
    • Check if the messaging service is busy or experiencing problems.
    • Increase the re-dial on busy setting in Communications Setup, Advanced Modem Settings, Dialing Options.







    63. (1399) Communications Error

    The generic communications error that appears when there is some problem reading data from the communications port.
    • Check for any device conflicts.






    64. (1400) TAPI error: TAPI initialization failed

    To start up TAPI, the program must load some TAPI / operating system DLLs. If the DLLs cannot be loaded, this error will appear. You may need to install/reinstall TAPI. You can do so by downloading and installing the latest Service Pack for Windows. Microsoft's Internet Explorer may also come with TAPI. If that does not help, then you may need to add or configure TAPI under Start, Control Panel, double click on the Phone and Modem Options, Click on the Advanced tab and make sure that all of the appropriate Service Providers are added. Windows should have them configured properly for you. You may also want to try restarting the PC. If the problem persists, try reinstalling the InfoRad software and/or your Modem driver.







    65. (1401) TAPI error: Could not negotiate common API version

    There are different versions of TAPI available. Windows 95 shipped with TAPI 1.4 and Windows NT 4.0 shipped with TAPI 2.0. InfoRad Wireless tells the system that it can support TAPI 1.4 and the system responds by enabling only the features available in that version. If there is some problem with this process (for example, if the system only supports TAPI 1.3 or lower), you may see this error. Normally, simply rebooting the computer should fix this problem.







    66. (1402) TAPI error: Unable to query TAPI address capabilities

    Before placing a call on a device, the program queries TAPI about the line’s capabilities. This message shows up when TAPI will not or can not respond to the request.







    67. (1405) TAPI error: Selected device does not support data calls

    TAPI devices include modems, fax boards, ISDN telephones, and other devices, not all of which can transfer data the way modems can. Before sending messages, InfoRad Wireless checks to be sure that the device the user selected is in fact a data modem, and not some other TAPI device.







    68. (1410) TAPI error: Could not open line device

    Before placing a call, InfoRad Wireless checks to be sure that the line is available (and shows error 1105 if it is not), but if there is some problem opening the line (even if TAPI claimed the line was available) this is the error message.







    69. (1415) TAPI error: Could not specify status messages to monitor

    After opening a line device, the InfoRad Wireless software informs TAPI which status messages are important for the call. If there is a problem doing this, this error appears.







    70. (1425) TAPI error: Could not specify port settings prior to opening port

    Before placing a call, the InfoRad Wireless software attempts to set the baud rate, data bits, stop bits, flow control, error correction and data compression settings specified for the modem and messaging service in use. If there is a problem doing this, this error appears. Verify with your modem manufacturer that your modem supports the baud rate and data settings required by your messaging service (usually 300, 100, or 2400 baud with 7 Data Bits, Even parity, 1 Stop Bit).







    71. (1435) TAPI error: Could not create call parameters

    This error appears if the data structure containing parameters for TAPI cannot be created. This would only happen if the computer ran out of memory.






    72. (1440) TAPI error: Call to lineMakeCall() failed

    InfoRad wireless uses the lineMakeCall() function of TAPI, which opens the serial port. This error appears when this call fails.







    73. (1450) TAPI error: No response to lineMakeCall()

    After the InfoRad software places a phone call with TAPI (or after you attempt to send a message), the InfoRad Wireless software expects to get some responses back from TAPI, which is software that comes with Windows and handles other software trying to get access to the dialup modem, including an announcement that the modems have either connected or disconnected. If those responses do not arrive within 60 seconds, this error appears. InfoRad is confident that your InfoRad software will connect and disconnect your modem properly (from years of experience). However, there may be other software that does not release the modem properly. Sometimes, you may even have to log off or reboot the PC in order to get the modem disconnected. You may want to investigate other software that is using the modem to see if there are any issues with that software. This could be critical to the InfoRad software working properly.







    74. (1455) TAPI error: Could not get port handle from TAPI

    After placing the phone call, the InfoRad Wireless software asks TAPI for direct access to the COM port, through which it can send and receive data. If the port handle is unavailable for some reason, this error appears.







    75. (1460) TAPI error: Could not change call parameters

    After dialing a call in Override mode (Modem Configuration), the InfoRad Wireless software attempts to switch back to standard TAPI mode to actually send pages, then hang up. If the switch back to standard TAPI mode does not work, this error appears.







    76. (1499) TAPI error: Unexpected TAPI error

    This is error message used in cases where the InfoRad Wireless software is able to detect that something has gone wrong with TAPI, but the error is not one of the above listed errors.







    77. (7002) WCTP Error: Could not POST WCTP message to gateway

    • First attempt to fix error 7002, using our website, verify the WCTP information (Show Me) making sure that a valid WCTP Server address is entered correctly for the appropriate Messaging Service under Edit, Messaging Services, or that the WCTP Server address has not changed. Verify the name of the Messaging Service that is being used by the affected Receivers (under Edit, Receivers) by matching it to the appropriate Messaging Service listed under Edit, Messaging Services.
    • Second attempt to fix error 7002, do you have a working Internet connection? Simply opening up your Internet browser and seeing the pages you normally go to may not be enough because those pages can be cached locally on your computer. Try browsing to a page that you've never been to before to make sure your Internet connection is working properly.
    • Third attempt to fix error 7002,  is there a firewall / Internet security software blocking your Internet connection?  Sending text messages via WCTP is, in many respects, just like browsing the Internet. However, make sure that there is no firewall blocking your connection or that your network does not require use of a Proxy Server (See next item). Contact your local IT/IS personnel for support with your PC's firewall / Internet security software.
    • Fourth attempt to fix error 7002, some networks utilize a Proxy Server for internet access. If your network utilizes a Proxy Server, you need to setup Proxy Server Authentication under Setup, Internet Settings, HTTP Proxy Server Authentication, check the ‘Proxy server requires authentication’ checkbox and enter your Username and Password for Proxy Server access. (Typically, Proxy Server access can be the same as your Windows Logon Username and Password, but you may need to check with your network admin for Proxy Logon settings). Refer to Error 7004 or Error 7005 for more information on Proxy errors.
    • Fifth attempt to fix error 7002, it may be possible that the Messaging Service to which you are sending is down temporarily or undergoing maintenance. If none of the items above are the source of the 7002 error, another possible cause is that the Messaging Services WCTP Server to which you need to send text messages is currently not operational. Here we recommend that you contact your local paging representative to find out if they are having difficulties or if they are performing maintenance. You can also send us an email to see if we are getting bombarded by customers having this same problem.



    • 7002 error Temporary Workaround #1  - Some Messaging Services (or Paging Companies) have merged from two or more Messaging Services into one company and your device(s) may work through one of their original and still operational WCTP Servers. Therefore, try switching to an alternative, but equivalent Messaging Service. For example, American Messaging pagers may work through the Verizon WCTP Server, while USA Mobility pagers may work through Arch or etrocall WCTP Servers.
    •  7002 error Temporary Workaround #2 – Most Messaging Services support multiple or alternative protocols for message submission. Try switching your Receivers to an alternate protocol supported by your Messaging Service. For instance, if you are currently using your Messaging Services WCTP service, try switching to the SNPP or TAP or SMTP service for the same Messaging Service (Please note that alternate protocols may require a change to te format of the ReceiverID. For example, SMTP will require the ReceiverID to be the e-mail address of the device, or a local TAP dial-up service may require the 7- digit phone number of the device, instead of the 10-digit number required for most nationwide TAP numbers and WCTP and SNPP services).
    • 7002 error Temporary Workaround #3 -- Turn on ‘Automatic Retries’.  Desktop, Watch-IT and Enterprise products: Under the Setup Menu | Select Preferences | Check the option to ‘Retry failed manually entered messages’. Enterprise SV product: Enterprise SV Controller -- Under the Edit Menu | Select Preferences | Check the option to ‘Retry failed messages’ and enter Retry settings. With Retries turned on,  see if messages now go through without returning an error. You may also want to check the pager to make sure that the Receiver is not receiving duplicate messages.

     







    78. System Code 1460 : Operation Timed Out

    Make sure you have the Dialup Properties set for TAPI, even if you are not using a Dialup Modem. Go to Control Panel >> Phone and Modem Options >> Enter a Default Area Code under the Dialing Tab.









    Powered by smallcapitalbusiness.com
    www.InfoRad.com