Cross Connect Span 0x001C

SwitchKit Name

CrossConnectSpan

Type

EXS API and SwitchKit API message

Description

Cross Connect Span 0x001C

This message connects all data paths on Logical Span ID A to data paths on Logical Span ID B.

When in E1 clear channel mode, this message does not connect time slot 16 (channel 30). You must use the Cross Connect Channel message to connect the data paths.

Cross-connection of T1 and E1 spans is not supported. Multiframe alignment does not propagate from one side of the connection to the other.

NOTE: When cross-connecting channels across nodes in a multi-node system, a separate message must be sent to each channel in the connection.

For example, you would send one message to Node 1: Cross Connect Span 0,1. You would send another message to Node 2: Cross Connect Span 1,0.

You can use optional fields for Encoding Format and Pad Value, which are described below the message table. The Encoding Format and Pad Value fields are required for cross-connections involving separate nodes in a multi-node CSP system only.

Sent by

Host

SwitchKit Code

Configuration

CrossConnectSpan (

Node = integer,

SpanA = integer,

SpanB = integer,

ChannelAEncoding = integer,

ChannelAPad = integer,

ChannelBEncoding = integer,

ChannelBPad = integer);

C Structure

typedef struct {

unsigned short SpanA;

unsigned short SpanB;

UBYTE ChannelAEncoding;

UBYTE ChannelAPad;

UBYTE ChannelBEncoding;

UBYTE ChannelBPad;

} XL_CrossConnectSpan;

C++ Class

class XLC_CrossConnectSpan : public XLC_OutboundMessage {

public:

unsigned short getSpanA() const;

void setSpanA(unsigned short x);

unsigned short getSpanB() const;

void setSpanB(unsigned short x);

UBYTE getChannelAEncoding() const;

void setChannelAEncoding(UBYTE x);

UBYTE getChannelAPad() const;

void setChannelAPad(UBYTE x);

UBYTE getChannelBEncoding() const;

void setChannelBEncoding(UBYTE x);

UBYTE getChannelBPad() const;

void setChannelBPad(UBYTE x);

};

EXS API Hex Format