TANDBERG MPS API
User Guide
<RemoteIPAddress item="1" />
<LocalIPAddress item="1">10.47.8.41:2326</LocalIPAddress> <Encryption item="1" status="On">
<Type
<RSVP item="1">Off</RSVP> <RSVPRate item="1">0</RSVPRate>
<DynamicRate item="1">64</DynamicRate> <TotalPackets item="1">367</TotalPackets> <PacketLoss item="1">0</PacketLoss> <Jitter item="1">0</Jitter>
</Audio>
.
.
.
</Call>
<Call item="2" status="Synced" type="Vtlph" protocol="H320" direction="Outgoing">
<CallRate item="1">384</CallRate> <Bonding item="1">On</Bonding> <RemoteNumber item="1">8796</RemoteNumber> <RemoteNumber item="2" /> <RemoteSubAddress item="1" />
<Mute item="1">Off</Mute> <Microphone item="1">Off</Microphone> <LogTag item="1">25</LogTag> <Channels item="1" type="Incoming">
<Rate item="1">384</Rate> <Restrict item="1">Off</Restrict> <Encryption item="1" status="Off" /> <Audio item="1" status="Active">
<Protocol item="1">G722</Protocol> <Rate item="1">56</Rate>
</Audio>
.
.
.
</Call>
<Call item="6" status="Disconnected" type="NA" protocol="NA" direction="NA">
<Cause item="1">255</Cause> </Call>
In the above example we see that the Bonding element, RemoteNumber[2] and SubAddress is not present for H323 calls. On the other hand, for H323 calls, the Audio channel element holds information regarding packet loss etc., which is not present for H320 calls. If the call is disconnected, the Call element only contains the disconnect cause value.
1.4.3 Configuration documents (rw)
The structure of the Configuration documents is independent of system state, i.e. the structure will be constant in time. In addition to holding the values for the various
configurations, each configuration
10