This section contains the following information:
The MetaSwitch Basic Translations course is intended for those individuals
whose job it is to maintain and troubleshoot translations and routing information on the MetaSwitch.
The overall goal of the Basic Translations course is to build the basic skills necessary to maintain
an existing set of switch translations. The course is the first of a pair of courses that deal with
the subject.
Attendance of the MetaSwitch
System Overview course (or equivalent MetaSwitch-specific experience) is highly recommended
before attending this course. It is also recommended that you have a grounding in translations concepts,
including rate center structure, LERG updates, and local / IntraLATA and InterLATA routing practices.
Note: The course depends on each student being able to access the MetaSwitch Portal
using an individual username and password. Please be sure you have a username/password to access the portal
prior to attending class. You can get the required information from your CSE or account manager.
The MetaSwitch Basic Translations Course is a 5-day course. Class hours are
9:00 AM to 5:00 PM Monday – Thursday and 9:00 AM to 2:00PM on Friday. The schedule for Friday includes
time for individual exercises and troubleshooting to create some flexibility in planning your
return flights home.
Check the course schedule to see
what dates are scheduled for future courses.
The course is split into the following modules.
- M1 Overview of call processing and Translations Configuration
This module starts with an overview of translations configuration on the MetaSwitch and how
it fits into overall call processing. The class then moves on to review important Subscriber values
that affect call processing and to consider how the different parts of the translations fit together.
- M2 Digit Maps
This module looks at the details of configuring Digit Maps and discusses how Assume_9 Business Groups
affect their use. The import/export function to create new digit maps is demonstrated as a way
to work more efficiently with translations entities.
- M3 Number Validation
All MetaSwitches ship with a base translations configuration which customers then modify according to
their particular needs. This module takes an in-depth look at the base configuration for Number Validation.
Participants will learn how various types of calls are processed, particularly 7, 10, and 1+10-digit
local, intraLATA, and interLATA calls. The module includes exercises covering the most common changes
to Number Validation such as adding new NPA-NXXs to a LATA, modifying old and adding new
Local Calling Areas and playing announcements for mis-dialed calls. The use of Route Verification Tests
will be discussed and students will create their own RVT groups for the week's work.
- M4 On-Switch and LNP lookups
This module looks at the phase of translations where the MetaSwitch chooses whether to terminate a call
on-switch, perform an LNP lookup, or route the call off-switch. Participants will learn how to control
LNP lookups in their network and handle basic number management tasks in the MetaSwitch.
- M5 Trunk Routing
This module looks at the Trunk Routing portion of translations and the many options available
on the MetaSwitch for choosing how to route calls. Routing calls by carrier, call type and destination
is explored as the most common means for trunk-routing a call. This module also covers how to handle
routing failures and overflows as well as augmenting existing routing configuration. Practical examples
and exercises with solutions are again used to build skills and confidence in this complex area.
- M6 Inbound Calling
This final module looks at how calls arriving at the MetaSwitch are handled by translations.
The default configuration shipped with the MetaSwitch can be easily modified to care for
a service provider's needs to filter by carrier, media channel, or other feature of the call.
Post-query processing for toll-free and LNP calls is also covered in this module. Finally,
an overview of the MetaSwitch long distance functionality is provided.