Patton electronic SmartNode 4110 Series manual FXS interface configuration task list

SmartWare Software Configuration Guide 35 • FXS interface configuration

Introduction

This chapter provides an overview of FXS interfaces, and the tasks involved in their configuration. This chapter does not explain the basic configuration steps equal to all CS interfaces. Information about basic interface con- figuration can be found in the general chapter about CS interface configuration (see chapter 33, “CS interface configuration” on page 381).

An FXS interface represents the connection of an analog FXS port signaling to the call control of SmartWare. It encapsulates the signaling of the exchange side of a FXS line, allows incoming and outgoing calls on this line, controls the line events, tones and datapath, and provides a set of supplementary services. There is a one-to-one relation between the port and the interface: Only one port can bind to an existing interface, and there must be a port that binds to the interface for the interface to become functional (see figure 57).

FXS Interfaces

Context CS

encapsulation cc-fxs

bind commands

FXS	FXS
Port	Port

Figure 57. FXS interfaces on the CS context

FXS interface configuration task list

This section describes the configuration tasks for FXS interfaces. There is no mandatory configuration for basic FXS operation.

•Configuring a subscriber number (recommended) (see page 405)

•Using an alternate PSTN profile (optional) (see page 406)

•Configuring caller-id presentation (optional) (see page 406)

•Configuring flash hook processing (optional) (see page 406)

Configuring a subscriber number (recommended)

Contrary to ISDN, where each terminal knows its own subscriber number (MSN), an analog device doesn't have this capability. If such a device is connected to an FXS port and makes an outgoing call (goes off hook and dials), the dialed digits form the called party number. But there is no calling party information available from the FXS protocol. To insert calling party information and make it available to other protocols over which the call may be transported, a subscriber number must be configured on the interface.

Note The configured subscriber number does not affect the routing of incoming calls on the interface.

Introduction 405