Using Multiservice Interface Modules - Juniper Networks

Using Multiservice Interface Modules
Published: 2012-08-20
Copyright © 2012, Juniper Networks, Inc.

Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Copyright © 2012, Juniper Networks, Inc. All rights reserved.
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.
Using Multiservice Interface Modules
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
Copyright © 2012, Juniper Networks, Inc.

Table of Contents
Part 1 Overview
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Chapter 1 Multiservice Interface Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Part 2 Configuration
CTP150 Multiservice Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
CTP2000 Multiservice Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Serial Multiservice Interface Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Audio Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4WTO Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
IRIG Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
TDC Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 2 Configuring Multiservice Port Parameters for CTP Bundles (CTPView) . . . 11
Configuring Multiservice Audio Mode Port Parameters for CTP Bundles
(CTPView) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Configuring Multiservice IRIG-B Mode Port Parameters for CTP Bundles
(CTPView) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Configuring Multiservice TDC Mode Parameters for CTP Bundles (CTPView) . . . 14
Configuring Multiservice 4WTO Mode Port Parameters for CTP Bundles
(CTPView) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 3 Configuring Multiservice Port Parameters for CTP Bundles (CTP
Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Copyright © 2012, Juniper Networks, Inc.
Configuring Multiservice Audio Mode Port Parameters for CTP Bundles (CTP
Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuring Multiservice IRIG-B Mode Port Parameters for CTP Bundles (CTP
Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configuring Multiservice TDC Mode Parameters for CTP Bundles (CTP
Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Configuring Multiservice 4WTO Mode Port Parameters for CTP Bundles (CTP
Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
iii

Using Multiservice Interface Modules
iv
Chapter 4 Configuring 4WTO Daughter Cards to Interoperate with Multiservice
Interface Modules (CTPView) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configuring 4WTO Daughter Cards to Interoperate with Multiservice Interface
Modules (CTPView) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Chapter 5 Configuring 4WTO Daughter Cards to Interoperate with Multiservice
Interface Modules (CTP Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Part 3 Index
Configuring 4WTO Daughter Cards to Interoperate with Multiservice Interface
Modules (CTP Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Copyright © 2012, Juniper Networks, Inc.

List of Figures
Part 1 Overview
Chapter 1 Multiservice Interface Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Copyright © 2012, Juniper Networks, Inc.
Figure 1: CTP150 Serial Multiservice Interface Module . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 2: CTP2000 Serial Multiservice Interface Module . . . . . . . . . . . . . . . . . . . . . 4
Figure 3: Cable Pinouts and Data Flow When the Multiservice Interface Module
Operates in Audio Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 4: Cable Pinouts and Data Flow When the Multiservice Interface Module
Operates in TDC Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
v

Using Multiservice Interface Modules
vi
Copyright © 2012, Juniper Networks, Inc.

List of Tables
Part 2 Configuration
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Chapter 2 Configuring Multiservice Port Parameters for CTP Bundles (CTPView) . . . 11
Table 3: CTP Bundle Multiservice Audio Port Parameter Settings in CTPView . . . . 11
Table 4: CTP Bundle Multiservice IRIG-B Port Parameter Settings in
CTPView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 5: CTP Bundle Multiservice TDC Port Parameter Settings in CTPView . . . . 15
Table 6: CTP Bundle Multiservice 4WTO Mode Port Parameter Settings in
CTPView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 3 Configuring Multiservice Port Parameters for CTP Bundles (CTP
Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Table 7: CTP Bundle Multiservice Audio Mode Port Parameter Settings in the
CTP Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table 8: CTP Bundle Multiservice IRIG-B Port Parameter Settings in the CTP
Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 9: CTP Bundle Multiservice TDC Port Parameter Settings in the CTP
Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 10: CTP Bundle Multiservice 4WTO Port Parameter Settings in the CTP
Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Chapter 4 Configuring 4WTO Daughter Cards to Interoperate with Multiservice
Interface Modules (CTPView) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 11: CTP Bundle 4WTO Interoperability Parameter Setting in CTPView . . . . 28
Chapter 5 Configuring 4WTO Daughter Cards to Interoperate with Multiservice
Interface Modules (CTP Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Copyright © 2012, Juniper Networks, Inc.
Table 12: CTP Bundle 4WTO Port Parameter Settings in the CTP Menu . . . . . . . . 30
vii

Using Multiservice Interface Modules
viii
Copyright © 2012, Juniper Networks, Inc.

About the Documentation
• Documentation and Release Notes on page ix
• Documentation Conventions on page ix
• Documentation Feedback on page xi
Documentation and Release Notes
Documentation Conventions
Copyright © 2012, Juniper Networks, Inc.
• Requesting Technical Support on page xi
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 .
Table 1 on page x defines notice icons used in this guide.
ix

Using Multiservice Interface Modules
Table 1: Notice Icons
Icon
Meaning
Informational note
Caution
Warning
Laser warning
Table 2: Text and Syntax Conventions
x
Convention
Bold text like this
Fixed-width text like this
Italic text like this
Italic text like this
Text like this
< > (angle brackets)
Description
Indicates important features or instructions.
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 on page x defines the text and syntax conventions used in this guide.
Description
Represents text that you type.
Represents output that appears on the
terminal screen.
• Introduces or emphasizes important
new terms.
• Identifies book names.
• Identifies RFC and Internet draft titles.
Represents variables (options for which
you substitute a value) in commands or
configuration statements.
Represents names of configuration
statements, commands, files, and
directories; configuration hierarchy levels;
or labels on routing platform
components.
Enclose optional keywords or variables.
Examples
To enter configuration mode, type
theconfigure command:
user@host> configure
user@host> show chassis alarms
No alarms currently active
• A policy term is a named structure
that defines match conditions and
actions.
• Junos OS System Basics Configuration
Guide
• RFC 1997, BGP Communities Attribute
Configure the machine’s domain name:
[edit]
root@# set system domain-name
domain-name
• 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.
stub ;
Copyright © 2012, Juniper Networks, Inc.

Table 2: Text and Syntax Conventions (continued)
Convention
| (pipe symbol)
# (pound sign)
[ ] (square brackets)
Indention and braces ( { } )
; (semicolon)
J-Web GUI Conventions
Bold text like this
> (bold right angle bracket)
Documentation Feedback
Description
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.
Represents J-Web graphical user
interface (GUI) items you click or select.
Separates levels in a hierarchy of J-Web
selections.
Examples
broadcast | multicast
(string1 | string2 | string3)
rsvp { # Required for dynamic MPLS only
community name members [
community-ids ]
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
• In the Logical Interfaces box, select
All Interfaces.
• To cancel the configuration, click
Cancel.
In the configuration editor hierarchy,
select Protocols>Ospf.
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
Requesting Technical Support
Copyright © 2012, Juniper Networks, Inc.
• Software release version (if applicable)
About the Documentation
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,
xi

Using Multiservice Interface Modules
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 policies—For 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 warranties—For product warranty information, visit
http://www.juniper.net/support/warranty/ .
• JTAC hours of operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
Self-Help Online Tools and Resources
Opening a Case with JTAC
xii
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/
• 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/
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 .
Copyright © 2012, Juniper Networks, Inc.

PART 1
Overview
Copyright © 2012, Juniper Networks, Inc.
• Multiservice Interface Module Overview on page 3
1

Using Multiservice Interface Modules
2
Copyright © 2012, Juniper Networks, Inc.

CHAPTER 1
Multiservice Interface Module Overview
CTP150 Multiservice Interface Module
Copyright © 2012, Juniper Networks, Inc.
• CTP150 Multiservice Interface Module on page 3
• CTP2000 Multiservice Interface Module on page 4
• Serial Multiservice Interface Module Overview on page 5
The Juniper Networks CTP150 Circuit to Packet platform optionally includes a Serial
Multiservice Interface module CTP150-IM-SER-MS. The module provides 4-KHz or high
quality analog audio, or interrange instrumentation group (IRIG) signals.
The multiservice card enables an IRIG time code (IRIG-B) signal to be transported through
an IP network. The IRIG-B standard consists of a family of rate-scaled serial time codes
with formats containing up to three coded expressions or words. The IRIG-B pulse code
contains one frame of 100 elements per second for the time of the year and GPS receiver
status. IRIG-B encodes day of year, hour, minute, and second data on a 1-KHz carrier
frequency, with an update rate of once per second.
NOTE: Only ports 0 and 2 (the bottom two ports) on the front of the serial
module can be used for the multiservice features. You can configure direction,
output high and low levels, and data range for this module.
The four-port serial interface module supports individual cabling for each port. The
CTP150 ports have small serial ports for HD-26 26-pin connectors (see Figure 1 on
page 3). The lowest-numbered port (marked 0) is at the bottom left, and the
highest-numbered port (marked 3) is at the top right.
Figure 1: CTP150 Serial Multiservice Interface Module
1
0
3
2
HD-26 26-pin
connectors
CLK
STATUS
Clock
connector
g004483
3

Using Multiservice Interface Modules
Related
Documentation
The software-selectable interfaces for the module on all ports are RS-232/V.24,
EIA530/X.21, EIA530A, V.35, and IRIG. Software-selectable rates range from 50 bps to
12.228 Mbps. On ports 0 and 2 there are also options for 4Khz (4WTO) analog, or high
quality analog.
The module also includes an external clock reference port for an HD-26 connector. Note
that only one external clock reference is required even if there are two interface modules,
serial or T1/E1.
•
NOTE: The external clock reference port must be the one in module slot 0,
the right-most slot in the front of the CTP150 chassis.
CTP150 Serial Interface Module
• Serial Multiservice Interface Module Overview on page 5
CTP2000 Multiservice Interface Module
4
Related
Documentation
The Juniper Networks CTP2000 Circuit to Packet platform optionally includes an 8-port
Serial Multiservice Interface module (CTP2000-IM-8p-MS) as shown in Figure 2 on
page 4.
Figure 2: CTP2000 Serial Multiservice Interface Module
CTP200 IM 8PIRIG
CTP2000 IM 8P MS
The cable used with the Serial Multiservice Interface module is CTP-CBL-4Q.
The module can operate in the following modes:
• Audio—Provides single and dual channel audio support for varying quality audio from
8-bit, 8-KHz quality to 8-bit up to 16-bit, 48-KHz quality (CD quality).
• 4WTO—Provides single and dual channel audio support for 8-bit, 8-KHz quality with
squelch support for radio backhaul. In 4WTO mode, the Multiservice interface module
is interoperable with 4WTO daughter cards.
• IRIG—Enables an interrange instrumentation group time code (IRIG-B) signal to be
transported through an IP network.
• TDC—Provides combined time-correlated support for IRIG/NRZ data for telemetry
applications.
The interface module is supported on CTP bundles; You use the bundles to configure
the modes of operation.
•
Serial Multiservice Interface Module Overview on page 5
g015452
Copyright © 2012, Juniper Networks, Inc.

Serial Multiservice Interface Module Overview
Audio Mode
CTP bundles are supported on the Serial Multiservice Interface module. CTP bundles on
Multiservice Interface modules can operate with the following modes:
• Audio—Provides single and dual channel audio support for varying quality audio from
8-bit, 8-KHz quality to 8-bit up to 16-bit, 48-KHz quality (CD quality).
• 4WTO—Provides single and dual channel audio support for 8-bit, 8-KHz quality with
squelch support for radio backhaul. In 4WTO mode, the Multiservice Interface module
is interoperable with 4WTO daughter cards.
• IRIG—Enables an interrange instrumentation group time code (IRIG-B) signal to be
transported through an IP network.
• TDC—Provides combined time-correlated support for IRIG/NRZ data for telemetry
applications.
Audio mode provides a high-quality audio (CD quality) interface. Audio mode supports
the following features:
• One or two simultaneous channels.
• Codec sampling rates up to 48 KHz.
• Optional μ-law encoding and decoding.
• Embedded frame requiring no additional bandwidth.
• Configurable output level from 0x to 2x.
• Signaling capability with talk squelch.
Figure 3 on page 5 shows the cable pinouts and the data flow when the Multiservice
Interface module operates in audio mode.
Figure 3: Cable Pinouts and Data Flow When the Multiservice Interface
Module Operates in Audio Mode
Pinouts
2
14
3
16
20
23
Pinouts
24
11
17
9
4
19
Copyright © 2012, Juniper Networks, Inc.
Audio input
Audio output
Squelch input
Audio input
Audio output
Squelch input
Audio codec
Audio codec
Dual channel only
Chapter 1: Multiservice Interface Module Overview
Framer
ST - 12.288 MHz
RT - 32.768 MHz
TT
RD
SD
Multiservice
Interface
Module
IP network
g015450
5

Using Multiservice Interface Modules
4WTO Mode
IRIG Mode
TDC Mode
6
The CTP 4-wire trunk only (4WTO) analog option provides encoding for one or two
analog voice channels into a single CTP IP data stream.
4WTO mode supports the following features:
• One or two simultaneous channels.
• Codec sampling rate of 8 KHz.
• Optional μ-law encoding.
• Signaling capability with talk squelch.
• Configurable output level from 0x to 2x.
• Interoperability with a 4WTO daughter card. Interoperability is supported only on
daughter cards that have firmware revision 4 or later. You enable interoperability in
the 4WTO daughter card configuration by setting MS interwork to enabled.
The Multiservice Interface module enables an interrange instrumentation group time
code (IRIG-B) signal to be transported through an IP network. The IRIG-B standard
consists of a family of rate-scaled serial time codes with formats containing up to three
coded expressions or words. The IRIG-B pulse code contains one frame of 100 elements
per second for the time of the year and GPS receiver status. IRIG-B encodes day of year,
hour, minute, and second data on a 1-KHz carrier frequency, with an update rate of once
per second.
IRIG-B mode supports the following features:
• IRIG-B transported at rates between 1 Kbps and 25.5 Kbps.
• Configurable output level from 0 to 7.85 volts peak-to-peak based on a 50-ohm
termination.
Time domain correlation (TDC) mode supports special applications in which digital data
(NRZ) needs to be closely time correlated with a timing signal (IRIG-B). In TDC mode,
the IRIG-B signal is transported on an 8-KHz audio path, and the NRZ data is transported
using RTS/DTR (NRZ input) and CTS/DSR (NRZ output). Circuitry on the Multiservice
Interface module accepts these two streams and combines them into a single digital
data stream that is carried through the IP network in one direction, while making sure
that the time relationship between the two signals is closely maintained.
Here is a list of the features of the TDC transport function:
• IRIG-B transported at 8-KHz with 16-bit samples; that is, no companding.
• NRZ data rates supported from 0.5 KHz to 5000 KHz in 0.5 KHz steps.
Copyright © 2012, Juniper Networks, Inc.

• Embedded frame requiring no additional bandwidth.
• Configurable IRIG-B output level from 0x to 2x.
Figure 4 on page 7 shows the cable pinouts and the data flow when the Multiservice
Interface module operates in TDC mode.
Figure 4: Cable Pinouts and Data Flow When the Multiservice Interface
Module Operates in TDC Mode
Pinouts
2
14
20
23
4
19
Copyright © 2012, Juniper Networks, Inc.
Audio input
Data input
Clock input
Audio
codec
NRZ
rate
adapt
Framer
ST
RT
TT
RD
SD
Multiservice
Interface
Module
IP network
Chapter 1: Multiservice Interface Module Overview
Multiservice
Interface
Module
ST
RT
TT
RD
SD
Framer
Audio
codec
NRZ
rate
adapt
Audio output
Data output
Clock output
Pinouts
3
16
6
22
5
13
g015451
7

Using Multiservice Interface Modules
8
Copyright © 2012, Juniper Networks, Inc.

PART 2
Configuration
Copyright © 2012, Juniper Networks, Inc.
• Configuring Multiservice Port Parameters for CTP Bundles (CTPView) on page 11
• Configuring Multiservice Port Parameters for CTP Bundles (CTP Menu) on page 19
• Configuring 4WTO Daughter Cards to Interoperate with Multiservice Interface Modules
(CTPView) on page 27
• Configuring 4WTO Daughter Cards to Interoperate with Multiservice Interface Modules
(CTP Menu) on page 29
9

Using Multiservice Interface Modules
10
Copyright © 2012, Juniper Networks, Inc.

CHAPTER 2
Configuring Multiservice Port Parameters
for CTP Bundles (CTPView)
• Configuring Multiservice Audio Mode Port Parameters for CTP Bundles
(CTPView) on page 11
• Configuring Multiservice IRIG-B Mode Port Parameters for CTP Bundles
(CTPView) on page 13
• Configuring Multiservice TDC Mode Parameters for CTP Bundles (CTPView) on page 14
• Configuring Multiservice 4WTO Mode Port Parameters for CTP Bundles
(CTPView) on page 15
Configuring Multiservice Audio Mode Port Parameters for CTP Bundles (CTPView)
Before you begin:
• Log in to the CTPView software at least at the Net_Admin level.
• Connect the CTPView server to the CTP device for which you want to configure bundles.
To configure Multiservice audio mode port parameters using CTPView:
1. In the side pane, select Bundle > Configuration.
2. Run your mouse over the Display and Select an Existing Bundle bar.
3. In the table of bundles, select the bundle that you want to modify.
4. Under Bundle Options, configure the parameters as described in Table 3 on page 11
and click Click to Submit Bundle AND Port Changes.
Table 3: CTP Bundle Multiservice Audio Port Parameter Settings in CTPView
Field
Port Description
I/F Type
Function
Copyright © 2012, Juniper Networks, Inc.
Specifies a description for the port.
Specifies the daughter card as the interface type.
Your Action
Enter a description of up to 64 alphanumeric
characters. Do not use the following
characters:
( ; ' " ) ]
Select DCARD.
11

Using Multiservice Interface Modules
Table 3: CTP Bundle Multiservice Audio Port Parameter Settings in CTPView (continued)
12
Field
Multi-Service Mode
Audio Mode
Audio Channel
Audio Sample Rate
[ KHz ]
Audio μ-law
Encoding
Audio Squelch
Audio Channel 0
Output Level
Function
Specifies that the bundle will run in audio mode.
Specifies whether this end of the circuit provides clocking
or uses adaptive clocking.
If the CTP devices at both ends of the circuit are
synchronized, you can configure both ends as Master.
Specifies the channel or channels to enable.
Specifies the sample rate for audio circuits in kilohertz. The
sample rate determines the audio quality and the network
bandwidth needed. Higher sample rates create an IP data
flow that requires higher bandwidth.
8 KHz corresponds to standard toll quality voice.
48 KHz corresponds to CD quality audio.
Enables or disables μ-law encoding. Standard audio code
samples are 16 bits. If you enable μ-law encoding, the 16-bit
samples are converted to 8 bits, consuming half of the
bandwidth without significant audio degradation.
Enables or disables the active squelch function on the
circuit.
If enabled, specifies whether the squelch is active or
inactive.
The squelch function gates local audio output when DSR-A
(channel 0) or RTS-A (channel 1) inputs are active or
inactive.
Specifies the output level for channel 0.
Note the following information about the values:
• 0—There is no output.
• 128—Unity gain, which means there is no attenuation or
gain.
• 255—Gain is 2:1.
Your Action
Select Audio.
Select one:
• Master—This end of the circuit provides
clocking.
• Slave—This end of the circuit uses
adaptive clocking.
Select one:
• Channel 0—Enables only channel 0.
• Dual Channel—Enables both channel 0
and channel 1.
Select one:
• 8
• 12
• 16
• 24
• 32
• 48
Select one:
• DISABLED (16 bit samples)—Generates
16-bit audio samples.
• ENABLED (8 bit samples)—Generates
8-bit audio samples.
Select one:
• DISABLED—Disables the active squelch
function on the circuit (audio output is
always enabled).
• ENABLED/ACTIVE—Squelch input is
grounded and analog output is disabled.
• ENABLED/INACTIVE—No signal is applied
to the squelch input. Input is open and
analog output is possible.
Enter a number from 0 through 255.
Copyright © 2012, Juniper Networks, Inc.

Table 3: CTP Bundle Multiservice Audio Port Parameter Settings in CTPView (continued)
Field
Audio Channel 1
Output Level
Related
Documentation
Function
Specifies the output level for channel 1.
Note the following information about the values:
• 0—There is no output.
• 128—Unity gain, which means there is no attenuation or
gain.
• 255—Gain is 2:1.
•
Your Action
Serial Multiservice Interface Module Overview on page 5
Enter a number from 0 through 255.
Configuring Multiservice IRIG-B Mode Port Parameters for CTP Bundles (CTPView)
Before you begin:
• Log in to the CTPView software at least at the Net_Admin level.
• Connect the CTPView server to the CTP device for which you want to configure bundles.
To configure Multiservice IRIG-B mode port parameters using CTPView:
1. In the side pane, select Bundle > Configuration.
2. Run your mouse over the Display and Select an Existing Bundle bar.
3. In the table of bundles, select the bundle that you want to modify.
4. Under Bundle Options, configure the parameters as described in Table 4 on page 13
and click Click to Submit Bundle AND Port Changes.
Table 4: CTP Bundle Multiservice IRIG-B Port Parameter Settings in CTPView
Field
Port Description
I/F Type
Multi-Service
Mode
Function
Copyright © 2012, Juniper Networks, Inc.
Specifies a description for the port.
Specifies the daughter card as the interface type.
Specifies that the bundle will run in IRIG-B mode.
Chapter 2: Configuring Multiservice Port Parameters for CTP Bundles (CTPView)
Your Action
Enter a description of up to 64
alphanumeric characters. Do not use the
following characters:
( ; ' " ) ]
Select DCARD.
Select IRIG-B.
13

Using Multiservice Interface Modules
Table 4: CTP Bundle Multiservice IRIG-B Port Parameter Settings in CTPView (continued)
Field
IRIG-B Source
IRIG-B Data Rate
Output High
Volts Level
Output Low
Volts Level
Function
Specifies the direction of the circuit. Although the IP circuit
connection through the network is full duplex, an IRIG-B circuit
is a simplex application, and the interface can operate only
in Rx or Tx mode and not both at the same time.
(Although the bundle is by default a full duplex IP connection,
you can configure it for simplex to save network bandwidth.)
Specifies the data rate on the IP connection.
Note the following about setting the IRIG rate:
• Unless network bandwidth is at a premium, we do not
recommend that you change this value from the default
of 16,000 bps.
• Although the IRIG information can be transported through
the network at the minimum configured rate (1000 bps),
a CTP bundle running at this rate is subject to high latency.
This option appears only if you set the direction of the port
to Tx.
Specifies the high output level, which is measured in
peak-to-peak voltage. This setting is based on a 50-ohm
termination
This option appears only if you set the direction of the port
to Tx.
Specifies the low output level, which is measured in
peak-to-peak voltage. This setting is based on a 50-ohm
termination.
Related
Documentation
•
Your Action
Select one:
Serial Multiservice Interface Module Overview on page 5
• TX (signal enters CTP)—The end of the
circuit that accepts IP packets, extracts
the IRIG-B data codes, and transmits
IRIG-B signaling output onto the cable.
• RX (signal exits CTP)—The end of the
circuit that recovers IRIG-B from the
attached cable and generates IP packets
toward the network.
Enter a number from 1000 through 25,500
bps. The port speed must be a multiple of
100 bps.
Enter a number from 0.00 through 7.85
volts peak-to-peak.
Enter a number from 0.00 through 7.85
volts peak-to-peak.
Configuring Multiservice TDC Mode Parameters for CTP Bundles (CTPView)
14
Before you begin:
• Log in to the CTPView software at least at the Net_Admin level.
• Connect the CTPView server to the CTP device for which you want to configure bundles.
To configure Multiservice TDC mode port parameters using CTPView:
1. In the side pane, select Bundle > Configuration.
2. Run your mouse over the Display and Select an Existing Bundle bar.
Copyright © 2012, Juniper Networks, Inc.

3. In the table of bundles, select the bundle that you want to modify.
4. Under Bundle Options, configure the parameters as described in Table 5 on page 15
and click Click to Submit Bundle AND Port Changes.
Table 5: CTP Bundle Multiservice TDC Port Parameter Settings in CTPView
Field
Port Description
I/F Type
Multi-Service Mode
TDC Source
TDC NRZ Rate
TDC IRIG Output Level
Related
Documentation
Function
Specifies a description for the port.
Specifies the daughter card as the interface type.
Specifies that the bundle will run in TDC mode.
Specifies the direction of the circuit.
Specifies the NRZ data rate on the IP connection.
Specifies the output level.
Note the following information about the values:
• 0—There is no output.
• 128—Unity gain, which means there is no
attenuation or gain.
• 255—Gain is 2:1.
•
Your Action
Enter a description of up to 64 alphanumeric
characters. Do not use the following characters:
( ; ' " ) ]
Select DCARD.
Select TDC.
Select one:
Serial Multiservice Interface Module Overview on page 5
• Source (signal enters CTP)—End of the circuit
that receives NRZ/IRIG data.
• Destination (signal exits CTP)—End of the circuit
that sends NRZ/IRIG data toward the network.
Enter a number from 500 through 5,000,000 bps
in multiples of 500.
Enter a number from 0 through 255.
Configuring Multiservice 4WTO Mode Port Parameters for CTP Bundles (CTPView)
Copyright © 2012, Juniper Networks, Inc.
Before you begin:
Chapter 2: Configuring Multiservice Port Parameters for CTP Bundles (CTPView)
• Log in to the CTPView software at least at the Net_Admin level.
• Connect the CTPView server to the CTP device for which you want to configure bundles.
To configure Multiservice 4WTO mode port parameters using CTPView:
1. In the side pane, select Bundle > Configuration.
2. Run your mouse over the Display and Select an Existing Bundle bar.
3. In the table of bundles, select the bundle that you want to modify.
15

Using Multiservice Interface Modules
4. Under Bundle Options, configure the parameters as described in Table 6 on page 16.
5. Click Click to Submit Bundle AND Port Changes.
Table 6: CTP Bundle Multiservice 4WTO Mode Port Parameter Settings in CTPView
16
Field
Port Description
I/F Type
Multi-Service Mode
4WTO Mode
4WTO Channel
4WTO Sample Rate [ KHz ]
4WTO μ-law Encoding
4WTO Squelch
Function
Specifies a description for the port.
Specifies the daughter card as the
interface type.
Specifies that the bundle will run in
4WTO mode.
Specifies whether this end of the circuit
provides clocking or uses adaptive
clocking.
If the CTP devices at both ends of the
circuit are synchronized, you can
configure both ends as Master.
Specifies the channel or channels to
enable.
Each CTP bundle can support either one
or two channels.
Sample rate for audio circuits in kilohertz.
The sample rate determines the audio
quality and the network bandwidth
needed.
4WTO μ-law encoding is not
configurable.
Enables or disables the active squelch
function on the circuit.
If enabled, specifies whether the squelch
is active or inactive.
The squelch function gates local audio
output when DSR-A (channel 0) or
RTS-A (channel 1) inputs are active or
inactive.
Your Action
Enter a description of up to 64
alphanumeric characters. Do not use the
following characters:
( ; ' " ) ]
Select DCARD.
Select 4WTO
Select one:
• Master—This end of the circuit
provides clocking.
• Slave—This end of the circuit uses
adaptive clocking.
Select one:
• Channel 0—Enables only channel 0.
• Dual Channel—Enables both channel
0 and channel 1.
Sample rate is fixed at 8 KHz, which
corresponds to standard toll quality
voice.
4WTO μ-law encoding is fixed at
DISABLED.
Select one:
• DISABLED—Disables the active
squelch function on the circuit
• ENABLED/ACTIVE—Squelch input is
grounded and analog output is
disabled.
• ENABLED/INACTIVE—No signal is
applied to the squelch input. Input is
open and analog output is possible.
Copyright © 2012, Juniper Networks, Inc.

Table 6: CTP Bundle Multiservice 4WTO Mode Port Parameter Settings in CTPView (continued)
Field
4WTO Channel 0 Output Level
4WTO Channel 1 Output Level
Related
Documentation
Copyright © 2012, Juniper Networks, Inc.
Function
Chapter 2: Configuring Multiservice Port Parameters for CTP Bundles (CTPView)
Specifies the output level for channel 0.
Note the following information about the
values:
• 0—There is no output.
• 128—Unity gain, which means there is
no attenuation or gain.
• 255—Gain is 2:1.
Specifies the output level for channel 1.
Note the following information about the
values:
• 0—There is no output.
• 128—Unity gain, which means there is
no attenuation or gain.
• 255—Gain is 2:1.
Your Action
• Serial Multiservice Interface Module Overview on page 5
• Configuring 4WTO Port Parameters for CTP Bundles (CTPView)
Enter a number from 0 through 255.
Enter a number from 0 through 255.
17

Using Multiservice Interface Modules
18
Copyright © 2012, Juniper Networks, Inc.

CHAPTER 3
Configuring Multiservice Port Parameters
for CTP Bundles (CTP Menu)
• Configuring Multiservice Audio Mode Port Parameters for CTP Bundles (CTP
Menu) on page 19
• Configuring Multiservice IRIG-B Mode Port Parameters for CTP Bundles (CTP
Menu) on page 21
• Configuring Multiservice TDC Mode Parameters for CTP Bundles (CTP Menu) on page 23
• Configuring Multiservice 4WTO Mode Port Parameters for CTP Bundles (CTP
Menu) on page 24
Configuring Multiservice Audio Mode Port Parameters for CTP Bundles (CTP Menu)
Copyright © 2012, Juniper Networks, Inc.
Before you begin:
• Disable the bundle before you modify the bundle options.
To configure Multiservice audio mode port parameters using the CTP Menu:
1. From the CTP Main Menu, select 1) Bundle Operations.
2. Select 1) CTP.
3. Select a bundle from the list.
If you select an active bundle, you are prompted to disable the bundle before
configuring it.
4. Select 3) Port Config.
5. Select 2) Interface.
6. Select 1) Type, and set the type to Optional Interface: MultiSvc.
7. Follow the onscreen instructions and configure the options as described in Table 7 on
page 20.
19

Using Multiservice Interface Modules
Table 7: CTP Bundle Multiservice Audio Mode Port Parameter Settings in the CTP Menu
20
Field
Mode
Master/Slave
Dual Channel
Audio Sample Rate
μ-law Encoding:
Talk Squelch
Function
Specifies that the bundle will run in audio
mode.
Specifies whether this end of the circuit
provides clocking or uses adaptive
clocking.
If the CTP devices at both ends of the
circuit are synchronized, you can
configure both ends as Master.
Two channels are supported—channel
0 and channel 1.
Enables or disables the use of both
channels.
Specifies the sample rate for audio
circuits in kilohertz. The sample rate
determines the audio quality and the
network bandwidth needed. Higher
sample rates create an IP data flow that
requires higher bandwidth.
8 KHz corresponds to standard toll
quality voice.
48 KHz corresponds to CD quality audio.
Enables or disables μ-law encoding.
Standard audio code samples are 16 bits.
If you enable μ-law encoding, the 16-bit
samples are converted to 8 bits,
consuming half of the bandwidth
without significant audio degradation.
Enables or disables the active squelch
function on the circuit.
If enabled, specifies whether the squelch
is active or inactive.
The squelch function gates local audio
output when DSR-A (channel 0) or
RTS-A (channel 1) inputs are active or
inactive.
Your Action
Select AUDIO.
Select one:
• Master—This end of the circuit provides
clocking.
• Slave—This end of the circuit uses
adaptive clocking.
Select one:
• Disable—Channel 0 is the only active
channel.
• Enable—Both channel 0 and channel
1 are active.
Select one:
• 8
• 12
• 16
• 24
• 32
• 48
Select one:
• Disable—Generates 16-bit audio
samples.
• Enable—Generates 8-bit audio
samples.
Select one:
• Disable—Disables the active squelch
function on the circuit (audio output is
always enabled).
• Enable and active—Squelch input is
grounded and analog output is
disabled.
• Enable and inactive—No signal is
applied to the squelch input. Input is
open and analog output is possible.
Copyright © 2012, Juniper Networks, Inc.

Table 7: CTP Bundle Multiservice Audio Mode Port Parameter Settings in the CTP
Menu (continued)
Field
Ch 0 Output Level: 1.00x (decimal 128)
Ch 1 Output Level: 1.00x (decimal 128)
Related
Documentation
•
Function
Specifies the output level for channel 0.
Note the following information about the
values:
• 0—There is no output.
• 128—Unity gain, which means there is
no attenuation or gain.
• 255—Gain is 2:1.
Specifies the output level for channel 1.
Note the following information about the
values:
• 0—There is no output.
• 128—Unity gain, which means there is
no attenuation or gain.
• 255—Gain is 2:1.
Your Action
Serial Multiservice Interface Module Overview on page 5
Enter a number from 0 through 255.
Enter a number from 0 through 255.
Configuring Multiservice IRIG-B Mode Port Parameters for CTP Bundles (CTP Menu)
Copyright © 2012, Juniper Networks, Inc.
Before you begin:
• Disable the bundle before you modify the bundle options.
To configure Multiservice IRIG-B mode port parameters using the CTP Menu:
1. From the CTP Main Menu, select 1) Bundle Operations.
2. Select 1) CTP.
3. Select a bundle from the list.
If you select an active bundle, you are prompted to disable the bundle before
configuring it.
4. Select 3) Port Config.
5. Select 2) Interface.
6. Select 1) Type and set the type to Optional Interface: MultiSvc.
7. Follow the onscreen instructions and configure the options as described in Table 8
on page 22.
Chapter 3: Configuring Multiservice Port Parameters for CTP Bundles (CTP Menu)
21

Using Multiservice Interface Modules
Table 8: CTP Bundle Multiservice IRIG-B Port Parameter Settings in the CTP Menu
22
Field
Mode
Src/Dest
IRIG Rate
Output High Level
Output Low Level
Related
Documentation
•
Function
Specifies that the bundle will run in
IRIG-B mode.
Specifies the direction of the circuit.
Although the IP circuit connection
through the network is full duplex, an
IRIG-B circuit is a simplex application,
and the interface can operate only in Rx
or Tx mode and not both at the same
time.
(Although the bundle is by default a full
duplex IP connection, you can configure
it for simplex to save network
bandwidth.)
Specifies the data rate on the IP
connection.
Note the following about setting the IRIG
rate:
• Unless network bandwidth is at a
premium, we do not recommend that
you change this value from the default
of 16,000 bps.
• Although the IRIG information can be
transported through the network at
the minimum configured rate (1000
bps), a CTP bundle running at this rate
is subject to high latency.
This setting applies only if you set the
direction of the port to Tx.
Specifies the high output level, which is
measured in peak-to-peak voltage. This
setting is based on a 50-ohm
termination.
This setting applies only if you set the
direction of the port to Tx.
Specifies the low output level, which is
measured in peak-to-peak voltage. This
setting is based on a 50-ohm
termination.
Your Action
Select IRIG.
Serial Multiservice Interface Module Overview on page 5
Specify yes or no to the question: Is this
an IRIG-B source end (IRIG-B signal
enters CTP)?
• Yes (y)—Sets direction to Rx. This end
of the circuit recovers IRIG-B from the
attached cable and generates IP
packets toward the network.
• No (n)—Sets the direction to Tx. This
end of the circuit accepts IP packets,
extracts the IRIG-B data codes, and
transmits IRIG-B signaling output onto
the cable.
Enter a number from 1000 through
25,500 bps. The port speed must be a
multiple of 100 bps.
Enter a number from 0.00 through 7.85
volts peak-to-peak.
Enter a number from 0.00 through 7.85
volts peak-to-peak.
Copyright © 2012, Juniper Networks, Inc.

Configuring Multiservice TDC Mode Parameters for CTP Bundles (CTP Menu)
Before you begin:
• Disable the bundle before you modify the bundle options.
To configure Multiservice TDC mode port parameters using the CTP Menu:
1. From the CTP Main Menu, select 1) Bundle Operations.
2. Select 1) CTP.
3. Select a bundle from the list.
If you select an active bundle, you are prompted to disable the bundle before
configuring it.
4. Select 3) Port Config.
5. Select 2) Interface.
6. Select 1) Typeand set the type to Optional Interface: MultiSvc.
7. Follow the onscreen instructions and configure the options as described in Table 9
on page 23.
Table 9: CTP Bundle Multiservice TDC Port Parameter Settings in the CTP Menu
Field
Mode
Src/Dest
NRZ/Rate
IRIG Output Level
Copyright © 2012, Juniper Networks, Inc.
Function
Chapter 3: Configuring Multiservice Port Parameters for CTP Bundles (CTP Menu)
Specifies that the bundle will run in TDC
mode.
Specifies the direction of the circuit.
Specifies the data rate on the IP
connection.
Specifies the output level.
Note the following information about the
values:
• 0—There is no output.
• 128—Unity gain, which means there is
no attenuation or gain.
• 255—Gain is 2:1.
Your Action
Select TDC/IRIG.
Select one:
• Src (signal enters CTP)—End of the
circuit that receives NRZ/IRIG data.
• Dst (signal exits CTP)—End of the
circuit that sends NRZ/IRIG data
toward the network.
Enter a number from 500 through
5,000,000 bps. The port speed must be
a multiple of 500 bps.
Enter a number from 0 through 255.
23

Using Multiservice Interface Modules
Related
Documentation
•
Serial Multiservice Interface Module Overview on page 5
Configuring Multiservice 4WTO Mode Port Parameters for CTP Bundles (CTP Menu)
Before you begin:
• Disable the bundle before you modify the bundle options.
To configure Multiservice 4WTO mode port parameters using the CTP Menu:
1. From the CTP Main Menu, select 1) Bundle Operations.
2. Select 1) CTP.
3. Select a bundle from the list. The bundle port must have a 4WTO daughter card
installed.
If you select an active bundle, you are prompted to disable the bundle before
configuring it.
4. Select 3) Port Config.
5. Select 2) Interface.
6. Select 1) Type and set the type to Optional Interface: MultiSvc.
7. Configure the options as described in Table 10 on page 24.
Table 10: CTP Bundle Multiservice 4WTO Port Parameter Settings in the CTP Menu
24
Field
Mode
Master/Slave
Dual Channel
Function
Specifies that the bundle will run in
4WTO mode.
Specifies whether this end of the circuit
provides clocking or uses adaptive
clocking.
If the CTP devices at both ends of the
circuit are synchronized, you can
configure both ends as Master.
Two channels are supported—channel
0 and channel 1.
Enables or disables the use of both
channels.
Your Action
Select 4WTO-Em.
Select one:
• Master—This end of the circuit
provides clocking.
• Slave—This end of the circuit uses
adaptive clocking.
Select one:
• Disable—Channel 0 is the only active
channel.
• Enable—Both channel 0 and channel
1 are active.
Copyright © 2012, Juniper Networks, Inc.

Table 10: CTP Bundle Multiservice 4WTO Port Parameter Settings in the CTP Menu (continued)
Field
Talk Squelch
Ch 0 Output Level: 1.00x (decimal 128)
Ch 1 Output Level: 1.00x (decimal 128)
Related
Documentation
Copyright © 2012, Juniper Networks, Inc.
Function
Enables or disables the active squelch
function on the circuit.
If enabled, specifies whether the squelch
is active or inactive.
The squelch function gates local audio
output when DSR-A (channel 0) or
RTS-A (channel 1) inputs are active or
inactive.
Specifies the output level for channel 0.
Note the following information about the
values:
• 0—There is no output.
• 128—Unity gain, which means there is
no attenuation or gain.
• 255—Gain is 2:1.
Specifies the output level for channel 1.
Note the following information about the
values:
• 0—There is no output.
• 128—Unity gain, which means there is
no attenuation or gain.
• 255—Gain is 2:1.
Your Action
Select one:
• Serial Multiservice Interface Module Overview on page 5
• Disable—Disables the active squelch
function on the circuit.
• Enable and active—Squelch input is
grounded and analog output is
disabled.
• Enable and inactive—No signal is
applied to the squelch input. Input is
open and analog output is possible.
Enter a number from 0 through 255.
Enter a number from 0 through 255.
• Configuring 4WTO Daughter Cards to Interoperate with Multiservice Interface Modules
(CTP Menu) on page 29
Chapter 3: Configuring Multiservice Port Parameters for CTP Bundles (CTP Menu)
25

Using Multiservice Interface Modules
26
Copyright © 2012, Juniper Networks, Inc.

CHAPTER 4
Configuring 4WTO Daughter Cards to
Interoperate with Multiservice Interface
Modules (CTPView)
• Configuring 4WTO Daughter Cards to Interoperate with Multiservice Interface Modules
(CTPView) on page 27
Configuring 4WTO Daughter Cards to Interoperate with Multiservice Interface Modules
(CTPView)
Interoperability of Multiservice Interface modules with 4WTO daughter cards requires
the following:
Copyright © 2012, Juniper Networks, Inc.
• Firmware revision 4 or higher on the 4WTO daughter card.
• CTPView releases 3.4R4 or 4.x.
• CTPOS release 6.0 or higher.
• Channel 1 cannot be configured as the channel option.
When you enable interoperability of the 4WTO daughter card with Multiservice Interface
modules, the port speed for the bundle is set as follows:
• 64 when only channel 0 is enabled.
• 128 when dual channel is enabled.
Before you begin:
• Log in to the CTPView software at least at the Net_Admin level.
• Connect the CTPView server to the CTP device for which you want to configure bundles.
To configure 4WTO daughter cards to interoperate with Multiservice Interface module
using CTPView:
1. In the side pane, select Bundle > Configuration.
2. Run your mouse over the Display and Select an Existing Bundle bar.
3. In the table of bundles, select the bundle that you want to modify.
27

Using Multiservice Interface Modules
4. Under Port Options, configure the MS Interwork parameter as described in Table 11
on page 28.
5. Click Click to Submit Bundle AND Port Changes.
Table 11: CTP Bundle 4WTO Interoperability Parameter Setting in CTPView
28
Field
MS Interwork
Function
Enables or disables interoperability of
the 4WTO daughter card with
Multiservice Interface modules.
Your Action
• ENABLED—Interoperability with the
Multiservice Interface module is
enabled.
• DISABLED—Interoperability with the
Multiservice Interface module is
disabled.
Copyright © 2012, Juniper Networks, Inc.

CHAPTER 5
Configuring 4WTO Daughter Cards to
Interoperate with Multiservice Interface
Modules (CTP Menu)
• Configuring 4WTO Daughter Cards to Interoperate with Multiservice Interface Modules
(CTP Menu) on page 29
Configuring 4WTO Daughter Cards to Interoperate with Multiservice Interface Modules
(CTP Menu)
To interoperate with Multiservice Interface modules, your 4WTO daughter card must
have firmware revision 4 or higher and you must be using CTPOS 6.0 or higher.
Interoperability of Multiservice Interface modules with 4WTO daughter cards requires
the following:
Copyright © 2012, Juniper Networks, Inc.
• Firmware revision 4 or higher on the 4WTO daughter card.
• CTPView releases 3.4R4 or 4.x.
• CTPOS release 6.0 or higher.
• Channel 1 cannot be the enabled channel.
When you enable interoperability of the 4WTO daughter card with Multiservice Interface
modules, the port speed for the bundle is set as follows:
• 64 when only channel 0 is enabled.
• 128 when dual channel is enabled.
Before you begin:
• Disable the bundle before you modify the bundle options.
To configure 4WTO daughter cards to interoperate with Multiservice Interface module
using the CTP Menu:
1. From the Main Menu, select 1) Bundle Operations.
2. Select 1) CTP.
29

Using Multiservice Interface Modules
3. Select a bundle from the list. The bundle port must have a 4WTO daughter card
installed.
If you select an active bundle, you are prompted to disable the bundle before
configuring it.
4. Select 3) Port Config.
5. Select 2) Interface.
6. Select 1) Type, and set the type to Optional Interface: Voice 4W/TO.
7. Follow the onscreen instructions.
8. Configure the Ms interwork option as described in Table 12 on page 30.
Table 12: CTP Bundle 4WTO Port Parameter Settings in the CTP Menu
30
Field
Ms interwork
Function
Enables or disables interoperability of
the 4WTO daughter card with
Multiservice Interface modules.
Your Action
• Enabled—Interoperability with the
Multiservice Interface module is
enabled.
• Disabled—Interoperability with the
Multiservice Interface module is
disabled.
Copyright © 2012, Juniper Networks, Inc.

PART 3
Index
Copyright © 2012, Juniper Networks, Inc.
• Index on page 33
31

Using Multiservice Interface Modules
32
Copyright © 2012, Juniper Networks, Inc.

Index
Symbols
#, comments in configuration statements.....................xi
( ), in syntax descriptions.......................................................xi
< >, in syntax descriptions......................................................x
[ ], in configuration statements...........................................xi
{ }, in configuration statements..........................................xi
| (pipe), in syntax descriptions............................................xi
B
braces, in configuration statements..................................xi
brackets
angle, in syntax descriptions.........................................x
square, in configuration statements.........................xi
C
comments, in configuration statements.........................xi
conventions
text and syntax...................................................................x
CTP150 multiservice interface module.............................3
CTP2000 multiservice interface module........................4
curly braces, in configuration statements.......................xi
customer support.....................................................................xi
contacting JTAC................................................................xi
D
documentation
comments on....................................................................xi
F
font conventions........................................................................x
H
HD-26 connector.......................................................................3
M
manuals
comments on....................................................................xi
P
parentheses, in syntax descriptions..................................xi
Copyright © 2012, Juniper Networks, Inc.
S
support, technical See technical support
syntax conventions...................................................................x
T
technical support
contacting JTAC................................................................xi
33

Using Multiservice Interface Modules
34
Copyright © 2012, Juniper Networks, Inc.