This document contains information relating to the safe
installation, maintenance, and use of the Oki BV1250. Carefully
note all safety precautions and procedures contained in this
document before installing and using the product.
Rev. 1.0Page i
Page 4
BV1250 Technical Reference
The BV1250 Internet Voice Gateway and the Maintenance Console
Software are products of Oki Electric Industry Co. Ltd.
Right to reproduce this manual and/or the Maintenance Console
Software is restricted by the Copyright Act.
No part of this document may be reproduced, stored on a retrieval
system, or transmitted in any form or by any means, electronic,
mechanical, photocopying, recording, or otherwise, without the
written permission of Oki Electric Industry Co. Ltd.
Information in this document is subject to change without notice.
The contents of this document and the Maintenance Console
Software have been prepared with the utmost care. However, if you
notice an ambiguous point or omission, please contact an authorized
agent.
No responsibility will be taken by our company with respect to
consequences resulting from the use of the Maintenance Console
Software and/or the content and interpretation of the information
contained in this manual.
2000, Oki Electric Industry Co. Ltd.
Ethernet is a registered trademark of Xerox Corporation.
MS-DOS and Windows are registered trademarks of Microsoft
Corporation.
Other companies and product names mentioned in this manual are
the registered trademarks or services marks of their respective
companies.
Revision 1.0
Printed in the USA
Page iiRev. 1.0
Page 5
BV1250 Technical Reference
Limited Warranty
Oki Electric Industry Co., Ltd. warrants that these products (BV1250 and
Maintenance Console Software) are free of manufacturing defects during the
warranty period and while operating under normal conditions. In the event of
failure, a replacement unit and/or software will be provided free of charge.
This warranty covers this product only and is subject to the following conditions:
1.Oki Electric warrants the media upon which the Maintenance Console
Software is recorded to be free from defects in materials and workmanship
under normal use for a period of ninety (90) days from the date of purchase.
In the event any media prove to be defective during the warranty period,
user’s remedy shall be to return media to Oki Electric for replacement.
2.Oki Electric does not accept liability for loss or damage caused by the user's
mishandling, misoperation, or damages occurring as a consequence of
unusual events such as fire, earthquake, or flood.
3.Regarding the quality and functionality of the Maintenance Console Software
and this Installation Guide, Oki Electric holds no liability for the conformity of
the equipment to the purpose of use by the user and the marketability. Oki
Electric does not accept liability for any loss or damage occurring directly or
indirectly thereof.
4.No responsibility will be taken regarding the results obtained by the use of the
BV1250 and/or the Maintenance Console Software and/or this Installation
Guide.
5.Media such as this Installation Guide, floppy disks, CDs, etc., are supplied
with the Maintenance Console Software as a package and shall be used for
the Maintenance Console Software only. It is strictly forbidden to make a
copy of the Maintenance Console Software other than a back-up copy. Oki
Electric holds no liability for consequences incurred by the use of the copied
media.
Others
1. It is strictly forbidden to offer the MCS program to a third party as such or
after adding modifications. If this program is used by a third party, that use
infringes upon the copyright of the author and it becomes the author's right to
demand compensation.
2. Customer services are available at our company's head office and at our
service locations.
The Oki BV1250 Internet Voice Gateway (IVG) is a self-contained device that
allows organizations to route both voice and fax communications over any IP
compatible network. Oki’s IVG seamlessly bridges existing PBX, key telephone,
analog, and PSTN telephone systems with digital data networks. This technology
allows organizations to more fully utilize existing intranet and Internet facilities.
Most importantly, since communications take place over digital data networks, the
high cost of long distance communications over conventional public telephone
networks is eliminated.
Salient features of the BV1250 include:
•
Analog terminal, PBX, PSTN, and G3 Fax communications achieved
over IP network.
•
High-quality voice compression encoding that can be configured on a
priority basis to automatically select between 64kbps PCM stream as
either G.729A (8kbps), G.723.1 (5.3kbps) or G.723.1 (6.3kbps)
compression, packet priority control, and bandwidth management.
•
Oki’s proprietary dynamic jitter buffer and Dynamic Echo
Cancellation assure uninterrupted and natural speech communications.
•
All four BV1250 unit ports are capable of real-time fax transmission
using IP transmission, taking full advantage of the data network’s
flow and data control (TCP transmission).
•
Compliant with H.323 Version 2 network protocols and interoperable
with all H.323 compliant devices.
•
In non-H.323 networks, provides unified telephone numbering
management using both internal (within the unit) and external DNS
(Domain Name System) functions.
•
Network management control through SNMP (Simple Network
Management Protocol – MIBI and MIBII).
Connection ConfirmationImmediate, Delay-dial, or Wink-start
Selection signalDP 10/20 PPS or DTMF
ConnectorSimple solderless / RJ45
ComplianceITU-T Rec. Q.517
Model Name :EMIF FIC :TL11E, TL12E, TL31E, TL32E
Registrant :OKI INDUSTRY CO LTD , Reg. No.:1XLUSA-33761-CN-E, Grant Date :04/27/1999
Canadian Approval CS03, Model Name :EMIF E&M Certification No. :187 9837 A
ComponentPCB board
TerminalAnalog Telephone or Key Telephone System
Lines4 maximum
Channels4 simultaneous
Resistance400 ohms
Start-up methodLoop start
Selection signalDP 10/20 PPS or DTMF
ConnectorSimple solderless / RJ11
Ringer freq.20Hz/25Hz/50Hz
ComplianceITU-T Rec. Q.517
A functional BV1250 unit must have a Line Interface card installed. The interface may be FXS
(analog), FXO (analog), E&M (Types 1 and 2), or E&M–OD (Type 5). The G3 facsimile interface is
available with all of the above.
US
= Type 1 or Type 2
JPN
= Type 5 EU = Type 1, Type 2, Type 5 (OD)
(Including terminal resistance)
FXO(option):
Fax
ComponentPCB board
TerminalAnalog CO Lines, Key Telephone System, PBX
Lines4 maximum
Channels4 simultaneous
Resistance288 ohms
Start-up methodLoop start
Selection signalDP 10/20 PPS or DTMF
ConnectorSimple solderless / RJ 11
ComplianceITU-T Rec. Q.517
Model Name :FXO FIC :O2LS2
Registrant :OKI INDUSTRY CO LTD, Reg. No:1XLJPN-33760-CN-E Grant Date :04/27/1999
Canadian Approval CS03, Model Name: FXO, Certification No:187 9903 X
Lines 4 max
Data transfer9600 bps/4800bps
Transmission ControlG3
(Including terminal resistance)
Page 4Rev. 1.0
Page 13
BV1250 Technical ReferenceDescription
2. BV1250 External Views
The external characteristics of a BV1250 unit are shown below.
2.1 Base Unit Configuration
Figure 2-1 illustrates the basic configuration of all versions BV1250 units.
The only difference between unit configurations is that the line interface
connector ports appearing on the front panel vary between FXS, FXO,
E&M, and E&M-OD equipped units. These differences are noted in Figure
2-2.
Figure 2-1: BV1250 External View (FXS shown)
Height =
53mm (3")
Depth = 400mm (14")
Rear
Front
Width = 420mm (17")
:
NOTE
Appearance of Line
Interface varies
based on type of
interface installed.
(See description in
following section,
External Features.)
2.2
Rev. 1.0Page 5
Page 14
DescriptionBV1250 Technical Reference
BV1250 External Features
The BV1250 base unit front and rear panels have various physical elements
associated with supplying power to the unit and providing operational status
information. Figure 2-2 illustrates these features. These features are
described in greater detail in Table 2-1 on the following page.
Figure 2-2: BV1250 External Features
Page 6Rev. 1.0
Page 15
BV1250 Technical ReferenceDescription
Table 2-1: Description of BV1250 External Feature
ItemDescription
1Power lampIndicates power ON when lamp litGreen lamp
2Busy lampWhen port is in use, lit lamp indicates line is busyOrange lamp
3Alarm lampIndicates alarmed condition detected in unit when lamp lit or blinkingRed lamp
5Serial portConnector for serial cable connection of maintenance console terminalDB9-F
6Link lampIndicates LAN link is operating normally when litGreen lamp
7Uplink connector10BaseT connector for LANRJ45
9Collision lampIndicates frame collisions are occurring when lit.Yellow lamp
8Data lampIndicates that data is being sent/received when lamp is lit or blinkingGreen lamp
10.Line interface
a. FXS
b. FXO
c. E&M
d. E&M-OD
11Fan assemblyServiceable fan assembly for cooling of unit
12FG terminalTerminal strip for frame ground
Line interface board connectors
Four TEL connectors of FXS board equipped units
Four FXO connectors of FXO board equipped units
Eight E&M connectors for E&M board equipped units
Four E&M-OD connectors for E&M-OD board equipped units
Green lamp
Connectors
supplied with
board
13Power connectorConnector for AC power cord
14Fuse holderHousing for fuse
15Power switchTurns power to the base unit ON and OFFToggle switch
Rev. 1.0Page 7
Page 16
DescriptionBV1250 Technical Reference
3. BV1250 Parts
Below is a listing of BV1250 parts along with the part and product numbers.
Product NameOki Networks Part NumberOki-J Product No.
Basic Parts
BV1250 Base Unit1001014YA1158-1121G002
BV1250 Accessories
BV1250 Accessories, Europe
BV1250 FXS Interface kit
BV1250 FXO Interface kit
BV1250 E&M Interface kit
BV1250 AP interface retrofit kit
BV1250 FXO interface retrofit kit
BV1250 EM interface retrofit kit
BV1250 OD Interface retrofit kit (Japan)
BV1250 FXO Interface kit, Japan
BV1250 Rack Mount Kit1001064YA1158-1122G001
Maintenance Console Software103012
BV1250 Installation Guide
BV1250 Technical reference
Ancillary Parts and Spares
BV1250 General Description103115
BV1250 User's Guide1010043PP1158-5120P101
BV1250 Indicator Label for FXS unit1011013PP1158-5220P001
BV1250 Indicator Label for FXO unit1011023PP1158-5220P002
BV1250 Indicator Label for E&M unit1011033PP1158-5220P004
DDK Connectors for AP unit Installation101006224A3223P0020
DDK Connectors for E&M unit Installation101008224A3231P0040
DDK Connectors for OD unit Installation101010224A3231P0060
Screws for Base unit Type M4101011P(SW+W)4-10-FRC
Screws for Interface card Type M3101012P(SW+W)3-8-FRC
BV1250 Cooling Fan unit101105
BV1250 Fuse, Rating 250V, 3.15A101106
PC Serial cable for Maintenance Console101013--
100102
100114
100103
100104
100105
100107
100108
100109
100113
100112
103111
103112
4YA1158-1123G002
4YA1158-1123G003
4YA1158-1124G001
4YA1158-1125G002
4YA1158-1146G001
4YA1158-1144G001
4YA1158-1142G001
4YA1158-1143G001
4YA1158-1145G001
4YA1158-1125G001
Page 8Rev. 1.0
Page 17
BV1250 Technical ReferenceMaintenance and Troubleshooting
BV1250 Maintenance
and Troubleshooting
The BV1250 unit is a low maintenance electronic device that, once installed and properly
configured, should need only infrequent attention.
Other than an occasional external cleaning, all maintenance activities should be performed
by qualified personnel. General maintenance activities include routine checks of data logs
maintained in the unit’s log files, system file updates, and should it becomes necessary, the
replacement of the unit’s fuse and fan assembly.
In the event that a unit’s performance fails or becomes unstable, it may be necessary to
troubleshoot the unit to diagnose and correct the problem.
In this section, the following topics are discussed:
•
Routine Maintenance
•
Troubleshooting and Corrective Action
•
Fault Messages and Reports
•
Error Traps
•
Fuse Replacement
•
Fan Unit Replacement
Rev. 1.0Page 1
Page 18
Maintenance and TroubleshootingBV1250 Technical Reference
Page 2Rev. 1.0
Page 19
BV1250 Technical ReferenceMaintenance and Troubleshooting
1. Routine Maintenance
Routine maintenance involves tasks to be performed on a regular basis even when the
unit gives no evidence of problems or malfunction. These activities are generally
preventative in nature.
1.1 External Cleaning
Depending on the environment in which it is installed, a BV1250 unit may
need occasional cleaning. Cleaning will help to remove accumulated dust and
dirt which can interfere with the proper cooling of the unit and can affect the
operation of the unit’s external switches and buttons.
External cleaning is performed using a cloth dampened with a mild soapy
solution. Simply wipe down the unit to remove dirt and dust taking care that no
excess moisture penetrates the unit.
!
Do not allow moisture to penetrate the unit. Moisture in the
unit can cause serious damage and may produce an electrical
hazard.
When cleaning the external base unit, it is also useful to check the unit fan for
dust build-up. If an excessive amount of dust is present, the fan unit should be
cleaned. See Section 6 for a description of the fan assembly.
Rev. 1.0Page 3
Page 20
Maintenance and TroubleshootingBV1250 Technical Reference
1.2 Periodic inspection
Periodic inspection activities should be organized using a maintenance
schedule that specifies regular inspection intervals. Inspection need not occur
frequently but is best when conducted on a routine basis.
With the exception of external inspection, all inspection activities can be
conducted remotely using the Maintenance Console Software or with On-line
commands on a terminal.
Recommended inspection and maintenance activities are shown in Table 1-1
below.
Table 1-1: Periodic Inspection Procedure
StepActionNominal ConditionIf trouble. . .
1. Check general
operation.
2. Check Trouble
Log.
3. Restart unit.Power cycle the unit being careful to
4. Check voice
communication.
5. Check fax
communication
Check the Alarm lamp on the front
panel of the unit.
Use the MCS to view the equipment
status.
Use the MCS Fault Log display or
enter the on-line
retrieve the unit’s fault log.
use the Shutdown procedure
described in the BV1250 Installation
Guide.
OR
Reboot the equipment using the
MCS Reboot item or the on-line
REBOOT command.
After restart repeat Step 1 this table.
Place test calls to and from
extensions associated with the unit.
Send test faxes to and from
extensions associated with the unit.
ELOG
command to
Red ALARM lamp not lit.
All lamps are operating,
(e.g. PWR, CONT, PP.
FAX, and FAN)
No fault conditions are
displayed in the log.
Red ALARM lamp not lit.
All lamps are operating,
(e.g. PWR, CONT, PP.
FAX, and FAN)
The ring-back tone (RBT)
can be heard.
Speech quality is normal
and there is little or no
ambient background
noise.
Fax transmitted
successfully.
Use the MCS Fault Log display or enter the on-line
command to retrieve the unit’s fault log,
ELOG
record listed trouble code(s), and refer to the Fault
Messages table for corrective action.
Record listed trouble code(s) and refer to the Fault
Messages table for corrective action.
Use the MCS Fault Log display or enter the on-line
command to retrieve the unit’s fault log,
ELOG
record listed trouble code(s), and refer to the Fault
Messages table for corrective action.
Verify that the access code and destination number
dialed are correct.
Use the MCS or other facility to send a Ping test to
the remote IVG to verify communication.
Use the MCS Fault Log display or enter the on-line
command to retrieve the unit’s fault log,
ELOG
record listed trouble code(s), and refer to the Fault
Messages table for corrective action.
Verify that the access code and destination
numbers dialed are correct.
Use the MCS or other facility to send a Ping test to
the remote IVG to verify communication.
Use the MCS Fault Log display or enter the on-line
command to retrieve the unit’s fault log,
ELOG
record listed trouble code(s), and refer to the Fault
Messages table for corrective action.
The ELOG must be cleared following the correction of a
problem listed in the log. If this is not done, a previously
resolved item will be erroneously displayed in subsequent
reports. After resolving a problem always clear the trouble
log using the MCS or the on-line ELOG-CLR command.
Page 4Rev. 1.0
NOTE:
Page 21
BV1250 Technical ReferenceMaintenance and Troubleshooting
1.3 File Management
On occasion it may be necessary to update or restore a BV1250 unit’s system
files. The updating or restoration of unit’s system files is performed using the
Maintenance Console Software or with the On-line commands. The procedures
for this are discussed in the BV1250 Installation Guide and in the On-line
Command Reference section in this document.
Table 1-2 shows the files installed in a BV1250 unit.
Each BV1250 has an office data file, OFDD.VHO, which resides in the
directory
This file contains unit specific configuration information such as network data,
numbering plan data, line data, and operational data.
When a BV1250 unit is replaced or should a unit’s OFDD.VHO file become
lost or corrupted, this file must be restored to the unit using the procedures
described in the BV1250 Installation Guide. Maintaining backup copies of all
BV1250 unit OFDD.VHO files is strongly recommended. See the Maintenance
Console Software Operations Manual for the recommended procedure.
The Maintenance Console Software (MCS) stores backup versions of all units
configured using the MCS.
By default, the MCS stores OFDD backup files in the directory
Files\Cons50\DATA\(Group_Name)\(Unit_Name)\
with the extension .OLD.
C:\Program
Rev. 1.0Page 5
Page 22
Maintenance and TroubleshootingBV1250 Technical Reference
Page 6Rev. 1.0
Page 23
BV1250 Technical ReferenceMaintenance and Troubleshooting
2. Trouble Diagnosis and Corrective
Action
When a BV1250 unit problem is detected/reported, a systematic methodology
will assist in the diagnosis and correction of the problem.
The recommended procedure involves the following steps.
1. Retrieve the unit’s trouble log.
2. Analyze the fault information.
3. Identify the fault location.
4. Correct the problem.
5. Clear the fault log.
!
Before opening the cover of a BV1250 unit be certain to read
and understand all safety precautions listed at the beginning
of the BV1250 Installation Guide.
Rev. 1.0Page 7
Page 24
Maintenance and TroubleshootingBV1250 Technical Reference
2.1 Fault Processing
On occasion, a fault condition may arise which causes a unit to behave
erratically or fail altogether. Should this occur, it is important to take timely
action to obtain a trouble report, diagnose, and resolve the problem. In addition,
it is recommended that some form of trouble ticket be maintained in order to
track actions taken to resolve the problem and to preserve a maintenance record
for the affected unit(s).
The first steps in dealing with a trouble report can be handled remotely. If
remote activities are not sufficient to resolve the problem, it may be necessary
to perform on-site tasks to resolve the difficulty.
1. Check the situation by telephone
When a problem occurs, it should be reported by the user or network manager and
a record of the problem should be made. Important elements of the report include
the unit identification/location information, time of the event, symptoms of the
event, and conditions/use under which the event occurred.
In addition, it may be necessary to provide the reporting person with instructions
regarding action to be taken immediately to prevent broader network problems.
2. Confirm the fault situation using a remote connection with the unit
If communications with the problem unit are intact, use the MCS Fault Log
display or the on-line
related trouble code(s).
Once any fault codes have been retrieved, refer to the Table 2-2 Fault Conditions
in this document to diagnose the problem. If the trouble is due to a software or data
error, it will usually be possible to correct the problem remotely, using the
Maintenance Console Software.
3. Troubleshoot on-site
If a fault condition is due to hardware, such as a blown fuse for example, it will
be necessary to make a service call to the site where the unit is located.
ELOG
command, to retrieve the unit’s fault log and to record
Page 8Rev. 1.0
Page 25
BV1250 Technical ReferenceMaintenance and Troubleshooting
2.2 Guide to Trouble Indications
Table 2-1 provides a general troubleshooting guide. In many cases this
information will be sufficient to diagnose and correct a problem.
If an error not mentioned in the table has occurred, check the unit’s Fault Log
and refer to the Fault Conditions table (Table 2-1) in this document. In
addition, the unit automatically sends SNMP traps for a Network Management
System (NMS) giving notification of the fault. See Section 3 for details
regarding Trap Information.
Table 2-1: Trouble Indications and Corrective Action
SymptomCauseCorrective Action
POWER lamp not on when POWER is
on.
ALARM lamp is lit.
LINK lamp does not turn on when LAN
cable connected to UPLINK socket.
Can not set office data using
Maintenance Console Software.
No dial tone even if when phone is offhook.
Dial tone continues after dialing.
Voice/fax transmission disconnects while
receiving or sending a fax.
Connect tone (CON) status continues
when dialing from a telephone and then
changes to Restricted Outward Tone
(ROT).
Calls can be made from a telephone but
calls cannot be received.
Power cord not connected or damaged.
•
Fuse blown.
•
Defective/damaged part(s).
•
Unit configuration error.
•
Cable is not correctly installed or is
•
defective.
Equipment failure has occurred.
•
Power to the destination equipment
•
(router, hub, etc.) not turned on.
IP address, gateway address, or subnet
•
address wrong.
Incorrect cable connection.
•
Cable between telephone and the BV1250
unit not connected or is damaged.
Dial type (DP/DTMF) of telephone set
•
does not match BV1250 unit office data
configuration.
Network is congested or a trouble has
•
occurred on the network.
Registered DNS server information is
•
incorrect.
DNS numbering information for BV1250
•
unit has not been set.
Registered Gatekeeper information is
•
incorrect.
Gatekeeper not operated.
•
Router Address Resolution Protocol
•
(ARP) information (IP address Ethernet address correspondence
information) does not match with the
BV1250 information.
Inspect and connect power cord.
•
(Replace cord if required.)
Replace fuse.
•
Check for defective part(s) and correct
•
condition.
Correct configuration error.
•
Inspect and reconnect LAN cable.
•
(Replace cable if required.)
Determine if there is an equipment
•
fault and correct condition.
Turn destination equipment power on.
•
Correct address(es).
•
Inspect cable for damage and type and
•
reconnect. (Replace cable if required.)
Inspect and connect cable.
•
(Replace cable if required.)
Correct office data configuration for
•
BV1250 unit.
Try again later.
•
Check the registered DNS information.
•
Verify that the DNS numbering plan
•
information for the BV1250 unit is
properly configured.
Check the registered Gatekeeper
•
information.
Check the Gatekeeper status.
•
Clear the router’s ARP information.
•
(To clear the ARP information, refer to
the router’s manual.)
: This symptom may occur even if
Note
the BV1250 has been replaced.
Rev. 1.0Page 9
Page 26
Maintenance and TroubleshootingBV1250 Technical Reference
2.3 Fault Log Codes and Corrective Action
The BV1250 maintains a fault log in which fault conditions are recorded as
they occur. The fault log is useful in diagnosing problems with a unit and in
determining appropriate corrective action.
NOTE:
Not all conditions recorded in the fault log represent faults
with the equipment. In some cases, the log records events
such as powering the unit up and down or rebooting the unit.
The Maintenance Console Software or the on-line command
ELOG
can be used
to retrieve a unit’s fault log. See the Maintenance Console Software
Operations Guide and the BV1250 On-line Command Reference section in this
document, for retrieval procedures.
Below is an example of a fault log report.
# ELOG
There are 003 Messages
10(Remove) 20(Voice) 00(DSP-Fault) SEQ=01 TUE Jan 06 12:29:30 1998
4EF9400015784E71 009029D0 009029D0 N.@..xNq..)...).
00(Fault) 20(Voice) 00(DSP-Fault) SEQ=01 TUE Jan 06 12:29:00 1998
0008F75C4FEF000C 300748CO 00000000 ...\0...0.H.r...
01(Report) 00(System) 00(Power-ON) SEQ=00 TUE Jan 06 12:28:52 1998
The information shown in the sample log output reveals that:
•
The equipment restarted at 12:28:52 PM on the 6th of January 1998 by
being powered ON (PowerON).
•
DSP trouble occurred in voice processing DSP of line no. 1 at 12:29:00
PM on the 6th of January 1998.
•
Voice processing DSP for line no. 1 was restored at 12:29:30 PM on the
6th of January 1998.
Table 2-2 on the following page provides definitions of the fields in a fault log
report. In addition, the table provides explanations and suggested corrective
actions associated with the various fault conditions.
Page 10Rev. 1.0
Page 27
BV1250 Technical ReferenceMaintenance and Troubleshooting
Rev. 1.0Page 11
Table 2-2: Fault Conditions
CodeCode
Detail
EquipmentMessage TypeFault
Abbreviation
SEQFault ExplanationAlarm LampComments and Corrective Action
On eventOn restore
0000SYSTEMReportPowerON00Power ONOff--No trouble.
01ReportResetKey00Reboot by reset keyOff--No trouble.
BV1250 Technical ReferenceMaintenance and Troubleshooting
Rev. 1.0Page 13
CodeCode
Detail
EquipmentMessage TypeFault
Abbreviation
SEQFault ExplanationAlarm LampComments and Corrective Action
On eventOn restore
1501
02
2002VOICEReportRFIFO_OVF00-03Receive FIFO
disconnected
Status hold--Excessive traffic on network. Try call
later.
03ReportNonPacket00-03Receive packet
disconnected
Status hold--Excessive traffic on network. Try call
later.
04ReportVCL_ERROR00-03Voice communications
error
Status hold--Excessive traffic on network. Try call
later.
3001FAXReportFaxError00
Fax communication
error
Status hold--
Excessive traffic on network. Try call
later.
4000CCLReportSockError
00-03
or FF
Communication errorStatus hold--Voice communications interrupted.
5000DNSReportSockError00Communication errorStatus hold--DNS communication interrupted.
01Report
RrqRrj
00
GK Communication
error
Status holdCheck Office data
02ReportXrsRcv00GK Communication
error
Status hold--Contact dealer or customer service.
Page 30
Maintenance and TroubleshootingBV1250 Technical Reference
3. Trap Information Sent to NMS
A Trap is one of the signals included in the Simple Network Management Protocol
(SNMP). In the case of the BV1250, a trap signal is sent to a Network
Management System (NMS) when a fault is detected in the unit. The trap
information is recorded in an NMS trouble log which, when retrieved by
maintenance personnel, can be useful in diagnosing and correcting problems with
the BV1250 unit.
The trap signal is sent to an NMS when an abnormality in the equipment or a
change in status is detected by the BV1250 unit’s software. If the fault is of a
critical nature, the equipment reboot processing is automatically started before
sending the trap. When this occurs, the unit sends the trap message to the NMS
during the system reboot.
A trap message is output using the fields shown in Table 3-1:
Table 3-1: Trap messages
FieldTypeValue
VersionINTEGERO(SNMP-Version1)
communityOCTET STRING“public”
enterpriseOBJECT INDENTIFIERObject ID of BV1250
agent-addrNETWORK ADDRESSIP address of BV1250
generic-trapINTEGER0(coldStart)
specific-trapINTERGERFault number
time-stampTimeTicksTime elapsed
variable-bindingsVarBindListNULL
6(enterpriseSpecific)
community:The community name value is configured in the BV1250
unit’s office data file (OFDD.VHO). The default value
in the OFDD.VHO file is “public”.
enterprise value:The enterprise value shows the object ID for a BV1250
unit, e.g. 1.3.6.1.4.1.666.90.3.3.1).
generic-trap:The cold start (coldStart) after the system startup causes
the trap value to be output as a generic-trap which is
displayed as 0. Messages other than this generic output,
such as fault, recovery, and report messages, are output
as the enterprise Specific trap value which is displayed as
a generic trap equal to 6.
Page 14Revision 1.0
Page 31
BV1250 Technical ReferenceMaintenance and Troubleshooting
specific-trap number:See the list and descriptions of traps in Table 3-2 below.
time-stamp value:The time-stamp value corresponds to the system setting
for sysUpTime of the internet standard MIB (MIB2).
This means that this value is not simply a date and time
but uses a time-stamp value that indicates the time that
has elapsed since the last unit initialization. This value is
reported in units of 1/100 sec.
Table 3-2: Traps
EventDisplay
Equipment
Name
DetailsFault
Trap?
Fault Code
(Specific Trap)
Recovery
Trap?
Recovery Code
(Specific Trap)
Comments and Corrective
Action
System
Flash
memory
End of power-ON
reboot
End of reset key
reboot
End of shutdownYes16777728No--See Table 2.2, Code 00-02
End of command
reboot
End of fault rebootYes16778240No--See Table 2.2, Code 00-04
Emergency
maintenance mode
startup
No office dataYes16778752No--See Table 2.2, Code 00-06
Office data errorYes16779008No--See Table 2.2, Code 00-07
Terminal information
not registered
No system dataYes16779520No--See Table 2.2, Code 00-09
System data errorYes16779776No--See Table 2.2, Code 00-0A
PP category
mismatch
No DNS dataNo--No--See Table 2.2, Code 00-OC
DNS data errorYes16780544No--See Table 2.2, Code 00-OD
H.323 port No. error
Network address
error
SOS callYes4096No--See Table 2.2, Code 00-10
CPU exceptionYes4352No--See Table 2.2, Code 00-11
K_fatal callYes4608No--See Table 2.2, Code 00-12
Infinite loop
detected
Watch dog timeoutYes5120No--See Table 2.2, Code 00-14
System message
error
Flash memory
mount fault
Flash memory write
fault
Flash disk fullYes16843275No--See Table 2.2, Code 01-02
Yes16777216No--See Table 2.2, Code 00-00
Yes16777472No--See Table 2.2, Code 00-01
Yes16777984No--See Table 2.2, Code 00-03
Yes1280No--See Table 2.2, Code 00-05
Yes16779264No--See Table 2.2, Code 00-08
Yes2816No--See Table 2.2, Code 00-OB
Yes3584No--See Table 2.2, Code 00-OE
Yes3840No--See Table 2.2, Code 00-OF
Yes4864No--See Table 2.2, Code 00-13
Yes5376No--See Table 2.2, Code 00-15
Yes65547No--See Table 2.2, Code 01-00
Yes65803No--See Table 2.2, Code 01-01
Revision 1.0Page 15
Page 32
Maintenance and TroubleshootingBV1250 Technical Reference
BV1250 Technical ReferenceMaintenance and Troubleshooting
4. FAX Issues
In most circumstances, BV1250 fax communications are effective and error free.
In some cases though, fax communications may be interrupted when there are high
network loads.
This condition occurs because the network is not able to guarantee the timings
stipulated in the ITU-T Rec. T.30 for fax communication. The chances that this
will occur vary based upon type of G3 fax machines in use and the general
configuration of the network.
If the automatic paper-cut function is activated on a thermal paper fax machine
which has a small receive-memory capacity, this problem may become more
noticeable. If possible, large-capacity plain-paper fax machine such as Oki’s
Models OKIFAX2450 and OKIFAX5600, are recommended. Contact Oki’s
offices for information regarding the characteristics to be selected in other types of
fax machines,
Revision 1.0Page 17
Page 34
Maintenance and TroubleshootingBV1250 Technical Reference
5. Fuse Replacement
The BV1250 unit has one fuse which is located in the rear panel of the base unit.
The fuse protects the unit against over-voltages and power spikes. If the unit’s fuse
should burn out, it must be replaced but first, the service person should attempt to
diagnose the correct the underlying problem. This will usually have something to
do with the power supply to the unit.
NOTE
Before replacing the fuse, turn the power to the unit OFF,
taking care to use the Power-off procedure described in the
BV1250 Installation Guide, Section 4.9.
To replace a fuse:
1. Unplug the unit’s power cord from the power outlet.
2. Pull the fuse holder assembly out from the rear panel of the unit.
3. Remove the fuse from the fuse holder and discard the failed fuse.
4. Replace the 7 x 30 fuse with a fuse of the same specification.
5. Reinsert the fuse into the fuse holder and reinstall the holder.
6. Reconnect the power cable plug to the power outlet, and turn the unit power
switch to the ON position.
7. Verify that the unit power is on and that the power-up cycle is correctly
completed as described in the BV1250 Installation Guide.
Figure 5-1: Fuse location
The table below describes the correct fuse type for the BV1250 unit.
Part NameManufacturerType
FuseNone7x30
Page 18Revision 1.0
Page 35
BV1250 Technical ReferenceMaintenance and Troubleshooting
6. Replacing the BV1250 Fan
The BV1250 unit fan provides cooling to the components contained in the base
unit. If the fan should fail, the unit should immediately be turned off to prevent
excessive heat build-up. The unit should not be power-up again until the fan has
been replaced.
NOTE
Before replacing the fuse, turn the power to the unit OFF,
taking care to use the Power-off procedure described in the
BV1250 Installation Guide, Section 4.9.
To replace the BV1250 fan assembly:
1. Unplug the unit’s power cord from the power outlet.
2. Remove five screws securing Base Unit chassis cover.
Revision 1.0Page 19
Figure 6-1: BV1250 chassis cover removal
Page 36
Maintenance and TroubleshootingBV1250 Technical Reference
3. Slide the chassis cover back from the chassis until clear of the locking tab.
4. Lift chassis cover clear of chassis.
5. Store chassis cover in a safe location.
6. Remove the cable that interconnects Main board and fan.
7. Unscrew the four fan securing screws located on the bottom of the Base Unit’s and
remove the fan guard, fan, and fan fixing plate.
8. Reverse the process described in step 7 above to install the new fan subassembly.
9. Reconnect the fan connecting cable to the Main Board.
10. Reconnect the power cable plug to the power outlet, and turn the unit power switch to
the ON position.
11. Verify that the unit power is on and that the power-up cycle is correctly completed.
(See the section: Powering-up the BV1250 and Verify Operation, in the BV1250
Installation Guide, Section 4.8, for details.)
Part NameDrawing No.Manufacturer
BV1250 fan270A2354P0001Oki
Page 20Revision 1.0
Figure 6-2: Fan assembly replacement
Page 37
BV1250 Technical ReferenceMaintenance and Troubleshooting
7. Common Problems and Solutions
In this section some common problem conditions are described along with appropriate
corrective action. Each item begins with a statement of symptoms and is followed by an
explanation of the cause and actions that can be taken to resolve the difficulty.
IP Address Error (FXS, FXO and E&M/E&M-OD)
Symptom:After reboot the ALARM lamp is ON and ONLINE lamp is
flashing.
Cause: When a unit’s IP address, Gateway (Router) IP address and
Subnet Mask IP address do not belong to the same subnet, the
OFDD.VHO file is overwritten with the unit’s default settings
after issuing the OUP command.
Action:Follow the installation procedure to fully reconfigure the unit’s
OFDD.VHO file, correcting the unit’s addressing scheme. See
BV1250 Installation Guide, Section 5.7, for details.
Date Error (FXS, FXO and E&M/E&M-OD)
Symptom:After reboot the ALARM light is ON and ONLINE lamp ON.
Cause: The unit’s NiCD battery has become depleted and the unit’s time
and date have reverted to the default settings.
Action:Follow the installation procedure for setting the unit’s time and
date. See BV1250 Installation Guide, Section 5.11, for details.
No Dial Tone, BUSY lamp ON (E&M/E&M-OD)
Symptom:No dial tone is heard when grabbing the E&M trunk form the
PBX. The unit’s BUSY lamp is ON.
Cause: Voice cabling problem.
Action:Check to see that the voice cabling conforms to the information
provided in the installation instructions. See BV1250 Installation
Guide, Section 4.5, for details.
Revision 1.0Page 21
Page 38
Maintenance and TroubleshootingBV1250 Technical Reference
No Dial Tone, BUSY lamp OFF (E&M/E&M-OD)
Symptom:No dial tone is heard when grabbing the E&M trunk form the
PBX. The unit’s BUSY lamp is OFF.
Cause: The unit’s TERMDLD and PBX trunk parameters are incorrectly
configured and the E&M cabling may be incorrect.
Action:Refer to the installation instruction and check the TERMDLD and
PBX trunk parameters. See BV1250 Installation Guide, Section
5.9, for details.
If the problem persists, check the E&M cabling to verify that it
conforms to the installation instructions. See BV1250 Installation
Guide, Section 4.5, for details.
Connected Call Dropped (E&M/E&M-OD)
Symptom:When calling a remote unit, the call is connected but is dropped
within couple of seconds.
Cause: It is likely that the unit and PBX trunk parameters are in conflict.
For example, the unit is configured for Immediate-start but the
PBX trunk is configured for Delayed start.
Action:Refer to the installation instructions for configuring E&M trunk
parameters and correct conflicts between the PBX parameters
(TERMDLD) and the unit’s trunk parameters. See BV1250
Installation Guide, Section 5.9.1, for details.
Unable to connect through PBX Type 1 (E&M/E&M-OD)
Symptom:Call cannot be connected with a unit that is connected through a
PBX using Type 1 start-up.
Cause: It is likely that the BV1250 base unit and the PBX using Type 1
start-up have not been installed so that they share a common
ground.
Action:When installing a unit for use with a PBX Type 1 E&M interface
the BV1250 unit and the PBX must be connected to a common
ground. Refer to the installation instructions to install the ground
properly. See BV1250 Installation Guide, Section 4.5, for details.
Page 22Revision 1.0
Page 39
BV1250 Technical ReferenceMaintenance and Troubleshooting
When calling, a fast busy tone is returned (FXS, FXO and E&M/E&M-OD)
Symptom:When calling a terminal connected through and E&M, FXS, or
FXO unit, a fast busy tone is returned and connection cannot be
made.
Cause: The calling party's BV1250 unit is programmed with the
DNSSEANUM value set too high. The DNSSEANUM value
(referred to as Remaining Digits in the DNS Connection
Information Worksheet in the BV1250 Installation Guide) must
be configured to match the smallest number of digits used for an
Office Code in the network. The default value for this item is
DNSSEANUM=2. If one or more Office Codes with single digits
exist in the network, this problem is more likely to occur.
For example, if a called BV1250 unit has a single-digit office
code and a caller dials the number, the calling BV1250 attempts
to look for the DNS entry but searches for the first two matching
digits. Since only one is present, the call cannot be processed.
Action:Check the DNSSEANUM value for calling BV1250 unit and
change it to match the smallest number of digits used for a
network Office Code. See BV1250 Installation Guide,
Appendix D, for details.
When calling, a fast busy tone is returned (FXS, FXO and E&M/E&M-OD)
Symptom:When calling a terminal connected through a unit, a fast busy tone
is returned and connection cannot be made.
Cause: The DNS.DAT has not been uploaded or has been uploaded using
an incorrect directory and/or filename.
Since the directory and filename parameters are case sensitive,
this problem often results from entering parameters using the
wrong character case during FTP uploads.
In the case of an FXS unit only, this condition can be easily
checked by placing a call from one unit port to another. If a Ring
Back Tone is returned, the DNS.DAT file for the unit has been
correctly uploaded.
E&M units, must be checked manually.
Action:Upload the BV1250 unit’s DNS.DAT file again. If using FTP, use
care to properly enter all directory and filename parameters. See
BV1250 Installation Guide, Section 5.10 and Appendix J, for
details.
Revision 1.0Page 23
Page 40
Maintenance and TroubleshootingBV1250 Technical Reference
Connection with a remote unit works some times and not at other times
(E&M/E&M-OD)
Symptom: Sometimes a connection to the remote E&M unit can be made but
at other times the connection cannot be established. This is the
case even when the unit on the remote side is not in use.
When no connection is made, units connected using Wink-start
return a fast busy tone. Units connected using Immediate or
Delayed-start return no activity.
Cause: When all ports are not connected from BV1250 unit to the PBX,
the unused ports have not been disabled in the unit’s OFDD.VHO
file. If unused ports are not disabled, some calls to the unit may be
erroneously routed through an unused port.
Action:Ensure that all unconnected ports are configured as disabled in the
unit’s OFDD.VHO file. See BV1250 Installation Guide, Section
5.9.1, for details.
When calling a unit, fast busy tone is returned and the BUSY lamp on the
remote side is not illuminated (E&M/E&M-OD)
Symptom:When calling an E&M unit from either an FXS, FXO or E&M
unit, a fast busy tone is returned. The remote E&M unit’s busy
lamp is not illuminated.
Cause: The calling unit’s DNS.DAT file is correctly configured with the
office code for the called unit, but the called E&M unit’s HNTPN
(Hunt Pattern) Office Code parameter code parameter is incorrect.
The HNTPTN Called Number parameter must match the
DNS.DAT connection information number Office Code.
Action:Correct the HNTPTN parameter for the called unit so that the
Office Code matches the calling unit’s DNS.DAT Connection
Information entry for the Called Number. See BV1250
Installation Guide, Section 5.9.1 and Appendix D, for details.
Page 24Revision 1.0
Page 41
BV1250 Technical ReferenceMaintenance and Troubleshooting
Called PBX returns a busy tone1 (E&M/E&M-OD)
Symptom:Call to E&M unit from a another unit cannot be connected. A
busy tone is returned.
Cause: Called unit’s Delete Digits parameter incorrectly configured. The
Delete Digits parameter (TGNPRIORITY) in the unit’s
OFDD.VHO must match the number of digits making up the
Office Code for the PBX to which the unit is connected.
Action:Correct the TGNPRIORITY Delete Digits parameter so that it
matches the number of digits making up the Office Code of the
PBX to which the unit is connected. See BV1250 Installation
Guide, Section 5.9.1, for details.
When calling a remote unit, BUSY lamp illuminates and fast busy is
returned or there is not activity (E&M/E&M-OD)
Symptom:When calling an E&M unit connected to a PBX using Wink-start
from an FXS, FXO, or E&M unit, the called unit’s BUSY lamp
illuminates and a fast busy tone is returned. When calling an
E&M unit connected to a PBX using Immediate or Delayed-start,
no activity occurs.
Cause: This may be due to incorrect cabling at the unit side or the PBX
side.
Action:Inspect the cable connections at the unit and at the PBX. Correct
any cabling errors. See BV1250 Installation Guide, Section 4.5,
for details.
LINK lamp not illuminated when LAN cable is connected and connection is
active (FXS, FXO and E&M/E&M-OD)
Symptom:When a LAN connection is made between the unit and LAN and
communication is attempted, the LINK lamp does not illuminate.
Cause:It is possible that the wrong cable type is being used. A CAT5
Straight cable must be used to interconnect a BV1250 unit with a
hub/switch. A CAT5 Cross/Rollover cable must be used to
interconnect a BV1250 unit with a router.
Action:Check cable type and correct if necessary. See BV1250
Installation Guide, Section 4.5.3, for details.
1
Return may vary depending on PBX type.
Revision 1.0Page 25
Page 42
Maintenance and TroubleshootingBV1250 Technical Reference
Network connection not working when using Telnet & File Transfer
Protocol (FXS, FXO and E&M/E&M-OD)
Symptom:Cannot communicate with unit through a Telnet/FTP connection.
Cause:The power to the unit is not turned ON. Also, the unit IP address
is incorrect and/or the computer and unit are not configured as
members of the same domain (Gateway and subnet addresses.)
Finally, if communicating across a firewall, the Telnet/FTP
requests the Firewall restrictions parameter is not selected.
Action:Turn the unit’s power ON. Also, check the IP addressing scheme
for the computer host settings and the unit and correct them if
necessary. See BV1250 Installation Guide, Section 5.7, for
details.
Finally, if a firewall is present, configure the Telent/FTP requests
for Firewall restrictions. See BV1250 Installation Guide,
Appendix G for details.
Outgoing calls okay, but incoming calls are restricted (FXS, FXO and
E&M/E&M-OD)
Symptom:Units connected to the network through an Ethernet switch using
an ARP cache outgoing calls can be placed but cannot receive
incoming calls.
Cause:If an Ethernet switch using an ARP cache is configured with a
refresh rate that is shorter than that of the routers used to connect
network workgroups, the switch may not be able to accept the
incoming data and forward it to the correct node.
2
Action:Reconfigure the Ethernet switch ARP cache table refresh rate so
that it is longer than the router ARP table refresh rate. See the
Router’s documentation for details.
Unit installed a far end of network cannot make or receive calls (FXS, FXO
and E&M/E&M-OD)
Symptom:Even after checking all cabling and network connectivity, it is not
possible to setup calls. The problem unit is located on a branch at
the far end of the network.
Cause:The unit’s gateway address represents the network’s main router,
but there is another router that is closer.
Action:Change the unit’s gateway address to that of the router that is
closest to the unit. See BV1250 Installation Guide, Appendix G,
for details.
2
This conditions will not occur if a hub is used as the connection point for BV1250 units.
Page 26Revision 1.0
Page 43
BV1250 Technical ReferenceMaintenance and Troubleshooting
Calls and fax communications for units communicating with the network
through a Firewall are erratic or cannot be setup (FXS, FXO, and
E&M/E&M-OD)
Symptom:Cabling and network connectivity have been checked for proper
operation but calls and faxes cannot be setup. The unit(s) are
connected to the WAN through a Firewall.
Cause:Routing a BV1250 network through a Firewall installation
requires that the Firewall be specifically configured to allow
BV1250 unit TCP/UDP port communication in both directions
Action:See BV1250 Installation Guide, Appendix G, for details and
verify that the Firewall is properly configured. Also see below.
Ensure that the source port on the firewall is configured as ANY
(Random) and that the destination port is fixed according to the
table shown below.
The following rules apply to Firewall port configuration.
•TCP/UDP ports used by BV1250 must be opened in
Firewall rules.
• Ports must be opened for both input and output detection.
• Source ports for TCP/UDP packets must be configured as
Random port numbers.
When installing the BV1250 network within a firewall, voice and
fax packets must be routed through specified firewall ports using
the information in the following table.
Table 7-1: Firewall port configuration
Port TypeSource PortDestination PortNotes
TCPAny / Random1720Used for Q.931
TCPAny / Random1721Used for H.245
TCPAny / Random1722Used for H.245
TCPAny / Random1723Used for H.245
TCPAny / Random1724Used for H.245
UCPAny / Random5004Used for RTP
UCPAny / Random5005Used for RTCP
UCPAny / Random5006Used for RTP
UCPAny / Random5007Used for RTCP
UCPAny / Random5008Used for RTP
UCPAny / Random5009Used for RTCP
UCPAny / Random5010Used for RTP
UCPAny / Random5011Used for RTCP
UCPAny / Random1718Used for RAS (When gatekeeper used)
UCPAny / Random1719Used for RAS (When gatekeeper used)
3
3
The values in Table 7-1 are default values and can be modified using the MCS Call Control folder.
Revision 1.0Page 27
Page 44
Maintenance and TroubleshootingBV1250 Technical Reference
Voice volume too low or voice is distorted and has echo (FXS, FXO, and
E&M/E&M-OD)
Symptom:When using the telephone set, the vice volume is too low or the
voice sounds distorted and has echo.
Cause:The gain setting parameter (PAD-VALUE) in the unit’s
OFDD.VHO file is incorrectly configured.
Action:If the voice volume is too low, increase the PAD setting to
increase gain. If the voice sounds distorted and has echo, reduce
the PAD value. See BV1250 Installation Guide, Appendix F, for
details.
Page 28Revision 1.0
Page 45
BV1250 Technical ReferenceOn-line Commands
On-line Command
Reference
The on-line commands described in this reference allow remote control of the BV1250
through a simple text line interface. For experienced users, this interface can be used to
quickly configure and manage BV1250 units installed in a network.
When using a Telnet or LAN connection, these commands can be entered using a simple
VT100 compatible terminal or terminal window (e.g. The Terminal Mode window in the
Maintenance Console Software).
In addition, these commands make it possible for programming personnel to integrate
BV1250 IVG control and management functions into legacy Network Management
Systems.
This reference is divided into the following sections.
1. Command Overview
2. List of Utility Commands
3. Common Errors for Maintenance Commands
4. Command List
5. Command Descriptions
The command descriptions presented in this document are intended for the use of persons
experienced in line command interfaces. Below are some important notes regarding the
conventions used in this document and the use of the on-line commands.
The command descriptions provided in Section 5 of this document are organized in
the following manner.
Title: Includes the command item identifier number and command(s)
to be described.
Class:The class in which the command is grouped.
Function:The general function of the command.
Characteristics: Description of the function of the command including any input
parameters (P1, P2, P3, etc.) if required, and the output of the
command.
When necessary, the Input Parameter(s) and Output sections may
include additional description and explanation of the data.
Access:The methods of access (RS-232C and/or LAN) through which
the command(s) can be transmitted.
4
Examples:Provides practical examples of the command(s), including inputs
Errors:Description of the command specific error that may be returned
1.2 ACT and SBY
In most cases, the SET, GET, and RST (Reset) argument is used to enter one or
more configuration parameters into a BV1250 unit. When these commands are
used, two values are returned through the on-line interface. These are the ACT
value and the SBY value.
ACT:The ACT value stands for Active and refers to the value that is currently
configured and in use within the unit.
SBY:The SBY value stands for the new value that has been entered using the
SET command but has not yet been written (backed-up) to the unit’s
internal memory using the OUP command.
All parameters entered using the on-line commands must be written to the unit
using the OUP command before they can take effect. Rebooting or power cycling a
unit before the OUP command is issued will cause all SBY values to be lost.
When one or more parameters are not changed the SET and GET commands will
return identical ACT and SBY values for all unchanged parameters.
and outputs.
by the command and typical remedies for the error condition.
4
The GET argument returns ALL unit information for the specified command. In most cases where the P1 Set
parameter refers to a port or index number, appending the P1 parameter to the GET command will limit the
information returned to the specified item.
Command inputs, prompts, and return messages are displayed throughout this
document in a fixed Courier font.
All command examples are presented in a format that emulates the way in which
the data entry and command returns will actually appear on a terminal screen. For
the purposes of clarity, the command information to be entered by the user is
underscored.
The screen prompt for all commands is an # symbol, indicating that the system is
ready to accept the next user input.
NOTE
All command are case sensitive!
1.4 Parameter Notation
In the command descriptions, input parameters are indicated by the letter P and a
number indicating the order in which the parameter is entered in the command line,
e.g. P1, P2, and P3.
In some cases, when describing a command in which an alpha /numeric input is
required, the input requirements are indicated in the following manner.
Numeric = Parameter indicated as nnnnnnnn, where n is a number and
the total or maximum number of digits is represented. In some
cases the # and * may be permitted. This is noted when
applicable.
Alpha/numeric = Parameter indicated by alphanumeric string in lower case
letters, where the input string may include any numeric or
alpha characters. See parameter description for conditions.
1.5 Response Messages
There are two types of response messages (end of command messages): Normal
and Abnormal.
Normal
A normal end-of-command message appears in the following example.
Example:
XXXXXXXX Command End. [Tue Jan 27 17:00:23 1998]
(Command Name)(Day Month Date Time (Hour: Minute: Second)
Year)
#
In the following example, the message output indicates that the system could not
execute the command and that a problem exists with the command syntax or the
equipment itself.
Example:
XXXXXXXX Command Error(nnn-nn) End.
(Command Name)(Error no. + Parameter no.)
[Tue Jan 27 17:00:23 1998]
(Day Month Data Time (Hours: Minutes: Seconds)Year)
#
When this occurs and the cause of the error is the parameter entered, the output
shows an error number and the parameter number that caused this error.
If there was no parameter, the parameter number is returned as 00 (nnn-00).
If too few parameters were entered, the parameter number returned is the number
of input parameters plus 1.
If too many parameters were entered, the parameter number returned is the
maximum number of the parameters that can be input.
1.6 Continuous Mode and Page Mode Display
Some commands (e.g. Report commands such as ELOG, HIST, and TRF) will
produce lengthy returns. When the terminal display is configured for Continuous
mode, the information at the top of the output message may be scrolled off the
screen.
Use the SET-LIST-MOD to change the List Mode from Continuous to Page
display. This will cause the output to be paused when the screen display becomes
full. The output to the screen can then be controlled by the user. See the SETLIST-MOD command in the Commands Description section of this document for
more information.
The Utility commands (pSH) used in the maintenance of the BV1250 IVG are listed in
alphabetical order in Table 2-1 . In addition, the access authorization level required to use
these commands is indicated the Access column.
Table 2-1: Utility Commands
Item
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
Command
Name
arp
cat
cd
cdmount
clear
cmp
cp
du
date
echo
setenv
getid
getpri
head
help
ifconf
kill
ls
mkdir
mkfs
mount
mv
netstat
pcmkfs
pcmount
ping
popd
pushed
pwd
Summary
Command to set, delete and display ARP table informationM
Join and output file commandM
Change directory commandM
Command to mount CD-ROM file system--
Clear terminal screen commandU and M
Command to compare two files in unit of byte--
Copy file command--
Display disk condition of use command--
Date and time set/display command--
Command to output augments to standard output--
Command to set environment variables--
Command to get user ID and group ID from Network File System (NFS)--
Task priority display command--
Command to display the number of digits at the head of a fileM
Equipment commands are used to configure a BV1250 unit’s Office Data file
(OFDD.VHO). All parameters entered are displayed as SBY until they are backed-up in
the unit using the OUP command and the unit is rebooted.
Commands used to set, get, and reset the DNS IP address(s) of BV1250
SET-DNS-IP
Writes from 1 to 3 DNS IP address to a BV1250 unit and displays original and new addresses
(maximum of 3).
Input Parameter(s):
Output Parameter(s):
GET-DNS-IP
Returns current DNS IP address(s) of a BV1250 (maximum of 3).
Input Parameter(s):
Output Parameter(s):
RST-DNS-IP
Resets the current DNS IP address(s) of a BV1250 to an unassigned state.
Input Parameter(s):
Output Parameter(s):
RST)
and
P1 - IP address for DNS 1. Input value entered in standard IP format which consists of numeric
values separated by period in the range of 0 ~ 255 in decimal notation where the range is nnn
when the IP address is nnn.nnn.nnn.nnn
P2 - IP address for DNS 2. Input value entered in standard IP format which consists of numeric
values separated by period in the range of 0 ~ 255 in decimal notation where the range is nnn
when the IP address is nnn.nnn.nnn.nnn
P3 - IP address for DNS 3. Input value entered in standard IP format which consists of numeric
values separated by period in the range of 0 ~ 255 in decimal notation where the range is nnn
when the IP address is nnn.nnn.nnn.nnn
Displays current (ACT) and new (SBY) parameters for each DNS address (DNS_IP_1, DNS_IP_2,
etc.) in BV1250 where an unassigned DNS IP address values are displayed as ***.***.***.***.
None
Displays current (ACT) and new (SBY) parameters for each DNS address (DNS_IP_1, DNS_IP_2,
etc.) in BV1250, reported in standard IP addressing format. Unassigned (reset) DNS IP address
values are displayed as ***.***.***.***.
None
Displays current (ACT) and new (SBY) parameters for each DNS address (DNS_IP_1, DNS_IP_2,
etc.) in BV1250, reported in standard IP addressing format. Unassigned (reset) DNS IP address
values are displayed as ***.***.***.***.
Commands to set and get the DNS search start digits number
SET-DNS-SERNUM
Writes a value (1 to 32) representing the number of digits required to start the telephone number to IP
address translation look-up process in the DNS server/DNS.DAT.
Input Parameter(s):
Output Parameter(s):
Displays current (ACT) and new (SBY) parameters as start digits 1 to 32
GET-DNS-SERNUM
Returns the current setting for the DNS start digits
Input Parameter(s):
Output Parameter(s):
Displays current (ACT) and new (SBY) parameters as start digits 1 to 32
Writes access start time and access cycle time to the BV1250. Start time is the time at which the
BV1250 will reinitialize its DNS cache. Cycle time is the period of time that will elapse (following the
start time) until the cache is cyclically reinitialized
Input Parameter(s):
Output Parameter(s):
GET-DNS-TIME
Returns current DNS access and cycle time settings in the BV1250.
Input Parameter(s):
Output Parameter(s):
GET)
and
P1 - Start time is entered as a four digit number where the first two digits are for start hour and the
second two digits are minutes, e.g. hhmm
P2 - Access time is entered as a two digit value between 01 and 24 representing from 1 to 24 hours
Displays current (ACT) and new (SBY) parameters for DNS start and access times
None
Displays current (ACT) and new (SBY) parameters for DNS start and access times
ACCESS
SET-DNS-TIME:
GET-DNS-TIME:
EXAMPLE(S)
SET-DNS-TIME nnnn nn
GET-DNS-TIME
ERRORS
RS-232C and LAN
RS-232C and LAN
#SET-DNS-TIME 0915 12
ACT Start Time=00:00 ACT Time Interval to Update=24
SBY Start Time=09:15 SBY Time Interval to Update=12
...SET-DNS-TIME Command End. [Thu May 28 17:00:23 1996]
#
#GET-DNS-TIME
ACT Start Time=00:00 ACT Time Interval to Update=24
SBY Start Time=09:15 SBY Time Interval to Update=12
...GET-DNS-TIME Command End. [Thu May 28 17:00:23 1996]
#
Commands used to set, reset, and get IP address of Gatekeeper configured in a BV1250 unit.
SET-GK-IP
Writes Gatekeeper IP address(es) to a BV1250 unit
Input Parameter(s):
Output Parameter(s):
RST-GK-IP
Resets the current Gatekeeper IP address(es).
Input Parameter(s):
Output Parameter(s):
GET-GK-IP
Returns current Gatekeeper IP address(es) set in a BV1250 unit
Input Parameter(s):
Output Parameter(s):
RST)
and
P1 - Primary Gatekeeper IP address (Gatekeeper 1) entered in standard IP format which consists of
numeric values separated by period in the range of 0 ~ 255 in decimal notation (Range is nnn
when the IP address is nnn.nnn.nnn.nnn). In the case of the BV1250 the Gateway address is
usually the address of the Router to which the unit is connected
P2 - Optional secondary Gatekeeper IP address (Gatekeeper 2) entered in standard IP format which
consists of numeric values separated by period in the range of 0 ~ 255 in decimal notation
(Range is nnn when the IP address is nnn.nnn.nnn.nnn). In the case of the BV1250 the
Gateway address is usually the address of the Router to which the unit is connected
Displays current (ACT) and new (SBY) parameters for Gatekeeper address(es) in standard IP format
which consists of numeric values separated by period in the range of 0 ~ 255 in decimal notation
where range of nnn when the IP address is nnn.nnn.nnn.nnn
None
Displays current (ACT) and new (SBY) parameters for Gatekeeper IP address where a deleted (reset)
Gatekeeper address is shown as ***.***.***.***.
None
Displays current (ACT) and new (SBY) parameters for Gatekeeper address(es) in standard IP format
which consists of numeric values separated by period in the range of 0 ~ 255 in decimal notation
(Range of nnn when the IP address is nnn.nnn.nnn.nnn)
#GET-GK-IP
Gatekeeper 1 ACT IP Address=***.***.***.*** SBY IP Address=***.***.***.***
Gatekeeper 2 ACT IP Address=***.***.***.*** SBY IP Address=***.***.***.***
Currentry NO Active Gatekeeper.
...GET-GK-IP Command End. [FRI May 21 16:50:32 1999 GW]
Commands used to set, reset, and get Gateway IP address of BV1250
SET-GW-IP
Writes Gateway IP address to a BV1250 unit and displays new address
Input Parameter(s):
Output Parameter(s):
RST-GW-IP
Resets the current Gateway IP address.
Input Parameter(s):
Output Parameter(s):
GET-GW-IP
Returns current Gateway IP address of a BV1250.
Input Parameter(s):
Output Parameter(s):
RST)
and
P1 - Gateway IP address entered in standard IP format which consists of numeric values separated
by period in the range of 0 ~ 255 in decimal notation (Range is nnn when the IP address is
nnn.nnn.nnn.nnn). In the case of the BV1250 the Gateway address is usually the address of the
Router to which the unit is connected
P2 - Optional secondary Gateway IP address entered in standard IP format which consists of
numeric values separated by period in the range of 0 ~ 255 in decimal notation (Range is nnn
when the IP address is nnn.nnn.nnn.nnn). In the case of the BV1250 the Gateway address is
usually the address of the Router to which the unit is connected
Displays current (ACT) and new (SBY) parameters for Gateway address in standard IP format which
consists of numeric values separated by period in the range of 0 ~ 255 in decimal notation where
range of nnn when the IP address is nnn.nnn.nnn.nnn
None
Displays current (ACT) and new (SBY) parameters for Gateway IP address where a deleted (reset)
Gateway address is shown as. ***.***.***.***.
None
Displays current (ACT) and new (SBY) parameters for Gateway address in standard IP format which
consists of numeric values separated by period in the range of 0 ~ 255 in decimal notation (Range of
nnn when the IP address is nnn.nnn.nnn.nnn)
Writes IP address to a BV1250 unit and displays new address
Input Parameter(s):
Output Parameter(s):
Returns current IP address of a BV1250
Input Parameter(s):
Output Parameter(s):
SET
P1 - Input value entered in standard IP format which consists of numeric values separated by period
in the range of 0 ~ 255 in decimal notation (Range is nnn when the IP address is
nnn.nnn.nnn.nnn)
Output values for current (ACT) and new (SBY) parameters displayed in standard IP format which
consists of numeric values separated by period in the range of 0 ~ 255 in decimal notation (Range of
nnn when the IP address is nnn.nnn.nnn.nnn)
None
Returned values for current (ACT) and new (SBY) parameters displayed in standard IP format which
consists of numeric values separated by period in the range of 0 ~ 255 in decimal notation (Range of
nnn when the IP address is nnn.nnn.nnn.nnn)
and
GET)
ACCESS
SET-IP:
GET-IP:
EXAMPLE(S)
SET-IP nnn.nnn.nnn.nnn
GET-IP
ERRORS
RS-232C and LAN
RS-232C and LAN
#SET-IP 133.149.33.23
ACT IP Address=133.149.33.2 SBY IP Address=133.149.33.23
...SET-IP Command End. [Thu May 28 17:00:23 1996]
#
#GET-IP
ACT IP Address=133.149.33.2 SBY IP Address=133.149.33.23
...GET-IP Command End. [Thu May 28 17:00:23 1996]
#
Set, get, and reset SMTP address(es) to be associated with unit.
SET-SMTP-ADR
Input Parameter(s):
Output Parameter(s):
GET-SMTP-ADR
Returns current for SMTP-server destination IP addresses in a BV1250 unit.
Input Parameter(s):
Output Parameter(s):
RST-SMTP-ADR
Resets SMTP-server destination IP addresses in a BV1250 unit.
Input Parameter(s):
Output Parameter(s):
RST)
and
P1 - Input for SMTP-server IP address 1, entered in standard IP format which consists of numeric
values separated by period in the range of 0 ~ 255 in decimal notation (Range is nnn when the
IP address is nnn.nnn.nnn.nnn)
P2 - Input for SMTP-server IP address 2, entered in standard IP format which consists of numeric
values separated by period in the range of 0 ~ 255 in decimal notation (Range is nnn when the
IP address is nnn.nnn.nnn.nnn)
Displays current (ACT) and new (SBY) parameters for SMTP-server IP addresses. Addresses
displayed in standard IP format which consists of numeric values separated by period in the range of
0 ~ 255 in decimal notation (Range is nnn when the IP address is nnn.nnn.nnn.nnn)
None
Displays current (ACT) and new (SBY) parameters SMTP-server IP addresses. Addresses displayed
in standard IP format which consists of numeric values separated by period in the range of 0 ~ 255 in
decimal notation (Range is nnn when the IP address is nnn.nnn.nnn.nnn)
None
Displays current (ACT) and new (SBY) parameters for SMTP-server IP address(s) where the reset
(deleted) SMTP-server IP address is shown as ***.***.***.***.
Commands used to set, reset and get SNMP Trap destination of BV1250
SET-SNMP-TRPDST
Writes from 1 to 3 SNMP trap destination IP addresses to a BV1250 unit and displays new address. IP
address set in the first parameter (P1) is of the highest priority
Input Parameter(s):
Output Parameter(s):
GET-SNMP-TRPDST
Returns current SNMP trap destination IP addresses in a BV1250 unit.
Input Parameter(s):
Output Parameter(s):
RST-SNMP-TRPDST
Resets SNMP trap destination IP addresses in a BV1250 unit.
Input Parameter(s):
Output Parameter(s):
RST)
and
7
P1 - Input for SNMP trap IP address 1, entered in standard IP format which consists of numeric
values separated by period in the range of 0 ~ 255 in decimal notation (Range is nnn when the
IP address is nnn.nnn.nnn.nnn)
P2 - Input for SNMP trap IP address 2, entered in standard IP format which consists of numeric
values separated by period in the range of 0 ~ 255 in decimal notation (Range is nnn when the
IP address is nnn.nnn.nnn.nnn)
P3 - Input for SNMP trap IP address 3, entered in standard IP format which consists of numeric
values separated by period in the range of 0 ~ 255 in decimal notation (Range is nnn when the
IP address is nnn.nnn.nnn.nnn)
Displays current (ACT) and new (SBY) parameters for SNMP trap IP addresses. Addresses
displayed in standard IP format which consists of numeric values separated by period in the range of
0 ~ 255 in decimal notation (Range is nnn when the IP address is nnn.nnn.nnn.nnn)
None
Displays current (ACT) and new (SBY) parameters for SNMP trap IP addresses. Addresses
displayed in standard IP format which consists of numeric values separated by period in the range of
0 ~ 255 in decimal notation (Range is nnn when the IP address is nnn.nnn.nnn.nnn)
None
Displays current (ACT) and new (SBY) parameters for SNMP trap IP address(s) where the reset
(deleted) SNMP trap IP address is shown as ***.***.***.***.
ACCESS
SET-SNMP-TRPDST:
RST-SNMP-TRPDST:
GET-SNMP-TRPDST:
7
hecks for identical IP addresses are not performed in a parameter.
8Control toneHowler toneHWTTelephone is off the hook
GET)
and
8
P1 - Tone type input as a value of 1 to 8 (See Tone Types in table below)
Table: Tone Types
BV1250
unit
P2 - Tone type input as a value of 0 to 17 and 100. See Tone Type tables at the end of this
command description
P3 - Input customize tone
Output Parameter(s):
Displays current (ACT) and new (SBY) parameters for Tone parameters in BV1250 unit
GET-TONE
BV1250
unit
BV1250
unit
ACCESS
Returns Tone parameters in
Input Parameter(s):
Output Parameter(s):
SET-TONE:
GET-TONE:
None
Displays current (ACT) and new (SBY) parameters for Tone parameters in
RS-232C and LAN
RS-232C and LAN
8
Use the SET-AREA command to write/initialize a base configuration (US, EU, JP) to the BV1250 unit, then
use the SET_TONE command to modify individual tone settings. See Initial Tone Values table at the end of
this command description.
Command to set and get community name for trap transmission
SET-TRP-COMMU
Writes a community name for trap transmission to a BV1250 unit and displays current and new name
Input Parameter(s):
Output Parameter(s):
GET-TRP-COMMU
Returns current community name for trap transmission.
Input Parameter(s):
Output Parameter(s):
SET-TRP-COMMU:
GET-TRP-COMMU:
GET)
and
P1 - Community name Input entered as a string of 1 to 8 characters
Displays current (ACT) and new (SBY) parameters for community name
None
Displays current (ACT) and new (SBY) parameters for community name
RS-232C and LAN
RS-232C and LAN
EXAMPLE(S)
SET-TRP-COMMU name
GET-TRP-COMMU
ERRORS
#SET-TRP-COMMU Name2
ACT Community Name for Trap Transmission=Name1 SBY Community Name
for Trap Transmission=Name2
...SET-TRP-COMMU Command End. [‘Thu May 28 17:00:23 1996]
#
#GET-TRP-COMMU
ACT Community Name for Trap Transmission =Name1 SBY Community Name
for Trap Transmission=Name2
...GET-TRP-COMMU Command End. [Thu May 28 17:00:23 1996]
#
No. 0101:
Cause -Community name exceeds maximum number of characters.
Commands to set, get, and reset domain name in a BV1250 unit.
SET-VBM-DOMAIN
Writes domain name to a BV1250 unit and displays new name
Input Parameter(s):
Output Parameter(s):
GET-VBM-DOMAIN
Returns current domain name a BV1250
Input Parameter(s):
Output Parameter(s):
RST-VBM-DOMAIN
Resets Domain name in a BV1250 unit to a null value
Input Parameter(s):
Output Parameter(s):
RST)
and
P1 - Domain name may consist of up to 63 alphanumeric characters (from Aa to Zz and 0 to 9), and
may use hyphen (-), underscores ( _ ), and periods (.). No spaces may appear in the name and
uppercase letters and lower case letters are not differentiated. A name must start with an alpha
character and may not end with a hyphen.
Output values for current (ACT) and new (SBY) parameters displayed for Domain name
None
Current (ACT) and new (SBY) parameters displayed for BV1250 Domain name
None
Displays current (ACT) and new (SBY) parameters for BV1250 Domain name where the reset
(deleted) BV1250 Domain name is shown as
Commands used set and get the subnet mask of BV1250
SET-VBM-SUBNET
Writes subnet address to a BV1250 unit and displays new address
Input Parameter(s):
Output Parameter(s):
GET-VBM-SUBNET
Returns current subnet address of a BV1250
Input Parameter(s):
Output Parameter(s):
Returned values for current (ACT) and new (SBY) parameters displayed in standard IP format which
consists of numeric values separated by period in the range of 0 ~ 255 in decimal notation (Range of
nnn when the IP address is nnn.nnn.nnn.nnn). The IP address of the BV1250 is also returned.
GET)
and
P1 - Input value entered in standard IP format which consists of numeric values separated by period
in the range of 0 ~ 255 in decimal notation (Range is nnn when the IP address is
nnn.nnn.nnn.nnn). The all 0 (zero) check of the subnet mask is not performed.
Output values for current (ACT) and new (SBY) parameters displayed in standard IP format which
consists of numeric values separated by period in the range of 0 ~ 255 in decimal notation (Range of
nnn when the IP address is nnn.nnn.nnn.nnn). The IP address of the BV1250 is also returned.
Returns parameter description summary for the command specified as an input parameter. If no input
parameter specified, displays list of command names.
RS-232C and LAN
ERRORS
No. 0101:
Cause -Help for specified command cannot not be found
Remedy - Correct command name and retry
Page 56 Revision 1.0
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.