You are here: CSP API Reference > 1 EXS & SwitchKit API Messages > Connect One-Way Forced 0x0050

Connect One-Way Forced 0x0050

SwitchKit Name

ConnectOneWayForced

Type

EXS API and SwitchKit API message

Description

Connect One-Way Forced 0x0050

This message establishes a one-way connection between two channels, where Channel A is the source channel (talk only) and Channel B is the destination channel (listen only).

With this connection, the CSP does not do any checking on the state of Channel A; it can be in any state. This lessens the degree of call processing required, resulting in a significantly faster call rate. Channel B, however, must be in an acceptable connection state.

The connection will only be torn down if Channel B is released by the host, or as a result of a network-initiated release.

When performing a "Connect One-Way Forced A-to-B" on a multi-node system, you must send this message to the node containing the "B" channel.

For SwitchKit: If you use the ConnectOneWayForced message in your call control application, you need to specify which node you want the message to be sent to. You can specify the node within the C Structure field BaseFields Base (NodeID) or within in the C++ Class through inheritance from SKC_Message (getNode, setNode).

Sent by

Host

SwitchKit Code

C Structure

typedef struct {

unsigned short SpanA;

UBYTE ChannelA;

unsigned short SpanB;

UBYTE ChannelB;

UBYTE BPad;

} XL_ConnectOneWayForced;

C++ Class

class XLC_ConnectOneWayForced : public XLC_OutboundMessage {

public:

unsigned short getSpanA() const;

void setSpanA(unsigned short x);

UBYTE getChannelA() const;

void setChannelA(UBYTE x);

unsigned short getSpanB() const;

void setSpanB(unsigned short x);

UBYTE getChannelB() const;

void setChannelB(UBYTE x);

UBYTE getBPad() const;

void setBPad(UBYTE x);

};

EXS API Hex Format

MESSAGE (White) | RESPONSE (Gray)
Byte | Field Description | Byte | Field Description
0 | Frame (0xFE) | 0 | Frame (0xFE)
1, 2 | Length (0x00NN) | 1, 2 | Length (0x0007)
3, 4 | Message Type (0x0050) | 3, 4 | Message Type (0x0050)
5 | Reserved (0x00) | 5 | Reserved (0x00)
6 | Sequence Number | 6 | Same Sequence Number
7 | Logical Node ID | 7 | Logical Node ID
: | AIB Address Method 0x00 - Individual AEs | 8, 9 | Status (MSB, LSB)
10, 11 | State (MSB, LSB) If the MSB of the preceding Status field is 0x18 (Invalid Channel B State) or 0x1D (Invalid Channel A State), then this field indicates the component state. If the State value is greater than 0xFF (255), then it is truncated to 0xFF. If the MSB of the preceding Status field is neither 0x18 nor 0x1D, then the value in this field is 0x0000. If the preceding Status field is a positive acknowledgement, this field does not apply.
12 | Checksum
Number of AEs to follow
AEs 0x0D Channel A 0x0D Channel B
: | Channel B Pad Value The db gain/loss adjustment of the signal being transmitted to Channel B. Value dB Gain/Loss 0x00 +3 dB 0x01 0 dB 0x02 2 dB 0x03 3 dB 0x04 4 dB 0x05 6 dB 0x06 9 dB
| Number of ICBs to follow |  |
| Data (presented in an ICB) 0x03 Extended Data 0x00E1 Generic PPL |  |
: | Checksum

A computer, attached to the Excel platform through an RS-232 or Ethernet link, from which you run the telecommunications application that controls the Excel platform.
A group of data bits in a specific format, with a flag at each end to indicate the beginning and the end of the frame.
See Address Information Block.
Most Significant Bit
Least Significant Bit
The condition of a component at a given instant. The current "context" of a PPL object, such as Idle, Seizing, Answered. In PPL files, a State is represented by a circle.
See Information Control Block.
See Programmable Protocol Language.