2N NetSpeaker Manual page 79

Basic Information
XML Interface for Network Services
Local Connections
By default, the
ports. External applications are connected to this port.
Communication between external applications and the
s starts with the BIND command. This command is sent by the client server.
Applications cannot continue communicating until they receive the <bind
Status="OK"/> reply from the
connection and creation of a communication channel.
Clients can choose to implement a full XMPP client or to simply run a streaming XML
parser, such as the libxml2 Simple API for XML (SAX) parser.
XML Interface
After communication initialisation is completed, the
<bind Status="OK"/>. There are two types of XML messages for communication:
The request and response messages define the request-message content using the
"<msg Id=" ID information element command, the "<CTI_IE_REFERENCE Ref" tag and
IE </msg> termination at the end of message. This type of XML message is used for
communication commands and replies from the
communication is also used for event registration and unregistration of events.
Event messages use the "<CTI_IE_REFERENCE Ref" tag. This type of IE is used for
recognition of responses sent asynchronously on events in the 2N
Server
Message Request and Response
The 2N
This document also contains XML schemes which prove details on the incoming and
outgoing combinations using the XML request and response.
®
2N TELEKOMUNIKACE a.s., www.2n.cz
®
2N NetSpeaker Server
.
®
NetSpeaker Server
Request
<msg Id="command identify">
<CTI_IE_REFERENCE Ref="0x421"/>
<CTI_REQUEST >
</msg>
Response
<msg Id="command identify">
<CTI_IE_REFERENCE Ref="0x421"/>
<CTI_IE_RESULT Result=""/>
</msg>
listens on TCP port 6543 on all eth server
®
2N NetSpeaker Server
®
2N
XML interface has two different formats:
®
2N NetSpeaker Server
. The server thus confirms the
®
2N NetSpeaker Server
NetSpeaker Server . This type of
®
NetSpeaker
alway
sends
79