VoIP Interfaces

Junos OS
VoIP Interfaces
Release
12.1
Published: 2012-08-30
Copyright 2012, Juniper Networks, Inc.
Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net This product includes the Envoy SNMP Engine, developed by Epilogue Technology, an Integrated Systems Company. Copyright 1986-1997, Epilogue Technology Corporation. All rights reserved. This program and its documentation were developed at private expense, and no part of them is in the public domain. This product includes memory allocation software developed by Mark Moraes, copyright 1988, 1989, 1993, University of Toronto. This product includes FreeBSD software developed by the University of California, Berkeley, and its contributors. All of the documentation and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by the Regents of the University of California. Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994. The Regents of the University of California. All rights reserved. GateD software copyright 1995, the Regents of the University. All rights reserved. Gate Daemon was originated and developed through release 3.0 by Cornell University and its collaborators. Gated is based on Kirtons EGP, UC Berkeleys routing daemon (routed), and DCNs HELLO routing protocol. Development of Gated has been supported in part by the National Science Foundation. Portions of the GateD software copyright 1988, Regents of the University of California. All rights reserved. Portions of the GateD software copyright 1991, D. L. S. Associates. This product includes software developed by Maker Communications, Inc., copyright 1996, 1997, Maker Communications, Inc. Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Junos OS VoIP Interfaces 12.1 Copyright 2012, Juniper Networks, Inc. All rights reserved. The information in this document is current as of the date on the title page. YEAR 2000 NOTICE Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT

The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement (EULA) posted at
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions
of that EULA.
ii
Table of Contents
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Using the Examples in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Merging a Full Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Merging a Snippet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Part 1
Chapter 1
Overview
Supported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Voice over Internet Protocol with Avaya . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 2
Avaya VoIP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Avaya VoIP Modules Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Supported Avaya VoIP Modules and Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Avaya VoIP Modules Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 J2320 and J2350 Avaya VoIP Module Summary . . . . . . . . . . . . . . . . . . . . . 7 J4350 and J6350 Avaya VoIP Module Summary . . . . . . . . . . . . . . . . . . . . 8
Chapter 3
Avaya IG550 Integrated Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Avaya IG550 Integrated Gateway Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Media Gateway Controller Server Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Avaya Communication Manager Software Overview . . . . . . . . . . . . . . . . . . . . . . . 14 Dynamic Call Admission Control Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Dynamic CAC Interface Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Supported Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Bearer Bandwidth Limit and Activation Priority . . . . . . . . . . . . . . . . . . . . 15 Rules for Determining Reported BBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 4
TGM550 Telephony Gateway Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Understanding the TGM550 Telephony Gateway Module . . . . . . . . . . . . . . . . . . . 17 TGM550 Guidelines and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 TGM550 Firmware Compatibility with Junos OS . . . . . . . . . . . . . . . . . . . 18 TGM550 IP Addressing Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
iii
VoIP Interfaces
TGM550 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 TGM550 Access Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 TGM550 Console Port Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 TGM550 RJ-11 Connector Pinout for Analog Ports . . . . . . . . . . . . . . . . . . . . . . . . . 22 TGM550 Maximum Media Gateway Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 TGM550 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 5
TIM508 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Understanding the TIM508 Analog Telephony Interface Module . . . . . . . . . . . . . 27 TIM508 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 TIM508 Possible Port Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 TIM508 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Chapter 6
TIM510 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Understanding the TIM510 E1/T1 Telephony Interface Module . . . . . . . . . . . . . . . . 31 TIM510 RJ-45 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 TIM510 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 7

Understanding the TIM514 Analog Telephony Interface Module . . . . . . . . . . . . . . 35 TIM514 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 TIM514 Possible Port Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 TIM514 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 8

Understanding the TIM516 Analog Telephony Interface Module . . . . . . . . . . . . . . 39 TIM516 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 TIM516 Possible Port Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 TIM516 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Chapter 9

Understanding the TIM518 Analog Telephony Interface Module . . . . . . . . . . . . . . 45 TIM518 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 TIM518 Possible Port Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 TIM518 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Chapter 10
TIM521 BRI Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Understanding the TIM521 BRI Telephony Interface Module . . . . . . . . . . . . . . . . . 51 TIM521 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Part 2
Chapter 11
Configuration
Avaya VoIP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Avaya VoIP Modules Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Configuring VoIP Interfaces with EPW and Disk-on-Key . . . . . . . . . . . . . . . . . . . . 56 Example: Configuring VoIP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Chapter 12
Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Interfaces Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 activation-priority (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 bearer-bandwidth-limit (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 dynamic-call-admission-control (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
iv
Table of Contents
family bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Part 3
Chapter 13
Administration
TGM550 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Connecting Through the TGM550 Module Console Port . . . . . . . . . . . . . . . . . . . . 87 Connecting to the TGM550 with SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 TGM550 Module with Telnet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Enabling Telnet Service on the TGM550 Module . . . . . . . . . . . . . . . . . . . . . . 89 Connecting to the TGM550 Module with Telnet . . . . . . . . . . . . . . . . . . . . . . . 89 Disabling Telnet Service on the TGM550 Module . . . . . . . . . . . . . . . . . . . . . . 89 Accessing the Services Router from the TGM550 Module . . . . . . . . . . . . . . . . . . 90 Resetting the TGM550 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Saving the TGM550 Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Chapter 14
Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
restart (Reset) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 show chassis hardware (View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 show interfaces (View J Series and SRX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . 101 show interfaces flow-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 show interfaces statistics (View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Part 4
Chapter 15
Troubleshooting
TGM550 Module Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
TGM550 Module and VoIP Interface Troubleshooting . . . . . . . . . . . . . . . . . . . . . . 115
Part 5
Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
VoIP Interfaces
vi
List of Figures
Part 1
Chapter 2
Overview
Figure 1: Typical VoIP Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 4

Figure 2: TGM550 Telephony Gateway Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 5

Figure 3: TIM508 Analog Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . 27
Chapter 6

Figure 4: TIM510 E1/T1 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 7

Chapter 8

Chapter 9

Chapter 10

Figure 8: TIM521 BRI Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . 51
vii
VoIP Interfaces
viii
List of Tables
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Part 1
Chapter 1
Overview
Supported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Table 3: VoIP with Avaya Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 2

Table 4: J2320 and J2350 Avaya VoIP Module Summary . . . . . . . . . . . . . . . . . . . . . 8 Table 5: J4350 and J6350 Avaya VoIP Module Summary . . . . . . . . . . . . . . . . . . . . 9
Chapter 3
Avaya IG550 Integrated Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Table 6: Interfaces on Avaya VoIP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 4

Table 7: TGM550 RJ-45 Console Connector Pinouts . . . . . . . . . . . . . . . . . . . . . . . . 21 Table 8: TGM550 RJ-11 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Table 9: TGM550 Maximum Media Gateway Capacities . . . . . . . . . . . . . . . . . . . . 23 Table 10: LEDs for TGM550 Gateway Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 5

Table 11: TIM508 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Table 12: TIM508 Possible Port Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Table 13: LEDs for TIM508 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Chapter 6

Table 14: TIM510 RJ-45 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Table 15: LEDs for TIM510 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 7

Table 16: TIM514 RJ-11 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Table 17: TIM514 Possible Port Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Table 18: LEDs for TIM514 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 8

Table 19: TIM516 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Table 20: TIM516 Possible Port Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Table 21: LEDs for TIM516 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Chapter 9

Table 22: TIM518 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Table 23: TIM518 Possible Port Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
ix
VoIP Interfaces
Table 24: LEDs for TIM518 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Chapter 10

Table 25: LEDs for TIM521 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Part 3
Chapter 14
Administration
Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Table 26: show chassis hardware Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Table 27: show interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Table 28: show interfaces flow-statistics Output Fields . . . . . . . . . . . . . . . . . . . . 107 Table 29: Flow Error Statistics (packet drop statistics for the flow module) . . . . 108
About the Documentation

Documentation and Release Notes on page xi Supported Platforms on page xi Using the Examples in This Manual on page xi Documentation Conventions on page xiii Documentation Feedback on page xv Requesting Technical Support on page xv
Documentation and Release Notes

To obtain the most current version of all Juniper Networks technical documentation, see the product documentation page on the Juniper Networks website at http://www.juniper.net/techpubs/. If the information in the latest release notes differs from the information in the documentation, follow the product Release Notes. Juniper Networks Books publishes books by Juniper Networks engineers and subject matter experts. These books go beyond the technical documentation to explore the nuances of network architecture, deployment, and administration. The current list can be viewed at http://www.juniper.net/books .
Supported Platforms
For the features described in this document, the following platforms are supported:
J Series
Using the Examples in This Manual

If you want to use the examples in this manual, you can use the load merge or the load merge relative command. These commands cause the software to merge the incoming configuration into the current candidate configuration. The example does not become active until you commit the candidate configuration. If the example configuration contains the top level of the hierarchy (or multiple hierarchies), the example is a full example. In this case, use the load merge command.
xi
VoIP Interfaces
If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In this case, use the load merge relative command. These procedures are described in the following sections.
Merging a Full Example

To merge a full example, follow these steps:
1.
From the HTML or PDF version of the manual, copy a configuration example into a text file, save the file with a name, and copy the file to a directory on your routing platform. For example, copy the following configuration to a file and name the file ex-script.conf. Copy the ex-script.conf file to the /var/tmp directory on your routing platform.
system { scripts { commit { file ex-script.xsl; } } } interfaces { fxp0 { disable; unit 0 { family inet { address 10.0.0.1/24; } } } }
2. Merge the contents of the file into your routing platform configuration by issuing the
load merge configuration mode command: [edit] user@host# load merge /var/tmp/ex-script.conf load complete
Merging a Snippet
To merge a snippet, follow these steps:
1.
From the HTML or PDF version of the manual, copy a configuration snippet into a text file, save the file with a name, and copy the file to a directory on your routing platform. For example, copy the following snippet to a file and name the file ex-script-snippet.conf. Copy the ex-script-snippet.conf file to the /var/tmp directory on your routing platform.
commit { file ex-script-snippet.xsl; }
2. Move to the hierarchy level that is relevant for this snippet by issuing the following
configuration mode command:
xii
[edit] user@host# edit system scripts [edit system scripts]

3. Merge the contents of the file into your routing platform configuration by issuing the
load merge relative configuration mode command: [edit system scripts] user@host# load merge relative /var/tmp/ex-script-snippet.conf load complete
For more information about the load command, see the Junos OS CLI User Guide.
Documentation Conventions
Table 1 on page xiii defines notice icons used in this guide.
Table 1: Notice Icons

Icon Meaning
Informational note
Description
Indicates important features or instructions.
Caution
Indicates a situation that might result in loss of data or hardware damage.
Warning
Alerts you to the risk of personal injury or death.
Laser warning
Alerts you to the risk of personal injury from a laser.
Table 2 on page xiii defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions

Convention
Bold text like this
Description
Represents text that you type.
Examples
To enter configuration mode, type theconfigure command: user@host> configure
Fixed-width text like this
Represents output that appears on the terminal screen.
user@host> show chassis alarms No alarms currently active
xiii
VoIP Interfaces
Table 2: Text and Syntax Conventions (continued)

Convention
Italic text like this
Description
Examples
Introduces or emphasizes important new terms. Identifies book names. Identifies RFC and Internet draft titles.
A policy term is a named structure that defines match conditions and actions. Junos OS System Basics Configuration Guide RFC 1997, BGP Communities Attribute
Italic text like this
Represents variables (options for which you substitute a value) in commands or configuration statements.
Configure the machines domain name: [edit] root@# set system domain-name domain-name
Text like this
Represents names of configuration statements, commands, files, and directories; configuration hierarchy levels; or labels on routing platform components. Enclose optional keywords or variables. Indicates a choice between the mutually exclusive keywords or variables on either side of the symbol. The set of choices is often enclosed in parentheses for clarity. Indicates a comment specified on the same line as the configuration statement to which it applies. Enclose a variable for which you can substitute one or more values. Identify a level in the configuration hierarchy. Identifies a leaf statement at a configuration hierarchy level.
To configure a stub area, include the stub statement at the[edit protocols ospf area area-id] hierarchy level. The console port is labeled CONSOLE.
< > (angle brackets) | (pipe symbol)
stub <default-metric metric>; broadcast | multicast (string1 | string2 | string3)
# (pound sign)
rsvp { # Required for dynamic MPLS only
[ ] (square brackets)
community name members [ community-ids ]
Indention and braces ( { } )
; (semicolon)
[edit] routing-options { static { route default { nexthop address; retain; } } }
J-Web GUI Conventions

Bold text like this Represents J-Web graphical user interface (GUI) items you click or select.
In the Logical Interfaces box, select All Interfaces. To cancel the configuration, click Cancel.
> (bold right angle bracket)
Separates levels in a hierarchy of J-Web selections.
In the configuration editor hierarchy, select Protocols>Ospf.
xiv
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation. You can send your comments to techpubs-comments@juniper.net, or fill out the documentation feedback form at https://www.juniper.net/cgi-bin/docbugreport/ . If you are using e-mail, be sure to include the following information with your comments:

Document or topic name URL or page number Software release version (if applicable)
Requesting Technical Support

Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC). If you are a customer with an active J-Care or JNASC support contract, or are covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC.
JTAC policiesFor a complete understanding of our JTAC procedures and policies, review the JTAC User Guide located at http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf . Product warrantiesFor product warranty information, visit http://www.juniper.net/support/warranty/ . JTAC hours of operationThe JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year.
Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features:

Find CSC offerings: http://www.juniper.net/customers/support/ Search for known bugs: http://www2.juniper.net/kb/ Find product documentation: http://www.juniper.net/techpubs/ Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/ Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
Search technical bulletins for relevant hardware and software notifications:

https://www.juniper.net/alerts/
xv
VoIP Interfaces
Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
Opening a Case with JTAC

You can open a case with JTAC on the Web or by telephone.

Use the Case Management tool in the CSC at http://www.juniper.net/cm/ . Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
For international or direct-dial options in countries without toll-free numbers, see http://www.juniper.net/support/requesting-support.html .
xvi
PART 1
Overview

Supported Features on page 3 Avaya VoIP Module on page 5 Avaya IG550 Integrated Gateway on page 11 TGM550 Telephony Gateway Module on page 17 TIM508 Telephony Interface Module on page 27 TIM510 Telephony Interface Module on page 31 TIM514 Telephony Interface Module on page 35 TIM516 Telephony Interface Module on page 39 TIM518 Telephony Interface Module on page 45 TIM521 BRI Telephony Interface Module on page 51
VoIP Interfaces
CHAPTER 1
Supported Features
Voice over Internet Protocol with Avaya on page 3
Voice over Internet Protocol with Avaya

J2320, J2350, J4350, and J6350 Services Routers support voice over IP (VoIP) connectivity for branch offices with the Avaya IG550 Integrated Gateway. The Avaya IG550 Integrated Gateway consists of four VoIP modulesa TGM550 Telephony Gateway Module and three types of Telephony Interface Modules (TIMs). Table 3 on page 3 lists the VoIP with Avaya features that are supported only on J Series devices.
Table 3: VoIP with Avaya Support

SRX100 SRX110 SRX210 SRX220 SRX240
No
Feature
Avaya Communication Manager
SRX550 SRX650
No

No
J Series
Yes
VoIP Interfaces
Table 3: VoIP with Avaya Support (continued)

No
Feature
Avaya VoIP Modules:
SRX550 SRX650
No

No
J Series
Yes
TGM550 Telephony Gateway Module TIM508 Analog Telephony Interface Module TIM510 E1/T1 Telephony Interface Module TIM514 Analog Telephony Interface Module TIM516 Analog Telephony Interface Module TIM518 Analog Telephony Interface Module TIM521 BRI Telephony Interface Module No No No Yes
Dynamic Call Admission Control Media Gateway Controller VoIP interfaces:
No
No
No
Yes
No
No
No
Yes
Analog telephone or trunk port E1 port ISDN BRI telephone or trunk port T1 port
Related Documentation
Junos OS Interfaces Configuration Guide for Security Devices
CHAPTER 2
Avaya VoIP Module

Avaya VoIP Modules Overview on page 5 Supported Avaya VoIP Modules and Interfaces on page 7
Avaya VoIP Modules Overview

J2320, J2350, J4350, and J6350 Services Routers support voice over IP (VoIP) connectivity for branch offices with the Avaya IG550 Integrated Gateway. The Avaya IG550 Integrated Gateway consists of four VoIP modulesa TGM550 Telephony Gateway Module and three types of Telephony Interface Modules (TIMs). The VoIP modules installed in a Services Router at a branch office connect the IP and analog telephones and trunk lines at the branch to headquarters and to the public-switched telephone network (PSTN). Figure 1 on page 6 shows a typical VoIP topology. The small branch office shown in the expanded illustration on the right is connected over the corporate WAN to the head office through a J6300 Services Router with VoIP modules installed. The Avaya Media Gateway Controller, S8700 Media Server, and integrated Management tools at the head office manage telephony services for headquarters and the branch offices on the WAN, connecting the corporation's legacy analog telephones, VoIP telephones, PCs, and fax machines to the PSTN.
VoIP Interfaces
Figure 1: Typical VoIP Topology
You must assign a local IP address to the vp-pim/0/0 interface on the Services Router and also a destination IP address to the TGM550 so that they can communicate with each other. The following rules apply for configuring the source IPv4 address:

You cannot specify more than one IPv4 address. Do not assign the following IPv4 addresses:

A broadcast address (255.255.255.255) A class E address (240.0.0.0 to 255.255.255.254) A loopback address (127.0.0.0 to 127.255.255.255) A multicast address (224.0.0.0 to 239.255.255.255) An address with 0 as the first byte or an address with 0 or 255 as the last byte
The VoIP interface needs a point-to-point connection to the TGM550. To configure the point-to-point connection, specify /32 as the subnet mask in the IPv4 address. The TGM550 uses the destination IP address to identify itself when communicating with other devices, particularly the Media Gateway Controller (MGC).
Chapter 2: Avaya VoIP Module
CAUTION: Applying a new or modified IP address resets the TGM550. For existing configurations, ensure that the TGM550 configuration is saved (see Saving the TGM550 Module Configuration on page 91) and that the TGM550 module is carrying no voice traffic.
To provide telephony services, the TGM550 must be registered with at least one Media Gateway Controller (MGC). You can configure the IP addresses of up to four MGCs that the TGM550 can connect to in the event of a link failure. In addition to configuring the MGC list from J-Web and the CLI, you can log in to the TGM550 and configure the list. Related Documentation

Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Configuration Overview on page 55 Supported Avaya VoIP Modules and Interfaces on page 7 Understanding the TGM550 Telephony Gateway Module on page 17 Understanding the TIM508 Analog Telephony Interface Module on page 27 Understanding the TIM510 E1/T1 Telephony Interface Module on page 31 Understanding the TIM514 Analog Telephony Interface Module on page 35 Understanding the TIM516 Analog Telephony Interface Module on page 39 Understanding the TIM518 Analog Telephony Interface Module on page 45 Understanding the TIM521 BRI Telephony Interface Module on page 51 Example: Configuring VoIP Interfaces on page 58
Supported Avaya VoIP Modules and Interfaces

J2320, J2350, J4350, and J6350 Services Routers support VoIP connectivity for branch offices with the Avaya IG550 Integrated Gateway.
Avaya VoIP Modules Summary

The following sections describe the supported Avaya VoIP modules and interfaces:

J2320 and J2350 Avaya VoIP Module Summary on page 7 J4350 and J6350 Avaya VoIP Module Summary on page 8
J2320 and J2350 Avaya VoIP Module Summary

Table 4 on page 8 provides the module names, slot and port numbers, maximum number allowed on a chassis, and sample interface names (where applicable) for the J2320 and J2350 Avaya VoIP modules.
VoIP Interfaces
Table 4: J2320 and J2350 Avaya VoIP Module Summary

Sample Interface Name PIM Name
TGM550 Telephony Gateway Module
Also Called

Slot and Port Numbering
Maximum Number on a Chassis

One (required) If more than one TGM550 is installed, only the one in the lowest numbered slot is enabled. For example, if TGM550s are installed in slots 2 and 3, only the one in slot 2 is enabled. One on J2320 Three on J2350
(type-pim/0/port)
vp-3/0/0
TGM550 Gateway Module TGM550
J2320Slots 1 through 3 J2350Slots 1 through 5
TIM508 Analog Telephony Interface Module
TIM508 media module TIM508
J2320Slots 1 through 3 J2350Slots 1 through 5 J2320Slots 1 through 3 J2350Slots 1 through 5 J2320Slots 1 through 3 J2350Slots 1 through 5 J2320Slots 1 through 3 J2350Slots 1 through 5 J2320Slots 1 through 3 J2350Slots 1 through 5 J2320Slots 1 through 3 J2350Slots 1 through 5
TIM510 E1/T1 Telephony Interface Module
TIM510 E1/T1 media module TIM510
Two
TIM514 analog media module TIM514
Two
One on J2320 Three on J2350
One on J2320 Three on J2350
TIM521 BRI Telephony Interface Module
TIM521 BRI media module TIM521
Two
J4350 and J6350 Avaya VoIP Module Summary

Table 5 on page 9 provides the module names, slot and port numbers, maximum number allowed on a chassis, and sample interface names (where applicable) for the J4350 and J6350 Avaya VoIP modules.
Table 5: J4350 and J6350 Avaya VoIP Module Summary

Sample Interface Name PIM Name
Also Called
Slot and Port Numbering

Slots 1 through 6
Maximum Number on a Chassis

One (required) If more than one TGM550 is installed, only the one in the lowest numbered slot is enabled. For example, if TGM550s are installed in slots 2 and 3, only the one in slot 2 is enabled.
(type-pim/0/port)
vp-3/0/0
TGM550 Gateway Module TGM550
TIM508 Analog Telephony Interface Module TIM510 E1/T1 Telephony Interface Module TIM514 Analog Telephony Interface Module TIM516 Analog Telephony Interface Module TIM518 Analog Telephony Interface Module TIM521 BRI Telephony Interface Module
TIM508 media module TIM508
Slots 1 through 6
Three
TIM510 E1/T1 media module TIM510
Slots 1 through 6
Two
Slots 1 through 6
Four
Slots 1 through 6
Three
Slots 1 through 6
Three
TIM521 BRI media module TIM521
Slots 1 through 6
Two
Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55
VoIP Interfaces
Understanding the TGM550 Telephony Gateway Module on page 17 Understanding the TIM508 Analog Telephony Interface Module on page 27 Understanding the TIM510 E1/T1 Telephony Interface Module on page 31 Understanding the TIM514 Analog Telephony Interface Module on page 35 Understanding the TIM516 Analog Telephony Interface Module on page 39 Understanding the TIM518 Analog Telephony Interface Module on page 45 Understanding the TIM521 BRI Telephony Interface Module on page 51 Example: Configuring VoIP Interfaces on page 58
10
CHAPTER 3
Avaya IG550 Integrated Gateway

Avaya IG550 Integrated Gateway Overview on page 11 Media Gateway Controller Server Overview on page 13 Avaya Communication Manager Software Overview on page 14 Dynamic Call Admission Control Overview on page 15
Avaya IG550 Integrated Gateway Overview

The Avaya IG550 Integrated Gateway consists of the TGM550 Telephony Gateway Module and one or more Telephony Interface Modules (TIMs) that are installed in the slots on the J4350 and J6350 Services Routers to provide VoIP connectivity. The TGM550 is an H.248 media gateway that works with the TIMs to connect IP and legacy analog telephones and trunks over IP networks and enable IP telephones to communicate through analog telephone lines and trunks. The TGM550 is also connected over a LAN or WAN to a Media Gateway Controller (MGC)an Avaya media server running Avaya Communication Manager (CM) call processing software. The telephony services on the TGM550 are managed by an MGC located at headquarters or in a branch office. When the primary MGC is located at a remote location, the TGM550 uses standard local survivability (SLS) for partial MGC backup in the event that the connection to the primary MGC is lost. Devices can thereby provide reliable telephony services to branch offices. Four types of VoIP interfaces on Avaya VoIP modules provide VoIP connectivity on J4350 and J6350 Services Routers:

Analog telephone or trunk port T1 port E1 port ISDN BRI telephone or trunk port
These interfaces are available on the field-replaceable Avaya VoIP modules listed in Table 6 on page 12.
11
VoIP Interfaces
Table 6: Interfaces on Avaya VoIP Modules

Junos OS Interface Module Name
TGM550
Description
Avaya Telephony Gateway Module (TGM). See Understanding the TGM550 Telephony Gateway Module on page 17. Avaya E1/T1 Telephony Interface Module (TIM). See Understanding the TIM510 E1/T1 Telephony Interface Module on page 31. Avaya Analog TIM. See Understanding the TIM514 Analog Telephony Interface Module on page 35. Avaya BRI TIM. See Understanding the TIM521 BRI Telephony Interface Module on page 51.
VoIP Interfaces

(type-pim/0/port)
vp-pim/0/0
Two analog telephone ports Two analog trunk ports One serial port for console access
On a VoIP interface, the port is always 0.
TIM510
One E1/T1 trunk port providing up to 30 E1 or 24 T1 channels
TIM514
Four analog telephone ports Four analog trunk ports
TIM521
Four ISDN BRI trunk ports providing up to eight channels
Only the TGM550 has a Junos OS interface. Because the TIMs do not have corresponding physical interfaces, you cannot configure or administer them with the J-Web interface or the Junos OS CLI. However, you can display TGM550 and TIM status from J-Web Monitor>Chassis pages and with the CLI show chassis command.
CAUTION: The TGM550 and TIMs are not hot-swappable. You must power off the router before installing or removing the Avaya VoIP modules. Ensure that the Avaya VoIP modules are installed in the router chassis before booting up the system.
Junos OS Feature Support Reference for SRX Series and J Series Devices Hardware Description and Reference for Avaya Communication Manager at
http://support.avaya.com
System Capacities Table for Avaya Communication Manager on Avaya Media Servers at
Administration Guide and CLI Reference for the Avaya IG550 Integrated Gateway at
Avaya VoIP Modules Overview on page 5 Media Gateway Controller Server Overview on page 13 Avaya Communication Manager Software Overview on page 14
12
Chapter 3: Avaya IG550 Integrated Gateway
Dynamic Call Admission Control Overview on page 15 Configuring VoIP Interfaces with EPW and Disk-on-Key on page 56 Example: Configuring VoIP Interfaces on page 58
Media Gateway Controller Server Overview

A Media Gateway Controller (MGC) is a media server (call controller) that controls telephone services on the TGM550. An Avaya media server running Avaya Communication Manager (CM) software acts as an MGC for the TGM550. The following media servers running Avaya Communication Manager can be used as an MGC with the TGM550:

Avaya S8300 Media ServerControls up to 49 TGM550s. Avaya S8400 Media ServerControls up to 5 TGM550s. Avaya S8500 Media ServerControls up to 250 TGM550s. Avaya S8700 Media ServerControls up to 250 TGM550s. Avaya S8710 Media ServerControls up to 250 TGM550s. Avaya S8720 Media ServerControls up to 250 TGM550s.
To provide telephony services, the TGM550 must be registered with at least one MGC. You can configure the IP addresses of up to four MGCs that the TGM550 can connect to in the event of a link failure. The MGC list consists of the IP addresses of the MGCs to connect to and the order in which to reestablish the H.248 link. The first MGC on the list is the primary MGC. The TGM550 searches for the primary MGC first. If it cannot connect to the primary MGC or loses its connection to the primary MGC, it attempts to connect to the next MGC in the list, and so on.
NOTE: The MGC list is stored in the TGM550. It is not written to the Junos OS configuration file.
You must also administer Avaya Communication Manager on the configured MGCs to support the TGM550. For more information, see the following Avaya IG550 Integrated Gateway manuals at http://support.avaya.com:

Installing and Configuring the Avaya IG550 Integrated Gateway Administration Guide and CLI Reference for the Avaya IG550 Integrated Gateway Administrator Guide for Avaya Communication Manager Avaya Maintenance Procedures for Communication Manager, Media Servers, and Media Gateways Avaya Maintenance Commands for Communication Manager, Media Servers, and Media Gateways
13
VoIP Interfaces
Avaya Maintenance Alarms for Communication Manager, Media Servers, and Media Gateways Hardware Description and Reference for Avaya Communication Manager System Capacities Table for Avaya Communication Manager on Avaya Media Servers Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Overview on page 5 Avaya IG550 Integrated Gateway Overview on page 11 Avaya Communication Manager Software Overview on page 14 Dynamic Call Admission Control Overview on page 15 Configuring VoIP Interfaces with EPW and Disk-on-Key on page 56
Avaya Communication Manager Software Overview

Avaya Communication Manager (CM) software manages the Media Gateway Controller (MGC). Avaya CM allows you to do the following:

Assign numbers to local telephones. Determine where to connect your telephone call based on the number you dial. Play dial tones, busy signals, and prerecorded voice announcements. Allow or prohibit access to outside lines for specific telephones. Assign telephone numbers and buttons to special features. Exchange call switching information with older telephone switches that do not support VoIP.
NOTE: The TGM550 supports Avaya Communication Manager (CM) release 4.0 and later releases. The TGM550 does not support Avaya Communication Manager (CM) releases earlier than release 4.0.
Junos OS Feature Support Reference for SRX Series and J Series Devices Administrator Guide for Avaya Communication Manager at http://support.avaya.com Avaya VoIP Modules Overview on page 5 Avaya IG550 Integrated Gateway Overview on page 11 Media Gateway Controller Server Overview on page 13 Dynamic Call Admission Control Overview on page 15 Configuring VoIP Interfaces with EPW and Disk-on-Key on page 56
14
Chapter 3: Avaya IG550 Integrated Gateway
Dynamic Call Admission Control Overview

Dynamic call admission control (CAC) enables the Media Gateway Controller (MGC) to automatically assign the bandwidth available for voice traffic on WAN interfaces and block new calls when the existing call bandwidth is completely engaged. You configure dynamic CAC on a high-bandwidth primary interface and on one or more backup interfaces with less bandwidth. Without dynamic CAC, the MGC cannot detect the switchover to the backup link or the resulting changes in network topology and available bandwidth. As a result, the MGC continues to admit calls at the bandwidth of the primary link, causing network congestion and possible jitter, delay, and loss of calls.
Dynamic CAC Interface Requirements

This topic contains the following sections:

Supported Interfaces on page 15 Bearer Bandwidth Limit and Activation Priority on page 15 Rules for Determining Reported BBL on page 16
Supported Interfaces
Dynamic CAC must be configured on each Services Router interface responsible for providing call bandwidth. You can configure dynamic CAC on the following types of interfaces on Services Routers:

ADSL E1 E3 Fast Ethernet Gigabit Ethernet GRE G.SHDSL ISDN BRI Serial interfaces T1 T3
Bearer Bandwidth Limit and Activation Priority

The dynamic CAC bearer bandwidth limit (BBL) configured on an interface specifies the maximum bandwidth available for voice traffic on the interface. The TGM550 reports the BBL to the MGC. When the call bandwidth exceeds the BBL, the MGC blocks new calls and alerts the user with a busy tone.
15
VoIP Interfaces
You configure the dynamic CAC activation priority value on interfaces to specify the order in which the interfaces are used for providing call bandwidth.
Rules for Determining Reported BBL

To assess the WAN interfaces that have an activation priority value and determine a single BBL to report to the MGC, the TGM550 uses the following rules. The reported BBL (RBBL) allows the MGC to automatically control the call bandwidth when interfaces responsible for providing call bandwidth become available or unavailable.
Report the BBL of the active interface with the highest activation priority. For example, if one interface has the activation priority of 200 and a BBL of 1500 Kbps and another interface has the activation priority of 100 and a BBL of 1000 Kbps, the RBBL is 1500 Kbps. If more than one active interface has the same activation priority, report a BBL that is the number of interfaces times their lowest BBL. For example, if two interfaces with the same activation priority have BBLs of 2000 Kbps and 1500 Kbps, the RBBL is 3000 Kbps (2 x 1500 Kbps). If the interface with the highest activation priority is unavailable, report the BBL of the active interface with the next highest activation priority. If all the interfaces on which dynamic CAC is configured are inactive, report a BBL of 0. The MGC does not allow calls to go through when the RBBL is 0.
NOTE: Dynamic CAC works in conjunction with the Avaya Communication Manager (CM) Call Admission Control: Bandwidth Limitation (CAC-BL) feature. If you configure dynamic CAC on WAN interfaces, you must also configure CAC-BL on Avaya CM.
Junos OS Feature Support Reference for SRX Series and J Series Devices Administrator Guide for Avaya Communication Manager at http://support.avaya.com Avaya VoIP Modules Overview on page 5 Avaya IG550 Integrated Gateway Overview on page 11 Media Gateway Controller Server Overview on page 13 Avaya Communication Manager Software Overview on page 14 Configuring VoIP Interfaces with EPW and Disk-on-Key on page 56
16
CHAPTER 4

Understanding the TGM550 Telephony Gateway Module on page 17 TGM550 Access Requirements on page 20 TGM550 Console Port Pinouts on page 21 TGM550 RJ-11 Connector Pinout for Analog Ports on page 22 TGM550 Maximum Media Gateway Capacities on page 23 TGM550 LEDs on page 25
Understanding the TGM550 Telephony Gateway Module

The TGM550 Telephony Gateway Module (Figure 2 on page 17), also known as the TGM550 Gateway Module, has two analog telephone ports, two analog trunk ports, and a serial console port. A TGM550 and one or more TIMs installed in a Services Router provide telephony exchange services to a branch office over IP networks. Different TIMs have access ports for different types of VoIP and analog telephones and telephone lines. You connect the telephones and lines to the ports on the TGM550 and the TIMs. VoIP telephones require connection to a Power over Ethernet (PoE) adapter or switch that is plugged into an Ethernet port on the Services Router. VoIP capabilities on the TGM550 enable the Services Router to provide VoIP services to telephones and trunks that do not directly support VoIP. The TGM550 translates voice and signaling data between VoIP and the system used by the telephones and trunks. TIMs convert the voice path of traditional circuits such as analog trunk and T1 or E1 to a TDM bus inside the router. The TGM550 then converts the voice path from the TDM bus to compressed or uncompressed and packetized VoIP on an Ethernet connection.
Figure 2: TGM550 Telephony Gateway Module
17
VoIP Interfaces
TGM550 Guidelines and Features

This topic contains the following sections:

TGM550 Firmware Compatibility with Junos OS on page 18 TGM550 IP Addressing Guidelines on page 18 TGM550 Features on page 19
TGM550 Firmware Compatibility with Junos OS

The TGM550 firmware version must be compatible with the Junos OS version installed on the device.
CAUTION: If the TGM550 firmware version is not compatible with the Junos OS version on the device, the device does not detect the VoIP interface (vp-pim/0/0) and the interface is unavailable. For more information, see TGM550 Module and VoIP Interface Troubleshooting on page 115.
If you are upgrading both the TGM550 firmware and the Junos OS on the router, first upgrade the TGM550 firmware, and then upgrade the Junos OS.
TGM550 IP Addressing Guidelines

For operational purposes, the TGM550 is identified as a host on the device. Hence, the TGM550 needs to be assigned an IP address that is reachable both externally and internally from the device. The TGM550 uses this IP address to identify itself when communicating with other devices, particularly the Media Gateway Controller (MGC). To assign the IP address for the TGM550, you configure the destination address on the vp-pim/0/0 interface.
CAUTION: Applying a new or modified IP address resets the TGM550. Before modifying the IP address, take the following precautions:
Log in to the TGM550 and enter copy running-config startup-config to save the TGM550 configuration. (For login instructions, see Saving the TGM550 Module Configuration on page 91.) Ensure that the TGM550 is not currently handling voice traffic.
To enable easier administration of the TGM550, we recommend the following guidelines for assigning the IP address of the TGM550:
Assign an address from one of the subnets that is already configured in the branch office where the device is installed. Decide on a block of IP addresses for VoIP services, and assign an IP address from that block to the TGM550.
18
Chapter 4: TGM550 Telephony Gateway Module
Do not assign the following IP addresses to the TGM550:

A broadcast address (255.255.255.255) A class E address (240.0.0.0 to 255.255.255.254) A loopback address (127.0.0.0 to 127.255.255.255) A multicast address (224.0.0.0 to 239.255.255.255) An address with 0 as the first byte or an address with 0 or 255 as the last byte
TGM550 Features
The TGM550 provides the following features:
Voice

VoIP Media Gateway services. Two analog telephone (LINE) ports to support two analog telephones or incoming analog direct inward dialing (DID) trunks with either wink start or immediate start. An analog relay supports emergency transfer relay (ETR). Two analog trunk (TRUNK) ports to support loop start, ground start, centralized automatic message accounting (CAMA), and direct inward and outward dialing (DIOD) trunks (for Japan only). Survivability features for continuous voice services. Call center capabilities.
Provisioning

Avaya Communication Manager (CM) media server management. Extensive alarm and troubleshooting features.
Survivability
Media Gateway Controller (MGC) automatic switchover, migration, and survivability features. Modem backup connection to the MGC. Dynamic call admission control (CAC) for WAN interfaces.
Management: One serial port for console access over an RJ-45 connector cable.
NOTE: The RJ-45 console cable and DB-9 adapter supplied with the TGM550 are different from those supplied with the Services Router. You cannot use the RJ-45 cable and DB-9 adapter supplied with the Services Router for console connections to the TGM550.
19
VoIP Interfaces
Communication Manager Software & Firmware Compatibility Matrix at

Administration Guide and CLI Reference for the Avaya IG550 Integrated Gateway at
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 TGM550 Access Requirements on page 20 TGM550 Console Port Pinouts on page 21 TGM550 RJ-11 Connector Pinout for Analog Ports on page 22 TGM550 Maximum Media Gateway Capacities on page 23 TGM550 LEDs on page 25 Example: Configuring VoIP Interfaces on page 58
TGM550 Access Requirements

The CLI on the TGM550 allows you to configure, monitor, and diagnose the TGM550 and TIMs installed in a Services Router. You can access the TGM550 from a management device attached to the TGM550 console port or by opening a Telnet or secure shell (SSH) session from the Junos OS CLI on the Services Router. You can also open a remote Telnet or SSH session directly to the TGM550 from a network location, or indirectly through the Junos OS CLI from a dial-up connection with a USB modem attached to the router. Administrators can use the root password to access the TGM550 initially, but all users need a TGM550 user account (username and password) set up by the network administrator for regular access to the module.
NOTE: You cannot use a Services Router user account to access the TGM550 CLI.
A console connection requires the Ethernet rollover cable and adapter provided with the TGM550. An SSH connection requires that the TGM550 have an IP address assigned.
20
A Telnet connection to the TGM550 requires that the module have an IP address and that Telnet service be enabled on the module. Junos OS Feature Support Reference for SRX Series and J Series Devices Administration Guide and CLI Reference for the Avaya IG550 Integrated Gateway at
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TGM550 Telephony Gateway Module on page 17 TGM550 Console Port Pinouts on page 21 TGM550 RJ-11 Connector Pinout for Analog Ports on page 22 TGM550 Maximum Media Gateway Capacities on page 23 TGM550 LEDs on page 25 Example: Configuring VoIP Interfaces on page 58
TGM550 Console Port Pinouts

The console port on a TGM550 Telephony Gateway Module has an RJ-45 connector. Table 7 on page 21 provides TGM550 RJ-45 console connector pinout information. An RJ-45 cable is supplied with the TGM550.
NOTE: Two different RJ-45 cables and RJ-45 to DB-9 adapters are provided. Do not use the RJ-45 cable and adapter for the Services Router console port to connect to the TGM550 console port.
To connect the console port to an external management device, you need an RJ-45 to DB-9 serial port adapter, which is also supplied with the TGM550.
Table 7: TGM550 RJ-45 Console Connector Pinouts

TGM550 RJ-45 Pin
1 2 3 4 5
Signal
For future use TXD (TGM550 input) RXD (TGM550 output) CD GND
Terminal DB-9 Pin

NC 3 2 4 5
21
VoIP Interfaces
Table 7: TGM550 RJ-45 Console Connector Pinouts (continued)

TGM550 RJ-45 Pin
6 7 8
Signal
DTR RTS CTS
Terminal DB-9 Pin

1 8 7
Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TGM550 Telephony Gateway Module on page 17 TGM550 Access Requirements on page 20 TGM550 RJ-11 Connector Pinout for Analog Ports on page 22 TGM550 Maximum Media Gateway Capacities on page 23 TGM550 LEDs on page 25 Example: Configuring VoIP Interfaces on page 58
TGM550 RJ-11 Connector Pinout for Analog Ports

The two analog telephone ports and two analog trunk ports on the TGM550 use an RJ-11 cable. Table 8 on page 22 describes the TGM550 RJ-11 connector pinout.
Table 8: TGM550 RJ-11 Connector Pinout

Pin
1 2 3 4 5 6
Signal
No connection No connection Ring Tip No connection No connection
Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Overview on page 5
22
Avaya VoIP Modules Configuration Overview on page 55 Understanding the TGM550 Telephony Gateway Module on page 17 TGM550 Access Requirements on page 20 TGM550 Console Port Pinouts on page 21 TGM550 Maximum Media Gateway Capacities on page 23 TGM550 LEDs on page 25 Example: Configuring VoIP Interfaces on page 58
TGM550 Maximum Media Gateway Capacities

Table 9 on page 23 lists the maximum number of media servers, telephones, and so on that are supported by the TGM550 installed on a J4350, J6350, J2320, or J2350 device.
Table 9: TGM550 Maximum Media Gateway Capacities

Hardware or Feature
TGM550s that can be controlled by an Avaya S8500 or S8700 Media Server
TGM550 Maximum Capacity

250
Additional Information
This number also applies if a combination of Avaya G700 Media Gateways, G250 Media Gateways, and G350 Media Gateways are controlled by the same media server. This number also applies if a combination of Avaya G700 Media Gateways, G250 Media Gateways, and G350 Media Gateways are controlled by the same media server. This capacity is 50 if a combination of Avaya G700 Media Gateways, G250 Media Gateways, and G350 Media Gateways are controlled by the same media server. The S8300 must reside in a G700 or G350 media gateway. Therefore, the maximum of 50 H.248 gateways supported by the S8300 means that only 49 of the 50 can be TGM550s.
TGM550s that can be controlled by an Avaya S8400 Media Server
TGM550s that can be controlled by an Avaya S8300 Media Server
49
Media servers that can be registered as Media Gateway Controllers (MGCs) on a TGM550
If an MGC becomes unavailable, the TGM550 uses the next MGC on the list. The built-in SLS module can be considered a fifth MGC, although its functionality is limited from that of a full-scale media server.
Fixed analog line ports Fixed analog trunk ports
2 2
23
VoIP Interfaces
Table 9: TGM550 Maximum Media Gateway Capacities (continued)

Hardware or Feature
Digital signal processors (DSPs)
TGM550 Maximum Capacity

1 (up to 80 channels)
Additional Information
For calls using voice codec sets with 20 ms or higher packet sizes, the DSP supports:

80 channels 20 channels 10 channels
For calls with 10 ms or lower packet sizes, the 80channel DSP supports 40 channels. For TTY, fax, or modem over IP calls, the 80channel DSP supports 40 channels. Busy hour call completion rate (BHCC) Total of IP and analog telephones that can be connected to a TGM550 and TIMs Touch-tone recognition (TTR) Tone generation 800
70 (J4350) 100 (J6350) 32 As much as necessary for all TDM calls. 16 playback channels for playing announcements, one of which can be used for recording. 20 minutes for G711-quality stored announcements and music-on-hold. 256 maximum announcements stored.
Maximum includes a combination of analog and IP telephones
Receivers
Announcements (VAL)
Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TGM550 Telephony Gateway Module on page 17 TGM550 Access Requirements on page 20 TGM550 Console Port Pinouts on page 21 TGM550 RJ-11 Connector Pinout for Analog Ports on page 22 TGM550 LEDs on page 25 Example: Configuring VoIP Interfaces on page 58
24
TGM550 LEDs
TGM550 LEDs indicate link status and activity. Table 10 on page 25 describes the meaning of the LEDs.
Table 10: LEDs for TGM550 Gateway Module

Label
ALM
Color
Red
State
On steadily
Description
Alarm. A failure in the TGM550 requires monitoring or maintenance. Active. The TGM550 is online with network traffic. Alternate software bank. The software is not running from the selected boot bank. Emergency transfer relay (ETR) feature is active.
ACT
Yellow
On steadily
ASB
Green
On steadily
ETR
Green
On steadily
Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TGM550 Telephony Gateway Module on page 17 TGM550 Access Requirements on page 20 TGM550 Console Port Pinouts on page 21 TGM550 RJ-11 Connector Pinout for Analog Ports on page 22 TGM550 Maximum Media Gateway Capacities on page 23 Example: Configuring VoIP Interfaces on page 58
25
VoIP Interfaces
26
CHAPTER 5
TIM508 Telephony Interface Module

Understanding the TIM508 Analog Telephony Interface Module on page 27 TIM508 Connector Pinout on page 28 TIM508 Possible Port Configurations on page 29 TIM508 LEDs on page 30
Understanding the TIM508 Analog Telephony Interface Module

The TIM508 Analog Telephony Interface Module (Figure 3 on page 27), also known as the TIM508 Analog Media Module, has eight analog telephone lines that can be used as trunk ports.
Figure 3: TIM508 Analog Telephony Interface Module
LINE
8 S 1
ALM ACT TIM 50 8
NOTE: All eight analog lines can be configured as analog direct inward dialing (DID) trunks.
The TIM508 provides the following features:
Three ringer loads, the ringer equivalency number for up to 2,000 ft (610 m), for all eight lines Up to eight simultaneously ringing lines Type 1 caller ID and Type 2 caller ID for lines Ring voltage generation for a variety of international frequencies and cadences
g003865
Analo
27
VoIP Interfaces
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 TIM508 Connector Pinout on page 28 TIM508 Possible Port Configurations on page 29 TIM508 LEDs on page 30 Example: Configuring VoIP Interfaces on page 58
TIM508 Connector Pinout

The TIM508 Analog Telephony Interface Module uses a B25A unshielded 25pair Amphenol cable. Table 11 on page 28 describes the TIM508 connector pinout.
Table 11: TIM508 Connector Pinout

Pin
1 2 3 4 5 6 7 8 26 27 28 29 30
Signal
Tip Tip Tip Tip Tip Tip Tip Tip R - Receive Ring Ring Ring Ring
28
Chapter 5: TIM508 Telephony Interface Module
Table 11: TIM508 Connector Pinout (continued)

Pin
31 32 33
Signal
Ring Ring Ring
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TIM508 Analog Telephony Interface Module on page 27 TIM508 Possible Port Configurations on page 29 TIM508 LEDs on page 30 Example: Configuring VoIP Interfaces on page 58
TIM508 Possible Port Configurations

You can configure TIM508 ports as described in Table 12 on page 29.
Table 12: TIM508 Possible Port Configurations

Possible Analog Telephone Line Configurations
Wink-start or immed-start DID trunk Analog tip/ring devices such as single-line telephones with or without LED message-waiting indication
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TIM508 Analog Telephony Interface Module on page 27
29
VoIP Interfaces
TIM508 Connector Pinout on page 28 TIM508 LEDs on page 30 Example: Configuring VoIP Interfaces on page 58
TIM508 LEDs
TIM508 LEDs indicate link status and activity. Table 13 on page 30 describes the meaning of the LEDs.
Table 13: LEDs for TIM508

Label
ALM
Color
Red
State
On steadily
Description
Alarm. A TIM508 failure requires monitoring or maintenance. Active. A device connected to the TIM508 is in use. This situation can include a telephone that is off the hook.
ACT
Yellow
Blinking
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TIM508 Analog Telephony Interface Module on page 27 TIM508 Connector Pinout on page 28 TIM508 Possible Port Configurations on page 29 Example: Configuring VoIP Interfaces on page 58
30
CHAPTER 6

Understanding the TIM510 E1/T1 Telephony Interface Module on page 31 TIM510 RJ-45 Connector Pinout on page 32 TIM510 LEDs on page 33
Understanding the TIM510 E1/T1 Telephony Interface Module

The TIM510 E1/T1 Telephony Interface Module (Figure 4 on page 31), also known as the TIM510 E1/T1 media module, terminates an E1 or T1 trunk. The TIM510 T1/E1 media module has a built-in channel service unit (CSU) so an external CSU is not necessary. The CSU is used for a T1 circuit only. Up to two TIM510s can be installed in any of the slots on the Services Router.
Figure 4: TIM510 E1/T1 Telephony Interface Module
The TIM510 provides the following key features:
One E1 or T1 trunk port with up to 30 channels on an E1 port and 24 channels on a T1 port. DS1-level support for a variety of E1 and T1 trunk types. Trunk signaling to support U.S. and international central office (CO) or tie trunks. Echo cancellation in either directionincoming or outgoing. Junos OS Feature Support Reference for SRX Series and J Series Devices Hardware Description and Reference for Avaya Communication Manager at
31
VoIP Interfaces
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 TIM510 RJ-45 Connector Pinout on page 32 TIM510 LEDs on page 33 Example: Configuring VoIP Interfaces on page 58
TIM510 RJ-45 Connector Pinout

The TIM510 Telephony Interface Module uses an RJ-45 cable. Table 14 on page 32 describes the TIM510 RJ-45 connector pinout.
Table 14: TIM510 RJ-45 Connector Pinout

Pin
1 2 3 4 5 6 7 8
Signal
Ring Tip No connection R1 - Transmit T1 - Transmit No connection No connection No connection
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TIM510 E1/T1 Telephony Interface Module on page 31 TIM510 LEDs on page 33 Example: Configuring VoIP Interfaces on page 58
32
TIM510 LEDs

Label
ALM
Color
Red
State
On steadily
Description
Alarm. A TIM510 failure requires monitoring or maintenance. Active. The TIM510 is online with network traffic. Test. A test is being performed on the TIM510 through the Media Gateway Controller (MGC). Signal. The link to the central office (CO) is active.
ACT
Green
On steadily
TST
Yellow
On steadily
SIG
Green
On steadily
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TIM510 E1/T1 Telephony Interface Module on page 31 TIM510 RJ-45 Connector Pinout on page 32 Example: Configuring VoIP Interfaces on page 58
33
VoIP Interfaces
34
CHAPTER 7


The TIM514 Analog Telephony Interface Module (Figure 5 on page 35), also known as the TIM514 analog media module, has four analog telephone ports and four analog trunk ports.
NOTE: For analog direct inward dialing (DID) trunks, you must use the four analog telephone (LINE) ports. You cannot use the four analog trunk (TRUNK) ports for analog DID trunks.
Three ringer loads, the ringer equivalency number for up to 2,000 ft (610 m), for all eight ports. Up to four simultaneously ringing ports. Type 1 caller ID and Type 2 caller ID. Ring voltage generation for a variety of international frequencies and cadences.
35
VoIP Interfaces

The TIM514 Telephony Interface Module uses an RJ-11 cable. Table 16 on page 36 describes the TIM514 RJ-11 connector pinout information.
Table 16: TIM514 RJ-11 Connector Pinout

Pin
1 2 3 4 5 6
Signal
No connection No connection Ring Tip No connection No connection
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TIM514 Analog Telephony Interface Module on page 35 TIM514 Possible Port Configurations on page 37
36
TIM514 LEDs on page 37 Example: Configuring VoIP Interfaces on page 58

You can configure TIM514 ports as described in Table 17 on page 37.

Possible Analog Telephone (LINE) Port Configurations
Wink-start or immediate-start DID trunk
Possible Analog Trunk (TRUNK) Port Configurations

Loop-start or ground-start central office trunk with a loop current of 18 to 120 mA. Two-wire analog outgoing centralized automatic message accounting (CAMA) emergency E911 trunk, for connectivity to the PSTN. Multifrequency (MF) signaling is supported for CAMA ports.
Analog tip/ring devices such as single-line telephones with or without LED message-waiting indication
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TIM514 Analog Telephony Interface Module on page 35 TIM514 Connector Pinout on page 36 TIM514 LEDs on page 37 Example: Configuring VoIP Interfaces on page 58
TIM514 LEDs

Label
ALM
Color
Red
State
On steadily
Description
Alarm. A TIM514 failure requires monitoring or maintenance.
37
VoIP Interfaces
Table 18: LEDs for TIM514 (continued)

Label
ACT
Color
Yellow
State
Blinking
Description
Active. A device connected to the TIM514 is in use. This situation can include a telephone that is off the hook.
38
CHAPTER 8


The TIM516 Analog Telephony Interface Module (Figure 6 on page 39), also known as the TIM516 analog media module, has 16 analog telephone lines.
8 S 1 LIINE S L NE
24 17 LINES
Analog
ALM ACT 6 TIM 51
Three ringer loads, the ringer equivalency number for up to 2,000 ft (610 m), for all 16 lines Up to 16 simultaneously ringing lines Type 1 caller ID and Type 2 caller ID for line lines Ring voltage generation for a variety of international frequencies and cadences Junos OS Feature Support Reference for SRX Series and J Series Devices Hardware Description and Reference for Avaya Communication Manager at
g003866
39
VoIP Interfaces


Pin
1 2 3 4 5 6 7 8 17 18 19 20 21 22 23
Signal
Tip Tip Tip Tip Tip Tip Tip Tip Tip Tip Tip Tip Tip Tip Tip
40

Pin
24 26 27 28 29 30 31 32 33 42 43 44 45 46 47 48 49
Signal
Tip Ring Ring Ring Ring Ring Ring Ring Ring Ring Ring Ring Ring Ring Ring Ring Ring
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TIM516 Analog Telephony Interface Module on page 39 TIM516 Possible Port Configurations on page 42
41
VoIP Interfaces
TIM516 LEDs on page 42 Example: Configuring VoIP Interfaces on page 58

You can configure TIM516 lines as described in Table 20 on page 42.

Possible Analog Telephone (LINE) Line Configurations
Analog tip/ring devices such as single-line telephones with or without LED message-waiting indication
TIM516 LEDs

Label
ALM
Color
Red
State
On steadily
Description
ACT
Yellow
Blinking
Junos OS Feature Support Reference for SRX Series and J Series Devices
42
Hardware Description and Reference for Avaya Communication Manager at

43
VoIP Interfaces
44
CHAPTER 9


The TIM518 Analog Telephony Interface Module (Figure 7 on page 45), also known as the TIM518 analog media module, has eight analog telephone lines and eight analog trunk lines.
LINES
18
LINES
17
24
Analog
ALM ACT TIM 51 8
NOTE: For analog direct inward dialing (DID) trunks, you can use all eight analog telephone lines.
Three ringer loads, the ringer equivalency number for up to 2,000 ft (610 m), for all 16 lines Up to 16 simultaneously ringing lines Type 1 caller ID and Type 2 caller ID for line lines
g003867
45
VoIP Interfaces
Type 1 caller ID for trunk lines Ring voltage generation for a variety of international frequencies and cadences Junos OS Feature Support Reference for SRX Series and J Series Devices Hardware Description and Reference for Avaya Communication Manager at


Pin
1 2 3 4 5 6 7 8 17 18 19
Signal
Ring Ring Ring Ring Ring Ring Ring Ring Ring Ring Ring
46

Pin
20 21 22 23 24 26 27 28 29 30 31 32 33 42 43 44 45 46 47 48 49
Signal
Ring Ring Ring Ring Ring Tip Tip Tip Tip Tip Tip Tip Tip Tip Tip Tip Tip Tip Tip
47
VoIP Interfaces
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TIM518 Analog Telephony Interface Module on page 45 TIM518 Possible Port Configurations on page 48 TIM518 LEDs on page 48 Example: Configuring VoIP Interfaces on page 58

You can configure eight TIM518 analog telephone lines as described in Table 23 on page 48.

Possible Analog Telephone Port Configurations
Wink-start or immed-start DID trunk
Possible Analog Trunk Port Configurations

Loop-start or ground-start central office trunk with a loop current of 18 to 120 mA Two-wire analog outgoing centralized automatic message accounting (CAMA) emergency E911 trunk for connectivity to the PSTN
Analog tip or ring devices such as single-line telephones with or without LED message-waiting indication
TIM518 LEDs
48

Label
ALM
Color
Red
State
On steadily
Description
ACT
Yellow
Blinking
49
VoIP Interfaces
50
CHAPTER 10
TIM521 BRI Telephony Interface Module

Understanding the TIM521 BRI Telephony Interface Module on page 51 TIM521 LEDs on page 52
Understanding the TIM521 BRI Telephony Interface Module

The TIM521 BRI Telephony Interface Module (Figure 8 on page 51), also known as the TIM521 BRI media module, has four ports with RJ-45 jacks that can be administered as ISDN Basic Rate Interface (BRI) trunk connections. Each ISDN BRI port has two B-channels plus a D-channel. Up to two TIM521 modules (with four BRI trunk ports each) can be installed in any of the slots on the Services Router.
Figure 8: TIM521 BRI Telephony Interface Module
For ISDN BRI trunking, the TIM521 supports up to four BRI interfaces to the central office at the ISDN T reference point. Information is communicated on each port in two ways:
Over two 64-Kbps B-channels, called B1 and B2, that can be circuit-switched simultaneously.
NOTE: The TIM521 does not support BRI stations or combining both B-channels together to form a 128-Kbps channel.
Over a 16-Kbps channel, called the D-channel, that is used for signaling. The TIM521 occupies one time slot for all four D-channels.
The circuit-switched connections have an a-law or mu-law option for voice operation. The circuit-switched connections operate as 64-Kbps clear channels transmitting data.
51
VoIP Interfaces
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 TIM521 LEDs on page 52 Example: Configuring VoIP Interfaces on page 58
TIM521 LEDs

Label
ALM
Color
Red
State
On steadily
Description
Alarm. A TIM521 failure requires monitoring or maintenance. Active. A trunk connected to the TIM521 is in use.
ACT
Yellow
On steadily
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TIM521 BRI Telephony Interface Module on page 51 Example: Configuring VoIP Interfaces on page 58
52
PART 2
Configuration

Avaya VoIP Module on page 55 Configuration Statements on page 67
53
VoIP Interfaces
54
CHAPTER 11
Avaya VoIP Module

Avaya VoIP Modules Configuration Overview on page 55 Configuring VoIP Interfaces with EPW and Disk-on-Key on page 56 Example: Configuring VoIP Interfaces on page 58
Avaya VoIP Modules Configuration Overview

You can use either J-Web or the CLI configuration editor to configure VoIP. Alternatively, you can download a complete router configuration that includes VoIP from an Electronic Preinstallation Worksheet (EPW) and a disk-on-key USB memory stick. The Avaya VoIP modules are installed in a J Series chassis like Physical Interface Modules (PIMs), but they are controlled by Avaya Communication Manager software rather than the Junos OS.
CAUTION: PIMs and VoIP modules are not hot-swappable. You must power off the Services Router before removing or inserting a PIM or VoIP module. Ensure that the PIMs and VoIP modules are installed in the router chassis before booting up the system.
CAUTION: The grounding cable for J Series devices must be, at minimum, 14 AWG cable.
On each J Series device with Avaya VoIP, a single TGM550 Telephony Gateway Module (TGM) and at least one telephony interface module (TIM) is required. No more than four TIMs of any kind can be installed on a single chassis.
CAUTION: Do not install a combination of PIMs in a single chassis that exceeds the maximum power and heat capacity of the chassis. If power management is enabled, PIMs that exceed the maximum power and heat capacity remain offline for a J Series device when the chassis is powered on.
55
VoIP Interfaces
Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Overview on page 5 Supported Avaya VoIP Modules and Interfaces on page 7 Understanding the TGM550 Telephony Gateway Module on page 17 Understanding the TIM508 Analog Telephony Interface Module on page 27 Understanding the TIM510 E1/T1 Telephony Interface Module on page 31 Understanding the TIM514 Analog Telephony Interface Module on page 35 Understanding the TIM516 Analog Telephony Interface Module on page 39 Understanding the TIM518 Analog Telephony Interface Module on page 45 Understanding the TIM521 BRI Telephony Interface Module on page 51 Example: Configuring VoIP Interfaces on page 58
Configuring VoIP Interfaces with EPW and Disk-on-Key

If you have a new J4350 or J6350 Services Router with the TGM550 and TIMs installed in the router, you can use the Avaya Electronic Preinstallation Worksheet (EPW) and a disk-on-key USB memory stick to configure VoIP on the router. The EPW is a customized Microsoft Excel spreadsheet that you use to collect a complete set of VoIP configuration information and create a configuration file named juniper-config.txt. You can copy the juniper-config.txt file to a disk-on-key device and boot the router from the device to configure VoIP on the router. This configuration method has the following requirements:

A management device (PC or laptop) running Microsoft Excel version 2000 or later. A disk-on-key device with one of the following 16-bit or 32-bit file allocation table (FAT) file systems:

DOS 3.0+ 16-bit FAT (up to 32 MB) DOS 3.31+ 16-bit FAT (over 32 MB) WIN95 OSR2 FAT32 WIN95 OSR2 FAT32, LBA-mapped WIN95 DOS 16-bit FAT, LBA-mapped
A Services Router with the factory configuration and the TGM550 and TIMs installed. If other Junos OS configuration files exist on the Services Router, the router cannot read the juniper-config.txt file from the disk-on-key device. To remove the configuration files from the router, press and hold the RESET CONFIG button for 15 seconds or more, until the STATUS LED blinks red.
56
CAUTION: Pressing and holding the RESET CONFIG button for 15 seconds or moreuntil the STATUS LED blinks reddeletes all configurations on the router, including the backup configurations and rescue configuration, and loads and commits the factory configuration.
To configure a VoIP interface using EPW and disk-on-key:

1.
Download the EPW to a PC or laptop computer. a. Go to http://support.avaya.com. b. On the Avaya support page, click Find Documentation and Technical Information by Product Name. c. Scroll down and click Integrated Management Provisioning & Installation Manager. d. Select the 4.0 release from the select a release box and click View all documents. e. Scroll down and double-click the Electronic Preinstallation Worksheet for Provisioning Installation Manager link. f. Scroll down and double-click the View XLS link. g. In the File Open window, click the Open button. h. In the Security Warning window, open the EPW by clicking Enable Macros. Be sure to open the EPW in Microsoft Excel version 2000 or later versions.
2. Enter information in the individual worksheets. Ensure that all mandatory fields
(highlighted in blue color) are filled in.

3. Select File>Save. 4. Open the InitialConfig worksheet and click Create Configuration File.
The Select Location page is displayed.

5. Choose a location where you want to create the configuration file.
The configuration file with the name juniper-config.txt is created.

6. Copy the juniper-config.txt file to a disk-on-key device. 7. Press and release the power button to power off the router. Wait for the POWER LED
to turn off.
8. Plug the disk-on-key device into the USB port on the Services Router. 9. Press the POWER button on the front panel of the router. Verify that the POWER LED
on the front panel turns green. The router reads the juniper-config.txt file from the disk-on-key device and commits the configuration.
10. Remove the disk-on-key device.
57
VoIP Interfaces
Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Overview on page 5 Avaya IG550 Integrated Gateway Overview on page 11 Media Gateway Controller Server Overview on page 13 Avaya Communication Manager Software Overview on page 14 Dynamic Call Admission Control Overview on page 15 Example: Configuring VoIP Interfaces on page 58
Example: Configuring VoIP Interfaces

This example shows how to configure VoIP interfaces on a device.

Requirements on page 58 Overview on page 59 Configuration on page 59 Verification on page 64
Requirements
Before you begin:
Install Services Router hardware, including the TGM550 and the TIMs. Before power is connected, ensure that the router is grounded with a 10 AWG cable. Then establish basic connectivity.
CAUTION: The original grounding cable for SSG Services Routers is 14 AWG only and must be replaced with a 10 AWG cable.
Install device hardware. See J4350 and J6350 Services Router Getting Started Guide. Verify that you have connectivity to at least one Avaya media server running Avaya Communication Manager (CM) release 4.0 or later. See Media Gateway Controller Server Overview on page 13. Verify that the Services Router is running Junos OS Release 8.2R1 or later. Download and install the most recent firmware for the TGM550. Verify that the TGM550 firmware version is compatible with the Junos OS version installed on the Services Router. Order a disk-on-key USB memory stick if you are configuring VoIP using the Avaya Electronic Preinstallation Worksheet (EPW) and a disk-on-key USB memory stick. For disk-on-key requirements, see Configuring VoIP Interfaces with EPW and Disk-on-Key on page 56.
58
Get a basic understanding of physical and logical interfaces and Juniper Networks interface conventions. See Understanding Interfaces. Be aware that if you apply an IP address to the TGM550, then it resets the module. If you are updating an existing VoIP configuration by modifying the TGM550 IP address, take the following precautions:
Log in to the TGM550 and enter copy running-config startup-config to save the TGM550 configuration. See Saving the TGM550 Module Configuration on page 91. Ensure that the TGM550 is not currently handling voice traffic.
Overview
In this example, you first create a VoIP interface called vp3/0/0 and set the logical unit to 0. You set the source IPv4 address to 10.10.10.1/32 and the destination IP address to 10.10.10.2. You configure the IP addresses of the MGC to 172.16.0.0, 10.10.10.30, and 10.10.10.40. You log in to the TGM550 with SSH, and verify that each MGC can be reached over the network. Then you remove all of the IP addresses from the MGC list using the clear command. You then configure dynamic CAC on the Services Router WAN interfaces. You create a Gigabit Ethernet interface called ge-0/0/3 and set the logical unit to 0 with an activation priority value of 200 and a BBL value of 3000. You then configure a T1 interface called t1-6/0/0 and set the logical unit to 0 with an activation priority value of 150 and a BBL value of 1000. Then you specify an ISDN BRI interface called br-1/0/3 and set the logical unit to 0 with an activation priority value of 100 and a BBL value of 128. Finally, you specify a logical VoIP interface called vp-3/0/0 and set the logical unit to 0. You then modify the destination IP address for the TGM550 by changing the IP address form 10.10.10.1/32 to a different address such as 10.10.10.80.
Configuration

Configuring the VoIP Interface on page 59 Configuring the Media Gateway Controller List on page 60 Configuring Dynamic Call Admission Control on WAN Interfaces on page 61 Modifying the IP Address of the TGM550 on page 63
Configuring the VoIP Interface

CLI Quick Configuration To quickly configure this example, copy the following command, paste it into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the command into the CLI at the [edit] hierarchy level.
set interfaces vp3/0/0 unit 0 family inet address 10.10.10.1/32 destination 10.10.10.2
59
VoIP Interfaces
Step-by-Step Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode in the Junos OS CLI User Guide. To configure the VoIP interface:
1.
Create the VoIP interface and set the logical unit.

[edit] user@host# edit interfaces vp3/0/0 unit 0
NOTE: You cannot configure more than one logical unit on the VoIP interface. The logical unit number must be 0.
2.
Configure the source IPv4 address and destination IPv4 address.

[edit interfaces vp3/0/0 unit 0] user@host# set family inet address 10.10.10.1/32 destination 10.10.10.2
NOTE: You cannot specify more than one IP address
Results
From configuration mode, confirm your configuration by entering the show interfaces vp-3/0/0 command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
[edit] user@host# show interfaces vp-3/0/0 unit 0 { family inet { address 10.10.10.1/32 { destination 10.10.10.2; } } }
If you are done configuring the device, enter commit from configuration mode.
Configuring the Media Gateway Controller List

CLI Quick Configuration To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.
set tgm fpc 2 media-gateway-controller [172.16.0.0 10.10.10.30 10.10.10.40] ssh 10.10.10.2 ping 172.16.0.0 ping 10.10.10.30 ping 10.10.10.40
60
clear tgm fpc 2 media-gateway-controller
To configure the MGC list from operational mode:

1.
Configure the IP addresses of the MGC.

user@host> set tgm fpc 2 media-gateway-controller [172.16.0.0 10.10.10.30 10.10.10.40]
NOTE: Running the set tgm slot media-gateway-controller command updates the startup configuration on the TGM550. You do not need to run the copy running-config start-config command to save the configuration on the module.
2.
Log in to the TGM550 with SSH, and verify that each MGC can be reached over the network.
[edit] user@host> ssh 10.10.10.2 TGM550-00<root># ping 172.16.0.0 TGM550-00<root># ping 10.10.10.30 TGM550-00<root># ping 10.10.10.40
3.
Remove all of the IP addresses from the MGC list.

user@host> clear tgm fpc 2 media-gateway-controller
NOTE: The clear command removes all the MGC IP addresses. You cannot clear the IP address of a single MGC with this command.
Configuring Dynamic Call Admission Control on WAN Interfaces

CLI Quick Configuration To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.
set interfaces ge-0/0/3.0 dynamic-call-admission-control activation-priority 200 bearer-bandwidth-limit 3000 set interfaces t1-6/0/0.0 dynamic-call-admission-control activation-priority 150 bearer-bandwidth-limit 1000 set interfaces br-1/0/3.0 dynamic-call-admission-control activation-priority 100 bearer-bandwidth-limit 128
61
VoIP Interfaces
The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode in the Junos OS CLI User Guide. To configure dynamic CAC on WAN interfaces:
1.
Create the Gigabit Ethernet interface.

[edit] user@host# edit interfaces ge-0/0/3
2.
Configure dynamic CAC on the logical unit with the activation priority and BBL values.
[edit interfaces ge-0/0/3] user@host# edit unit 0 user@host# set dynamic-call-admission-control activation-priority 200 bearer-bandwidth-limit 3000
3.
Create the T1 interface.

[edit] user@host# edit interfaces t1-6/0/0
4.
[edit interfaces t1-6/0/0] user@host# edit unit 0 user@host# set dynamic-call-admission-control activation-priority 150 bearer-bandwidth-limit 1000
5.
Configure the ISDN BRI interface.

[edit] user@host# edit interfaces br-1/0/3.0
6.
[edit interfaces br-1/0/3 unit 0] user@host# set dynamic-call-admission-control activation-priority 100 bearer-bandwidth-limit 128
Results
From configuration mode, confirm your configuration by entering the show interfaces ge-0/0/3, show interfaces t1-6/0/0, and show interfaces br-1/0/3 commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
[edit] user@host# show interfaces ge-0/0/3 unit 0 { dynamic-call-admission-control { bearer-bandwidth-limit 3000; activation-priority 200; } } [edit]
62
user@host# show interfaces t1-6/0/0 unit 0 { dynamic-call-admission-control { bearer-bandwidth-limit 1000; activation-priority 150 } } [edit] user@host# show interfaces br-1/0/3 unit 0 { dynamic-call-admission-control { bearer-bandwidth-limit 128; activation-priority 100; } }
Modifying the IP Address of the TGM550

CLI Quick Configuration To quickly configure this example, copy the following command, paste it into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the command into the CLI at the [edit] hierarchy level.
set interfaces vp-3/0/0 unit 0 family inet address 10.10.10.1/32 destination 10.10.10.80
The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode in the Junos OS CLI User Guide. To modify the IP address of the TGM550:
1.
Select the logical VoIP interface.

[edit] user@host# edit interfaces vp-3/0/0 unit 0
2.
Modify the destination IP address for the TGM550 by giving it to a different IP address.
[edit interfaces vp-3/0/0 unit 0] user@host# set family inet address 10.10.10.1/32 destination 10.10.10.80
NOTE: You cannot specify more than one IP address.
Results
From configuration mode, confirm your configuration by entering the show interfaces vp-3/0/0 command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
[edit] user@host# show interfaces vp-3/0/0 unit 0 {
63
VoIP Interfaces
family inet { address 10.10.10.1/32 { destination 10.10.10.80; } } }
Verification
To confirm that the configuration is working properly, perform these tasks:

Verifying the VoIP Interface on page 64 Verifying the Media Gateway Controller List on page 65 Verifying Bandwidth Available for VoIP Traffic on page 66
Verifying the VoIP Interface

Purpose Action Verify that the VoIP interface is correctly configured. From operational mode, enter the show interfaces vp-3/0/0 extensive command.
user@host> show interfaces vp-3/0/0 extensive Physical interface: vp-3/0/0, Enabled, Physical link is Up Interface index: 141, SNMP ifIndex: 21, Generation: 142 Type: VP-AV, Link-level type: VP-AV, MTU: 1518, Speed: 10mbps Device flags : Present Running Link type : Full-Duplex Link flags : None Physical info : Unspecified CoS queues : 8 supported, 8 maximum usable queues Last flapped : 2006-09-29 09:28:32 UTC (4d 18:35 ago) Statistics last cleared: Never Traffic statistics: Input bytes : 8886912 0 bps Output bytes : 6624354 0 bps Input packets: 90760 0 pps Output packets: 65099 0 pps Input errors: Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards: 0, Resource errors: 0 Output errors: Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors: 0 Egress queues: 8 supported, 8 in use Queue counters: Queued packets Transmitted packets Dropped packets 0 best-effort 1 expedited-fo 2 assured-forw 3 network-cont 65099 0 0 0 65099 0 0 0 0 0 0 0
Packet Forwarding Engine configuration:
64
Destination slot: 2 CoS transmit queue Limit 0 best-effort none 3 network-control none % 95 5
Bandwidth bps 9500000 500000 % 95 5
Buffer Priority usec 0 0
low low
Logical interface vp-3/0/0.0 (Index 71) (SNMP ifIndex 47) (Generation 137) Flags: Point-To-Point SNMP-Traps Encapsulation: VP-AV Protocol inet, MTU: 1500, Generation: 142, Route table: 0 Flags: None Filters: Input: pcap, Output: pcap Addresses, Flags: Is-Preferred Is-Primary Destination: 10.10.10.2, Local: 10.10.10.1, Broadcast: Unspecified, Generation: 144
The output shows a summary of interface information. Verify the following information:
The physical interface is enabled. If the interface is shown as disabled, do either of the following:
In the CLI configuration editor, delete the disable statement at the [edit interfaces interface-name] level of the configuration hierarchy. In the J-Web configuration editor, clear the Disable check box on the Interfaces>interface-name page.
The physical link is up. A link state of down indicates that the interface is disabled. Do one of the following:
In the CLI configuration editor, delete the disable statement at the [edit interfaces interface-name] level of the configuration hierarchy. In the J-Web configuration editor, clear the Disable check box on the Interfaces>interface-name page.
The last flapped time is an expected value. The last flapped time indicates the last time the physical interface became unavailable and then available again. Unexpected flapping indicates likely link-layer errors. The traffic statistics reflect expected input and output rates. Verify that the number of inbound and outbound bytes and packets matches expected throughput for the physical interface. To clear the statistics and see only new changes, use the clear interfaces statistics interface-name command.
Verifying the Media Gateway Controller List

Purpose Verify that the MGC list is correctly configured and that the MGCs are reachable over the network. From operational mode, enter the show tgm fpc 2 media-gateway-controller command.
user@host> show tgm fpc 2 media-gateway-controller
Action
65
VoIP Interfaces
Media gateway controller(s): 173.26.232.77 10.10.10.30 10.10.10.40
The output shows the configured MGC list. Verify the following:
The IP addresses and the order of the IP addresses in the MGC list are correct. The first MGC on the list is the primary MGC. The TGM550 searches for the primary MGC first. If it cannot connect to the primary MGC or loses its connection to the primary MGC, it attempts to connect to the next MGC in the list, and so on. Use the Junos OS CLI ping command or the J-Web ping host tool (Troubleshoot>Ping Host) to verify that the configured MGCs can be reached over the network.
Verifying Bandwidth Available for VoIP Traffic

Purpose Action Verify that the dynamic CAC configuration supports sufficient bandwidth for VoIP traffic. From operational mode, enter the show tgm dynamic-call-admission-control command.
user@host> show tgm dynamic-call-admission-control Reported bearer bandwidth limit: 3000 Kbps Interface State Activation Bearer bandwidth priority limit (Kbps) ge-0/0/3.0 up 200 3000 t1-6/0/0.0 up 150 1000 br-1/0/3.0 up 50 128
The output shows the dynamic CAC configuration. Verify the following information:
The activation priority and the bearer bandwidth limit (BBL) configured on individual interfaces are correct. The Reported bearer bandwidth limit field displays the bandwidth available for VoIP traffic. Ensure that the bandwidth is sufficient for VoIP traffic.
Junos OS Feature Support Reference for SRX Series and J Series Devices Administration for the Avaya IG550 Integrated Gateway at http://support.avaya.com Administrator Guide for Avaya Communication Manager at http://support.avaya.com Avaya VoIP Modules Overview on page 5 Understanding the TGM550 Telephony Gateway Module on page 17 Avaya IG550 Integrated Gateway Overview on page 11 TGM550 Module and VoIP Interface Troubleshooting on page 115
66
CHAPTER 12
Configuration Statements
Interfaces Configuration Statement Hierarchy on page 67
Interfaces Configuration Statement Hierarchy

Use the statements in the interfaces configuration hierarchy to configure interfaces on the device.
interfaces { interface-name { accounting-profile name ; atm-options { cell-bundle-size cells ; ilmi; linear-red-profiles profile-name { high-plp-max-threshold percent ; low-plp-max-threshold percent ; queue-depth cells high-plp-threshold percent low-plp-threshold percent ; } mpls { pop-all-labels { required-depth number; } } pic-type (atm1 | atm2); plp-to-clp; promiscuous-mode { vpi vpi-identifier; } scheduler-maps map-name { forwarding-class class-name { epd-threshold cells plp1 cells ; linear-red-profile profile-name ; priority (low | high); transmit-weight (cells number | percent number ); } vc-cos-mode (alternate | strict); } vpi vpi-identifier { maximum-vcs maximum-vcs ; oam-liveness { down-count cells;
67
VoIP Interfaces
up-count cells; } oam-period (disable | seconds); shaping { (cbr rate | rtvbr peak rate sustained rate burst length vbr peak rate sustained rate burst length ); queue-length number ; } } } cellular-options { roaming-mode (home only | automatic) gsm-options { select-profile profile-name; profiles { profile-name { sip-user-id simple-ip-user-id; sip-password simple-ip-password; access-point-nameapn; authentication-method (pap | chap | none) } } } } clocking (external | internal); dce; description text ; dialer-options { pool pool-identifier ; priority priority-number ; } disable; dsl-options { loopback local; operating-mode mode ; } ds0-options { bert-algorithm algorithm ; bert-error-rate rate ; bert-period seconds ; byte-encoding (nx56 | nx64); fcs (16 | 32); idle-cycle-flag (flags | ones); invert data; loopback (payload | remote); start-end-flag (shared | filler); } e1-options { bert-algorithm algorithm ; bert-error-rate rate ; bert-period seconds ; fcs (16 | 32); framing (g704 | g704-no-crc4 | unframed); idle-cycle-flag (flags | ones); invert data; loopback (local | remote);
68
Chapter 12: Configuration Statements
start-end-flag (shared | filler); timeslots time-slot-range; } e3-options { atm-encapsulation (direct | PLCP); bert-algorithm algorithm ; bert-error-rate rate ; bert-period seconds ; buildout feet; compatibility-mode (digital-link | kentrox | larscom) <subrate value >; fcs (16 | 32); framing (g.751 | g.832); idle-cycle-flag value ; loopback (local | remote); (payload-scrambler | no-payload-scrambler); start-end-flag value ; (unframed | no-unframed); } encapsulation type ; ether-vpls-over-atm-llc; es-options { backup-interface es- pim /0/ port ; } fabric-options { member-interfaces member-interface-name; } failure-options { [trigger-link-failure interface-name ]; } fastether-options { (flow-control | no-flow-control); ingress-rate-limit rate ; (loopback | no-loopback); mpls { pop-all-labels { required-depth [ number ]; } } redundant-parent interface-name; source-address-filter { mac-address ; } (source-filtering | no-source-filtering); } framing (lan-phy | sdh | sonet | wan-phy); gigether-options { (auto-negotiation <remote-fault> (local-interface-online | local-interface-offline)> | no-auto-negotiation); (flow-control | no-flow-control); ignore-l3-incompletes; (loopback | no-loopback); mpls { pop-all-labels { required-depth number ; } }
69
VoIP Interfaces
redundant-parent interface-name; source-address-filter { mac-address ; } (source-filtering | no-source-filtering); ethernet-switch-profile { ethernet-policer-profile { input-priority-map { ieee802.1p premium [ values ]; } output-priority-map { classifier { premium { forward-class class-name { loss-priority (high | low); } } } } policer cos-policer-name { aggregate { bandwidth-limit bps ; burst-size-limit bytes ; } premium { bandwidth-limit bps ; burst-size-limit bytes ; } } } (mac-learn-enable | no-mac-learn-enable); tag-protocol-id [ tpids ...]; } } (gratuitous-arp-reply | no-gratuitous-arp-reply); hold-time up milliseconds down milliseconds ; isdn-options { bchannel-allocation (ascending | descending); calling-number number; incoming-called-number number <reject>; media-type (voice | data); network-type (cpe | network); pool pool-name <priority priority> ; spid1 spid-string ; spid2 spid-string ; static-tei-val value ; switch-type (att5e | etsi | ni1 | ntdms100 | ntt); t310 seconds ; tei-option (first-call | power-up); } keepalives <down-count number > <interval seconds > <up-count number >; lmi { lmi-type (ansi | itu); n391dte number ; n392dce number ; n392dte number ;
70
n393dce number ; n393dte number ; t391dte seconds ; t392dce seconds ; } mac mac-address ; mlfr-uni-nni-bundle-options { acknowledge-retries number ; acknowledge-timer milliseconds ; action-red-differential-delay (disable-tx | remove-link); drop-timeout milliseconds ; fragment-threshold bytes ; hello-timer milliseconds ; link-layer-overhead percent ; lmi-type (ansi | itu); minimum-links number ; mrru bytes ; n391 number ; n392 number ; n393 number ; red-differential-delay milliseconds ; t391 seconds ; t392 seconds ; yellow-differential-delay milliseconds ; } modem-options { dialin (console | routable); init-command-string initialization-command-string ; } mtu bytes ; multiservice-options { boot-command filename; (core-dump | no-core-dump); (syslog | no-syslog); } native-vlan-idvlan-id; no-gratuitous-arp-request; no-keepalives; no-partition { interface-type type ; } passive-monitor-mode; per-unit-scheduler; ppp-options { chap { access-profile name; default-chap-secret name ; local-name name; passive; } compression { acfc; pfc; } no-termination-request; lcp-restart-timer milliseconds ;
71
VoIP Interfaces
ncp-restart-timer milliseconds ; promiscuous-mode; } redundant-ether-options { (flow-control | no-flow-control); lacp { (active | passive); periodic (fast | slow); } link-speed speed; (loopback | no-loopback); minimum-links number; redundancy-group number; source-address-filter mac-address; (source-filtering | no-source-filtering); } serial-options { clock-rate rate ; clocking-mode (dce | internal | loop); control-leads { control-signal (assert | de-assert | normal); cts (ignore | normal | require); dcd (ignore | normal | require); dsr (ignore | normal | require); dtr signal-handling-option ; ignore-all; indication (ignore | normal | require); rts (assert | de-assert | normal); tm (ignore | normal | require); } control-polarity (positive | negative); cts-polarity (positive | negative); dcd-polarity (positive | negative); dsr-polarity (positive | negative); dtr-circuit (balanced | unbalanced); dtr-polarity (positive | negative); encoding (nrz | nrzi); indication-polarity (positive | negative); line-protocol protocol ; loopback mode; rts-polarity (positive | negative); tm-polarity (positive | negative); transmit-clock invert; } services-options { inactivity-timeout seconds ; open-timeout seconds ; syslog { host hostname { facility-override facility-name ; log-prefix prefix-number ; services priority-level ; } } } shdsl-options {
72
annex (annex-a |annex-auto | annex-b); line-rate line-rate ; loopback (local | remote | payload); snr-margin { current margin ; snext margin ; } } t1-options { bert-algorithm algorithm ; bert-error-rate rate ; bert-period seconds ; buildout value ; byte-encoding (nx64 | nx56); fcs (16 | 32); framing (esf | sf); idle-cycle-flags (flags | ones); invert-data; line-encoding (ami | b8zs); loopback (local | payload | remote); remote-loopback-respond; start-end-flag (filler | shared); timeslots time-slot-range ; } t3-options { atm-encapsulation (direct | PLCP); bert-algorithm algorithm ; bert-error-rate rate ; bert-period seconds ; buildout feet; (cbit-parity | no-cbit-parity); compatibility-mode (adtran | digital-link | kentrox | larscom | verilink) <subrate value >; fcs (16 | 32); (feac-loop-respond | no-feac-loop-respond); idle-cycle-flag value ; (long-buildout | no-long-buildout); (loop-timing | no-loop-timing); loopback (local | payload | remote); (payload-scrambler | no-payload-scrambler); start-end-flag value (filler | shared); } threshold bytes ; traceoptions { flag flag < flag-modifier > <disable>; } (traps | no-traps); vdsl-options { vdsl-profile 17a; } unit logical-unit-number { accept-source-mac { mac-address mac-address ; policer { input policer-name ; output policer-name ;
73
VoIP Interfaces
} } accounting-profile name ; allow-any-vci; atm-scheduler-map (default | map-name ); arp-resp ( resricted | unresricted); backup-options { interface interface-name ; } bandwidth rate ; cell-bundle-size cells ; clear-dont-fragment-bit; compression { rtp { f-max-period number ; maximum-contexts number ; port { maximum port-number ; minimum port-number ; } queues [ queue-numbers ]; } } compression-device interface-name; copy-tos-to-outer-ip-header; description text ; dialer-options { activation-delay seconds ; callback; callback-wait-period seconds ; deactivation-delay seconds ; dial-string [ dial-string-numbers ]; idle-timeout seconds ; incoming-map (accept-all | caller caller-number ); initial-route-check seconds ; load-interval seconds ; load-threshold percent ; pool pool-name ; redial-delay time ; watch-list { [ routes ]; } } disable; disable-mlppp-inner-ppp-pfc; dlci dlci-identifier ; drop-timeout milliseconds ; dynamic-call-admission-control { activation-priority number ; bearer-bandwidth-limit threshold ; } encapsulation (cisco-hdlc | frame-relay | multilink-frame-relay-uni-nni | ppp | ppp-over-ether); epd-threshold cells plp1 cells ; f-max-period number ; family {
74
bridge { interface-mode { access vlan-id vlan-id | trunk { vlan-id-list vlan-list | vlan-rewrite translate from-vlan-id internal-vlan-id } } inet { address IPaddress ; } } inet6 { address IPaddress ; } } fragment-threshold bytes ; input-vlan-map { (pop | pop-pop | pop-swap | push | push-push | swap swap-push | swap-swap); inner-tag-protocol-id tpid; inner-vlan-id number ; tag-protocol-id tpid; vlan-id number ; } interleave-fragments; inverse-arp; (keepalives | no-keepalives); link-layer-overhead percent ; minimum-links number ; mrru bytes ; multicast-dlci dlci-identifier ; multicast-vci vpi-identifier.vci-identifier ; multilink-max-classes number ; multipoint number ; multipoint; oam-liveness { up-count cells ; down-count cells ; } oam-period (disable | seconds ); output-vlan-map { (pop | pop-pop | pop-swap | push | push-push | swap swap-push | swap-swap); inner-tag-protocol-id tpid; inner-vlan-id number ; tag-protocol-id tpid; vlan-id number ; } passive-monitor-mode; peer-unit unit-number ; plp-to-clp; point-to-point; ppp-options { chap { access-profile name ;
75
VoIP Interfaces
default-chap-secret name ; local-name name ; passive; } compression { acfc; pfc; } lcp-restart-timer milliseconds ; loopback-clear-timer seconds ; ncp-restart-timer milliseconds ; no-termination-request; pap; access-profile name ; default-password password ; local-name name ; local-password password ; passive; } } pppoe-options { access-concentrator name ; auto-reconnect seconds ; service-name name ; underlying-interface interface-name ; } proxy-arp; service-domain (inside | outside); shaping{ (cbr rate | rtvbr peak rate sustained rate burst length vbr peak rate sustained rate burst length ); queue-length number ; } short-sequence; three-color-policer { input policer-name ; output policer-name ; } transmit-weight number ; (traps | no-traps); trunk-bandwidth rate ; trunk-id number ; tunnel { backup-destination address ; destination address ; key number ; routing-instance { destination routing-instance-name; } source source-address ; ttl number ; } vci vpi-identifier.vci-identifier ; vpi vpi-identifier ; vlan-id number ; vlan-tagging native-vlan-id vlan-id;
76
vlan-tags inner tpid.vlan-id outer tpid.vlan-id ; family family { accounting { destination-class-usage; source-class-usage { direction ; } } address address { arp ip-address (mac | multicast-mac) mac-address <publish>; broadcast address ; destination address ; destination-profile name ; eui-64; multipoint-destination address dlci dlci-identifier ; multipoint-destination address { epd-threshold cells ; inverse-arp; oam-liveness { up-count cells ; down-count cells ; } oam-period ( disable | seconds ); shaping{ (cbr rate | rtvbr peak rate sustained rate burst length vbr peak rate sustained rate burst length ); queue-length number ; } vci vpi-identifier.vci-identifier ; } preferred; primary; vrrp-group group-number { (accept-data | no-accept-data): advertise-interval seconds ; authentication-type authentication ; authentication-key key ; fast-interval milliseconds; (preempt | no-preempt) { hold-time seconds ; } priority number ; track { interface interface-name { priority-cost priority ; bandwidth-threshold bits-per-second { priority-cost priority ; } } priority-hold-time seconds ; } virtual-address [ addresses ]; } web-authentication { http; }
77
VoIP Interfaces
} bundle interface-name ; dhcp { client-identifier (ascii ascii | hexadecimal hexadecimal); lease-time seconds; retransmission-attempt number; retransmission-interval seconds; server-address ip-address; update-server; vendor-id vendor-id; } dialer filter-name; filter { group filter-group-number; input filter-name; input-list { [filter-names]; } output filter-name ; output-list { [filter-names]; } } keep-address-and-control; mtu bytes ; multicast-only; next-hop-tunnel gateway-address ipsec-vpn vpn-name; no-redirects; policer { arp policer-template-name; input policer-template-name; output policer-template-name; } primary; proxy inet-address address ; receive-options-packets; receive-ttl-exceeded; remote (inet-address address | mac-address address); rpf-check <fail-filter filter-name> { <mode loose>; } sampling { direction ; } service { input { service-set service-set-name <service-filter filter-name >; post-service-filter filter-name ; } output { service-set service-set-name <service-filter filter-name >; } } simple-filter{ input filter-name; }
78
(translate-discard-eligible | no-translate-discard-eligible); (translate-fecn-and-becn | no-translate-fecn-and-becn); unnumbered-address { interface-name ; destination destination-address ; destination-profile profile-name ; preferred-source-address interface-name ; } traceoptions { flag flag <disable>; } } } interface-range interface-range-name { aggregated-ether-options { lacp { (active | passive); periodic (fast | slow); } link-speed speed; minimum-links number; } partition partition-number { interface-type type ; oc-slice oc-slice-range ; timeslots time-slot-range ; } } traceoptions { file filename <files number > <match regular-expression > <size maximum-file-size > <world-readable | no-world-readable>; flag flag <disable>; } }
Junos OS Interfaces Configuration Guide for Security Devices Junos OS Initial Configuration Guide for Security Devices Junos OS Monitoring and Troubleshooting Guide for Security Devices Junos OS Feature Support Reference for SRX Series and J Series Devices
Junos OS Services Interfaces Configuration Guide
79
VoIP Interfaces
activation-priority (Interfaces)
Syntax Hierarchy Level Release Information Description
activation-priority priority; [edit interfaces interface-name unit logical-unit-number dynamic-call-admission-control]
Statement introduced in Release 8.2 of Junos OS. This statement is used only in conjunction with J Series Services Routers that support voice over IP with the TGM550 media gateway module. For Fast Ethernet and Gigabit Ethernet interfaces, ISDN BRI interfaces, and serial interfaces with PPP or Frame Relay encapsulation, configure the dynamic call admission control (dynamic CAC) activation priority value.
priorityThe activation priority at which the interface is used for providing call bandwidth.
Options
The interface with the highest activation priority value is the primary link for providing call bandwidth. If the primary link becomes unavailable, the TGM550 switches over to the next active interface with the highest activation priority value, and so on. Range: 0 through 255 Default: 50 Required Privilege Level Related Documentation interfaceTo view this statement in the configuration. interface-controlTo add this statement to the configuration.
80
bearer-bandwidth-limit (Interfaces)
Syntax Hierarchy Level Release Information Description
bearer-bandwidth-limit kilobits-per-second; [edit interfaces interface-name unit logical-unit-number dynamic-call-admission-control]
Statement introduced in Release 8.2 of Junos OS. This statement is used only in conjunction with J Series Services Routers that support voice over IP with the TGM550. For Fast Ethernet and Gigabit Ethernet interfaces, ISDN BRI interfaces, and serial interfaces with PPP or Frame Relay encapsulation, configure the bearer bandwidth limit (BBL). The BBL is used for dynamic call admission control (dynamic CAC) to provide enhanced control over WAN bandwidth.
kilobits-per-secondThe bearer bandwidth limit to be reported to a TGM550, in kilobits
Options
per second (Kbps). Range: 0 through 9999 Kbps Default: 1 (dynamic CAC is not enabled on the interface) Required Privilege Level Related Documentation interfaceTo view this statement in the configuration. interface-controlTo add this statement to the configuration.
81
VoIP Interfaces
dynamic-call-admission-control (Interfaces)
Syntax
dynamic-call-admission-control { activation-priority priority; bearer-bandwidth-limit kilobits-per-second; } [edit interfaces interface-name unit logical-unit-number]
Hierarchy Level Release Information Description
Statement introduced in Release 8.2 of Junos OS. This statement is used only in conjunction with J Series Services Routers that support voice over IP with the TGM550. For Fast Ethernet and Gigabit Ethernet interfaces, ISDN BRI interfaces, and serial interfaces with PPP or Frame Relay encapsulation, configure dynamic call admission control (CAC). Dynamic CAC provides enhanced control over WAN bandwidth. When dynamic CAC is configured on an interface responsible for providing call bandwidth, the TGM550 informs the Media Gateway Controller (MGC) of the bandwidth limit available for voice packets on the interface and requests that the MGC block new calls when the bandwidth is exhausted. Dynamic CAC must be configured on each J Series Services Router interface responsible for providing call bandwidth. The remaining statements are explained separately.
Required Privilege Level Related Documentation
interfaceTo view this statement in the configuration. interface-controlTo add this statement to the configuration.
82
family bridge
Syntax
family bridge { interface-mode { access vlan-id vlan-id | trunk { vlan-id-list vlan-list | vlan-rewrite translate from-vlan-id internal-vlan-id } } } [edit interfaces interface unit unit ]
Hierarchy Level Release Information Description
Statement modified in Release 9.6 of Junos OS. Configure a Layer 2 logical interface.
NOTE: If a physical interface has a bridge family logical interface, it cannot have any other family type in its logical interfaces.
Options
interface-modeEither access or trunk:
An access mode interface accepts untagged packets, assigns the specified VLAN identifier to the packet, and forwards the packet within the bridge domain that is configured with the matching VLAN identifier. A trunk mode interface accepts any packet tagged with a VLAN identifier that matches a specified list of VLAN identifiers.
vlan-rewrite translateRewrites the from-vlan-id VLAN identifier with the internal-vlan-id
in packets arriving on a Layer 2 trunk port. The internal-vlan-id must be in the vlan-list for the trunk port.
NOTE: The from-vlan-id and internal-vlan-id must not be the same VLAN identifier configured with the native-vlan-id statement for the trunk port.
Required Privilege Level Related Documentation
interfaceTo view this statement in the configuration. interface-controlTo add this statement to the configuration.
83
VoIP Interfaces
84
PART 3
Administration

TGM550 Module on page 87 Operational Commands on page 93
85
VoIP Interfaces
86
CHAPTER 13
TGM550 Module

Connecting Through the TGM550 Module Console Port on page 87 Connecting to the TGM550 with SSH on page 88 TGM550 Module with Telnet Access on page 89 Accessing the Services Router from the TGM550 Module on page 90 Resetting the TGM550 Module on page 90 Saving the TGM550 Module Configuration on page 91
Connecting Through the TGM550 Module Console Port

To connect to the TGM550 through its console port:
1.
Turn off the power to the management device, such as a PC or laptop computer, that you are using to access the TGM550.
2. Plug one end of an Ethernet rollover cable provided with the TGM550 into the RJ-45
to DB-9 serial port adapter provided with the TGM550.
CAUTION: Two different RJ-45 cables and RJ-45 to DB-9 adapters are provided. Do not use the RJ-45 cable and adapter for the Services Router console port to connect to the TGM550 console port.
3. Plug the RJ-45 to DB-9 serial port adapter provided with the TGM550 into the serial
port on the management device.

4. Connect the other end of the Ethernet rollover cable to the console port (CONSOLE)
on the TGM550.
5. Turn on power to the management device. 6. Start your asynchronous terminal emulation application (such as Microsoft Windows
Hyper Terminal), and select the appropriate COM port to use (for example, COM1).
7. Configure the port settings as follows:

Bits per second: 9600 Data bits: 8
87
VoIP Interfaces
Parity: None Stop bits: 1 Flow control: Hardware
8. At the login prompt, type your username and press Enter. 9. At the password prompt, type your password and press Enter.
Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Overview on page 5 Understanding the TGM550 Telephony Gateway Module on page 17 Connecting to the TGM550 with SSH on page 88 Enabling Telnet Service on the TGM550 Module on page 89 Accessing the Services Router from the TGM550 Module on page 90 Resetting the TGM550 Module on page 90 Saving the TGM550 Module Configuration on page 91 TGM550 Module and VoIP Interface Troubleshooting on page 115
Connecting to the TGM550 with SSH

To connect to the TGM550 with SSH:
1.
Ensure that the TGM550 has an IP address.
2. From the Junos OS CLI or a remote connection, enter the following command: ssh ip-address
Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Overview on page 5 Understanding the TGM550 Telephony Gateway Module on page 17 Connecting Through the TGM550 Module Console Port on page 87 Enabling Telnet Service on the TGM550 Module on page 89 Accessing the Services Router from the TGM550 Module on page 90 Resetting the TGM550 Module on page 90 Saving the TGM550 Module Configuration on page 91 TGM550 Module and VoIP Interface Troubleshooting on page 115
88
Chapter 13: TGM550 Module
TGM550 Module with Telnet Access

This section contains the following topics:

Enabling Telnet Service on the TGM550 Module on page 89 Connecting to the TGM550 Module with Telnet on page 89 Disabling Telnet Service on the TGM550 Module on page 89
Enabling Telnet Service on the TGM550 Module

By default, Telnet service is not enabled on the TGM550. You must enable Telnet service on the TGM550 before you can telnet to the TGM550 from other devices or from the TGM550 to other devices.
CAUTION: Telnet connections are not encrypted and therefore can be intercepted.
To enable Telnet service on the TGM550:

1.
Connect to the TGM550 through the console port.
2. Enable incoming Telnet connections by entering the following command, and replacing
port with the Telnet port number.

TGM550-004(super)# ip telnet port port 3. Enable outgoing Telnet connections from the TGM550 to other devices. TGM550-004(super)# ip telnet-client 4. Save the configuration. TGM550-004(super)# copy running-config startup-config
Connecting to the TGM550 Module with Telnet

To connect to the TGM550 with Telnet:
1.
Ensure that Telnet is enabled on the TGM550.
2. Ensure that the TGM550 has an IP address. 3. From the Junos OS CLI or a remote connection, enter the following command. telnet ip-address
Disabling Telnet Service on the TGM550 Module

To disable Telnet service on the TGM550:
1.
Connect to the TGM550 through the console port.
2. Disable incoming Telnet connections by entering the following command, and replacing
port with the Telnet port number.

TGM550-004(super)# no ip telnet
89
VoIP Interfaces
3. Disable outgoing Telnet connections from the TGM550 to other devices. TGM550-004(super)# no ip telnet-client 4. Save the configuration. TGM550-004(super)# copy running-config startup-config
Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Overview on page 5 Connecting Through the TGM550 Module Console Port on page 87 Enabling Telnet Service on the TGM550 Module on page 89 Connecting to the TGM550 Module with Telnet on page 89 TGM550 Module and VoIP Interface Troubleshooting on page 115
Accessing the Services Router from the TGM550 Module

You can access the Services Router from the CLI on its installed TGM550 in the following ways:

Enter the session chassis command. Enter the telnet or ssh command.
NOTE: Before using the TGM550 CLI telnet command, ensure that Telnet service is enabled on the TGM550.
Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Overview on page 5 Understanding the TGM550 Telephony Gateway Module on page 17 Connecting Through the TGM550 Module Console Port on page 87 Enabling Telnet Service on the TGM550 Module on page 89 Resetting the TGM550 Module on page 90 Saving the TGM550 Module Configuration on page 91 TGM550 Module and VoIP Interface Troubleshooting on page 115
Resetting the TGM550 Module
CAUTION: Before resetting the TGM550, take the following precautions:
Log into the TGM550 and enter copy running-config startup-config to save the TGM550 configuration.
90
Chapter 13: TGM550 Module
Ensure that the TGM550 is not currently handling voice traffic.
You can reset the TGM550 from the module itself or from the Services Router. To reset the TGM550 from the module itself, do one of the following:

Press the RST button on the TGM550. Log into the TGM550, and enter the reset command.
To reset the TGM550 from the device:

1.
Enter operational mode in the CLI.
2. Enter the request chassis fpc slot slot-number restart command.
For example, to reset a TGM550 installed in slot 2 on the router chassis, enter
user@host> request chassis fpc slot 2 restart
NOTE: You cannot reset the TIMs using the request chassis fpc slot slot-number restart command. TIMs are administered only from the TGM550.
Junos OS Feature Support Reference for SRX Series and J Series Devices Avaya VoIP Modules Overview on page 5 Understanding the TGM550 Telephony Gateway Module on page 17 Connecting Through the TGM550 Module Console Port on page 87 Enabling Telnet Service on the TGM550 Module on page 89 Accessing the Services Router from the TGM550 Module on page 90 Saving the TGM550 Module Configuration on page 91 TGM550 Module and VoIP Interface Troubleshooting on page 115
Saving the TGM550 Module Configuration

To save the configuration on the TGM550:
1.
Log in to the TGM550.
2. Save the configuration. TGM550-004(super)# copy running-config startup-config
91
VoIP Interfaces
92
CHAPTER 14
Operational Commands
93
VoIP Interfaces
restart (Reset)
Syntax
restart <audit-process | chassis-control | class-of-service | dhcp | dialer-services |event-processing | firewall | group-key-server | interface-control | ipsec-key-management | isdn-signaling | l2ald | l2-learning | mib-process | pgm | ppp | pppoe | remote-operations | routing <logical-system logical-system-name> | sampling | service-deployment | snmp | usb-control | wan-acceleration | web-management> <gracefully | immediately | soft>
Release Information
Command introduced before Release 7.4 of Junos OS. wan-acceleration option added in Release 8.5 of Junos OS. group-key-server option added in Release 10.2 of Junos OS. Restart a Junos OS process.
Description
CAUTION: Never restart a software process unless instructed to do so by a customer support engineer. A restart might cause the router to drop calls and interrupt transmission, resulting in possible loss of data.
Options
dhcp(Optional) Restart the software process for a Dynamic Host Configuration Protocol (DHCP) server. A DHCP server allocates network IP addresses and delivers configuration settings to client hosts without user intervention. dialer-services(Optional) Restart the ISDN dial out process. group-key-server(Optional) Restart the group VPN server process. The group VPN server loses all its data, including TEK and KEK keys, when it restarts. New keys are generated, but the keys are not available to group members until they reregister. isdn-signaling(Optional) Restart the ISDN signaling process, which initiates ISDN connections. usb-control(Optional) Restart the USB control process. wan-acceleration(J Series devices only.) (Optional) Restart the WAN acceleration process. If the WXC Integrated Services Module (ISM 200) is not accessible, or is not responding, you can use this command to restart the WAN acceleration process. web-management(Optional) Restart the Web management process.
Required Privilege Level List of Sample Output Output Fields
reset
restart interfaces on page 95 When you enter this command, you are provided feedback on the status of your request.
94
Chapter 14: Operational Commands
Sample Output
restart interfaces
user@host> restart interfaces interfaces process terminated interfaces process restarted
95
VoIP Interfaces
show chassis hardware (View)

Syntax
show chassis hardware <clei-models | detail | extensive | models | node ( node-id | all | local | primary)>
Release Information
Command modified in Release 9.2 of Junos OS; node options added in Release 9.0 of Junos OS. Display chassis hardware information.
Description Options
clei-models(Optional) Display Common Language Equipment Identifier Code (CLEI)
barcode and model number for orderable field-replaceable units (FRUs).

detail | extensive(Optional) Display the specified level of output. models(Optional) Display model numbers and part numbers for orderable FRUs. node(Optional) For chassis cluster configurations, display chassis hardware
information on a specific node (device) in the cluster.

node-id Identification number of the node. It can be 0 or 1. localDisplay information about the local node. primaryDisplay information about the primary node.
Required Privilege Level Related Documentation List of Sample Output
view
Junos OS System Basics and Services Command Reference
show chassis hardware on page 98 show chassis hardware (SRX5600 and SRX5800 devices) on page 98 show chassis hardware detail on page 98 show chassis hardware detail node 1 on page 99 show chassis hardware extensive on page 99 show chassis hardware models (SRX5600 and SRX5800 devices) on page 100 show chassis hardware clei-models (SRX5600 and SRX5800 devices) on page 100 Table 26 on page 96 lists the output fields for the show chassis hardware command. Output fields are listed in the approximate order in which they appear.
Output Fields
Table 26: show chassis hardware Output Fields

Field Name
Item
Field Description
Chassis componentInformation about the backplane; power supplies; fan trays; Routing Engine; each Physical Interface Module (PIM)reported as FPC and PICand each fan, blower, and impeller. Revision level of the chassis component.
Version
96
Table 26: show chassis hardware Output Fields (continued)

Field Name
Part Number Serial Number
Field Description
Part number for the chassis component. Serial number of the chassis component. The serial number of the backplane is also the serial number of the device chassis. Use this serial number when you need to contact Juniper Networks Customer Support about the device chassis. Identification number that describes the FRU hardware. Model number of FRU hardware component. Common Language Equipment Identifier code. This value is displayed only for hardware components that use ID EEPROM format v2. This value is not displayed for components that use ID EEPROM format v1. ID EEPROM version used by hardware component: 0x01 (version 1) or 0x02 (version 2). Brief description of the hardware item:

Assb ID or Assembly ID FRU model number CLEI code
EEPROM Version Description
Type of power supply. Type of PIM. If the PIM type is not supported on the current software release, the output states Hardware Not Supported. Type of FPC: The FPC type corresponds to the PIM. The following shows the PIM abbreviation in the output and the corresponding PIM name:

2x FEDual-Port Fast Ethernet PIM 4x FE4-Port Fast Ethernet ePIM 1x GE CopperCopper Gigabit Ethernet ePIM (one 10-mpbs, 100-Mpbs, or 1000-Mpbs port) 1x GE SFPSFP Gigabit Ethernet ePIM (one fiber port) 1x SFP uPIM1-Port Gigabit Ethernet uPIM 6x GE SFP uPIM6-Port Gigabit Ethernet uPIM 8x GE SFP uPIM8-Port Gigabit Ethernet uPIM 16x GE SFP uPIM16-Port Gigabit Ethernet uPIM 4x GE Base PICFour built-in Gigabit Ethernet ports on a chassis (fixed PIM) 2x SerialDual-Port Serial PIM 2x T1Dual-Port T1 PIM 2x E1Dual-Port E1 PIM 2x CT1E1/PRIDual-Port Channelized T1/E1/ISDN PRI PIM 1x T3T3 PIM (one port) 1x E3E3 PIM (one port) 4x BRI S/T4-Port ISDN BRI S/T PIM 4x BRI U4-Port ISDN BRI U PIM 1x ADSL Annex AADSL 2/2 + Annex A PIM (one port, for POTS) 1x ADSL Annex BADSL 2/2 + Annex B PIM (one port, for ISDN 2x SHDSL (ATM)G.SHDSL PIM (2-port two-wire mode or 1-port four-wire mode) Integrated Services ModuleWXC Integrated Services Module (ISM 200)
For hosts, the Routing Engine type.
97
VoIP Interfaces
Sample Output
show chassis hardware
user@host> show chassis hardware Hardware inventory: Item Version Part number Chassis Routing Engine REV 07 750-009992 FPC 0 REV 04 750-010738 PIC 0 Power Supply 0
Serial number JN001340AA AA04350184 AB04330259
Description JSR2300 RE-J.1 FPC 2x FE, 2x T1
Sample Output
show chassis hardware (SRX5600 and SRX5800 devices)
user@host> show chassis hardware Hardware inventory: Item Version Part number Serial number Chassis JN10B7005AGA Midplane REV 03 710-013698 TR0779 FPM Board REV 03 710-014974 KC3406 PDM Rev 03 740-013110 QCS1122504F PEM 1 Rev 03 740-013683 QCS1134703V PEM 2 Rev 03 740-013683 QCS1134700E Routing Engine 0 REV 06 740-015113 1000696955 CB 0 REV 07 710-013385 JZ3257 FPC 3 BB-P2-39 710-020305 JS4847 CPU REV 06 710-013713 KC1180 PIC 0 BUILTIN BUILTIN PIC 1 BUILTIN BUILTIN FPC 6 REV 03 750-020751 JT0109 CPU REV 06 710-013713 KC3543 PIC 0 BUILTIN BUILTIN Xcvr 0 NON-JNPR A7C00SY PIC 1 BUILTIN BUILTIN Xcvr 0 REV 01 740-011571 C728XJ01W PIC 2 BUILTIN BUILTIN PIC 3 BUILTIN BUILTIN Fan Tray 0 REV 04 740-014971 TP1432 Fan Tray 1 REV 04 740-014971 TP1829
Description SRX 5800 SRX 5800 Backplane Front Panel Display Power Distribution Module DC Power Entry Module DC Power Entry Module RE-S-1300 SRX5k SCB SRX5k SPC DPC PMB SPU Cp SPU Flow SRX5k DPC 4x 10GE DPC PMB 1x 10GE(LAN/WAN) RichQ XFP-10G-SR 1x 10GE(LAN/WAN) RichQ XFP-10G-SR 1x 10GE(LAN/WAN) RichQ 1x 10GE(LAN/WAN) RichQ Fan Tray Fan Tray
Sample Output
show chassis hardware detail
user@host> show chassis hardware detail Hardware inventory: Item Version Part number Serial number Description Chassis JN000968AB J4300 Midplane REV 05 710-010001 ad04420077 System IO REV 07 710-010003 AE04420393 System IO board Routing Engine REV 08 750-010005 btrd43500196 RE-J.2 ad0 488 MB 512MB CHH 504754C53A711400 Compact Flash ad2 488 MB 512MB CHH 504754C43A711400 Removable Compact Flash FPC 2 REV 08 750-013493 NB9161 FPC PIC 0 Integrated Services Module ANNEX REV 08 750-013493 NB9161 Integrated Services
98
Sample Output
show chassis hardware detail node 1
user@host> show chassis hardware detail node 1 node1: -------------------------------------------------------------------------Hardware inventory: Item Version Part number Serial number Description Chassis JN108C688ADB J6350 Midplane REV 03 710-014593 NM7516 System IO REV 01 710-016210 NN9781 JX350 System IO Crypto Module Crypto Acceleration Routing Engine REV 08 710-015273 NM6569 RE-J6350-3400 ad0 991 MB 1GB CKS 20060000000000000800 Compact Flash FPC 0 FPC FPC 3 REV 06 750-013492 NM1294 FPC FPC 6 REV 11 750-015153 NP8750 FPC
Sample Output
show chassis hardware extensive
user@host> show chassis hardware extensive Hardware inventory: Item Version Part number Serial number Description Chassis JN107a494ADA J4350 Jedec Code: 0x0000 EEPROM Version: 0x00 P/N: ........... S/N: JN107a494ADA Assembly ID: 0x0513 Assembly Version: 00.00 Date: 00-00-0000 Assembly Flags: 0x00 Version: ........... ID: j4350 ... FPC 5 REV 08 750-013493 NB9161 FPC Jedec Code: 0x7fb0 EEPROM Version: 0x01 P/N: 750-013493 S/N: S/N NB9161 Assembly ID: 0x073c Assembly Version: 01.08 Date: 03-03-2006 Assembly Flags: 0x00 Version: REV 08 ID: FPC FRU Model Number: SSG-EPIM-1TX Board Information Record: Address 0x00: 34 01 05 05 02 ff ff ff ff ff ff ff ff ff ff ff I2C Hex Data: Address 0x00: 7f b0 01 ff 07 3c 01 08 52 45 56 20 30 38 00 00 Address 0x10: 00 00 00 00 37 35 30 2d 30 31 33 34 39 33 00 00 Address 0x20: 53 2f 4e 20 4e 42 39 31 36 31 00 00 00 03 03 07 Address 0x30: d6 ff ff ff 34 01 05 05 02 ff ff ff ff ff ff ff Address 0x40: ff ff ff ff 01 00 00 00 00 00 00 00 00 00 00 53 Address 0x50: 53 47 2d 45 50 49 4d 2d 31 54 58 00 00 00 00 00 Address 0x60: 00 00 00 00 00 00 ff ff ff ff ff ff ff ff ff ff Address 0x70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff PIC 0 Integrated Services Module Jedec Code: 0x7fb0 EEPROM Version: 0x01 Assembly ID: 0x063c Assembly Version: 01.08 Date: 03-03-2006 Assembly Flags: 0x00 ID: Integrated Services Module Board Information Record: Address 0x00: 34 01 05 05 02 ff ff ff ff ff ff ff ff ff ff ff I2C Hex Data: Address 0x00: 7f b0 01 ff 06 3c 01 08 00 00 00 00 00 00 00 00 Address 0x10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Address 0x20: 00 00 00 00 00 00 00 00 00 00 00 00 00 03 03 07
99
VoIP Interfaces
Address 0x30: d6 ff ff ff 34 01 05 05 02 ff ff ff Address 0x40: ff ff ff ff 00 00 00 00 00 00 00 00 Address 0x50: 53 47 2d 45 50 49 4d 2d 31 54 58 00 Address 0x60: 00 00 00 00 00 00 ff ff ff ff ff ff Address 0x70: ff ff ff ff ed c0 0e 0b 00 00 00 00 ANNEX REV 08 750-013493 NB9161 Jedec Code: 0x7fb0 EEPROM Version: P/N: 750-013493 S/N: Assembly ID: 0x0808 Assembly Version: Date: 03-03-2006 Assembly Flags: Version: REV 08 ID: Integrated Services FRU Model Number: Board Information Record: Address 0x00: 34 01 05 05 02 ff ff ff ff ff ff ff I2C Hex Data: Address 0x00: 7f b0 01 ff 08 08 01 08 52 45 56 20 Address 0x10: 00 00 00 00 37 35 30 2d 30 31 33 34 Address 0x20: 53 2f 4e 20 4e 42 39 31 36 31 00 00 Address 0x30: d6 ff ff ff 34 01 05 05 02 ff ff ff Address 0x40: ff ff ff ff 01 00 00 00 00 00 00 00 Address 0x50: 53 47 2d 45 50 49 4d 2d 31 54 58 00 Address 0x60: 00 00 00 00 00 00 ff ff ff ff ff ff Address 0x70: ff ff ff ff ff ff ff ff ff ff ff ff
ff 00 00 ff 00
ff 00 00 ff 00
ff ff 00 53 00 00 ff ff 00 00 Integrated Services
0x01 S/N NB9161 01.08 0x00 SSG-EPIM-1TX ff ff ff ff 30 39 00 ff 00 00 ff ff 38 33 03 ff 00 00 ff ff 00 00 03 ff 00 00 ff ff 00 00 07 ff 53 00 ff ff
Sample Output
show chassis hardware models (SRX5600 and SRX5800 devices)
user@host> show chassis hardware models Hardware inventory: Item Version Part number Midplane REV 03 710-013698 FPM Board REV 03 710-014974 Routing Engine 0 REV 06 740-015113 CB 0 REV 07 710-013385
Serial number TR0779 KC3406 1000696955 JZ3257
FRU model number CHAS-BP-MX960-S CRAFT-MX960-S RE-S-1300-2048-S SCB-MX960-S
Sample Output
show chassis hardware clei-models (SRX5600 and SRX5800 devices)
user@host> show chassis hardware clei-models Hardware inventory: Item Version Part number CLEI code FPM Board REV 02 710-017254 Routing Engine 0 REV 06 740-015113 CB 0 REV 07 710-013385 Fan Tray
FRU model number CRAFT-MX480-S RE-S-1300-2048-S SCB-MX960-S SRX5600-FAN
100
show interfaces (View J Series and SRX Series)

Syntax
show interfaces < interface-name > <extensive | terse>
Release Information Description
Command modified in Release 9.5 of Junos OS. Display status information and statistics about interfaces on J Series and SRX Series devices running Junos OS. On SRX Series devices, on configuring identical IPs on a single interface, you will not see a warning message; instead, you will see a syslog message.
Options
interface-name (Optional) Display standard information about the specified interface.
Following is a list of typical interface names. Replace pim with the PIM slot and port with the port number. For a complete list, see the Junos OS Interfaces Configuration Guide for Security Devices.

at- pim/0/portATM-over-ADSL or ATM-over-SHDSL interface. br-pim/0/portBasic Rate Interface for establishing ISDN connections. ce1-pim/0/ portChannelized E1 interface. cl-0/0/83G wireless modem interface for SRX210 devices. ct1-pim/0/portChannelized T1 interface. dl0Dialer Interface for initiating ISDN and USB modem connections. e1-pim/0/portE1 interface. e3-pim/0/portE3 interface. fe-pim/0/portFast Ethernet interface. ge-pim/0/portGigabit Ethernet interface. se-pim/0/portSerial interface. t1-pim/0/portT1 (also called DS1) interface. t3-pim/0/portT3 (also called DS3) interface. wx-slot/0/0WAN acceleration interface, for the WXC Integrated Services Module
(ISM 200).
extensive | terse(Optional) Display the specified level of output.
Required Privilege Level
view
101
VoIP Interfaces
Related Documentation List of Sample Output
Junos OS Interfaces Command Reference
show interfaces Gigabit Ethernet on page 102 show interfaces extensive (Gigabit Ethernet) on page 103 show interfaces terse on page 104 show interfaces extensive (WAN Acceleration) on page 104 show interfaces extensive (3G Wireless Modem) on page 106 Table 27 on page 102 lists the output fields for the show interfaces command. Output fields are listed in the approximate order in which they appear.
Output Fields
Table 27: show interfaces Output Fields

Field Name
Allowed host inbound traffic Traffic statistics Local statistics Transit statistics Flow input statistics Flow output statistics Flow error statistics Admin
Field Description
The allowed traffic through the interface. Number of packets and bytes transmitted and received on the physical interface. Number of packets and bytes transmitted and received on the physical interface. Number of packets and bytes transiting the physical interface. Statistics on packets received by flow module. Statistics on packets sent by flow module. Statistics on errors in the flow module. The interface is enabled (up) or disabled (down).
Sample Output
show interfaces Gigabit Ethernet
user@host> show interfaces ge-0/0/1.0 Logical interface ge-0/0/1.0 (Index 67) (SNMP ifIndex 36) Flags: Device-Down SNMP-Traps Encapsulation: ENET2 Protocol inet, MTU: 1500 Flags: None Addresses, Flags: Dest-route-down Is-Preferred Is-Primary Destination: 4.4.4/24, Local: 4.4.4.254, Broadcast: 4.4.4.255 Security: Zone: Untrust, ident-reset: on Allowed host-inbound traffic: bfd bgp bootp dhcp dvmrp finger ftp http https ike ident-reset igmp ldp mld msdp netconf ospf ospf3 pgm pim ping rip ripng rlogin router-discovery rpm rsh rsvp sap snmp snmp-trap ssh telnet traceroute vrrp xnm-clear xnm-sslshow interfaces <interface-name> extensive
102
Sample Output
show interfaces extensive (Gigabit Ethernet)
user@host> show interfaces ge-0/0/1.0 extensive Logical interface ge-0/0/1.0 (Index 67) (SNMP ifIndex 37) (Generation 134) Flags: SNMP-Traps VLAN-Tag [ 0x8100.100 ] Encapsulation: ENET2 Traffic statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Input bytes : IPv6 0 Output bytes : IPv6 0 Input packets: IPv6 0 Output packets: IPv6 0 Local statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Input bytes : IPv6 0 Output bytes : IPv6 0 Input packets: IPv6 0 Output packets: IPv6 0 Transit statistics: Input bytes : 0 0 bps Output bytes : 0 0 bps Input packets: 0 0 pps Output packets: 0 0 pps Input bytes : IPv6 0 Output bytes : IPv6 0 Input packets: IPv6 0 Output packets: IPv6 0 Flow statistics: Flow input statistics: Self packets : 0 ICMP packets : 113 VPN packets : 0 Bytes permitted by policy: 0 Connections established: 11 Flow output statistics: Multicast packets : 0 Bytes permitted by policy: 0 Flow error statistics (Packets dropped due to): Policy denied: 0 No parent for a gate: 0 Syn-attack protection: 0 Incoming NAT errors: 0 No session found: 0 No more sessions: 0 Invalid zone received packet: 0 User authentication errors: 0 Multiple user authentications: 0 Multiple Incoming NAT: 0 Address spoofing: 0 No zone or NULL zone binding 0 No NAT gate: 0 No minor session: 0 No session for a gate: 0 TCP sequence number out of window: 0
103
VoIP Interfaces
No Route present: 0 Authentication failed: 0 Security association not active: 0 No SA for incoming SPI: 0 No one interested in self packets: 0 Protocol inet, MTU: 1500, Generation: 139, Route table: 0 Flags: None Addresses, Flags: None Destination: Unspecified, Local: 2.2.2.2, Broadcast: Unspecified, Generation: 137 Addresses, Flags: Primary Is-Primary Destination: Unspecified, Local: 3.3.3.3, Broadcast: Unspecified, Generation: 139
Sample Output
show interfaces terse
user@host> show interfaces terse Interface Admin ge-0/0/0 up ge-0/0/0.0 up gr-0/0/0 up ip-0/0/0 up st0 up st0.1 up ls-0/0/0 up lt-0/0/0 up mt-0/0/0 up pd-0/0/0 up pe-0/0/0 up e3-1/0/0 up t3-2/0/0 up e1-3/0/0 up se-4/0/0 up t1-5/0/0 up br-6/0/0 up dc-6/0/0 up dc-6/0/0.32767 up bc-6/0/0:1 down bc-6/0/0:1.0 up dl0 up dl0.0 up dsc up gre up ipip up lo0 up lo0.16385 up lsi mtun pimd pime pp0 up up up up up Link Proto up up inet up up up ready inet up up up up up up up up down up up up up up down up up inet up up up up up inet up up up up up Local 10.209.4.61/18 Remote
10.0.0.1 10.0.0.16
--> 0/0 --> 0/0
Sample Output
show interfaces extensive (WAN Acceleration)
user@host> show interfaces wx-6/0/0 extensive Physical interface: wx-6/0/0, Enabled, Physical link is Up Interface index: 142, SNMP ifIndex: 41, Generation: 143 Type: PIC-Peer, Link-level type: PIC-Peer, MTU: 1522, Clocking: Unspecified, Speed: 1000mbps
104
Device flags : Present Running Interface flags: Point-To-Point Promiscuous SNMP-Traps Internal: 0x4000 Link type : Full-Duplex Link flags : None Physical info : Unspecified Hold-times : Up 0 ms, Down 0 ms Current address: Unspecified, Hardware address: Unspecified Alternate link address: Unspecified Last flapped : 2007-08-01 05:19:35 UTC (02:12:04 ago) Statistics last cleared: Never Traffic statistics: Input bytes : 58427 0 bps Output bytes : 115078 0 bps Input packets: 847 0 pps Output packets: 972 0 pps Input errors: Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards: 0, Resource errors: 0 Output errors: Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors: 0 Logical interface wx-6/0/0.0 (Index 68) (SNMP ifIndex 43) (Generation 135) Flags: Point-To-Point SNMP-Traps Encapsulation: PIC-Peering Security: Zone: wx-zone Allowed host-inbound traffic : any-service bootp bfd bgp dns dvmrp igmp ldp msdp nhrp ospf pgm pim rip router-discovery rsvp sap vrrp dhcp finger ftp tftp ident-reset http https ike netconf ping rlogin rpm rsh snmp snmp-trap ssh telnet traceroute xnm-clear-text xnm-ssl Flow Statistics : Flow Input statistics : Self packets : 0 ICMP packets : 0 VPN packets : 0 Bytes permitted by policy : 70137 Connections established : 4 Flow Output statistics: Multicast packets : 0 Bytes permitted by policy : 2866 Flow error statistics (Packets dropped due to): Address spoofing: 0 Authentication failed: 0 Incoming NAT errors: 0 Invalid zone received packet: 0 Multiple user authentications: 0 Multiple incoming NAT: 0 No parent for a gate: 0 No one interested in self packets: 0 No minor session: 0 No more sessions: 0 No NAT gate: 0 No route present: 0 No SA for incoming SPI: 0 No tunnel found: 0 No session for a gate: 0 No zone or NULL zone binding 0 Policy denied: 0 Security association not active: 0 TCP sequence number out of window: 0 Syn-attack protection: 0 User authentication errors: 0 Protocol inet, MTU: 1500, Generation: 141, Route table: 0
105
VoIP Interfaces
Flags: None Addresses, Flags: Is-Preferred Is-Primary Destination: 10.87.13.2, Local: 3.3.3.3, Broadcast: Unspecified, Generation: 142
Sample Output
show interfaces extensive (3G Wireless Modem)
user@host> show interfaces cl-0/0/8 extensive Physical interface: cl-0/0/8, Enabled, Physical link is Up Interface index: 67, SNMP ifIndex: 25, Generation: 4 Type: Async-Serial, Link-level type: PPP-Subordinate, MTU: 1504, Clocking: Unspecified, Speed: MODEM Device flags : Present Running Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000 Link flags : None Hold-times : Up 0 ms, Down 0 ms CoS queues : 8 supported, 8 maximum usable queues Last flapped : Never Statistics last cleared: Never Traffic statistics: Input bytes : 0 0 bps Output bytes : 868 0 bps Input packets: 0 0 pps Output packets: 16 0 pps Input errors: Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards: 0, Resource errors: 0 Output errors: Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors: 0 Egress queues: 8 supported, 4 in use Queue counters: Queued packets Transmitted packets Dropped packets 0 best-effort 6 6 1 expedited-fo 0 0 2 assured-forw 0 0 3 network-cont 10 10 MODEM status: Modem type : Sierra-USB-3G Data/Fax Modem Version Initialization command string : ATS0=2 Initialization status : Ok Call status : Connected to 14591 Call duration : 134316 seconds Call direction : Dialout Baud rate : <x> bps 0 0 0 0 2.27m
106
show interfaces flow-statistics

Syntax Release Information Description Options
show interfaces flow-statistics <interface-name>
Command introduced in Release 8.5 of Junos OS. Display interfaces flow statistics.
Interface-name (Optional) Display flow statistics about the specified interface. Following
is a list of typical interface names. Replace pim with the PIM slot and port with the port number. For a complete list, see the Junos OS Interfaces Configuration Guide for Security Devices.

at-pim/0/portATM-over-ADSL or ATM-over-SHDSL interface. br-pim/0/portBasic Rate Interface for establishing ISDN connections. ce1-pim/0/portChannelized E1 interface. ct1-pim/0/portChannelized T1 interface. dl0Dialer Interface for initiating ISDN and USB modem connections. e1-pim/0/portE1 interface. e3-pim/0/portE3 interface. fe-pim/0/ portFast Ethernet interface. ge-pim/0/portGigabit Ethernet interface. se-pim/0/portSerial interface. t1-pim/0/portT1 (also called DS1) interface. t3-pim/0/ portT3 (also called DS3) interface. wx-slot/0/0WAN acceleration interface, for the WXC Integrated Services Module
(ISM 200). Required Privilege Level List of Sample Output Output Fields view
show interfaces flow-statistics (Gigabit Ethernet) on page 110 Table 28 on page 107 lists the output fields for the show interfaces flow-statistics command. Output fields are listed in the approximate order in which they appear.
Table 28: show interfaces flow-statistics Output Fields

Field Name
Traffic statistics Local statistics
Field Description
Number of packets and bytes transmitted and received on the physical interface. Number of packets and bytes transmitted and received on the physical interface.
107
VoIP Interfaces
Table 28: show interfaces flow-statistics Output Fields (continued)

Field Name
Transit statistics Flow input statistics Flow output statistics Flow error statistics
Field Description
Number of packets and bytes transiting the physical interface. Statistics on packets received by flow module. Statistics on packets sent by flow module. Packet drop statistics for the flow module. For further detail, see Table 29 on page 108
Table 29: Flow Error Statistics (packet drop statistics for the flow module)
Error Screen:
Address spoofing Syn-attack protection The packet was dropped when the screen module detected address spoofing. The packet was dropped because of SYN attack protection or SYN cookie protection.
Error Description
VPN:
Authentication failed The packet was dropped because the IPsec Encapsulating Security Payload (ESP) or Authentication Header (AH) authentication failed. The packet was dropped because the incoming IPsec packet's security parameter index (SPI) does not match any known SPI. The packet was dropped because an IPsec packet was received for an inactive SA.
No SA for incoming SPI
Security association not active
NAT:
Incoming NAT errors The source NAT rule search failed, an invalid source NAT binding was found, or the NAT allocation failed. Sometimes packets are looped through the system more than once; if source NATing is specified more than once, the packet will be dropped.
Multiple incoming NAT
Auth:
Multiple user authentications Sometimes packets are looped through the system more than once. Each time a packet passes through the system, that packet must be permitted by a policy. If the packet matches more than one policy that specifies user authentication, then it will be dropped. Packet was dropped because policy requires authentication; however:

User authentication errors
Only Telnet, FTP, and HTTP traffic can be authenticated. The corresponding authentication entry could not be found, if web-auth is specified. The maximum number of authenticated sessions per user was exceeded.
Flow:
108
Table 29: Flow Error Statistics (packet drop statistics for the flow module) (continued)
No one interested in self packets This counter is incremented for one of the following reasons:
The outbound interface is a self interface, but the packet is not marked as a to-self packet and the destination address is in a source NAT pool. No service is interested in the to-self packet When a zone has ident-reset service enabled, the TCP RST to IDENT request for port 113 is sent back and this counter is incremented.
No minor session
The packet was dropped because no minor sessions are available and a minor session was requested. Minor sessions are allocated for storing additional TCP state information. The packet was dropped because there were no more free sessions available. The packet was dropped because a valid route was not available to forward the packet. For new sessions, the counter is incremented for one of the following reasons:

No more sessions No route present
No valid route was found to forward the packet. A discard or reject route was found. The route could not be added due to lack of memory. The reverse path forwarding check failed for an incoming multicast packet.
For existing sessions, the prior route was changed or deleted, or a more specific route was added. The session is rerouted, and this reroute could fail because:
A new route could not be found; either the previous route was removed, or the route was changed to discard or reject. Multiple packets may concurrently force rerouting to occur, and only one packet can successfully complete the rerouting process. Other packets will be dropped. The route table was locked for updates by the routing engine. Packets that match a new session are retried, whereas packets that match an existing session are not.
No tunnel found No session for a gate
The packet was dropped because a valid tunnel could not be found This counter is incremented when a packet is destined for an ALG, and the ALG decides to drop this packet. The packet was dropped because its incoming interface was not bound to any zone. The error counter is incremented for one of the following reasons:

No zone or NULL zone binding Policy denied
Source and/or destination NAT has occurred and policy says to drop the packet. Policy specifies user authentication, which failed. Policy was configured to deny this packet.
TCP sequence number out of window
A TCP packet with a sequence number failed the TCP sequence number check that was received.
Counters Not Currently in Use

No parent for a gate Invalid zone received packet -
109
VoIP Interfaces
Table 29: Flow Error Statistics (packet drop statistics for the flow module) (continued)
No NAT gate -
Sample Output
show interfaces flow-statistics (Gigabit Ethernet)
user@host> show interfaces flow-statistics ge-0/0/1.0 Logical interface ge-0/0/1.0 (Index 70) (SNMP ifIndex 49) Flags: SNMP-Traps Encapsulation: ENET2 Input packets : 5161 Output packets: 83 Security: Zone: zone2 Allowed host-inbound traffic : bootp bfd bgp dns dvmrp igmp ldp msdp nhrp ospf pgm pim rip router-discovery rsvp sap vrrp dhcp finger ftp tftp ident-reset http https ike netconf ping rlogin rpm rsh snmp snmp-trap ssh telnet traceroute xnm-clear-text xnm-ssl lsping Flow Statistics : Flow Input statistics : Self packets : 0 ICMP packets : 0 VPN packets : 2564 Bytes permitted by policy : 3478 Connections established : 1 Flow Output statistics: Multicast packets : 0 Bytes permitted by policy : 16994 Flow error statistics (Packets dropped due to): Address spoofing: 0 Authentication failed: 0 Incoming NAT errors: 0 Invalid zone received packet: 0 Multiple user authentications: 0 Multiple incoming NAT: 0 No parent for a gate: 0 No one interested in self packets: 0 No minor session: 0 No more sessions: 0 No NAT gate: 0 No route present: 0 No SA for incoming SPI: 0 No tunnel found: 0 No session for a gate: 0 No zone or NULL zone binding 0 Policy denied: 0 Security association not active: 0 TCP sequence number out of window: 0 Syn-attack protection: 0 User authentication errors: 0 Protocol inet, MTU: 1500 Flags: None Addresses, Flags: Is-Preferred Is-Primary Destination: 2.2.2/24, Local: 2.2.2.2, Broadcast: 2.2.2.255
110
show interfaces statistics (View)

Syntax Release Information Description Required Privilege Level List of Sample Output
show interfaces statistics interface-name
Command introduced in Release 10.1 of Junos OS. Displays the interface input and output statistics for physical and logical interface. view
show interfaces statistics on page 111
Sample Output
show interfaces statistics
user@host> show interfaces statistics st0.1 Logical interface st0.1 (Index 91) (SNMP ifIndex 268) Flags: Point-To-Point SNMP-Traps Encapsulation: Secure-Tunnel Input packets : 2743333 Output packets: 6790470992 Security: Zone: untrust Allowed host-inbound traffic : bootp bfd bgp dns dvmrp igmp ldp msdp nhrp ospf pgm pim rip router-discovery rsvp sap vrrp dhcp finger ftp tftp ident-reset http https ike netconf ping reverse-telnet reverse-ssh rlogin rpm rsh snmp snmp-trap ssh telnet traceroute xnm-clear-text xnm-ssl lsping ntp sip Protocol inet, MTU: 9192 Addresses, Flags: Is-Preferred Is-Primary Destination: 192.167.1.0/30, Local: 192.167.1.1
111
VoIP Interfaces
112
PART 4
Troubleshooting
TGM550 Module Troubleshooting on page 115
113
VoIP Interfaces
114
CHAPTER 15
TGM550 Module Troubleshooting
TGM550 Module and VoIP Interface Troubleshooting on page 115
TGM550 Module and VoIP Interface Troubleshooting

Problem The TGM550 module is installed but the VoIP interface is unavailable. The TGM550 module is installed and the VoIP interfacefor example, vp-3/0/0 is configured, but the interface is not accessible. The show chassis hardware command displays the TGM550 installed on slot 3. However, the show interfaces terse command does not display the vp-3/0/0 interface, and the show interfaces vp-3/0/0 command displays an error:
user@host> show interfaces vp-3/0/0 error: device vp-3/0/0 not found
Solution
The VoIP interface might be unavailable because the TGM550 firmware version is not compatible with the Junos OS version installed on the device. To correct the TGM550 firmware and Junos OS version compatibility error:
1.
Check the router's system log messages for a version incompatibility error similar to the following:
Jan 5 11:07:03 host fwdd[2857]: TGMT: RE (1.0) - TGM (2.0) major protocol version mismatch: not marking TGM slot ready
2. If the error exists, connect to the TGM550 through the console port. 3. View the TGM550 firmware version. TGM550-003(super)# show image version Bank Version ----------- ------A (current) 26.23.0 B 26.22.0
In this example, the current TGM550 firmware version is 26.23.0.

4. Identify the Junos OS version that is compatible with the current TGM550 firmware
version.
5. Upgrade the router with the compatible Junos OS version.
115
VoIP Interfaces
Junos OS Feature Support Reference for SRX Series and J Series Devices Communication Manager Software & Firmware Compatibility Matrix at
Avaya VoIP Modules Overview on page 5 Avaya VoIP Modules Configuration Overview on page 55 Understanding the TGM550 Telephony Gateway Module on page 17 Avaya IG550 Integrated Gateway Overview on page 11 Example: Configuring VoIP Interfaces on page 58
116
PART 5
Index
Index on page 119
117
VoIP Interfaces
118
Index
Symbols
#, comments in configuration statements...................xiv ( ), in syntax descriptions....................................................xiv < >, in syntax descriptions...................................................xiv [ ], in configuration statements........................................xiv { }, in configuration statements........................................xiv | (pipe), in syntax descriptions..........................................xiv
A
ACT LED......................................................................................25 TIM508..............................................................................30 TIM510................................................................................33 TIM514................................................................................37 TIM516................................................................................42 TIM518...............................................................................49 TIM521................................................................................52 activation priority description.........................................................................15 activation-priority statement............................................80 adapter, console port TGM550.............................................................................19 ALM LED.....................................................................................25 TIM508..............................................................................30 TIM510................................................................................33 TIM514................................................................................37 TIM516................................................................................42 TIM518...............................................................................49 TIM521................................................................................52 analog media module See TIM514 analog telephone (LINE) ports TGM550, pinouts............................................................22 TIM508, possible configurations.............................29 TIM514, pinouts..............................................................36 TIM514, possible configurations...............................37 TIM516, possible configurations...............................42 TIM518, possible configurations..............................48 analog trunk (TRUNK) ports TGM550, pinouts............................................................22 TIM508, possible configurations.............................29 TIM514, pinouts..............................................................36 TIM514, possible configurations...............................37
TIM516, possible configurations...............................42 TIM518, possible configurations..............................48 ASB LED......................................................................................25 Avaya Communication Manager (CM) CAC-BL requirement for WANs.................................16 description.........................................................................14 Avaya IG550 Integrated Gateway See Avaya VoIP modules Avaya Communication Manager (CM)...................14 Avaya manuals, list of...................................................13 description..........................................................................11 See also Avaya VoIP modules dynamic CAC See dynamic CAC TGM550Junos OS compatibility............................18 Avaya Media Gateway Controller (MGC) Avaya Communication Manager (CM)...................14 Avaya manuals, list of...................................................13 description..........................................................................11 dynamic CAC See dynamic CAC MGC list...............................................................................13 See also MGC list supported models..........................................................13 Avaya MGC See Avaya Media Gateway Controller Avaya VoIP Avaya Communication Manager (CM)...................14 Avaya manuals, list of...................................................13 Avaya Media Gateway Controllers supported......................................................................13 bandwidth management See dynamic CAC disk-on-key configuration...........................................56 dynamic CAC See dynamic CAC EPW configuration........................................................56 interfaces.............................................................................11 See also Avaya VoIP modules IP addressing guidelines..............................................18 modules See Avaya VoIP modules network................................................................................6 TGM550Junos OS compatibility............................18 troubleshooting..............................................................115 typical topology................................................................6 version incompatibility, correcting..........................115 Avaya VoIP modules accessing the router from..........................................90 administration.................................................................20 Avaya CLI access............................................................20 Avaya Communication Manager (CM)...................14 Avaya manuals, list of...................................................13 CLI access requirements.............................................20 console connection.......................................................87
119
VoIP Interfaces
disk-on-key configuration...........................................56 dynamic CAC See dynamic CAC grounding, 10 AWG replacement cable....................5 interface types...................................................................11 Junos OS configurability...............................................12 LEDs See LEDs non-hot-swappability...............................................5, 12 overview...............................................................................11 requirements.......................................................................7 resetting TGM550.........................................................90 saving the configuration...............................................91 SSH connection.............................................................88 summary..............................................................................8 Telnet access..................................................................89 TGM550..............................................................................17 TGM550 IP address, setting (configuration editor)...............................................................................6 TGM550 maximum gateway capacities...............23 TGM550Junos OS compatibility............................18 TIM508...............................................................................27 TIM510.................................................................................31 TIM514................................................................................35 TIM516................................................................................39 TIM518................................................................................45 TIM521.................................................................................51
C
cables Avaya VoIP 10 AWG replacement grounding cable..................................................................................5 TGM550 analog pinouts..............................................22 TGM550 console port, DB-9 connector pinouts............................................................................21 TGM550 console port, RJ-45 connector pinouts............................................................................21 TIM508 pinout................................................................28 TIM510 E1/T1 pinouts....................................................32 TIM514 analog pinouts................................................36 TIM516 pinouts...............................................................40 TIM518 pinouts...............................................................46 CAC See dynamic CAC CAC-BL requirement for dynamic CAC...........................16 call admission control See dynamic CAC Call Admission Control: Bandwidth Limitation (CAC-BL), requirement for dynamic CAC..................16 CLI Avaya VoIP..........................................................................6 VoIP........................................................................................6 CLI, Avaya VoIP, accessing..................................................20 CM, Avaya See Avaya Communication Manager comments, in configuration statements.......................xiv Communication Manager (CM), Avaya See Avaya Communication Manager connector pinouts TIM508 ports..................................................................28 TIM516 ports....................................................................40 TIM518 ports....................................................................46 console port adapter (TGM550)........................................................19 on TGM550, DB-9 connector pinouts.....................21 on TGM550, RJ-45 connector pinouts....................21 console port connection to TGM550..............................87 conventions text and syntax................................................................xiii copy running-config startup-config command...........91 curly braces, in configuration statements.....................xiv customer support....................................................................xv contacting JTAC...............................................................xv
B
bandwidth for Avaya VoIP, managing See dynamic CAC BBL (bearer bandwidth limit) description.........................................................................15 reported (RBBL), description.....................................16 bearer bandwidth limit See BBL bearer-bandwidth-limit statement..................................81 blinking TIM508 ACT (active) LED state..............................30 TIM514 ACT (active) LED state.................................37 TIM516 ACT (active) LED state................................42 TIM518 ACT (active) LED state................................49 braces, in configuration statements................................xiv brackets angle, in syntax descriptions.....................................xiv square, in configuration statements.......................xiv BRI media module See TIM521
D
DB-9 connector pinouts TGM550 console port...................................................21 device Avaya VoIP module overview.......................................5
120
Index
diagnosis VoIP interface..................................................................115 DID on line ports........................................................27, 35, 45 direct inward dialing, on line ports.....................27, 35, 45 disk-on-key configuration description........................................................................56 procedure..........................................................................57 requirements...................................................................56 RESET CONFIG button caution................................57 documentation comments on...................................................................xv dynamic CAC activation priority, description....................................15 BBL, description...............................................................15 CAC-BL requirement for WANs.................................16 overview..............................................................................15 supported interfaces......................................................15 dynamic call admission control See dynamic CAC dynamic-call-admission-control statement...............82
grounding Avaya VoIP 10 AWG replacement cable..................5
H
hardware Avaya VoIP module overview.......................................5 hardware features Avaya VoIP modules........................................................5
I
IG550 Integrated Gateway See Avaya IG550 Integrated Gateway; Avaya VoIP modules See Avaya VoIP modules interfaces Avaya VoIP..........................................................................11 See also Avaya VoIP modules supported for dynamic CAC, for Avaya VoIP..................................................................................15 See also dynamic CAC VoIP.......................................................................................11 See also Avaya VoIP modules Interfaces Configuration Statement Hierarchy............67 IP addresses Avaya VoIP module, guidelines for...........................18 TGM550, guidelines for................................................18 ip telnet port command.......................................................89 ip telnet-client command...................................................89 ISDN BRI ports for TIM521 See TIM521
E
E1 trunk ports, TIM510 description.........................................................................31 pinouts................................................................................32 E1/T1 media module See TIM508 See TIM510 See TIM516 See TIM518 Electronic Preinstallation Worksheet (EPW), for Avaya VoIP configuration................................................56 See also EPW configuration EPW (Electronic Preinstallation Worksheet) configuration description........................................................................56 procedure..........................................................................57 requirements...................................................................56 RESET CONFIG button caution................................57 Ethernet cable TGM550 console DB-9 connector pinouts...........21 TGM550 console, RJ-45 connector pinouts.........21 ETR LED......................................................................................25
J
J Series Avaya VoIP connectivity.................................................5 Avaya VoIP modules........................................................5 J2320 Avaya VoIP modules........................................................5 TGM550..............................................................................17 TIM508...............................................................................27 TIM510.................................................................................31 TIM514................................................................................35 TIM516................................................................................39 TIM518................................................................................45 TIM521.................................................................................51 J2350 Avaya VoIP modules........................................................5 TGM550..............................................................................17 TIM508...............................................................................27 TIM510.................................................................................31 TIM514................................................................................35
F
family bridge statement.......................................................83 FAQ (frequently asked questions) Why is the VoIP interface unavailable?................115 font conventions.....................................................................xiii
G
Gateway Module See TGM550
121
VoIP Interfaces
TIM516................................................................................39 TIM518................................................................................45 TIM521.................................................................................51 J4300 TGM550..............................................................................17 TIM508...............................................................................27 TIM510.................................................................................31 TIM514................................................................................35 TIM516................................................................................39 TIM518................................................................................45 TIM521.................................................................................51 J4350 Avaya VoIP modules........................................................5 J4350 routers Avaya VoIP connectivity.................................................5 J6300 TGM550..............................................................................17 TIM508...............................................................................27 TIM510.................................................................................31 TIM514................................................................................35 TIM516................................................................................39 TIM518................................................................................45 TIM521.................................................................................51 J6350 Avaya VoIP modules........................................................5 J6350 routers Avaya VoIP connectivity.................................................5 Junos operating system (Junos OS) Avaya VoIP configurability with.................................12 Avaya VoIP connectivity.................................................5 TGM550 firmware compatibility with....................18
ETR (emergency transfer relay)...............................25 SIG (signal)......................................................................33 TGM550 port status.....................................................25 TIM508 link status........................................................30 TIM510 link status..........................................................33 TIM514 link status...........................................................37 TIM516 link status..........................................................42 TIM518 link status..........................................................49 TIM521 link status...........................................................52 TST (test)..........................................................................33 LINE and TRUNK ports, on Avaya VoIP TGM550.........17 LINE ports, TIM514..................................................................35
M
manuals Avaya VoIP.........................................................................13 comments on...................................................................xv Media Gateway Controller See Avaya Media Gateway Controller; MGC list memory stick, USB, for Avaya VoIP configuration........................................................................56 MGC See Avaya Media Gateway Controller; MGC list MGC list overview..............................................................................13 See also Avaya VoIP
N
networks Avaya VoIP..........................................................................6 VoIP........................................................................................6 no ip telnet command..........................................................89 no ip telnet-client command.............................................90
L
LEDs ACT (TGM550 active)..................................................25 ACT (TIM508 active)...................................................30 ACT (TIM510 active).....................................................33 ACT (TIM514 active).....................................................37 ACT (TIM516 active).....................................................42 ACT (TIM518 active)....................................................49 ACT (TIM521 active).....................................................52 ALM (TGM550 alarm).................................................25 ALM (TIM508 alarm)...................................................30 ALM (TIM510 alarm).....................................................33 ALM (TIM514 alarm).....................................................37 ALM (TIM516 alarm).....................................................42 ALM (TIM518 alarm)....................................................49 ALM (TIM521 alarm).....................................................52 ASB (alternate software bank)................................25
P
parentheses, in syntax descriptions................................xiv password for TGM550 access.......................................................20 PIMs (Physical Interface Modules) Avaya VoIP modules See Avaya VoIP modules pinouts RJ-45 TGM550 console connector..........................21 TGM550 analog RJ-11 connector..............................22 TGM550 console DB-9 connector............................21 TGM550 console port...................................................21 TIM508..............................................................................28 TIM510 E1/T1 RJ-45.......................................................32 TIM514 analog RJ-11 connector.................................36
122
Index
TIM516...............................................................................40 TIM518...............................................................................46 ports Avaya VoIP..........................................................................11 See also Avaya VoIP modules console (TGM550).........................................................17 LINE and TRUNK, on Avaya VoIP TGM550...........17 telephone and trunk, on Avaya VoIP TGM550..........................................................................17 TGM550..............................................................................17 TIM510.................................................................................31 TIM514................................................................................35 TIM521.................................................................................51 VoIP.......................................................................................11 See also Avaya VoIP modules processes restarting...........................................................................94
T
T1 trunk ports, TIM510 description.........................................................................31 pinouts................................................................................32 T1/E1 media module See TIM508 See TIM510 See TIM516 See TIM518 technical support contacting JTAC...............................................................xv telephone and trunk ports, on Avaya VoIP TGM550...................................................................................17 Telephony Gateway Module See TGM550 Telephony Interface Module See TIM510; TIM514; TIM521 Telephony Interface Modules See TIM508; TIM510; TIM514; TIM516; TIM518; TIM521 Telnet access to TGM550 connecting to TGM550...............................................89 disabling Telnet service...............................................89 enabling Telnet service................................................89 overview............................................................................89 security caution..............................................................89 telnet command.....................................................................89 TGM550 accessing the router from..........................................90 administration.................................................................20 analog port pinouts.......................................................22 Avaya CLI access............................................................20 Avaya Media Gateway Controllers supported......................................................................13 CLI access requirements.............................................20 console connection.......................................................87 console port pinouts......................................................21 description.........................................................................17 interfaces............................................................................12 IP address, setting (configuration editor)...............6 IP addressing guidelines..............................................18 Junos OS compatibility.................................................18 maximum gateway capacities..................................23 MGCs supported..............................................................13 port LED states...............................................................25 ports......................................................................................17 resetting............................................................................90 RST (reset) button.........................................................91 saving the configuration...............................................91 SSH connection.............................................................88 Telnet access..................................................................89 Telnet connection to router.......................................90
R
RBBL See BBL reported bearer bandwidth limit See BBL request chassis fpc slot slot-number restart command...............................................................................91 restart command....................................................................94 restarting software processes.......................................................94 RJ-11 connector pinouts TGM550 analog ports..................................................22 TIM514 analog ports.....................................................36 RJ-45 connector pinouts TGM550 console port...................................................21 TIM510 E1/T1 ports........................................................32 RJ-45 to DB-9 serial port adapter TGM550 console port...................................................19 routing solutions managing VoIP bandwidth See dynamic CAC RST (reset) button, TGM550..............................................91
S
show chassis hardware command..................................96 show interfaces command................................................101 show interfaces flow-statistics command..................107 show interfaces statistics st0.1 command....................111 SIG LED.......................................................................................33 SSH connection to TGM550..............................................88 support, technical See technical support syntax conventions................................................................xiii
123
VoIP Interfaces
TIM508 connector port pinout..................................................28 description........................................................................27 port configurations........................................................29 ports, LED states............................................................30 TIM510 description.........................................................................31 E1 trunk ports....................................................................31 ports, LED states............................................................33 RJ-45 connector port pinouts....................................32 T1 trunk ports....................................................................31 TIM510 interfaces.....................................................................12 TIM514 analog port pinouts.......................................................36 analog telephone ports...............................................35 analog trunk ports.........................................................35 description........................................................................35 port configurations.........................................................37 ports, LED states.............................................................37 TIM514 interfaces.....................................................................12 TIM516 connector port pinouts................................................40 description........................................................................39 port configurations........................................................42 ports, LED states............................................................42 TIM518 connector port pinouts................................................46 description........................................................................45 port configurations........................................................48 ports, LED states............................................................49 TIM521 description.........................................................................51 ISDN BRI ports..................................................................51 ports, LED states............................................................52 TIM521 interfaces.....................................................................12 TIMs See TIM508; TIM510; TIM514; TIM516; TIM518; TIM521 topology Avaya VoIP..........................................................................6 VoIP........................................................................................6 troubleshooting Avaya VoIP.......................................................................115 TRUNK and LINE ports, on Avaya VoIP TGM550.........17 trunk ports, TIM508 pinouts...............................................................................28 TRUNK ports, TIM514............................................................35 trunk ports, TIM516 pinouts...............................................................................40
trunk ports, TIM518 pinouts...............................................................................46 TST LED......................................................................................33
U
URLs Avaya VoIP support........................................................13 USB memory stick, for Avaya VoIP configuration........................................................................56
V
Voice over Internet Protocol..................................................3 support table......................................................................3 voice over IP See Avaya VoIP See Avaya VoIP modules VoIP See Avaya VoIP modules See Voice over Internet Protocol VoIP (voice over IP) See Avaya VoIP; VoIP interface VoIP interface addressing guidelines....................................................18 correcting version incompatibility problem.........115 IP address, setting (configuration editor)...............6 naming convention.........................................................12 unavailability, correcting.............................................115 vp-0/0/0.....................................................................................12 See also VoIP interface
W
wireless LAN support table......................................................................3
124

VoIP Interfaces

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VoIP Interfaces

Uploaded by

Copyright:

Available Formats

Junos OS

Copyright 2012, Juniper Networks, Inc.

END USER LICENSE AGREEMENT

Copyright 2012, Juniper Networks, Inc.

Avaya VoIP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Avaya IG550 Integrated Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

TGM550 Telephony Gateway Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Copyright 2012, Juniper Networks, Inc.

TIM508 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

TIM510 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

TIM514 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

TIM516 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

TIM518 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

TIM521 BRI Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Copyright 2012, Juniper Networks, Inc.

Copyright 2012, Juniper Networks, Inc.

Copyright 2012, Juniper Networks, Inc.

TGM550 Telephony Gateway Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

TIM508 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

TIM510 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

TIM514 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

TIM516 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

TIM518 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

TIM521 BRI Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Copyright 2012, Juniper Networks, Inc.

Copyright 2012, Juniper Networks, Inc.

Avaya VoIP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Avaya IG550 Integrated Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

TGM550 Telephony Gateway Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

TIM508 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

TIM510 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

TIM514 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

TIM516 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

TIM518 Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Copyright 2012, Juniper Networks, Inc.

Table 24: LEDs for TIM518 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

TIM521 BRI Telephony Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Copyright 2012, Juniper Networks, Inc.

About the Documentation

Documentation and Release Notes

Using the Examples in This Manual

Copyright 2012, Juniper Networks, Inc.

Merging a Full Example

configuration mode command:

Copyright 2012, Juniper Networks, Inc.

About the Documentation

[edit] user@host# edit system scripts [edit system scripts]

Table 1: Notice Icons

Indicates a situation that might result in loss of data or hardware damage.

Alerts you to the risk of personal injury or death.

Alerts you to the risk of personal injury from a laser.

Table 2: Text and Syntax Conventions

Fixed-width text like this

Represents output that appears on the terminal screen.

user@host> show chassis alarms No alarms currently active

Copyright 2012, Juniper Networks, Inc.

Table 2: Text and Syntax Conventions (continued)

Italic text like this

Text like this

< > (angle brackets) | (pipe symbol)

stub <default-metric metric>; broadcast | multicast (string1 | string2 | string3)

rsvp { # Required for dynamic MPLS only

community name members [ community-ids ]