[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::netview

Title:	TME 10 NetView and related productscts
Notice:	Bugs-12; Kits-9; ECOs-20
Moderator:	TUXEDO::MINTZLL

Created:	Tue Aug 24 1993
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2257
Total number of notes:	7838

2208.0. " nvpaging fail after upgrade to V4.1B" by GIDDAY::CHONG (Andrew Chong - Sydney CSC) Mon Feb 10 1997 23:17

After upgrading PNV from V3.1B to V4.1B and Digital Unix to V4.0B paging does 
not work anymore. The configuration has not change except that V4.1B now has 
nvpaging.protocols file and the TEP protocol has been selected in nv.carriers 
for carrier: Telstra. 

	nvpage pager# @Telstra "message text"

	The response is message send successfully but no message is received. 

 contents of nvpagerd.log :


(C) Copyright IBM Corporation 1990, 1993, All Rights Reserved.
02/04/97 09:47:31 - START /usr/OV/bin/nvpagerd as PID 17075
IpcKey: 0x6e03f2dd
Warm start information is being checked, but will not be used...
Warm start file "/usr/OV/conf/nvpager.warm" has data that is not being used.
Service nvpagerd using TCP socket 1671.
Error: Message go-ahead not received from carrier Telstra.
Error: Carrier Telstra said "TIME LIMIT is up, drop CARRIER         "
Error: Carrier Telstra forced a disconnect during logon.
Error: Carrier Telstra forced a disconnect during logon.
Error: Message go-ahead not received from carrier Telstra.
Error: Carrier Telstra said "TIME LIMIT is up, drop CARRIER         "
Error: Carrier Telstra forced a disconnect during logon.
Error: Carrier Telstra forced a disconnect during logon.
nvpagerd terminating on command OVS_CMD_EXIT
02/04/97 09:50:36 - STOP /usr/OV/bin/nvpagerd as PID 17075


Since this was working in V3.1B , the question is what paging protocol was 
being used by netview (not selectable by the user) ? and how does that defer 
to the TEP protocol ? 

Any suggestions on how to get this to work ?

The config files nv.carriers, nvpager.conf and nvpaging.protocols as listed 
below  

Andrew


--------------------------------------------------------------------

nv.carriers
===========


# NetView Paging Carrier database
#
# Carrier				- Carrier name
# Modem phone #				- The data connection phone #
# Numeric IDs accepted on modem line	- Whether or not the paging carrier
#					  allows numeric IDs to be used during
#					  a data connection on the modem line.
#					  If Y (yes) pager id is numeric.
#					  If N (no)  pager id is alphanumeric.
# DTMF phone #				- The carrier wide touch tone input
#					  phone #
# Max. message length			- Maximum message length to alpha pagers
# Max. blocks/transaction		- Maximum blocks per transaction
# Max. transactions/call		- Maximum transactions per call
# Baud rate				- Baud rate (300,1200,2400,4800,9600
#					  19200,38400)
# Parity				- Parity (N=none, E=even, O=odd)
# Data bits				- Data bits (7,8)
# Stop bits				- Stop bits (1,2)
# Password				- Password to logon to carrier
#
Carrier: Telstra
        Modem phone #: 022819255
        Numeric IDs accepted on modem line: N
        DTMF phone #: 
        Max. message length: 190
        Max. digits in alphanumeric pager #: 8
        Max. blocks/transaction: 1
        Max. transactions/call: 3
        Baud rate: 2400
        Parity: E
        Data bits: 7
        Stop bits: 1
        Password: passwd
	Protocol: PET

Carrier: skytel
	Modem phone #: 1-800-759-6366
	Numeric IDs accepted on modem line: N
	DTMF phone #: 1-800-759-7243
	Max. message length: 190
	Max. digits in alphanumeric pager #: 8
	Max. blocks/transaction: 1
	Max. transactions/call: 7
	Baud rate: 300
	Parity: E
	Data bits: 7
	Stop bits: 1
	Password: 
        Protocol: TAP

Carrier: vodapage
        Modem phone #: 011-44-13991200
        Numeric IDs accepted on modem line: N
        DTMF phone #: 011-44-1399728950
        Max. message length: 190
        Max. digits in alphanumeric pager #: 18
        Max. blocks/transaction: 1
        Max. transactions/call: 7
        Baud rate: 300
        Parity: E
        Data bits: 7
        Stop bits: 1
        Password:
        Protocol: PAKNET

Carrier: pagenet
	Modem phone #: 1-800-720-8398
	Numeric IDs accepted on modem line: N
	DTMF phone #: 
	Max. message length: 200
	Max. digits in alphanumeric pager #: 8
	Max. blocks/transaction: 1
	Max. transactions/call: 30
	Baud rate: 300
	Parity: E
	Data bits: 7
	Stop bits: 1
	Password: 
        Protocol: TAP

Carrier: pagenetnw
	Modem phone #: 1-800-720-8398
        Numeric IDs accepted on modem line: N
        DTMF phone #: 
        Max. message length: 200
	Max. digits in alphanumeric pager #: 8
        Max. blocks/transaction: 1
        Max. transactions/call: 30
        Baud rate: 300
        Parity: E
        Data bits: 7
        Stop bits: 1
        Password:
        Protocol: TAP

Carrier: metromedia
	Modem phone #: 1-800-328-7587
	Numeric IDs accepted on modem line: N
	DTMF phone #: 
	Max. message length: 190
	Max. digits in alphanumeric pager #: 8
	Max. blocks/transaction: 1
	Max. transactions/call: 80
	Baud rate: 300
	Parity: E
	Data bits: 7
	Stop bits: 1
	Password: 
        Protocol: TAP

#Carrier: swbell
#	Modem phone #: 1-214-358-6727
#	Numeric IDs accepted on modem line: Y
#	DTMF phone #: 
#	Max. message length: 80
#	Max. digits in alphanumeric pager #: 8
#	Max. blocks/transaction: 1
#	Max. transactions/call: 80
#	Baud rate: 300
#	Parity: E
#	Data bits: 7
#	Stop bits: 1
#	Password: 

#Carrier: interlink
#	Modem phone #: 1-303-799-0056
#	Numeric IDs accepted on modem line: N
#	DTMF phone #:
#	Max. message length: 190
#	Max. digits in alphanumeric pager #: 8
#	Max. blocks/transaction: 1
#	Max. transactions/call: 3
#	Baud rate: 300
#	Parity: E
#	Data bits: 7
#	Stop bits: 1
#	Password:

#Carrier: mobilecom
#	Modem phone #: 1-512-478-4875
#	Numeric IDs accepted on modem line: N
#	DTMF phone #:
#	Max. message length: 190
#	Max. digits in alphanumeric pager #: 8
#	Max. blocks/transaction: 1
#	Max. transactions/call: 3
#	Baud rate: 300
#	Parity: E
#	Data bits: 7
#	Stop bits: 1
#	Password:

Carrier: MobilecomSJ
	Modem phone #: 1-800-924-4342
	Numeric IDs accepted on modem line: Y
	DTMF phone #:
        Max. message length: 190
	Max. digits in alphanumeric pager #: 8
        Max. blocks/transaction: 1
        Max. transactions/call: 3
        Baud rate: 300
        Parity: E
        Data bits: 7
        Stop bits: 1
        Password:
        Protocol: TAP

Carrier: Mobilecom2
	Modem phone #: 1-800-946-4644
	Numeric IDs accepted on modem line: N
	DTMF phone #:
	Max. message length: 190
	Max. digits in alphanumeric pager #: 8
	Max. blocks/transaction: 1
	Max. transactions/call: 3
	Baud rate: 300
	Parity: E
	Data bits: 7
	Stop bits: 1
	Password:
        Protocol: TAP

Carrier: MobilecomNY
	Modem phone #: 1-800-937-2532
	Numeric IDs accepted on modem line: N
	DTMF phone #:
	Max. message length: 190
	Max. digits in alphanumeric pager #: 8
	Max. blocks/transaction: 1
	Max. transactions/call: 3
	Baud rate: 300
	Parity: E
	Data bits: 7
	Stop bits: 1
	Password:
        Protocol: TAP

#Carrier: mobilecom3
#	Modem phone #: 1-713-960-7204
#	Numeric IDs accepted on modem line: N
#	DTMF phone #:
#	Max. message length: 190
#	Max. digits in alphanumeric pager #: 8
#	Max. blocks/transaction: 1
#	Max. transactions/call: 3
#	Baud rate: 300
#	Parity: E
#	Data bits: 7
#	Stop bits: 1
#	Password:

#Carrier: raleigh
#	Modem phone #: 1-919-832-4033
#	Numeric IDs accepted on modem line: N
#	DTMF phone #:
#	Max. message length: 190
#	Max. digits in alphanumeric pager #: 8
#	Max. blocks/transaction: 1
#	Max. transactions/call: 3
#	Baud rate: 300
#	Parity: E
#	Data bits: 7
#	Stop bits: 1
#	Password:

#Carrier: boca
#	Modem phone #: 1-407-443-2900
#	Numeric IDs accepted on modem line: N
#	DTMF phone #:
#	Max. message length: 190
#	Max. digits in alphanumeric pager #: 8
#	Max. blocks/transaction: 1
#	Max. transactions/call: 3
#	Baud rate: 300
#	Parity: E
#	Data bits: 7
#	Stop bits: 1
#	Password:

#Carrier: toronto
#	Modem phone #: 1-416-321-1360
#	Numeric IDs accepted on modem line: N
#	DTMF phone #:
#	Max. message length: 190
#	Max. digits in alphanumeric pager #: 8
#	Max. blocks/transaction: 1
#	Max. transactions/call: 3
#	Baud rate: 300
#	Parity: E
#	Data bits: 7
#	Stop bits: 1
#	Password:

Carrier: sig-net
	Modem phone #: 1-800-521-8557
	Numeric IDs accepted on modem line: N
	DTMF phone #:
	Max. message length: 190
	Max. digits in alphanumeric pager #: 8
	Max. blocks/transaction: 1
	Max. transactions/call: 3
	Baud rate: 300
	Parity: E
	Data bits: 7
	Stop bits: 1
	Password:
        Protocol: TAP

#Carrier: uswest
#	Modem phone #: 280-1000
#	Numeric IDs accepted on modem line: N
#	DTMF phone #:
#	Max. message length: 190
#	Max. digits in alphanumeric pager #: 8
#	Max. blocks/transaction: 1
#	Max. transactions/call: 80
#	Baud rate: 300
#	Parity: E
#	Data bits: 7
#	Stop bits: 1
#	Password:

Carrier: uswest2
	Modem phone #: 1-800-338-7827
	Numeric IDs accepted on modem line: N
	DTMF phone #:
	Max. message length: 190
	Max. digits in alphanumeric pager #: 8
	Max. blocks/transaction: 1
	Max. transactions/call: 80
	Baud rate: 300
	Parity: E
	Data bits: 7
	Stop bits: 1
	Password:
        Protocol: TAP


-------------------------------------------------------------------
nvpager.config
==============

#
# GSC Paging configuration file
#
# Outside Line # (p=Pause): 9p
#    This is any dialing that needs to be done for the attached modem to
#    get an outside dial tone.  Numeric pager numbers as well as carrier
#    phone number should NOT include this.  This will be dialed each time
#    a call is made by the modem.
#    Valid characters: 0123456789p
Outside Line # (p=Pause): 0p

# Default Modem File: newhayes.modem
#    This is the modem information file that describes the initialization
#    needed for the attached modem and other control information specific
#    to each type of modem.
Default Modem File: newhayes.modem

# Default Baud Rate (300,1200,2400,4800,9600,19200,38400): 300
#    This is the baud rate between the computer and modem when direct-dial
#    numeric pagers are contacted and when the carrier's direct-dial DTMF
#    number is used for numeric pagers.
#    Valid values: 300,1200,2400,4800,9600,19200,38400
Default Baud Rate (300,1200,2400,4800,9600,19200,38400): 2400

# Default Data Bits (7,8): 7
#    This is the number of data bits between the computer and modem when
#    direct-dial numeric pagers are contacted and when the carrier's direct-
#    dial DTMF number is used for numeric pagers.
#    Valid values: 7,8
Default Data Bits (7,8): 7

# Default Parity (N,E,O): E
#    This is the parity between the computer and modem when direct-dial numeric
#    pagers are contacted and when the carrier's direct-dial DTMF number is
#    used for numeric pagers.
#    Valid values: N,E,O
Default Parity (N,E,O): E

# Default Stop Bits (1,2): 1
#    This is the number of stop bits between the computer and modem when
#    direct-dial numeric pagers are contacted and when the carrier's direct-
#    dial DTMF number is used for numeric pagers.
#    Valid values: 1,2
Default Stop Bits (1,2): 1

# Default Device: tty1
#    This is the device that the modem is attached to.  It must be in the /dev
#    directory.  If your modem is attached to another tty port, this must be
#    changed.
Default Device: tty01



----------------------------------------------------


nvpaging.protocols
==================

#
#NetView Paging Protocols
#
#
# Protocol                              - Paging protocol used by this carrier
# Login prompt                          - Prompt sent by carrier to request user identification
# Login response                        - user response to login prompt
# Login accepted                        - Prompt sent by carrier if the login request is valid
# Send Go ahead                         - Send by the carrier when its ready to receive data 
# Confirmation response                 - Response returned by carrier if page data successfully
#                                         received.     

Protocol: TAP
	Login prompt: ID=
	Login response: PG1
	Login accepted:<CR><ACK><CR>
	Send Go Ahead: <ESC>[P<CR>
	Confirmation response: <CR><ACK><CR>

Protocol: PAKNET
	Login prompt: ?
	Login response: ID#
	Login accepted: Alpha-numeric
	Send Go Ahead: 
	Confirmation response: Accepted

Protocol: DIRECT_INPUT
	Login prompt: ?
	Login response: ID#
	Login accepted: Alpha-numeric
	Send Go Ahead: 
	Confirmation response: Accepted



Protocol: IXO
	Login prompt: ID=
	Login response: PG1
	Login accepted: <CR><ACK><CR>
	Send Go Ahead: <ESC>[P<CR>
	Confirmation response: <CR><ACK><CR>

Protocol: PET
	Login prompt: ID=
	Login response: PG1
	Login accepted: <CR><ACK><CR>
	Send Go Ahead: <ESC>[p<CR>
	Confirmation response: <CR><ACK><CR>

----------------------------------------------------------

T.R	Title	User	Personal Name	Date	Lines
2208.1	try PNV V4.1B ECO1	MOLAR::SIEGEL	MS: ZKO1-3/H18 DTN: 381-0035	`Wed Feb 12 1997 10:39`	15
	Andrew, PNV has not been tested on Digital Unix V4.0B. The maximum version supported by PNV V4.1C is DU V4.0A. If you've reinstalled the operating system I would check and make sure any system files that you've configured for paging are still the same. Can you hear the modem tones while dialing? There is an ECO for PNV V4.1B. (see note #20 for information) Install that and try it again. Joanna
2208.2		GIDDAY::CHONG	Andrew Chong - Sydney CSC	`Wed Feb 12 1997 22:28`	16
	> If you've reinstalled the operating system I would check and make sure > any system files that you've configured for paging are still the same. Which files in particular are you refering to besides the ones in .0 ? those files have not changed. > Can you hear the modem tones while dialing? Yes I will get him to try the eco but there is no mention of any paging fix in the release notes. Andrew
2208.3		MOLAR::SIEGEL	MS: ZKO1-3/H18 DTN: 381-0035	`Thu Feb 13 1997 12:39`	19
	Hi Andrew, Please have him try the eco and let me know the results. I have had one complaint of a problem like this last September/October. I definitely could not reproduce the problem. Also, I'm referring to files used by the operating system for modem configuration---like /etc/remote and/or whatever else you've modified. The NetView configuration paging files look ok to me. Also, it looks like the PET protocol is the same as the TAP protocol. Can you change Telestra to the TAP protocol and see if it works? Joanna
2208.4	any more thoughts ?	GIDDAY::CHONG	Andrew Chong - Sydney CSC	`Thu Feb 20 1997 00:45`	14
	Joanna, The customer assure me that he has not change any modem configuration files and he has tried using TAP protocol for Telstra with the same result. He was going to try eco1 and then he realise that he is already on V4.1C . Any more ideas ? When will Netview be supported on V4.0B DU ? Although in this case it does not seem like problem could be caused by DU. Andrew