As always, my advice is to open a problem to Support. They have helped
people through these things before.
If your pager is hanging up and re-dialing then no one is answering on the
other end, the page is timing out and being re-sent. Are you sure the
modem is properly connected and configured? Can you plug that phone line
into a real analog telephone and dial the pager company number? Make sure
the line is analog, many company phone systems these days are digital and
you have to have a real analog line to dial out with a modem. I don't know
what you are using but my preference for these things is always an
old-fashioned external modem with a speaker and blinky lights so I can
watch the thing work. That's how we troubleshoot it in the lab. Since
most pager companies cannot transmit at any speed greater than 9600 bps,
and most use 2400 or less, any old, piece-of-junk, obsolete modem will
usually work. The dumber the better. In my experience, it is the fancier
ones that give trouble.
The com port on NT is specified when you set up the modem and cannot be
changed, that is why there is no entry for it in any of our files on NT.
On UNIX it is configurable. The drop-down modem specification on the
daemon was supposed to allow for multiple modems but it has never been
fully implemented, so I would leave that alone.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
"Thomas Clarke" <tclarke@island.com>@tkg.com on 02/07/2001 06:48:27 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: <nv-l@tkg.com>
cc:
Subject: [NV-L] Nvpage Problem
Hi. I'm trying to setup nvpage using Netview 6.0.1 under WinNT but seem to
be having little luck. Why is there a configure option for modem setup
under
the daemons pull down menu "pager daemon" if I have to set the nv.carriers
file to do nearly the same thing? The com port isn't identified in the
carriers file I know but it's close. The problem is that while I can get
nvpagerd to dial-out it won't complete the connection for the TAP protocol
to go through. It hangs up and redials over and over The nv.carriers file
looks fine. I looked through the docs but it's sparse when it comes to
nv.carriers and nv.protocols.
TC
Network Operations Engineer
The Island, ECN.
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|