Skip to main content.
Index | Support | Documentation | FAQ

How Do I .... Check/Sort My Modem

On the hardware side here is a little guide to file incase needed.

Here are a few steps if your modem fails to work. (This applies to MultiTech modems only - anything else and the basics are here but for the fine detail you should refer to the modem manual.)

  1. Is it switched on? There should be AT LEAST one light lit - if not switch it on.

  2. Switch it off/on - to reset it.

  3. Is it plugged into a phone socket?
    Normally it will be but if you are in the bad habit of sharing with fax machines etc. then it may be un-plugged - check.

  4. Try dialing the modem number from a normal phone - are there any change in the lights? If it answers and you get 'funny' noises then the modem is correctly connected to the phone socket. Otherwise go back to step b)

  5. If the modem should automatically answer the phone then the 'TR' light should be lit? - Is it?

    If Not:

    1. Check the cables between the modem and computer
    2. Make sure the port is enabled
    3. Log in as root
    4. Modems are generally on tty2A so type
      disable tty2a tty2A (watch the lights any change?)
      enable tty2A (watch the lights any change?)
    5. If you don't know where it is plugged in type env | grep MODEM
      this should show you where it is - repeat step above.

  6. Check you can 'talk' to the modem.

    1. At the # prompt type xc
      You should see the xc menu - if you get 

             Lock file process 1600 on /dev/tty2A is still active - try later

      This means someone or some other process is using the modem. Have you left a screen logged in? To find out what/who has locked it type 

                ps -ef | grep number

      Where number is the process number from the Lock file line, in this example it would be 1600 e.g. 

                   ps -ef | grep 1600
             root  1600  1331  0 22:57:13   tty01    00:00:00 xc

      This indicates the user (root) is on the main screen (tty01) and is using the comms program (xc) - go to that screen and exit the application. What has locked it is shown on the right of the line - this should tell you what the m/c is trying to do. In most cases it's hung up as it can't communicate.

      Type disable tty2A tty2a and re-try the above step. If that works you will need to type enable tty2A after step vi) below.

    2. The 'TR' light should have come on - if not then either the modem is not connected to the computer or the system is mis-configured and xc does not know which port the modem is connected to.

    3. At the xc menu type 'T' to enter terminal mode.

    4. You will see 'Entering terminal mode escape character is ^O' The ^O (Control and O) may be replaced with ^A (Control and A) remember what it is set to.

    5. Type AT and press return - you should see OK If so, all is OK, type ^O (or ^A) to exit out of xc as the modem should be working.

    6. If nothing try until you get an OK
      ATZ (return)
      AT&F (return)
      switch modem off/on repeat above two commands

      If still nothing it would suggest the cable has come out off the back of the modem / computer or the modem is faulty.

    7. If you get an OK from v) above use this: (Note if you cannot get the modem to work, when you contact support they may get you to alter the next line - make a note of it for future).

      Type:

      AT&F
AT&D3&C1QE1X4$SB38400&W

      This resets the modem setting (note the $SB entry MAY need to checked with support). Exit out of xc with ^O (see iv above).

    8. If you have got this far and still nothing it is looking like the modem is faulty or the computer port is faulty - contact your hardware company.

  7. Make sure the system can dial-out, type: 

              /usr/lib/uucp/uutry -r bdsedin

    The screen will give some detail (a bit geeky) and in there you will see messages relating to

    NO DIALTONE Modem is not plugged into phone
    EXEC LOCAL FAILURE The system cannot 'talk' to the modem
    EXEC REMOTE FAILURE The wrong number has been dialed or the remote modem has not answered.
    NO CARRIER There is not a modem on the number dialed.

    If it reached 'Conversation Complete - Status Succeeded' then press the <DEL> key as all appears to be working.

    If you get 'Conversation Complete - Status Failed' then it failed!! press the <DEL> key and type lp /tmp/bdsedin send the printout up to support so they can see what is what.

  8. Get someone to dial into you computer - it should be working.

  9. Contact support.