Digi 55M1644B WR44v2 Wireless Router User Manual Manual pt 2

Download:
Mirror Download [FCC.gov]
Document ID	1821846
Application ID	DNB/yoef1Q4sBKKaf80Hug==
Document Description	Manual pt 2
Short Term Confidential	No
Permanent Confidential	No
Supercede	No
Document Type	User Manual
Display Format	Adobe Acrobat PDF - pdf
Filesize	124.67kB (1558349 bits)
Date Submitted	2012-10-24 00:00:00
Date Available	2012-10-24 00:00:00
Creation Date	2012-10-23 10:32:32
Producing Software	iText 2.1.7 by 1T3XT
Document Lastmod	2012-10-23 10:32:32
Document Title	Manual pt 2
Document Creator	pdfsam-console (Ver. 2.4.0e)

534
535
IR2140
536
537
538
IR2420
539
540
541
TA2020B & IR2110B
542
543
544
DR4410, DR4410i & DR4410p
545
546
547
MW3410, MW3520 & VC5100
548
549
550
ER4420, ER4420d, ER4420i, ER4420p, HR4420, HR4420d, HR4420i,
HR4420p & IR4420
551
552
553
MR4110, ER4110, HR4110, GR4110 & TR4110
554
555
556
RS-232 (V.24) Serial Cable Wiring
557
558
559
Configuring X.21 on Older Models
Some older Sarian legacy units require an X.21 daughter card to be fitted to enable X.21
operation. There are two versions of the X.21 daughter card. One version is compatible with
GR2130, IR2140 and IR2420 routers, and one version is compatible with MW3520, MW3410
and VC5100 routers.
The X.21 daughter card compatible with GR2130, IR2140 and IR2420 routers has three
internal jumpers that determine the clock mode. By default, these are set so that the unit
acts as a clock sink. For correct X.21 operation the jumper settings must match the setting
of the Clock source parameter configured on the Configuration - Network > Interfaces >
Serial > Serial Port 0 > Sync Port 0 pages. To change this you will need to open the unit by
removing the four rubber feet and fixing screws. Having done this, carefully remove the
case lid and locate the X.21 adapter card (illustrated below):
The correct settings for clock source or clock sink operation for the X.21 daughter card
compatible with GR2130, IR2140 and IR2420 routers are shown below:
Having set the links correctly, reassemble the case ensuring that the lid is correctly
oriented.
560
EMAIL TEMPLATES
One of the principal features provided by the event log function is the ability to configure
the unit to automatically generate and send an email alert message each time an event of
up to a specified priority occurs. The format of the message is determined by the email
template specified in the Use email template file parameter (normally EVENT.EML) in the
Configuration - Alarms > Event Settings > Email Notifications web page.
If the standard EVENT.EML template supplied with the unit is not suitable, you may create
your own template. An email template is simply a text file that defines the appearance and
content of the email messages generated by the event logger.
Template Structure
An email template consists of a header section followed by a body section. One or more
blank lines separate the two sections.
The Header Section
The header section MUST contain the following three fields:
TO:
This field is used to specify at least one recipient’s email address. Multiple addresses may be
included and must be separated by a space, comma or semicolon character. For example:
To: 123@456.com, 456@123.com; abc.def.com
FROM:
This field is normally used to supply the email address of the sending unit but alternatively
you may enter a simple string. This may depend on the SMTP server as to what is accepted.
For example:
FROM: WR44
Or
FROM: wr44@mycompany.com
SUBJECT:
This field should contain a string describing the subject of the email message. For example:
Subject: Automated message from router
Other Fields
In addition to the mandatory fields described above, the header section of an email may
also contain one or more optional fields. Many such fields are defined in the relevant RFCs
but there are some fields that the unit handles a little differently as described below. The
unit will insert other fields as necessary if it is required to send attachments with the email
Reply To:
If the unit discovers that this field is not present in the email template, the unit will insert
this field into the header. The string used for this field is that configured by the smtp 0
reply_to CLI command (or the use "Reply To" address parameter in the Configuration Alarms > SMTP Account web page). This allows for different reply addresses, and allows
a simple way of using the same (easily configurable) reply address for all emails.
Date:
561
If this field is present in the header, the unit will insert the current date and time into the
header. The date and time are values local to the unit and do not contain any time zone
information.
Body Section
The body section may include any text. This text is parsed for any function calls that may be
present. Function calls must be enclosed between “<%” and “%>”. These sequences are
substituted by text resulting from the function call. The following functions may be used:
Function
Description
TimeSmtp();
Inserts the unit’s date and time.
serial_number();
Inserts the unit’s serial number
Smtpip();
Inserts the IP address of the unit as seen by the SMTP server
during transmission
email_event()
Inserts a formatted description of the event that caused the
email transmission.
Smtpid()
Inserts the unit ID for this device as configured by the “Router
Identity” field in the Configuration - System > Device Identity
web page, or the cmd 0 unitid CLI command.
pppip(“instance”);
Inserts the IP address for a specific PPP instance, where
instance is the PPP instance number.
The following are examples of email templates.
1)
TO: 123@abc.co.nz
FROM: MyRouter
SUBJECT: Remote Configuration
 This blank line is required
Time: <%timeSmtp();%>
Serial Number: <%serial_number();%>
Req: CFG_RQ
IP Address: <%smtpip();%>
PPP 1 IP address: <%pppip("1");%>
2)
TO: fred@anyco.com, jane@anyco.co.uk
FROM: MyRouter
SUBJECT: automatic email
MIME-Version: 1.0
 This blank line is required
Unit: <%smtpid();%>
Event: <%email_event();%>
This event had sufficient priority to cause the transmission of this
email. Please check the attached logs and review.
CLI commands can also be executed and the output from up to 10 CLI commands will be
added to the body of the email. The command to be executed needs to be entered in place
of xxxxx below. To include the output from multiple commands, use the run_cmd() function
multiple times.
<%run_cmd("xxxxx");%>
562
e.g.
<%run_cmd("ati5");%>
<%run_cmd("bufs");%>
<%run_cmd("msgs");%>
An example template adding CLI commands would be:
TO: fred@anyco.com, jane@anyco.co.uk
FROM: MyRouter
SUBJECT: automatic email
MIME-Version: 1.0
Unit: <%smtpid();%>
Event: <%email_event();%>
This event had sufficient priority to cause the transmission of this
email. Please check the attached logs and review.
<%run_cmd("ati5");%>
<%run_cmd("bufs");%>
<%run_cmd("msgs");%>
It is also possible to specify an extra parameter which indicates the required priority of the
event before the command is executed. This allows events to be sent off without
attachments, but if the event has an equal or higher priority than the value of this
parameter, the attachments will be included. This ensures that the attachments are not
included unnecessarily with non-critical events and using up all the data allowance on a
wireless connection.
<%run_cmd("chkst","5");%>
An example template adding CLI commands with priority values would be:
TO: fred@anyco.com, jane@anyco.co.uk
FROM: MyRouter
SUBJECT: automatic email
MIME-Version: 1.0
Unit: <%smtpid();%>
Event: <%email_event();%>
This event had sufficient priority to cause the transmission of this
email. Please check the attached logs and review.
<%run_cmd("chkst","5");%>
In the example above, the command chkst will only be executed when an event with a
priority equal to or higher than 5 is detected.
563
Certifications
FCC Part 68 Declarations (for Transport DR models only)
This equipment complies with Part 68 of the FCC rules and the requirements adopted by the
ACTA. On the underside of this equipment is a label that contains, among other information,
a product identifier in the format US:AAAEQ##TXXXX. If requested, this number must be
provided to the telephone company.
Universal Service Order Codes
RJ11C
A plug and jack used to connect this equipment to the premises wiring and telephone
network must comply with the applicable FCC Part 68 rules and requirements adopted by
the ACTA. A compliant telephone cord and modular plug is provided with this product. It is
designed to be connected to a compatible modular jack that is also compliant. See
installation instructions for details.
Telephone Company Compliance
If the Transport DR, causes harm to the telephone network, the telephone company will
notify you in advance that temporary discontinuance of service may be required. But if
advance notice isn't practical, the telephone company will notify the customer as soon as
possible. Also, you will be advised of your right to file a complaint with the FCC if you
believe it is necessary.
The telephone company may make changes in its facilities, equipment, operations or
procedures that could affect the operation of the equipment. If this happens the telephone
company will provide advance notice in order for you to make necessary modifications to
maintain uninterrupted service. If trouble is experienced with the Transport DR, for repair or
warranty information, please contact Digi International at 877-912-3444. If the equipment
is causing harm to the telephone network, the telephone company may request that you
disconnect the equipment until the problem is resolved.
Connection to party line service is subject to state tariffs. Contact the state public utility
commission, public service commission or corporation commission for information.
The REN is used to determine the number of devices that may be connected to a telephone
line. Excessive RENs on a telephone line may result in the devices not ringing in response to
an incoming call. In most, but not all areas, the sum of RENs should not exceed five (5.0).
To be certain of the number of devices that may be connected to a line, as determined by
the total RENs, contact the local telephone company. For products approved after July 23,
2001, the REN for this product is noted in the part of the product identifier that has the
format US:AAAEQ##TXXXX. The digits represented by the ## are the REN without a
decimal point (e.g., 03 is a REN of 0.3). For early products, the REN is shown separately on
the label.
Home Security Advisory
If your home has specially wired alarm equipment connected to the telephone line, ensure
the installation of this Transport DR does not disable your alarm equipment. If you have
questions about what will disable alarm equipment, consult your telephone company or a
qualified installer.
564
OEM Advisory
For OEM use, the mounting of the Transport DR in the final assembly must be made so that
the Transport DR is isolated from exposure to any hazardous voltages within the assembly.
Adequate separation and restraint of cables and cords must be provided. The circuitry from
the Transport DR to the telephone line must be provided in wiring that carries no other
circuitry (such as PC or PR leads) unless specifically allowed by the rules. PC board traces
carrying tip and ring leads shall have sufficient spacing to avoid surge breakdown.
Electrical Safety Advisory
Digi International suggests that customers use a surge arrestor. Telephone companies
report that electrical surges, typically lightning transients, are very destructive to customer
terminal equipment connected to AC power sources. This has been identified as a major
nationwide problem.
565
GLOSSARY
0-9
3DES
Triple Data Encryption Standard
ACCM
Asynchronous Communication Channel Multiplexer
ACFC
Address Control Field Compression
ADSL
Asymmetric Digital Subscriber Line
AES
Advanced Encryption Standard
AFE
Analogue Front End
AH
Authentication Header
AIS
Alarm Indication Signal
AODI
Always On Dynamic ISDN
APACS
Association of Payment Clearing Services, the UK payments association
APN
Access Point Name
ATM
Asynchronous Transfer Mode or Automatic Teller Machine
ARFCN
Absolute Radio Frequency Channel Number
BACP
Bandwidth Allocation and Control Protocol
BAP
Bandwidth Allocation Protocol
BCC
Base station Colour Code
BCCH
Broadcast Control Channel
BGP
Border Gateway Protocol
CA
Certificate Authority
CHAP
Challenge Handshake Authentication Protocol
CLI
Calling Line Identification or Command Line Interface
CRC
Cyclic Redundancy Code
CTS
Clear To Send
CUD
Call User Data
CUG
Call User Group
DCE
Data Communication Equipment
DER
Distinguished Encoding Rules
DES
Data Encryption Standard
566
DHCP
Dynamic Host Configuration Protocol
DLSw
Data-Link Switching
DNS
Domain Name Server
DPD
Dead Peer Detection
DSCP
Differentiated Services Code Point
DSL
Digital Subscriber Line
DTE
Data Terminal Equipment
DUN
Dial-Up Networking
EDGE
Enhanced Data GSM Environment
ESP
Encapsulating Security Payload protocol
FCS
Frame Check Sequence
FEC
Forward Error Correction
FIFO
First In First Out
FQDN
Fully Qualified Domain Name
FTP
File Transfer Protocol
GPRS
General Packet Radio System
GPS
Global Positioning System
GRE
Generic Routing Encapsulation
GSM
Global System for Mobile Communications
HDLC
High-Level Data Link Control
HEC
Header Error Control
HMAC
Hash Message Authentication Code
HSDPA
High Speed Downlink Packet Access
HSUPA
High Speed Uplink Packet Access
ICMP
Internet Control Message Protocol
IETF
Internet Engineering Task Force
IGMP
Internet Group Management Protocol
IGP
Interior Gateway Protocol
IKE
Internet Key Exchange
IMEI
International Mobile Equipment Identification
567
IMSI
International Mobile Subscriber Identity
IP
Internet Protocol
IPCP
Internet Protocol Control Protocol
IPSec
Internet Protocol Security
ISAKMP
Internet Security Association and Key Management Protocol
ISDN
Integrated Services Digital Network
L2TP
Layer 2 Tunnelling Protocol
LAC
Location Area Code
LAI
Location Area Identity
LAN
Local Area Network
LAPB
Link Access Procedure Balanced
LAPD
Link Access Protocol D-channel
LCN
Logical Channel Number
LCP
Link Control Protocol
LRC
Longitudinal Redundancy Check
LSA
Link State Advertisement
MAC
Media Access Control
MCC
Mobile Country Code
MD5
Message-Digest algorithm 5
MIB
Management Information Base
MIME
Multipurpose Internet Mail Extensions
MLPPP
Multi-Link Point-to-Point Protocol
MNC
Mobile Network Code
MPPE
Microsoft Point to Point Encryption
MRU
Maximum Receive Unit
MSN
Multiple Subscriber Number
MSS
Maximum Segment Size
MTU
Maximum Transmit Unit
NAPT
Network Address and Port Translation
NAS
Network Access Server
NAT
Network Address Translation
NCC
Network Colour Code
568
NOM
Network Operation Mode
NUA
Network User Address
NUI
Network User Identifier
OAM
Operation, Administration and Maintenance
OOS
Out Of Service
OPNS
Online PUK Negotiation Service
OSPF
Open Shortest Path First
PANS
Polling Answering Service
PAD
Packet Assembler/Disassembler
PAP
Password Authentication Protocol
PAT
Priority Access Threshold
PBCCH
Packet Broadcast Control Channel
PEM
Privacy Enhanced MIME
PFC
Protocol Field Compression
PFS
Perfect Forwarding Security
PID
Protocol Identifier
PIN
Personal Identity Number
PLMN
Public Land Mobile Network
PPP
Point-to-Point Protocol
PPPoA
Point-to-Point Protocol over ATM
PPPoE
Point-to-Point Protocol over Ethernet
PSDN
Packet Switched Data Network
PSI
Packet System Information
PSTN
Public Switched Telephone Network
PUK
Power Up Key
PVC
Permanent Virtual Circuit
QOS
Quality of Service
569
R
RAC
Routing Area Code
RACH
Random Access Channel
RADIUS
Remote Authentication Dial-In User Service
RAT
Radio Access Technology
RDI
Remote Defect Indication
RIP
Routing Information Protocol
RSSI
Received Signal Strength Indication
RTS
Request To Send
SA
Security Association
SABM
Set Asynchronous Balanced Mode
SABME
Set Asynchronous Balanced Mode Extended
SCEP
Simple Certificate Enrolment Protocol
SDLC
Synchronous Data Link Control
SHA-1
Secure Hash Algorithm 1
SMS
Short Message Service
SMTP
Simple Mail Transfer Protocol
SNA
Systems Network Architecture
SNAIP
Systems Network Architecture over Internet Protocol
SNMP
Simple Network Management Protocol
SNTP
Simple Network Time Protocol
SPF
Shortest Path First
SPI
Security Parameters Index
SSH
Secure Shell
SSL
Secure Socket Layer
SVC
Switched Virtual Circuit
TANS
TPAD Answering
TCH
Traffic Channel
TCP
Transmission Control Protocol
TEI
Terminal Endpoint Identifier
TOS
Type of Service
TPAD
Transaction Packet Assembler/Disassembler
570
U
UBR
Unspecified Bit Rate
UDP
User Datagram Protocol
UMTS
Universal Mobile Telecommunications System
USB
Universal Serial Bus
VLAN
Virtual Local Area Network
VPN
Virtual Private Network
VRRP
Virtual Router Redundancy Protocol
WAN
Wide Area Network
WCDMA
Wide-band Code-Division Multiple Access
WRED
Weighted Random Early Dropping
W-WAN
Wireless Wide Area Network
XOT
X.25 Over TCP
571
ACKNOWLEDGEMENTS
Copyright Digi International Limited 1999-2011, all rights reserved.
In addition we would like to thank all those who have contributed to open software which
has done so much to improve and expand knowledge of IP protocols and the Internet
generally.
Notably software in this product contains portions of code from the OpenBSD project under
the following copyrights:
Copyright (c) 2003, 2004 Henning Brauer 
Copyright (c) 2004 Esben Norby 
Copyright (c) 2001 Markus Friedl. All rights reserved.
Copyright (c) 2001 Daniel Hartmeier. All rights reserved.
Copyright (c) 2001 Theo de Raadt. All rights reserved.
Copyright (c) 2001 Tobias Weingartner
This product also includes cryptographic software written by
Eric Young (eay@cryptsoft.com) copyright (C) 1995-1997 Eric Young (eay@cryptsoft.com)
Web Interface
Copyright (c) Go Ahead Software Inc., 1995-1999. All Rights Reserved.
Zlib compression library
Copyright (C) 1995-1998 Jean-loup Gailly and Mark Adler
Digi TransPort 6000 Series Routers
Portions Copyright Centillium Communications, Inc. 2003
Sarian Systems / Digi TransPort 3000 and 5000 series routers
Portions Copyright 2000-2002 Intel Corporation All Rights Reserved
Sarian Systems / Digi TransPort 4000 series Routers
Portions copyright (c) 2001,2002,2003,2004 Cirrus Logic, Inc.
All 2000, 3000, 4000 and 5000 series units:
Portions Copyright © ARM Limited 1998, 1999. All rights reserved.
Portions of this code:
Copyright (c) 1998, 1999 Niels Provos.
(c) 1999 Angelos D. Keromytis. All rights reserved.
Copyright (c) 2000, 2001 Niklas Hallqvist. All rights reserved.
In addition we would like to thank Peter Verhas for his outstanding work on the ScriptBasic
Interpreter, a SarOS Ported version together with libraries for many telemetry devices can
be provided free with any suitable Sarian Systems / Digi TransPort product. Several files in
this release of ScriptBasic are available under the GNU LPGL and full terms together with
source and linkable libraries are available on request.
572

---

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.5
Linearized                      : No
Page Count                      : 39
Creator                         : pdfsam-console (Ver. 2.4.0e)
Producer                        : iText 2.1.7 by 1T3XT
Modify Date                     : 2012:10:23 10:32:32+01:00
Create Date                     : 2012:10:23 10:32:32+01:00

EXIF Metadata provided by EXIF.tools