3.1 Introduction

3.2 Opening a Switch Handle

3.2.1 Specifying MVIP-95 or MVIP-90 Mode

3.2.2 Enabling Terminus Output State Restoration

3.3 Closing a Switch Handle

3.1 Introduction

A switch handle identifies a switch block on an open MVIP switching device. This chapter discusses opening and closing switch handles.

3.2 Opening a Switch Handle

swiOpenSwitch opens a switching device and creates a context for subsequent switching calls. The handle is used to refer to the switch block in the Switching service functions.

A switch handle is always associated with a CTA context. When you specify a switch handle, the CTA context is implied, as illustrated in Figure 3:

Figure 3. A Switch Handle Associated With a CTA Context

You cannot open an MVIP switch block in one CTA context and then refer to it in another CTA context.

Note: If you have multiple threads, each with its own CTA context and you want to make connections on a switch block, each thread must obtain its own switch handle for the switch block.

To open a switch handle:

• Specify MVIP-90 mode or MVIP-95 mode.

• Enable terminus output state restoration.

3.2.1 Specifying MVIP-95 or MVIP-90 Mode

Switch handles can be opened in the MVIP-95 mode or in the MVIP-90 mode.

In MVIP-95 mode, the terminus arguments to the Switching service functions are interpreted as MVIP-95 bus/stream/timeslot values. MVIP-95 is the default mode.

If the underlying device driver is an MVIP-95 device driver, the switch can only be opened in the default mode (MVIP-95).

Caution:

Since MVIP-95 device drivers can only be opened in MVIP-95 mode, it is recommended that all applications that may use MVIP-95 device drivers in the future, be written to use MVIP-95 mode even if the application is not currently using MVIP-95 device drivers.

If the underlying device driver is an MVIP-95 device driver or an MVIP-90 device driver and the SWI_MVIP90 constant is used as a parameter to swiOpenSwitch, the switch is opened as an MVIP-90 switch. The terminus streams and timeslots are interpreted as MVIP-90 streams and timeslots. The bus field of the terminus is ignored.

If the underlying device driver is an MVIP-90 device driver, and the switch was opened in MVIP-95 mode, the Switching service translates the MVIP-95 terminus parameters into the appropriate MVIP-90 streams and timeslots before passing the commands down to the MVIP-90 device driver.

3.2.2 Enabling Terminus Output State Restoration

When the SWI_ENABLE_RESTORE constant is used as a parameter to swiOpenSwitch, the states of the switch block outputs are saved so that they can be restored when the switch handle is closed using swiCloseSwitch. If you want to use the SWI_ENABLE_RESTORE mode, a single terminus should not be controlled by more than one switch handle. Otherwise, a terminus affected by your application might be restored to a condition set by another application or to a condition set through a different switch handle in your own application.

swiResetSwitch cannot be called if the switch handle is opened with the SWI_ENABLE_RESTORE constant enabled.

3.3 Closing a Switch Handle

swiCloseSwitch closes a switch handle, releases the associated switching context, and closes the MVIP switching device. Switching calls that are passed a closed switch handle or an uninitialized switch handle will return CTAERR_INVALID_HANDLE.

If the switch handle was opened with the SWI_ENABLE_RESTORE flag set in swiOpenSwitch, switch block outputs affected by switching calls (using this handle) will be restored to the state they were in when swiOpenSwitch was called.