37

r Pro v3.0

a phone system  does  (i.e. just because  you dial a  9  to get an outside  line on your phone  system, you may not

need one on your modem  line,  or vice versa).  After dialing  the number, you should  hear it ring and then  pickup.

Next you should  hear a long high pitched  tone (at least 10 seconds  and steady).  If you don t, you have the

wrong  number  for your paging service  provider s  terminal.   Often times  if you are given the wrong  number, you

will  hear a voice message  or a beep beep beep.

5.6.4

Make sure you are connecting  to a paging terminal

If you have gotten this far, you are at least  calling  a modem.   Next, we have to be sure  we  can connect to the

modem  on the other  end, and that it is  a paging  terminal  that supports  the TAP/IXO protocol.

Follow the steps  in the first section  so  that you are running  HyperTerminal  and are getting an  OK  response  to

typing  AT .  Now type  ATDT   where    should   be replaced  with the

phone  number  you entered into  the carrier in r  Pro.  After the modem  dials  it should  connect  to the

modem  at the other  end and you should  get a  CONNECT   message  on the HyperTerminal  screen.   If you can t

connect, either the phone  number  is  wrong  (there really isn t  a paging  terminal  at the other end) or you need to

use  an init string  to make  a connection  to it.  You will find  some  common  init strings  in the  Init Strings   section

of this manual  or on our website  (www.r.com).   To try an init string,  simply  type it into  HyperTerminal

and hit the enter key.  If the string  is  accepted, you should  get an  OK  back.  If the string is  invalid for your

modem,  you will  get and  ERROR  response.   After entering  a valid init string,  try connecting  to the carrier again

( ATDT ).   If HyperTerminal  can t connect  to the carrier, r  Pro won t  be able  to

either.

After you receive a  CONNECT  message,  you should  receive an  ID=  message  within  about five seconds.   If

not, try hitting the enter key about every three  seconds.   After retrying the carrier a couple  of times, if you still

don t get and  ID=  prompt,  either  you don t have a proper init  string, your communications  settings  are orrect

(baud,  data bits, etc.), or you aren t connecting  to a paging  terminal.   If you do receive the  ID=  prompt, quit  out of

HyperTerminal,  start  r  Net, and go to the next step.

Note:  If you used  a different  init string here to get this far, be sure  to update  the carrier s  init string  in r

Pro before continuing.

5.6.5

Check the Dialer Log

In r  Pro, select  the  Setup  from the  File  menu.  Make sure  that  Detailed  Log  is  checked.  Apply your

changes.   You can view the dialer s  log file by selecting  the  Dialer Log   item from the  View  menu.  Next, send  a

test message  and then  review the dialer  log.  Here  are failure  messages  for the dialers  and their possible

causes:

Unable to send init string

   the dialer init was  sent to the modem,  but not accepted.  Verify the syntax of the init

string,  or try a new  one.

Unable to connect to carrier

   the dialer didn t receive a  CONNECT  message  from the modem.   This  is

usually  caused  by a wrong  phone  number, orrect  modem  settings,  or improper  init string.

Checksum error

   your message  was  transmitted  to the carrier, but the data received didn t match  the data you

sent.   This can be caused  by a bad connection  or improper  init  string.

Bad message  content

   your message  was  received by the carrier without  any errors.  However, the carrier

rejected the message  due to invalid  data in it.  This is  almost  always caused  by an orrect  ID/PIN number,  or

by sending  a message  that is  longer than  what the carrier  will  accept in a single  message  (try lowering  the

 maxchars   setting  for the carrier).

Disconnect requested  by carrier 

  this  message  could mean  a number  of different  things.   It is sometimes

   ,  .