Cisco Acano X-series 開発者ガイド

Cisco Meeting Server Release 2.0 : CDR Guide

6 Example Traffic Flow

The following trace shows a typical example traffic flow. It covers two SIP clients connecting to
a meeting, then one ending the meeting, and the other SIP call then being dropped. The XML in
this example has be formatted to make it easier to read.

Events post #1

<?xml version="1.0"?>
<records session=“a865433a-4926-4549-a701-9bb5b93c75e6”
callBridge=“158ba4f7-70eb-4a35-982c-71d4f1674277”>

<record type="callLegStart" time="2015-07-23T07:32:55Z"

recordIndex="1" correlatorIndex="0">

<callLeg id="fc9c85ca-8c41-4a1a-9252-b16977d1e4e1">

<remoteParty>sipclient1@example.com</remoteParty>
<localAddress>access1@127.0.0.1</localAddress>
<type>sip</type>
<direction>incoming</direction>
<groupId>18da80f3-8a71-4255-aa90-e1677b99b588</groupId>
<sipCallId>b8a81da5-c24c-43db-ba58-742f587faec8</sipCallId>

</callLeg>

</record>

</records>

Events post #2

<?xml version="1.0"?>
<records session=“a865433a-4926-4549-a701-9bb5b93c75e6”
callBridge=“158ba4f7-70eb-4a35-982c-71d4f1674277”>

<record type="callStart" time="2015-07-23T07:32:55Z"

recordIndex="2" correlatorIndex="1">

<call id="46d49cb4-8171-4abc-97f5-b88035b1da0a">

<name>test564_1</name>
<callType>coSpace</callType>
<coSpace>50605235-60cf-484a-9fa1-278ad0646243</coSpace>
<callCorrelator>5f3300c5-ca67-40e0-a503-

91baec70dbbe</callCorrelator>

</call>

</record>
<record type="callLegUpdate" time="2015-07-23T07:32:55Z"

recordIndex="3" correlatorIndex="2">

<callLeg id="fc9c85ca-8c41-4a1a-9252-b16977d1e4e1">

<state>connected</state>
<call>46d49cb4-8171-4abc-97f5-b88035b1da0a</call>
<groupId>18da80f3-8a71-4255-aa90-e1677b99b588</groupId>
<sipCallId>b8a81da5-c24c-43db-ba58-742f587faec8</sipCallId>

</callLeg>

</record>

</records>

6 Example Traffic Flow