|
|
Table Of Contents
Cisco Unified Communications Manager Express Call Monitoring Interface Guide
Prerequisites for Cisco Unified CME Call Monitoring
Restrictions for Cisco Unified CME Call Monitoring
Information About Cisco Unified CME Call Monitoring
Registration Process for Call and Line Monitoring
Subscription Overview for Call and Line Monitoring
Call Monitoring Scenario Examples
Scenario 1: Basic Call Scenario
Scenario 2: Routing Point Transfer Call to Agent
Cisco Unified CME Configuration Examples
Minimum preconfiguration required before using the AXL interface
Typical configuration of the Unified CME
Cisco Unified Communications Manager Express Call Monitoring Interface Guide
First Published: June 20, 2007Last Updated: June 20, 2007This document describes call and line monitoring on the Session Initiation Protocol (SIP) interface between the Cisco Unified Communications Manager Express (Unified CME) and a session server, such as Cisco Unified Contact Center Express (Unified CCX). The Cisco Unified CME is a Cisco IOS-based IP PBX with a device capability dependent on your specific Cisco IOS release, the Cisco router you use as your Unified CME, and the combination of devices you include in your configuration. For example, a Cisco Unified CME running on a Cisco 3845 router can handle up to 720 directory numbers and up to 240 skinny client control protocol (SCCP) user agents (UAs) but when using the Cisco Unified CCX as your session server, your configuration is limited to a total of 50 UAs.
As of release 4.2, the Cisco Unified CME provides a monitoring interface, based on SIP, to report both line state and call activities in support of telephony applications such as a call center. SIP presence and dialog event packages are used for line and call monitoring using the SIP REGISTER, SUBSCRIBE, and NOTIFY mechanisms.
This document focuses primarily on a detailed description of how SIP provides interworking and interoperability between a session server (such as Cisco Unified CCX) and the Cisco Unified CME (formerly known as Cisco Unified CallManager Express) and the utilization of specific computer supported telecommunications applications (CSTA) and Cisco proprietary events defined by the standard extensible markup language (XML) protocol.
Contents
•
Prerequisites for Cisco Unified CME Call Monitoring
•
•
•
•
Prerequisites for Cisco Unified CME Call Monitoring
•
•
Restrictions for Cisco Unified CME Call Monitoring
•
•
•
•
Information About Cisco Unified CME Call Monitoring
The Cisco Unified CME interacts with a session server, such as Cisco Unified CCX. With this call monitoring feature, Unified CME customers access advanced session server applications, such as call queuing and call routing, without the complexity of the Cisco Unified Communications Manager (formerly known as Cisco Unified CallManager).
To understand the call and line monitoring features of the Cisco Unified CME, you should be familiar with the following concepts:
•
•
Note
Call Monitoring Basics
Cisco Unified CCX provides a single-box session server with automatic call distribution (ACD), interactive voice response (IVR), and computer telephony integration (CTI). Unified CCX interacts with a PBX, such as Cisco Unified Communications Manager, to provide intelligent call queueing and call routing for session server agent devices.
Some portions of this guide reference Cisco Unified CCX specifically, especially where examples are provided. However, the Cisco Unified CME is designed to interface with a session server application to provide call and line monitoring capability. To provide this capability, the Cisco Unified CME is configured to communicate with session server applications to perform three basic configuration and functional processes (see also Figure 1):
•
Note
•
•
Note
Calls are typically selected based on the called number, provided by the PSTN when the call is presented to the Unified CME. The called number is matched using the destination-pattern command line interface (CLI) under the dial peer. Session servers, such as Cisco Unified CCX, utilize this capability.
Figure 1 Overview of Unified CME and Session Server (Unified CCX) Interaction
When a call comes in to the Cisco Unified CME from the Internet (through the SIP trunk), it is checked against configured voice register pools. Those with a matched route point are routed to the session server (Unified CCX in Figure 1). The session server then initiates monitoring of service requests by sending a SUBSCRIBE request to the Cisco Unified CME through the SIP interface connection.
When presented with a subscription request, the Unified CME responds with a NOTIFY message to the session server, routes the call to the appropriate agent, and continues interacting with the session server during the call for monitoring purposes. See Figure 2 for an example of a call monitoring system flow between Unified CME and Unified CCX.
Figure 2 High Level Summary of Line and Call Monitoring System Flow
Administrative XML Layer
Cisco Unified CME provides the session server with an XML-based interface—the Administrative XML Layer (AXL) interface—to perform configuration-related tasks. Both the session server and the Cisco Unified CME must be configured with appropriate information about lines and route points available to the call and line monitoring functions.
Cisco Unified CCX uses the xml-admin-user account to complete the configuration changes on the Cisco Unified CME and uses the same user account to retrieve the required Unified CME configuration information. The credential for this account is manually supplied to the session server. The session server provision and configuration capabilities are broadly categorized into two areas, which are described in the following sections:
•
Remote Control Credential Authentication
The AXL interface provides the ability to authenticate the remote control credential belonging to the session server before accepting changes to the Unified CME configuration. This mechanism also prevents unauthenticated SIP REGISTER messages or SIP SUBSCRIBE messages for presence events.
TipRoute Point Configuration
The AXL interface provides the session server with the ability to create, delete, and modify configuration properties for the list of route points stored on the Cisco Unified CME. Using the AXL interface, you can configure route points once, at the session server terminal, and send, or "push," the route point configurations to the Unified CME. Without a properly configured list of route points, the Unified CME cannot provide those incoming calls access to their destinations.
A PSTN call received by the Unified CME has a specific destination, or endpoint—a call routing service on the session server, such as auto attendant (AA) or integrated contact distribution (ICD) on Cisco Unified CCX. Once the call reaches its endpoint on the session server it is forwarded to the appropriate user agent. However, for a call to pass through the Unified CME and reach its specified endpoint, the session server must first send endpoint information to the Unified CME.
Each call routing service on the session server is uniquely identified as a route point on the Unified CME. The session server sends information about each call routing service to the Unified CME over the AXL interface and the Unified CME then converts the unique identity of each call routing service into a unique route point ID. The route points are stored on the Unified CME as SIP endpoints (also called voice register pools (VRPs).
Once VRPs are created on the Unified CME, incoming calls can access their appropriate endpoint (call routing service) on the session server and be routed to the appropriate user agent. Additionally, the route points can be registered on the Unified CME so that associated calls and agent lines can be monitored. (See the "Route Point Registration" section.)
Registration Process for Call and Line Monitoring
The session server establishes and terminates a call monitoring channel with the Cisco Unified CME using the events and header fields described in the following sections:
Note
Session Server Registration
To establish an open session between the Cisco Unified CME and a session server, such as Cisco Unified CCX, the session server sends a SIP REGISTER message to the Unified CME. The primary purpose of this initial registration process is to open a monitoring session between the session server and the Unified CME. Once the session is established, the Unified CME and the session server are able to configure and reserve resources so that the session server can register and monitor route points and request status updates for agent lines and calls during the session.
The session server must exchange keepalive messages with the Cisco Unified CME to keep the session open. Cisco Unified CCX uses the xml-user-admin credential to send keepalive messages. Additionally, as a REGISTER message, the keepalive message requires authentication. The Unified CME challenges the initial keepalive REGISTER request and authenticates this request with an admin credential.
Once the admin credential is verified, a proprietary cisco-referenceID is generated by the Unified CME and sent in response to the keepalive REGISTER request with the cisco-referenceID included in the header. The Unified CME recognizes the session server by this cisco-referenceID. All future interactions in the same session include the cisco-referenceID header so that subsequent re-REGISTER and un-REGISTER messages can be processed without the need for additional authentication.
Note
When the session server restarts, it sends a REGISTER message. The REGISTER message has an expiration time that is configurable on both the session server and the Cisco Unified CME. If the Unified CME does not receive a re-REGISTER request after the existing registration expires, the Unified CME interprets the session server as down and initiates a cleanup of all associated internal resources.
To shut down a session between the Cisco Unified CME and the session server gracefully, either the Unified CME or the session server initiates a graceful shutdown request. This request is in the form of a SIP un-REGISTER message where the Expires header field is set to zero. The device that receives the un-REGISTER request releases or removes the resources associated with that session.
X-cisco-referenceID
The X-cisco-referenceID is a unique identification assigned to a session server when a session is established. The Cisco Unified CME supports a maximum of eight (8) X-cisco-referenceIDs at a time, one for each open session. The X-cisco-referenceID is used for all SUBSCRIBE requests for monitoring events. The session server decides which SUBSCRIBE requests are to be bundled and in which keepalive sessions to bundle them according to the X-cisco-referenceID specified in the SUBSCRIBE request. All subscriptions within a keepalive session inherit the same keepalive timer.
Incoming SUBSCRIBE or REGISTER requests with no X-cisco-referenceID or with an X-cisco-referenceID that is not in the Unified CME X-cisco-referenceID database are rejected with a 400 Bad Request response.
Route Point Registration
Before calls or agent lines can be monitored by a session server, all route points associated with those calls or user agent lines must first exist on the Cisco Unified CME and then be registered. (See the "Administrative XML Layer" section for information about creating route points on the Unified CME.)
Once a session is established between the Unified CME and the session server, the session server sends SIP REGISTER message requests for each route point it will monitor. The Unified CME replies to those SIP REGISTER requests with SIP 200 OK messages. Once registration is completed, the session server maintains each registered route point (as a VRP) on the Unified CME.
Registration Examples
The following are message examples (with cisco-referenceID) for a SIP REGISTER request to open a session, a SIP REGISTER request for route point registration, and a SIP un-REGISTER request to end a session.
Example: SIP REGISTER request received by the Unified CME to open a sessionREGISTER sip:192.0.2.105:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.200:5060;branch=z9hG4bK4sucdtfC.Aj0pZt8vaxhRw~~1Max-Forwards: 70To: <sip:CRS_controller@192.0.2.105>From: <sip:CRS_controller@192.0.2.105>;tag=ds3dbf7342Call-ID: 11739854999401@192.0.2.200CSeq: 2 REGISTERContent-Length: 0Contact: <sip:CRS_controller@192.0.2.200:5060;transport=tcp>;expires=300Allow: INVITE, BYE, CANCEL, ACK, NOTIFYUser-Agent: Cisco-CRS/5.0X-cisco-session-server: CISCO-L2IZ31WFE_1170978599000Authorization: Digestusername=''axluser'',realm='''',nonce=''C6F5410C0001A22A'',qop=auth,nc=00000001,cnonce=''08LAFIdaSVbCs+RsyyCLGQ=='',response=''eb08a551a403b4362af2832e5456ada2'',uri=''sip:192.0.2.105:5060;transport=tcp'',algorithm=MD5Response:
SIP/2.0 200 OKVia: SIP/2.0/TCP 192.0.2.200:5060;branch=z9hG4bK4sucdtfC.Aj0pZt8vaxhRw~~1From: <sip:CRS_controller@192.0.2.105>;tag=ds3dbf7342To: <sip:CRS_controller@192.0.2.105>;tag=1055E4-5B1Date: Thu, 15 Mar 2007 18:41:49 GMTCall-ID: 11739854999401@192.0.2.200Server: Cisco-SIPGateway/IOS-12.xCSeq: 2 REGISTERX-cisco-referenceID: EBC891CDContact: <sip:CRS_controller@192.0.2.200:5060;transport=tcp>;expires=300;x-cisco-newregExpires: 300Content-Length: 0Example: SIP REGISTRATION request received by the Unified CME for route point registrationREGISTER sip:192.0.2.105:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.200:5060;branch=z9hG4bK4sucdtfC.Aj0pZt8vaxhRw~~11Max-Forwards: 70To: <sip:6888@192.0.2.105>From: <sip:6888@192.0.2.105>;tag=ds73ab77e5Call-ID: 11739855011434@192.0.2.200CSeq: 2 REGISTERContent-Length: 0Contact: <sip:6888@192.0.2.200:5060;transport=tcp>;expires=360000Allow: INVITE, BYE, CANCEL, ACK, NOTIFYUser-Agent: Cisco-CRS/5.0X-cisco-referenceID: EBC891CDAuthorization: Digestusername="axluser",realm="",nonce="4B7A07260001A29A",qop=auth,nc=00000001,cnonce="puq8yH43mSC/iFnkeQtpJQ==",response="6f791cce5d3dd6b374cc5fabcd4eaf06",uri="sip:192.0.2.105:5060;transport=tcp",algorithm=MD5Response:
SIP/2.0 200 OKVia: SIP/2.0/TCP 192.0.2.200:5060;branch=z9hG4bK4sucdtfC.Aj0pZt8vaxhRw~~11From: <sip:6888@192.0.2.105>;tag=ds73ab77e5To: <sip:6888@192.0.2.105>;tag=105AB8-158DDate: Thu, 15 Mar 2007 18:41:50 GMTCall-ID: 11739855011434@192.0.2.200Server: Cisco-SIPGateway/IOS-12.xCSeq: 2 REGISTERX-cisco-referenceID: EBC891CDContact: <sip:6888@192.0.2.200:5060;transport=tcp>;expires=600;x-cisco-newregExpires: 600Content-Length: 0Example: Session-ending SIP un-REGISTER requestREGISTER sip:192.0.2.105:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.200:5060;branch=z9hG4bKlUdpwgHo.CSGK2K2kSH0eQ~~2708Max-Forwards: 70To: <sip:6888@192.0.2.105>From: <sip:6888@192.0.2.105>;tag=ds5c4924efCall-ID: 117398462795030@192.0.2.200CSeq: 7 REGISTERContent-Length: 0Allow: INVITE, BYE, CANCEL, ACK, NOTIFYUser-Agent: Cisco-CRS/5.0X-cisco-referenceID: BB24BC58Authorization: Digestusername=''axluser'',realm='''',nonce=''0991D070000137EA'',qop=auth,nc=00000001,cnonce=''g8WdlGvtvU240mYLl04PQg=='',response=''8ff6a328150878055b661f4d6efd9723'',uri=''sip:192.0.2.105:5060;transport=tcp'',algorithm=MD5Contact: *Expires: 0Subscription Overview for Call and Line Monitoring
The SIP interface provides complete call and line monitoring functions based on SIP presence and dialog event packages. Monitoring of calls, lines, and route points allows decisions to be made during call routing. The Cisco Unified CME and session server use the SIP SUBSCRIBE and NOTIFY mechanisms for dialog and presence events. Additionally, SUBSCRIBE requests and NOTIFY messages for call monitoring (dialog events) use the Computer Supported Telephony Applications (CSTA) payload type.
Dialog events apply to call monitoring, presence events apply to line monitoring, and both apply to registered route points. The session server must send two SIP SUBSCRIBE messages for each route point and user agent line for which it subscribes—one for presence events and one for dialog events—before call monitoring can take place.
The Cisco Unified CME follows up each successful SIP SUBSCRIBE process with an initial SIP NOTIFY message that includes the current status of the specified or associated user agent line. For dialog event subscriptions, the body portion of the NOTIFY message will be empty if no call activities occurred prior to the SUBSCRIBE request. Otherwise, the message body will include the last event for all calls on the specified user agent line.
The Cisco Unified CME uses general message support for all monitoring operations. This section defines the XML schema used to monitor service between the Unified CME and a session server, such as Unified CCX. If there is no existing XML standard, proprietary Cisco parameters are used.
Line Subscription
To route a call to the correct agent, the session server initiates a SUBSCRIBE request for line monitoring using the SIP presence event package. This SIP SUBSCRIBE message utilizes two Multipurpose Internet Mail Extensions (MIME) payload types to monitor line status: presence information data format (PIDF) and remote party ID (RPID). These concepts are described in more detail in the following sections:
•
Line Subscription Process
Before a session server can monitor calls, it must subscribe to all user agent lines (and associated route points) it intends to monitor. To subscribe, the session server sends a subscription request (SIP SUBSCRIBE message) with a presence event for the specified agent line to the Cisco Unified CME. The SIP SUBSCRIBE message notifies the Cisco Unified CME that the session server intends to monitor agent line specified in the subscription request and that it needs to be informed of any status changes during the time the subscription remains active.
Line subscription requires that the session server be notified of any line-related events or status changes. The Unified CME provides status change notification to the session server by sending SIP NOTIFY messages whenever the status changes for a subscribed line or associated route point. After the session server successfully subscribes to the SIP presence package for a specified user agent, it is notified of all presence events related to that line (see Table 1).
Note
Not all events or event attributes described in these RFCs are included or supported by the Cisco Unified CME. Where differences exist, this interface guide takes precedence.
Line monitoring events are essentially SIP presence information and are primarily available through the SIP presence package. The session server subscribes to and maps the presence information to internal events.
To gracefully shut down or end subscription to a line, the session server sends a SIP un-SUBSCRIBE message request to the Cisco Unified CME. The SIP un-SUBSCRIBE request is nearly the same as the original corresponding SIP SUBSCRIBE message request but the Expires header field is set to 0. When the Unified CME receives a message to unsubscribe from a line, it stops sending notification messages regarding presence events for that line.
The following examples show a SIP SUBSCRIBE request with the Cisco Unified CME SIP NOTIFY response for establishing subscription of a line and a SIP un-SUBSCRIBE request to end subscription to a line:
Example: SIP SUBSCRIBE request received by the Unified CME for line subscriptionSUBSCRIBE sip:6401@192.0.2.105:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.200:5060;branch=z9hG4bK4sucdtfC.Aj0pZt8vaxhRw~~44Max-Forwards: 70To: <sip:6401@192.0.2.105>From: <sip:CRS_controller@192.0.2.200>;tag=ds9517f1e3Call-ID: 117398618772314@192.0.2.200CSeq: 2 SUBSCRIBEContent-Length: 0Contact: <sip:CRS_controller@192.0.2.200:5060;transport=tcp>User-Agent: Cisco-CRS/5.0X-cisco-referenceID: EBC891CDEvent: presenceAccept: application/pidf+xml+axl;ciscogw1Expires: 280000Allow-Events: referAllow-Events: telephone-eventAuthorization: Digestusername=''axluser'',realm='''',nonce=''93F9B1DF0002AEC6'',qop=auth,nc=00000001,cnonce=''TUl4tAKxDa1k5dlJbpleNQ=='',response=''f50a04977e6ffc454636ec4220407bdf'',uri=''sip:6401@192.0.2.105:5060;transport=tcp'',algorithm=MD5Response:
NOTIFY sip:CRS_controller@192.0.2.200:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.105;branch=z9hG4bK1EDC6From: <sip:6401@192.0.2.105>;tag=1AD410-207ETo: <sip:CRS_controller@192.0.2.200>;tag=ds9517f1e3Call-ID: 117398618772314@192.0.2.200CSeq: 101 NOTIFYMax-Forwards: 70Date: Thu, 15 Mar 2007 18:53:17 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: presenceSubscription-State: active;expires=3600Contact: <sip:6401@192.0.2.105:5060;transport=tcp>Content-Type: application/pidf+xmlContent-Length: 444<?xml version=''1.0'' encoding=''UTF-8''?><presence xmlns=''urn:ietf:params:xml:ns:pidf''entity=''sip:6401@ 192.0.2.105'' xmlns:e=''urn:ietf:params:xml:ns:pidf:status:rpid''xmlns:rpid=''urn:ietf:params:xml:ns:pidf:status:rpid'' xmlns:dm=''urn:ietf:params:xml:ns:pidf:data-model''><dm:person><status><basic>Open</basic></status></dm:person><tuple>id=''cisco-cme''><status><basic>Open</basic><rpid:activeIdle>idle</rpid:activeIdle></status></tuple></presence>Example: SIP un-SUBSCRIBE message request received by the Unified CME to unsubscribe a lineSUBSCRIBE sip:6401@192.0.2.105:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.200:5060;branch=z9hG4bKlUdpwgHo.CSGK2K2kSH0eQ~~2672Max-Forwards: 70To: <sip:6401@192.0.2.105>;tag=30774-262From: <sip:CRS_controller@192.0.2.200>;tag=dscc7524ffCall-ID: 117398462796634@192.0.2.200CSeq: 3 SUBSCRIBEContent-Length: 0Contact: <sip:CRS_controller@192.0.2.200:5060;transport=tcp>User-Agent: Cisco-CRS/5.0X-cisco-referenceID: BB24BC58Event: presenceAccept: application/pidf+xml+axl;ciscogw1Expires: 0Allow-Events: referAllow-Events: telephone-eventAuthorization: Digest username=''axluser'',realm='''',nonce=''83AA79D800004D89'',qop=auth,nc=00000002,cnonce=''ybxqxaokjytpqK+tzEIB2g=='',response=''33f378d8c481b8d57dd0bde9cb7df2d7'',uri=''sip:6401@192.0.2.105:5060;transport=tcp'',algorithm=MD5Line Status Notification
The Cisco Unified CME sends unsolicited NOTIFY messages to inform the session server of any changes to the status of a subscribed line. The session server must receive and store this information so that it can monitor the line and any calls it wants to monitor on that line. Line monitoring events are reported for both agent lines and route points. Table 1 provides a summary of line subscription status notification values and links to sections that provide detailed information for those values.
Line In Service
The Cisco Unified CME sends a SIP NOTIFY message to the session server when a monitored line that was out of service makes the transition to an in-service state. The line-in-service NOTIFY message includes the OPEN value in the PIDF tag.
The Cisco attributes included in a line-in-service NOTIFY message are:
•
•
Line Out of Service
The Cisco Unified CME sends a SIP NOTIFY message to the session server when a monitored line that was in service makes the transition to an out-of-service state. The line-out-of-service NOTIFY message includes the CLOSED value in the PIDF tag.
The Cisco attributes included in a line-out-of-service NOTIFY message are:
•
•
•
Line Available
The Cisco Unified CME sends a SIP NOTIFY message to the session server when a monitored line accepts a call, signifying that it has become available. A line is available after accepting a new call if it still has open channels. The line available NOTIFY message includes the OPEN value in the PIDF tag and a value of active in the RPID tag.
The Cisco attributes included in a line available NOTIFY message are:
•
•
Note
Line Busy
The Cisco Unified CME sends a SIP NOTIFY message to the session server when an idle line changes to busy state. A line is busy when: it answers a call; originates a new call; has a call on hold; or has multiple calls on the same line. When a line is busy it has no more open channels and cannot accept any new calls.
The Cisco attributes included in a line busy NOTIFY message are:
•
•
Line Idle
The Cisco Unified CME sends a SIP NOTIFY message to the session server when a line that was busy changes to idle state. A line is idle when all calls for that line address are disconnected and there are no remaining calls, regardless of the call state (such as answered, ringing, or hold).
The Cisco attributes included in a line idle NOTIFY message are:
•
•
Note
For more information, refer to RFC 3863, RFC 4479, and RFC 4480.
Line Subscription Examples
The following are message examples for a SIP SUBSCRIBE request for line subscription:
Example: SIP SUBSCRIBE request received by the Unified CME to monitor a lineSUBSCRIBE sip:6888@192.0.2.105:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.200:5060;branch=z9hG4bK4sucdtfC.Aj0pZt8vaxhRw~~14Max-Forwards: 70To: <sip:6888@192.0.2.105>From: <sip:CRS_controller@192.0.2.200>;tag=ds7dff792dCall-ID: 117398550147110@192.0.2.200CSeq: 1 SUBSCRIBEContent-Length: 0Contact: <sip:CRS_controller@192.0.2.200:5060;transport=tcp>User-Agent: Cisco-CRS/5.0X-cisco-referenceID: EBC891CDEvent: presenceAccept: application/pidf+xml+axl; ciscogw1Expires: 280000Authorization: Digestusername="axluser",realm="",nonce="4B7A07260001A29A",qop=auth,nc=00000002,cnonce="puq8yH43mSC/iFnkeQtpJQ==",response="76fdf874e63934da88c33ed9b354b8d5",uri="sip:6888@192.0.2.105:5060;transport=tcp",algorithm=MD5Allow-Events:referAllow-Events: telephone-eventResponse for a registered line:
SIP/2.0 202 AcceptedVia: SIP/2.0/TCP 192.0.2.200:5060;branch=z9hG4bK4sucdtfC.Aj0pZt8vaxhRw~~14From: <sip:CRS_controller@192.0.2.200>;tag=ds7dff792dTo: <sip:6888@192.0.2.105>;tag=105B44-6E3Date: Thu, 15 Mar 2007 18:41:51 GMTCall-ID: 117398550147110@192.0.2.200CSeq: 1 SUBSCRIBEContent-Length: 0Contact: <sip:6888@192.0.2.105:5060;transport=tcp>Expires: 3600Line Status Notification Examples
The following are SIP NOTIFY message examples sent by Unified CME to notify the session server of changes in status to a monitored line:
Example: SIP NOTIFY message sent to notify the session server that the line is now availableNOTIFY sip:CRS_controller@192.0.2.200:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.105;branch=z9hG4bK16BBB8From: <sip:6401@192.0.2.105>;tag=1AD410-207ETo: <sip:CRS_controller@192.0.2.200>;tag=ds9517f1e3Call-ID: 117398618772314@192.0.2.200CSeq: 128 NOTIFYMax-Forwards: 70Date: Thu, 15 Mar 2007 19:36:43 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: presenceSubscription-State: active;expires=993Contact: <sip:6401@192.0.2.105:5060;transport=tcp>Content-Type: application/pidf+xmlContent-Length: 492<?xml version="1.0" encoding="UTF-8"?><presence xmlns="urn:ietf:params:xml:ns:pidf"entity="sip:6401@192.0.2.105" xmlns:e="urn:ietf:params:xml:ns:pidf:status:rpid"xmlns:rpid="urn:ietf:params:xml:ns:pidf:status:rpid" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"><dm:person><status><basic>Open</basic></status><e:activities><e:on-the-phone/></e:activities></dm:person><tuple id="ciscocme"><status><basic>Open</basic><rpid:activeIdle>active</rpid:activeIdle></status></tuple></presence>Example: SIP NOTIFY message sent to notify the session server that the line is now busyNOTIFY sip:CRS_controller@192.0.2.200:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.105;branch=z9hG4bK171683From: <sip:6401@192.0.2.105>;tag=1AD410-207ETo: <sip:CRS_controller@192.0.2.200>;tag=ds9517f1e3Call-ID: 117398618772314@192.0.2.200CSeq: 129 NOTIFYMax-Forwards: 70Date: Thu, 15 Mar 2007 19:37:09 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: presenceSubscription-State: active;expires=967Contact: <sip:6401@192.0.2.105:5060;transport=tcp>Content-Type: application/pidf+xmlContent-Length: 496<?xml version="1.0" encoding="UTF-8"?><presence xmlns="urn:ietf:params:xml:ns:pidf"entity="sip:6401@192.0.2.105" xmlns:e="urn:ietf:params:xml:ns:pidf:status:rpid"xmlns:rpid="urn:ietf:params:xml:ns:pidf:status:rpid" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"><dm:person><status><basic>Closed</basic></status><e:activities><e:on-thephone/></e:activities></dm:person><tuple id="ciscocme"><status><basic>Closed</basic><rpid:activeIdle>active</rpid:activeIdle></status></tuple></presence>Example: SIP NOTIFY message sent to notify the session server that the line is now idleNOTIFY sip:CRS_controller@192.0.2.200:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.105;branch=z9hG4bK1EDC6From: <sip:6401@192.0.2.105>;tag=1AD410-207ETo: <sip:CRS_controller@192.0.2.200>;tag=ds9517f1e3Call-ID: 117398618772314@192.0.2.200CSeq: 101 NOTIFYMax-Forwards: 70Date: Thu, 15 Mar 2007 18:53:17 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: presenceSubscription-State: active;expires=3600Contact: <sip:6401@192.0.2.105:5060;transport=tcp>Content-Type: application/pidf+xmlContent-Length: 444<?xml version="1.0" encoding="UTF-8"?><presence xmlns="urn:ietf:params:xml:ns:pidf"entity="sip:6401@192.0.2.105" xmlns:e="urn:ietf:params:xml:ns:pidf:status:rpid"xmlns:rpid="urn:ietf:params:xml:ns:pidf:status:rpid" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"><dm:person><status><basic>Open</basic></status></dm:person><tupleid="ciscocme"><status><basic>Open</basic><rpid:activeIdle>idle</rpid:activeIdle></status></tuple></presence>Example: SIP NOTIFY message sent to notify the session server that a line is unregisteredNOTIFY sip:CRS_controller@192.0.2.200:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.105:5060;branch=z9hG4bK542470From: <sip:6401@192.0.2.105>;tag=EB944-1FD8To: <sip:CRS_controller@192.0.2.200>;tag=dsf50857ceCall-ID: 117458697315814@192.0.2.200CSeq: 108 NOTIFYMax-Forwards: 70Date: Fri, 23 Mar 2007 00:16:08 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: presenceSubscription-State: active;expires=708Contact: <sip:6401@192.0.2.105:5060;transport=tcp>Content-Type: application/pidf+xmlContent-Length: 425<?xml version=''1.0'' encoding=''UTF-8''?><presence xmlns=''urn:ietf:params:xml:ns:pidf''entity=''sip:6401@192.0.2.105'' xmlns:e=''urn:ietf:params:xml:ns:pidf:status:rpid''xmlns:rpid=''urn:ietf:params:xml:ns:pidf:status:rpid'' xmlns:dm=''urn:ietf:params:xml:ns:pidf:data-model''><dm:person><status></status></dm:person><tuple id=''cisco-cme''><status><basic>Closed</basic><note errCode=''2''>UnRegistered</note></status></tuple></presence>Call Subscription
Call monitoring is based on the SIP SUBSCRIBE and NOTIFY mechanism using TCP for transport. Suggested payload types for these messages are found in ECMA standards and use MIME type "application/csta+xml."
Note
To route a call to the correct agent, the session server initiates a SIP SUBSCRIBE request for call monitoring. The session server uses the SIP dialog package, implemented by the Cisco Unified CME, for call monitoring. Using the SIP dialog event package enables dialog state information to be distributed among different applications over a generic event notification framework.
Call monitoring uses a SIP dialog event package with the CSTA payload type. Call events are received one per call, regardless of the number of connections associated with a given call. Each call maintains a watcher list of session servers for call monitoring events and, when a connection (user agent) joins a call, the watch list is updated with all session servers that have subscribed to that user agent line. When the Unified CME sends a notification of a call event, it checks the list and notifies all subscribed list members.
Additionally, the Cisco Unified CME tracks a list of route point subscriptions for a session server. The Unified CME uses the subscription context of the first list element to report call events for all route points and agents under that session server instead of using their individual contexts.
Call connection events are received one per call connection. If an event is related to a connection, then a single call can receive multiple call connection events, such as active and disconnected events. Call connection events are delivered even when the address corresponding to the connection is not an observed party but the call is monitored. So if the address corresponding to a specific connection is monitored, then the session server will receive the connection events for all connections associated with that call.
This section provides detailed information about the following call monitoring topics:
•
•
Global Call ID
The Cisco Unified CME adds a Cisco proprietary SIP header field, Global Call ID (GCID), in all outbound SIP messages. The GCID is an H.225-based globally unique call identifier composed of 16 octets. The GCID octets are derived from a combination of the time stamp and a MAC address. This unique ID is a key entity used by both the Unified CME and the session server to identify and authenticate a call. This GCID is the callID value in the event payload.
The GCID is used when a call is redirected or transferred. The SIP call ID changes with a transfer but the GCID field stays the same, regardless of the number of transfers and redirects. The Unified CME manages the GCID and the session server relies on the Unified CME to change or remove the GCID field as necessary.
When the session server generates an outbound call, it generates the GCID, and includes the GCID in the SIP INVITE message. The Unified CME then uses that GCID for the call.
The following is an example of a SIP INVITE message with the Global Call ID field:
INVITE sip:6888@192.0.2.200:5060 SIP/2.0Via: SIP/2.0/TCP 192.0.2.105;branch=z9hG4bKFB10EARemote-Party-ID: <sip:6501@192.0.2.105>;party=calling;screen=no;privacy=offFrom: <sip:6501@192.0.2.105>;tag=285FE8-1574To: <sip:6888@192.0.2.200>Date: Thu, 15 Mar 2007 19:08:04 GMTCall-ID: 5658E3AC-D25F11DB-80CBCC54-BAF89C4F@192.0.2.105Supported: 100rel,timer,resource-priority,replacesMin-SE: 1800Cisco-Guid: 1435306675-3529445851-2160512084-3136855119User-Agent: Cisco-SIPGateway/IOS-12.xAllow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTERCSeq: 101 INVITEMax-Forwards: 70Timestamp: 1173985684Contact: <sip:6501@192.0.2.105:5060;transport=tcp>Call-Info: <sip:192.0.2.105:5060>;method=''NOTIFY;Event=telephone-event;Duration=2000''Expires: 180Allow-Events: telephone-eventCisco-Gcid: 558D0AB3-D25F-11DB-80C6-CC54BAF89C4FContent-Type: application/sdpContent-Disposition: session;handling=requiredContent-Length: 211v=0o=CiscoSystemsSIP-GW-UserAgent 300 5155 IN IP4 192.0.2.105 s=SIP Call c=IN IP4 192.0.2.105 t=0 0 m=audio 19306 RTP/AVP 0 19 c=IN IP4 192.0.2.105 a=rtpmap:0 PCMU/8000a=rtpmap:19 CN/8000a=ptime:20Configure GCID using the gcid command in voice service voip configuration mode of the CLI. When configured, the Cisco Unified CME generates a GCID for outbound calls and adds the Cisco-Gcid header field to INVITE requests, REFER requests, and 180, 183, and 200 responses. The GCID header field is passed from the Unified CME to the session server for every call.
Note
The GCID header field propagates through the call leg to uniquely identify the monitored call. Only one GCID is needed for call monitoring except for the following scenarios, which require two GCIDs:
•
•
For these two GCIDs (those in calls changing to active or ringing state), the surviving GCID (the GCID used between transferee and transfer target) is listed first. With Cisco Unified CME, the surviving GCID is always the GCID between transferrer and transferee.
For a conference call event, only one GCID is included.
Call Monitoring SIP Header Example
The following are example headers for the SIP SUBSCRIBE and SIP NOTIFY messages:
Example: Header fields in a SIP SUBSCRIBE messageSUBSCRIBE sip:2777@mbenenso-cme1.example.com:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.107:5060;branch=z9hG4bKSQi8eZldK7iXqtgLL1Ediw~~4Max-Forwards: 70To: <sip:2777@mbenenso-cme1.example.com>From: <sip:CRS_controller@192.0.2.107>;tag=ds4d17470Call-ID: 11739153122734@192.0.2.107CSeq: 1 SUBSCRIBEContent-Length: 0Contact: <sip:CRS_controller@192.0.2.107:5060;transport=tcp>User-Agent: Cisco-CRS/4.6X-cisco-referenceID: D737A35FEvent: dialogAccept: application/csta+xmlExpires: 2800Authorization: Digestusername="mbenenso",realm="",nonce="F40D17330000B11A",qop=auth,nc=00000003,cnonce="G9052Wml/imp5R+sScjOCw==",response="955fd4c7e44b2b1df8f6658b060c5d78",uri="sip:2777@mbenenso-cme1.example.com:5060;transport=tcp",algorithm=MD5Allow-Events: referAllow-Events: telephone-eventExample: Header fields in a SIP NOTIFY messageNOTIFY sip:CRS_controller@192.0.2.107:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 172.19.238.158;branch=z9hG4bK1B5DFrom: <sip:2777@mbenenso-cme1.example.com>;tag=6EBA4-16FDTo: <sip:CRS_controller@192.0.2.107>;tag=ds4d17470Call-ID: 11739153122734@192.0.2.107CSeq: 101 NOTIFYMax-Forwards: 70Date: Wed, 14 Mar 2007 23:35:13 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2777@172.19.238.158:5060;transport=tcp>Content-Length: 0Call Monitoring CSTA Conventions
This section provides detailed information CSTA conventions in the following topics:
•
•
Device
A device can be either a physical or logical entity. CSTA allows users to observe and modify the device entity to access different telephony services. A device is identified by a deviceID, which functions similarly to a SIP Uniform Resource Identifier (URI) in a SIP network.
Call
A call is the communication relationships between one or more CSTA devices and is identified by a callID. During some call phases, such as establishment and release, the call is not completely formed and there may be only one CSTA device involved. In other call operations, such as a conference or transfer, one device in a call can be replaced by another device or two calls can be merged into one.
A call state refers to a collection of all associated connection states.
Connection
A connection refers to a relationship between a call and a device. Each connection in a call is associated with a connection state. A connection is identified by a connectionID, which consists of both a callID and a deviceID.
Table 2 lists CSTA defined names and descriptions of connection states.
Call Monitoring Cause Strings
There are specific strings used to provide a cause value when status of a call changes:
Call Monitoring Events
All call monitoring events contain the following information:
•
•
Note
Table 3 displays supported CSTA call control events and when they are reported by the Unified CME. The events are listed in semi-chronological order so that each event description and example in this document can build on related events. Each CSTA event name in the list also serves as a cross-reference link to more detailed information, including XML schema examples, for the events listed in this table.
ActiveEvent
The Cisco Unified CME reports an ActiveEvent to the session server when the connection for a given call moves to the active (answered) state. This is a Cisco proprietary event that provides additional information on a newly active connection.
The ActiveEvent is reported under the following circumstances:
•
•
•
•
This call connection event is a vendor-specific event designed for the interworking of Unified CME and a session server. The schema for this event is defined as a Cisco extension to CSTA with the encoded XML event for ActiveEvent included as a subelement to privateData.
Table 4 displays the parameters used for the ActiveEvent SIP NOTIFY message.
Note
OriginatedEvent
The Cisco Unified CME reports an OriginatedEvent to the session server when a monitored line (a local SCCP IP phone) attempts a new call, such as when the handset is lifted or a soft button is pressed on the agent but dialing has not yet taken place.
Table 5 displays the parameters used for the OriginatedEvent SIP NOTIFY message.
Example: privateData Extension schema for OriginatedEvent with associated ActiveEvent for a call attempt from directory number 1001<?xml version="1.0" encoding="UTF-8"?><OriginatedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/originated-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>E41B4F99</monitorCrossRefID><originatedConnection><callID>438AA8BD-D893-11DB-87F4-996E115FF692</callID><deviceID>1001</deviceID></originatedConnection><callingDevice><deviceIdentifier>1001</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier></deviceIdentifier></calledDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:originatedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></cisco-csta-ext:originatedPrivate></private></privateData></extensions></OriginatedEvent><?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>E41B4F99</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>438AA8BD-D893-11DB-87F4-996E115FF692</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>6401</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>1001</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></private></privateData></extensions></cisco-csta-ext:ActiveEvent>OfferedEvent
The Cisco Unified CME reports an OfferedEvent to the session server when an incoming call is delivered to an agent device on a monitored line.
Table 6 displays the parameters used for the OfferedEvent SIP NOTIFY message.
Example: privateData Extension schema for OfferedEvent for a call being offered to DN 1002<?xml version="1.0" encoding="UTF-8"?><OfferedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/offered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>EBC891CD</monitorCrossRefID><offeredConnection><callID>7CADC4A3-D25F-11DB-80D0-CC54BAF89C4F</callID><deviceID>1002</deviceID></offeredConnection><offeredDevice><deviceIdentifier>NULL</deviceIdentifier></offeredDevice><callingDevice><deviceIdentifier>1001</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>1002</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:OfferedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID><originalCalledAddress></originalCalledAddress></cisco-csta-ext:OfferedPrivate></private></privateData></extensions></OfferedEvent>DeliveredEvent
The Cisco Unified CME reports a DeliveredEvent to the session server when one of the connections on a monitored call is in the accept (ringing) state—either the agent device has started ringing for an incoming call or the agent device has begun sending alerts for an outgoing call.
The session server receives only one of these events per connection and only for the call connection that is in the accept (ringing) state regardless of which lines are monitored. For example, if Agent 1 calls Agent 2, then Unified CME reports this event only for Agent 2's connection when ringing regardless if Agent 1 is observed, Agent 2 is observed, or both are observed.
Table 7 displays the parameters used for the DeliveredEvent SIP NOTIFY message.
Example: privateData Extension schema for DeliveredEvent for agent device 1002 in ringing state<?xml version="1.0" encoding="UTF-8"?><DeliveredEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/delivered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>EBC891CD</monitorCrossRefID><connection><callID>7CADC4A3-D25F-11DB-80D0-CC54BAF89C4F</callID><deviceID>1002</deviceID></connection><alertingDevice><deviceIdentifier>NULL</deviceIdentifier></alertingDevice><callingDevice><deviceIdentifier>1001</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>1002</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:deliveredPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></cisco-csta-ext:deliveredPrivate></private></privateData></extensions></DeliveredEvent>EstablishedEvent
The Cisco Unified CME reports an EstablishedEvent to the session server when an incoming call to the agent device is answered or when a call originated from the agent device is answered by the far end. The event is generated when a call is answered by the party that has been ringing and is generated per call so that only one such event is generated when the call moves to the answer state and all call connections are in the active state.
Table 8 displays the parameters used for the EstablishedEvent SIP NOTIFY message.
Example: privateData Extension schema for EstablishedEvent with associated ActiveEvent sent when agent device 1002 answers a call<?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>EBC891CD</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>7CADC4A3-D25F-11DB-80D0-CC54BAF89C4F</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>1001</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>1002</cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>1002</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></private></privateData></extensions></cisco-csta-ext:ActiveEvent><?xml version="1.0" encoding="UTF-8"?><EstablishedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/established-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>EBC891CD</monitorCrossRefID><establishedConnection><callID>7CADC4A3-D25F-11DB-80D0-CC54BAF89C4F</callID><deviceID>NULL</deviceID></establishedConnection><answeringDevice><deviceIdentifier>NULL</deviceIdentifier></answeringDevice><callingDevice><deviceIdentifier>1001</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>1002</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed>NULL</numberDialed></lastRedirectionDevice><cause>normal</cause></EstablishedEvent>ConnectionClearedEvent
The Cisco Unified CME reports a ConnectionClearedEvent to the session server when a connection that is part of a monitored call drops out of the call, such as when one party drops out of a conference a call. However, disconnect is not limited to a conference scenario.
The ConnectionClearedEvent is reported under the following circumstances:
•
•
•
•
•
Table 9 displays the parameters used for the ConnectionClearedEvent SIP NOTIFY message.
Example: privateData Extension schema for ConnectionClearedEvent when route point 6888 drops out after successfully transferring the call to an agent<?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>EBC891CD</monitorCrossRefID><droppedConnection><callID>7CADC4A3-D25F-11DB-80D0-CC54BAF89C4F</callID><deviceID>6888</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>transfer</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>1001</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>6888</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent>CallClearedEvent
The Cisco Unified CME reports a CallClearedEvent to the session server when all connections for a call are disconnected and the call is cleared. This event implies that the call specified by the GCID can now be safely removed from the system.
Table 10 displays the parameters used for the CallClearedEvent SIP NOTIFY message.
Example: privateData Extension schema for CallClearedEvent when a call between DNs 1001 and 1002 is cleared due to a normal disconnection event<?xml version="1.0" encoding="UTF-8"?><CallClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/call-cleared-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>EBC891CD</monitorCrossRefID><clearedCall><callID>7CADC4A3-D25F-11DB-80D0-CC54BAF89C4F</callID><deviceID>NULL</deviceID></clearedCall><cause>normalClearing</cause><extensions><privateData><private><droppedPrivate><cisco-csta-ext:callingDirectoryNumber>1001</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>1002</cisco-csta-ext:calledDirectoryNumber></droppedPrivate></private></privateData></extensions></CallClearedEvent>FailedEvent
The Cisco Unified CME reports a FailedEvent to the session server when an outbound call cannot be completed, such as when a party is busy.
Table 11 displays the parameters used for the FailedEvent SIP NOTIFY message.
Example: privateData Extension schema for FailedEvent when a call from device 1001 to device 9999 cannot be completed due to an unallocated destination number (Unified CME cannot resolve to any outbound dial peer)<?xml version="1.0" encoding="UTF-8"?><FailedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/failed-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>306D4BB2</monitorCrossRefID><failedConnection><callID>3A780EF7-EDEB-11DB-8E93-C3B7F63094E9</callID><deviceID>9999</deviceID></failedConnection><failingDevice><deviceIdentifier>NULL</deviceIdentifier></failingDevice><callingDevice><deviceIdentifier>1001</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>9999</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed>NULL</numberDialed></lastRedirectionDevice><cause>numberUnallocated</cause><extensions><privateData><private><cisco-csta-ext:FailedPrivate><cisco-csta-ext:callDirection>TRUE</cisco-csta-ext:callDirection></cisco-csta-ext:FailedPrivate></private></privateData></extensions></FailedEvent>HeldEvent
The Cisco Unified CME reports HeldEvent to the session server when a call is put on hold, locally or remotely, by one of the parties connected to the call. This event is generated per connection to associate the connection with the held event.
Table 12 displays the parameters used for the HeldEvent SIP NOTIFY message.
Example: privateData Extension schema for HeldEvent when a call from device 2001 to route point 6888 is put on hold by the destination route point<?xml version="1.0" encoding="UTF-8"?><HeldEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/held-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>306D4BB2</monitorCrossRefID><heldConnection><callID>3A780EF7-EDEB-11DB-8E93-C3B7F63094E9</callID><deviceID>6888</deviceID></heldConnection><holdingDevice><deviceIdentifier>NULL</deviceIdentifier></holdingDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:HeldPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>1001</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>6888</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:HeldPrivate></private></privateData></extensions></HeldEvent>RetrievedEvent
The Cisco Unified CME reports RetrievedEvent to the session server when a call that was put on hold is resumed, locally or remotely. This event is generated per connection to associate the connection with the held event.
Table 13 displays the parameters used for the RetrievedEvent SIP NOTIFY message.
Example: privateData Extension schema for RetrievedEvent when a call from device 1001, put on hold by route point 6888, is resumed (taken off hold) by that same route point<?xml version="1.0" encoding="UTF-8"?><RetrievedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/retrieved-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>306D4BB2</monitorCrossRefID><retrievedConnection><callID>3A780EF7-EDEB-11DB-8E93-C3B7F63094E9</callID><deviceID>6888</deviceID></retrievedConnection><retrievingDevice><deviceIdentifier>NULL</deviceIdentifier></retrievingDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:RetrievedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>1001</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>6888</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:RetrievedPrivate></private></privateData></extensions></RetrievedEvent>TransferredEvent
The Cisco Unified CME reports a TransferredEvent to the session server when a consult transfer is successfully completed—a resulting call is established between the transferee and transfer-target, reusing the callID of the original primary call. Once the transfer is complete, the transferrer connections and the consult call are cleared.
A route point as a consult transferrer is not supported.
Note
The following sequence of events is typical following a TransferredEvent. (In this sequence, primary calls take GCID1 and secondary calls take GCID2.)
Table 14 displays the parameters used for the TransferredEvent SIP NOTIFY message.
Example: privateData Extension schema for TransferredEvent when device 1002 transfers caller 1001 to consulted party 1003
Note
The consult call (C2C3A6A9-D893-11DB-8801-996E115FF692) is cleared.This example, in addition to the TransferredEvent message, displays the associated ConnectionClearedEvent, CallClearedEvent, and ActiveEvent messages.
<?xml version="1.0" encoding="UTF-8"?><TransferredEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/transferred-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>E41B4F99</monitorCrossRefID><primaryOldCall><callID>AE48ECBC-D893-11DB-87FC-996E115FF692</callID><deviceID>NULL</deviceID></primaryOldCall><secondaryOldCall><callID></callID><deviceID>NULL</deviceID></secondaryOldCall><transferringDevice><deviceIdentifier>1002</deviceIdentifier></transferringDevice><transferredToDevice><deviceIdentifier>1003</deviceIdentifier></transferredToDevice><transferredConnections><connectionListItem><newConnection><callID>C2C3A6A9-D893-11DB-8801-996E115FF692</callID></newConnection><oldConnection><callID>AE48ECBC-D893-11DB-87FC-996E115FF692</callID></oldConnection><endpoint><deviceID>1001</deviceID></endpoint></connectionListItem></transferredConnections><cause>normal</cause></TransferredEvent><?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>E41B4F99</monitorCrossRefID><droppedConnection><callID>C2C3A6A9-D893-11DB-8801-996E115FF692</callID><deviceID>1002</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>transfer</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>1002</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>1003</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent><?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>E41B4F99</monitorCrossRefID><droppedConnection><callID>C2C3A6A9-D893-11DB-8801-996E115FF692</callID><deviceID>1003</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>transfer</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>1002</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>1003</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent><?xml version="1.0" encoding="UTF-8"?><CallClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/call-cleared-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>E41B4F99</monitorCrossRefID><clearedCall><callID>C2C3A6A9-D893-11DB-8801-996E115FF692</callID><deviceID>NULL</deviceID></clearedCall><cause>transfer</cause><extensions><privateData><private><droppedPrivate><cisco-csta-ext:callingDirectoryNumber>1002</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>1003</cisco-csta-ext:calledDirectoryNumber></droppedPrivate></private></privateData></extensions></CallClearedEvent><?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>E41B4F99</monitorCrossRefID><droppedConnection><callID>AE48ECBC-D893-11DB-87FC-996E115FF692</callID><deviceID>1002</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>transfer</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>1001</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>1002</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent><?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>E41B4F99</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>AE48ECBC-D893-11DB-87FC-996E115FF692</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>1001</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>1003</cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>1003</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></private></privateData></extensions></cisco-csta-ext:ActiveEvent>ConferencedEvent
The Cisco Unified CME reports a ConferencedEvent to the session server when a call conference is successfully established. This is a call event that indicates two or more calls are merging by connecting their connections into a single call after a conference operation, reusing the callID of the original primary call.
All secondary calls and associated connections are cleared and take on a new connectionID.
The following sequence of events is typical following a ConferencedEvent. (In this sequence, primary calls take GCID1 and secondary calls take GCID2.)
•
(controller,
GCID1)
•
(controller,
GCID2)
•
(participant 2,
GCID2)
•
(GCID2)
•
(participant 2,
GCID1)
Table 15 displays the parameters used for the ConferencedEvent SIP NOTIFY message.
Example: privateData Extension schema for ConferencedEvent when controller 2803 has conferenced primary party 2807 and secondary party 2808
Note
The consult call (C929F81E-13B7-11DC-8372-9790DDA32D45) is cleared.This example, in addition to the ConferencedEvent message, displays the associated RetrievedEvent, ConnectionClearedEvent, CallClearedEvent, and ActiveEvent messages.
<?xml version="1.0" encoding="UTF-8"?><ConferencedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/conferenced-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><primaryOldCall><callID>BE95D856-13B7-11DC-836A-9790DDA32D45</callID><deviceID>NULL</deviceID></primaryOldCall><secondaryOldCall><callID></callID><deviceID>NULL</deviceID></secondaryOldCall><conferencingDevice><deviceIdentifier>2803</deviceIdentifier></conferencingDevice><addedParty><deviceIdentifier>NULL</deviceIdentifier></addedParty><conferenceConnections><connectionListItem><newConnection><callID> C929F81E-13B7-11DC-8372-9790DDA32D45</callID><deviceID>2808</deviceID></newConnection><oldConnection><callID>BE95D856-13B7-11DC-836A-9790DDA32D45</callID><deviceID>2807</deviceID></oldConnection><endpoint><deviceID>2808</deviceID></endpoint></connectionListItem></conferenceConnections><cause>normal</cause></ConferencedEvent><?xml version="1.0" encoding="UTF-8"?><RetrievedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/retrieved-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><retrievedConnection><callID>BE95D856-13B7-11DC-836A-9790DDA32D45</callID><deviceID>2803</deviceID></retrievedConnection><retrievingDevice><deviceIdentifier>NULL</deviceIdentifier></retrievingDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:RetrievedPrivate><cisco-csta-ext:callDirection>TRUE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2807</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2803</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:RetrievedPrivate></private></privateData></extensions></RetrievedEvent><?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd " xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><droppedConnection><callID>C929F81E-13B7-11DC-8372-9790DDA32D45</callID><deviceID>2803</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>Conference</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent><?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd " xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><droppedConnection><callID>C929F81E-13B7-11DC-8372-9790DDA32D45</callID><deviceID>2808</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>Conference</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent><?xml version="1.0" encoding="UTF-8"?><CallClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/call-cleared-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><clearedCall><callID>C929F81E-13B7-11DC-8372-9790DDA32D45</callID><deviceID>NULL</deviceID></clearedCall><cause>Conference</cause><extensions><privateData><private><droppedPrivate><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber></droppedPrivate></private></privateData></extensions></CallClearedEvent><?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>BE95D856-13B7-11DC-836A-9790DDA32D45</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>2808</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>consult</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></private></privateData></extensions></cisco-csta-ext:ActiveEvent>ECMA-323 Standard Reference
Table 16 includes the various top-level element names and the specific section of the ECMA-323 standard that defines each element's XML schema. Use this table to find more detailed information about the XML schema used to send event messages between the Cisco Unified CME and a session server for call and line monitoring functions.
Table 16 Sectional References to ECMA-323 for CSTA Events
ConnectionClearedEvent
15.2.4
CallClearedEvent
15.2.2
FailedEvent
15.2.9
HeldEvent
15.2.10
OriginatedEvent
15.2.14
OfferedEvent
15.2.13
DeliveredEvent
15.2.5
RetrievedEvent
15.2.6
EstablisehdEvent
15.2.8
ConferencedEvent
15.2.3
TransferredEvent
15.2.18
PrivateEvent
26.3.1
MonitorStart
13.1.2
MonitorStartResponse
13.1.2
MonitorStop
13.1.3
MonitorStopResponse
13.1.3
Cisco Extension to ECMA-323
The following is an example of the Cisco proprietary extension to the ECMA-323 standard to provide private and vendor-specific information in call and line monitoring functions:
Example: Cisco-csta-ext.xsd<?xml version="1.0" encoding="UTD-8"?><xsd:schema targetNameSpace="Cisco-CSTA-Extension/V1"xmlns:xsd=http://www.example.org/2001/XMLSchemaxmlns:csta=http://www.ecma-internaitonal.org/standards/ecma-323/csta/ed3xmlns:cisco-csta-ext=cisco-csta-extelementFormDefault="qualified" attributeFormDefault="unqualified"><xsd:annotation><xsd:documentation>cisco-csta-ext-call-active-event</xsd:documentation></xsd:annotation><xsd:include schemaLocation="device-identifiers.xsd"/><xsd:include schemaLocation="call-connection-identifiers.xsd"/><xsd:element name="ActiveEvent"><xsd:complextType><xsd:sequence><xsd:element name="gcid" type="csta:CallID"><xsd:element name="callDirection" type="xsd:boolean"/><xsd:element name="callingDirectoryNumber" type="csta:deviceID" /><xsd:element name="calledDirectoryNumber" type="csta:deviceID" /><xsd:element name="connectionAddress" type="csta:deviceID"/><xsd:element name="lastRedirectedAddress" type="csta:deviceID" minOccurs="0" /><xsd:element name="originalCalledAddress" type="csta:deviceID" minOccurs="0" /><xsd:element name="callType" type="cisco-csta-ext:callType"/><xsd:element name="parentGCID" type="csta:CallID"minOccurs="0" /></xsd:sequence></xsd:complexType></xsd:element><xsd:annotation><xsd:documentation>cisco-csta-ext-CallConnectionClearedEvent-private-data</xsd:documentation></xsd:annotation><xsd:element name="CallConnectionClearedPrivate"><xsd:complextType><xsd:sequence><xsd:element name="callDirection" type="xsd:boolean"/><xsd:element name="callingDirectoryNumber" type="csta:deviceID" /><xsd:element name="calledDirectoryNumber" type="csta:deviceID" /></xsd:sequence></xsd:complextType></xsd:element><xsd:annotation><xsd:documentation>cisco-csta-ext-FailedEvent-private-data</xsd:documentation></xsd:annotation><xsd:element name="FailedPrivate"><xsd:complextType><xsd:sequence><xsd:element name="callDirection" type="xsd:boolean"/></xsd:sequence></xsd:complextType></xsd:element><xsd:annotation><xsd:documentation>cisco-csta-ext-HeldEvent-private-data</xsd:documentation></xsd:annotation><xsd:element name="HeldPrivate"><xsd:complextType><xsd:sequence><xsd:element name="callDirection" type="xsd:boolean"/><xsd:element name="callingDirectoryNumber" type="csta:deviceID" /><xsd:element name="calledDirectoryNumber" type="csta:deviceID" /></xsd:sequence></xsd:complextType></xsd:element><xsd:annotation><xsd:documentation>cisco-csta-ext-OriginatedEvent-private-data</xsd:documentation></xsd:annotation><xsd:element name="OriginatedPrivate"><xsd:complextType><xsd:sequence><xsd:element name="callDirection" type="xsd:boolean"/><xsd:element name="callType" type="cisco-csta-ext:callType"/><xsd:element name="parentGCID" type="csta:CallID" minOccurs="0" /></xsd:sequence></xsd:complextType></xsd:element><xsd:annotation><xsd:documentation>cisco-csta-ext-OfferedEvent-private-data</xsd:documentation></xsd:annotation><xsd:element name="OfferedPrivate"><xsd:complextType><xsd:sequence><xsd:element name="callDirection" type="xsd:boolean"/><xsd:element name="callType" type="cisco-csta-ext:callType"/><xsd:element name="parentGCID" type="csta:CallID" minOccurs="0" /><xsd:element name="originalCalledParty" type="csta:deviceID" /></xsd:sequence></xsd:complextType></xsd:element><xsd:annotation><xsd:documentation>cisco-csta-ext-DeliveredEvent-private-data</xsd:documentation></xsd:annotation><xsd:element name="DeliveredPrivate"><xsd:complextType><xsd:sequence><xsd:element name="callDirection" type="xsd:boolean"/><xsd:element name="parentGCID" type="csta:CallID" minOccurs="0" /><xsd:element name="callType" type="cisco-csta-ext:callType"/></xsd:sequence></xsd:complextType></xsd:element><xsd:annotation><xsd:documentation>cisco-csta-ext-RetrievedEvent-private-data</xsd:documentation></xsd:annotation><xsd:element name="RetrievedPrivate"><xsd:complextType><xsd:sequence><xsd:element name="callDirection" type="xsd:boolean"/><xsd:element name="callingDirectoryNumber" type="csta:deviceID" /><xsd:element name="calledDirectoryNumber" type="csta:deviceID" /></xsd:sequence></xsd:complextType></xsd:element><xsd:annotation><xsd:documentation>cisco-csta-ext-call-CallClearedEvent-private-data</xsd:documentation></xsd:annotation><xsd:element name="CallClearedPrivate"><xsd:complextType><xsd:sequence><xsd:element name="callingDirectoryNumber" type="csta:deviceID" /><xsd:element name="calledDirectoryNumber" type="csta:deviceID" /></xsd:sequence></xsd:complextType></xsd:element><xsd:element name="callType"><xsd:simpleType><xsd:restriction base="string"><xsd:enumeration value="direct"/><xsd:enumeration value="consult"/><xsd:enumeration value="unknown"/></xsd:restriction></xsd:eimpleType></xsd:element></xsd:schema>Additional References
The following sections provide references related to the call monitoring interface feature:
•
•
Related Documents
Using and managing:
•
•
•
•
Cisco Unified CME documentation, by version
Using Cisco Unified CME commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples
Cisco Unified Communications Manager Express Command Reference
Using and managing:
•
•
•
Cisco Customer Response Solutions Administration Guide, Release 4.1(1)
Using and managing:
•
•
Using and managing:
•
(formerly Cisco Unified CallManager)•
Cisco Unified CallManager System Guide, Release 4.0(1)
Implementing Cisco SIP to enable supported Cisco platforms to signal the configuration of voice and multimedia calls over IP networks
Cisco IOS SIP Configuration Guide, Release 12.4
Using and managing Cisco Unified Survivable Remote Site Telephony (SRST)
Cisco Unified SRST documentation, all versions
Configuring various Cisco IOS Voice products
Cisco IOS Voice Configuration Library
Accessing Voice and Unified Communications support resources
Voice and Unified Communications Support Resources
Standards
ECMA-323
XML Protocol for Computer Supported Telecommunications Applications (CSTA) Phase III
ECMA-269
Services for Computer Supported Telecommunications Applications (CSTA) Phase III
MIBs
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator.
The Cisco MIB Locator is located at the following URL:
RFCs
•
•
Session Initiation Protocol (SIP)-Specific Event Notification
•
A Presence Event Package for the Session Initiation Protocol (SIP)
•
•
An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)
•
•
RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)
Technical Assistance
Command Reference
For Cisco IOS CLI commands associated with this feature, refer to the Cisco Unified CME Command Reference.
Call Monitoring Scenario Examples
This section provides the overall SIP message flow for some of the more common call scenarios. The following example scenarios include the complete set of session control messages along with all presence (line monitoring) and dialog (call monitoring) event notifications.
•
•
•
Note
Scenario 1: Basic Call Scenario
This example scenario shows the user agent calling SCCP A, connecting, and then hanging up:
Jun 6 22:33:01.330: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK596BFFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 128 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:33:01 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1084<?xml version="1.0" encoding="UTF-8"?><OriginatedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/originated-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><originatedConnection><callID>B7AFD639-13B4-11DC-8330-9790DDA32D45</callID><deviceID>2803</deviceID></originatedConnection><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier></deviceIdentifier></calledDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:originatedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></cisco-csta-ext:originatedPrivate></private></privateData></extensions></OriginatedEvent>Jun 6 22:33:01.334: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK596BFTo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 128 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:33:01.334: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK5A15E5From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 129 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:33:01 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1190<?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>B7AFD639-13B4-11DC-8330-9790DDA32D45</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>2803</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></private></privateData></extensions></cisco-csta-ext:ActiveEvent>Jun 6 22:33:01.350: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK5A15E5To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 129 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:33:03.078: DestCheckTeleUnassBusy cvif OperStatus 5, Type 1A, status 40020Jun 6 22:33:03.086: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK5BA36From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 130 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:33:03 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1268<?xml version="1.0" encoding="UTF-8"?><OfferedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/offered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><offeredConnection><callID>B7AFD639-13B4-11DC-8330-9790DDA32D45</callID><deviceID>2807</deviceID></offeredConnection><offeredDevice><deviceIdentifier>NULL</deviceIdentifier></offeredDevice><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2807</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:OfferedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID><originalCalledAddress></originalCalledAddress></cisco-csta-ext:OfferedPrivate></private></privateData></extensions></OfferedEvent>Jun 6 22:33:03.094: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK5BA36To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 130 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:33:03.094: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK5C11C6From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 131 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:33:03 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1218<?xml version="1.0" encoding="UTF-8"?><DeliveredEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/delivered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><connection><callID>B7AFD639-13B4-11DC-8330-9790DDA32D45</callID><deviceID>2807</deviceID></connection><alertingDevice><deviceIdentifier>NULL</deviceIdentifier></alertingDevice><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2807</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:deliveredPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></cisco-csta-ext:deliveredPrivate></private></privateData></extensions></DeliveredEvent>Jun 6 22:33:03.106: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK5C11C6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 131 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:33:05.066: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK5DF49From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 132 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:33:05 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1194<?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>B7AFD639-13B4-11DC-8330-9790DDA32D45</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2807</cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>2807</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></private></privateData></extensions></cisco-csta-ext:ActiveEvent>Jun 6 22:33:05.086: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK5DF49To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 132 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:33:05.086: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK5E2371From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 133 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:33:05 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 925<?xml version="1.0" encoding="UTF-8"?><EstablishedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/established-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><establishedConnection><callID>B7AFD639-13B4-11DC-8330-9790DDA32D45</callID><deviceID>NULL</deviceID></establishedConnection><answeringDevice><deviceIdentifier>NULL</deviceIdentifier></answeringDevice><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2807</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed>NULL</numberDialed></lastRedirectionDevice><cause>normal</cause></EstablishedEvent>Jun 6 22:33:05.094: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK5E2371To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 133 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:33:05.706: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
REGISTER sip:192.0.2.7:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~22Max-Forwards: 70To: <sip:CRS_controller@192.0.2.7>From: <sip:CRS_controller@192.0.2.7>;tag=dsa8afec60Call-ID: 11811688223121@192.0.2.9CSeq: 13 REGISTERContent-Length: 0Contact: <sip:CRS_controller@192.0.2.9:5060;transport=tcp>;expires=160Allow: INVITE, BYE, CANCEL, ACK, NOTIFYUser-Agent: Cisco-CRS/4.6X-cisco-session-server: CRS1Jun 6 22:33:05.710: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
SIP/2.0 100 TryingVia: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~22From: <sip:CRS_controller@192.0.2.7>;tag=dsa8afec60To: <sip:CRS_controller@192.0.2.7>Date: Wed, 06 Jun 2007 22:33:05 GMTCall-ID: 11811688223121@192.0.2.9Server: Cisco-SIPGateway/IOS-12.xCSeq: 13 REGISTERContent-Length: 0Jun 6 22:33:05.710: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
SIP/2.0 200 OKVia: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~22From: <sip:CRS_controller@192.0.2.7>;tag=dsa8afec60To: <sip:CRS_controller@192.0.2.7>;tag=4D2E943C-1FB3Date: Wed, 06 Jun 2007 22:33:05 GMTCall-ID: 11811688223121@192.0.2.9Server: Cisco-SIPGateway/IOS-12.xCSeq: 13 REGISTERX-cisco-referenceID: 48F1DB51Contact: <sip:CRS_controller@192.0.2.9:5060;transport=tcp>;expires=160Expires: 160Content-Length: 0Jun 6 22:33:08.066: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK5F25A3From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 134 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:33:08 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1116<?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd " xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><droppedConnection><callID>B7AFD639-13B4-11DC-8330-9790DDA32D45</callID><deviceID>2803</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>normalClearing</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2807</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent>Jun 6 22:33:08.070: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK5F25A3To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 134 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:33:08.074: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6011BFFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 135 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:33:08 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1116<?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd " xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><droppedConnection><callID>B7AFD639-13B4-11DC-8330-9790DDA32D45</callID><deviceID>2807</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>normalClearing</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2807</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent>Jun 6 22:33:08.082: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6011BFTo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 135 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:33:08.086: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK615FFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 136 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:33:08 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 882<?xml version="1.0" encoding="UTF-8"?><CallClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/call-cleared-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><clearedCall><callID>B7AFD639-13B4-11DC-8330-9790DDA32D45</callID><deviceID>NULL</deviceID></clearedCall><cause>normalClearing</cause><extensions><privateData><private><droppedPrivate><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2807</cisco-csta-ext:calledDirectoryNumber></droppedPrivate></private></privateData></extensions></CallClearedEvent>Jun 6 22:33:08.098: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK615FTo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 136 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventScenario 2: Routing Point Transfer Call to Agent
This example displays message flow for a call coming into RP from SCCP A, connecting, and then being transferred by RP to AG:
Jun 6 22:36:41.282: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
INVITE sip:2229@192.0.2.9:5060 SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6215ADRemote-Party-ID: "Remote IP9" <sip:2807@192.0.2.7>;party=calling;screen=no;privacy=offFrom: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>Date: Wed, 06 Jun 2007 22:36:41 GMTCall-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7Supported: 100rel,timer,resource-priority,replacesMin-SE: 1800Cisco-Guid: 972226503-330633692-2201655184-3718458693User-Agent: Cisco-SIPGateway/IOS-12.xAllow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTERCSeq: 101 INVITEMax-Forwards: 70Timestamp: 1181169401Contact: <sip:2807@192.0.2.7:5060;transport=tcp>Call-Info: <sip:192.0.2.7:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"Expires: 180Allow-Events: telephone-eventCisco-Gcid: 39F2FFC7-13B5-11DC-833A-9790DDA32D45Content-Type: application/sdpContent-Disposition: session;handling=requiredContent-Length: 203v=0o=CiscoSystemsSIP-GW-UserAgent 4096 8192 IN IP4 192.0.2.7s=SIP Callc=IN IP4 192.0.2.7t=0 0m=audio 17738 RTP/AVP 0 19c=IN IP4 192.0.2.7a=rtpmap:0 PCMU/8000a=rtpmap:19 CN/8000a=ptime:20Jun 6 22:36:41.286: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK63690From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 137 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:41 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1268<?xml version="1.0" encoding="UTF-8"?><OfferedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/offered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><offeredConnection><callID>39F2FFC7-13B5-11DC-833A-9790DDA32D45</callID><deviceID>2229</deviceID></offeredConnection><offeredDevice><deviceIdentifier>NULL</deviceIdentifier></offeredDevice><callingDevice><deviceIdentifier>2807</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2229</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:OfferedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID><originalCalledAddress></originalCalledAddress></cisco-csta-ext:OfferedPrivate></private></privateData></extensions></OfferedEvent>Jun 6 22:36:41.286: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6415D3From: <sip:2229@192.0.2.7>;tag=4D1FEE90-31BTo: <sip:CRS_controller@192.0.2.9>;tag=ds1e98edb8Call-ID: 11811688226563@192.0.2.9CSeq: 104 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:41 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: presenceSubscription-State: active;expires=1624Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/pidf+xmlContent-Length: 489<?xml version="1.0" encoding="UTF-8"?><presence xmlns="urn:ietf:params:xml:ns:pidf" entity="sip:2229@192.0.2.7" xmlns:e="urn:ietf:params:xml:ns:pidf:status:rpid" xmlns:rpid="urn:ietf:params:xml:ns:pidf:status:rpid" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"><dm:person><status><basic>Open</basic></status><e:activities><e:on-the-phone/></e:activities></dm:person><tupleid="cisco-cme"><status><basic>Open</basic><rpid:activeIdle>active</rpid:activeIdle></status></tuple></presence>Jun 6 22:36:41.306: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 100 TryingVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6215ADTo: <sip:2229@192.0.2.9>From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 101 INVITEContent-Length: 0Timestamp: 1181169401Jun 6 22:36:41.306: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK63690To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 137 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:41.322: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6415D3To: <sip:CRS_controller@192.0.2.9>;tag=ds1e98edb8From: <sip:2229@192.0.2.7>;tag=4D1FEE90-31BCall-ID: 11811688226563@192.0.2.9CSeq: 104 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:41.346: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 180 RingingVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6215ADTo: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 101 INVITEContent-Length: 0Contact: <sip:2229@192.0.2.9:5060;transport=tcp>Allow: INVITE, BYE, CANCEL, ACK, NOTIFYServer: Cisco-CRS/4.6Cisco-Gcid: 39F2FFC7-13B5-11DC-833A-9790DDA32D45Jun 6 22:36:41.350: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK651F92From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 138 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:41 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1218<?xml version="1.0" encoding="UTF-8"?><DeliveredEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/delivered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><connection><callID>39F2FFC7-13B5-11DC-833A-9790DDA32D45</callID><deviceID>2229</deviceID></connection><alertingDevice><deviceIdentifier>NULL</deviceIdentifier></alertingDevice><callingDevice><deviceIdentifier>2807</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2229</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:deliveredPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></cisco-csta-ext:deliveredPrivate></private></privateData></extensions></DeliveredEvent>Jun 6 22:36:41.358: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK651F92To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 138 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:44.450: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6215ADTo: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 101 INVITEContent-Length: 126Contact: <sip:2229@192.0.2.9:5060;transport=tcp>Content-Type: application/sdpCall-Info: <sip:192.0.2.9:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"Allow-Events: telephone-eventAllow: INVITE, BYE, CANCEL, ACK, NOTIFYServer: Cisco-CRS/4.6Cisco-Gcid: 39F2FFC7-13B5-11DC-833A-9790DDA32D45v=0o=Cisco-CRS 1440 1 IN IP4 192.0.2.9s=SIP Callc=IN IP4 192.0.2.9t=0 0m=audio 1044 RTP/AVP 0a=rtpmap:0 PCMU/8000Jun 6 22:36:44.454: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
ACK sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6615A8From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Date: Wed, 06 Jun 2007 22:36:41 GMTCall-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7Max-Forwards: 70CSeq: 101 ACKAllow-Events: telephone-eventContent-Length: 0Jun 6 22:36:44.454: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK672699From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 139 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:44 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1194<?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>39F2FFC7-13B5-11DC-833A-9790DDA32D45</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2807</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2229</cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>2229</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></private></privateData></extensions></cisco-csta-ext:ActiveEvent>Jun 6 22:36:44.474: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK672699To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 139 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:44.474: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK68321From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 140 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:44 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 925<?xml version="1.0" encoding="UTF-8"?><EstablishedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/established-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><establishedConnection><callID>39F2FFC7-13B5-11DC-833A-9790DDA32D45</callID><deviceID>NULL</deviceID></establishedConnection><answeringDevice><deviceIdentifier>NULL</deviceIdentifier></answeringDevice><callingDevice><deviceIdentifier>2807</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2229</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed>NULL</numberDialed></lastRedirectionDevice><cause>normal</cause></EstablishedEvent>Jun 6 22:36:44.494: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK68321To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 140 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:46.718: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK692E4From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 102 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:46 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: telephone-eventSubscription-State: activeContact: <sip:192.0.2.7:5060;transport=tcp>Content-Type: audio/telephone-eventContent-Length: 4Jun 6 22:36:46.722: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK692E4To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 102 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:46.722: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6AB0CFrom: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 103 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:46 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: telephone-eventSubscription-State: activeContact: <sip:192.0.2.7:5060;transport=tcp>Content-Type: audio/telephone-eventContent-Length: 4Jun 6 22:36:46.730: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6AB0CTo: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 103 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:47.026: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6BDAFrom: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 104 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:47 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: telephone-eventSubscription-State: activeContact: <sip:192.0.2.7:5060;transport=tcp>Content-Type: audio/telephone-eventContent-Length: 4Jun 6 22:36:47.034: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6BDATo: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 104 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:47.034: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6C11C4From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 105 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:47 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: telephone-eventSubscription-State: activeContact: <sip:192.0.2.7:5060;transport=tcp>Content-Type: audio/telephone-eventContent-Length: 4Jun 6 22:36:47.038: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6C11C4To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 105 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:47.246: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6D1E26From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 106 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:47 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: telephone-eventSubscription-State: activeContact: <sip:192.0.2.7:5060;transport=tcp>Content-Type: audio/telephone-eventContent-Length: 4Jun 6 22:36:47.254: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6D1E26To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 106 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:47.254: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6E1747From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 107 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:47 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: telephone-eventSubscription-State: activeContact: <sip:192.0.2.7:5060;transport=tcp>Content-Type: audio/telephone-eventContent-Length: 4Jun 6 22:36:47.262: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6E1747To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 107 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:47.538: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6FEE4From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 108 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:47 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: telephone-eventSubscription-State: activeContact: <sip:192.0.2.7:5060;transport=tcp>Content-Type: audio/telephone-eventContent-Length: 4Jun 6 22:36:47.542: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK6FEE4To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 108 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:47.542: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK7016DFFrom: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 109 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:47 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: telephone-eventSubscription-State: activeContact: <sip:192.0.2.7:5060;transport=tcp>Content-Type: audio/telephone-eventContent-Length: 4Jun 6 22:36:47.550: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK7016DFTo: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 109 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:47.858: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK7118C8From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 110 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:47 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: telephone-eventSubscription-State: activeContact: <sip:192.0.2.7:5060;transport=tcp>Content-Type: audio/telephone-eventContent-Length: 4Jun 6 22:36:47.866: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK7118C8To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 110 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:47.866: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK72FC7From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 111 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:47 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: telephone-eventSubscription-State: activeContact: <sip:192.0.2.7:5060;transport=tcp>Content-Type: audio/telephone-eventContent-Length: 4Jun 6 22:36:47.874: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK72FC7To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 111 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:47.882: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
INVITE sip:2807@192.0.2.7:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~25Max-Forwards: 70To: <sip:2807@192.0.2.7>;tag=4D31DE54-1489From: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 1 INVITEContent-Length: 137Contact: <sip:2229@192.0.2.9:5060;transport=tcp>Content-Type: application/sdpCall-Info: <sip:192.0.2.9:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"Allow-Events: telephone-eventAllow: INVITE, BYE, CANCEL, ACK, NOTIFYUser-Agent: Cisco-CRS/4.6Cisco-Gcid: 39F2FFC7-13B5-11DC-833A-9790DDA32D45v=0o=Cisco-CRS 907 1 IN IP4 192.0.2.9s=SIP Callc=IN IP4 192.0.2.9t=0 0m=audio 1044 RTP/AVP 0a=rtpmap:0 PCMU/8000a=sendonlyJun 6 22:36:47.886: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
SIP/2.0 100 TryingVia: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~25From: <sip:2229@192.0.2.9>;tag=dsf8c9ed89To: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Date: Wed, 06 Jun 2007 22:36:47 GMTCall-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7Server: Cisco-SIPGateway/IOS-12.xCSeq: 1 INVITEAllow-Events: telephone-eventContent-Length: 0Jun 6 22:36:47.886: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
SIP/2.0 200 OKVia: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~25From: <sip:2229@192.0.2.9>;tag=dsf8c9ed89To: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Date: Wed, 06 Jun 2007 22:36:47 GMTCall-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7Server: Cisco-SIPGateway/IOS-12.xCSeq: 1 INVITEAllow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTERAllow-Events: telephone-eventRemote-Party-ID: "Remote IP9" <sip:2807@192.0.2.7>;party=called;screen=no;privacy=offContact: <sip:2807@192.0.2.7:5060;transport=tcp>Supported: replacesCall-Info: <sip:192.0.2.7:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"Content-Type: application/sdpContent-Length: 179v=0o=CiscoSystemsSIP-GW-UserAgent 4096 8192 IN IP4 192.0.2.7s=SIP Callc=IN IP4 192.0.2.7t=0 0m=audio 17738 RTP/AVP 0c=IN IP4 192.0.2.7a=recvonlya=rtpmap:0 PCMU/8000Jun 6 22:36:47.890: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK731FB5From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 141 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:47 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1024<?xml version="1.0" encoding="UTF-8"?><HeldEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/held-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><heldConnection><callID>39F2FFC7-13B5-11DC-833A-9790DDA32D45</callID><deviceID>2229</deviceID></heldConnection><holdingDevice><deviceIdentifier>NULL</deviceIdentifier></holdingDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:HeldPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2807</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2229</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:HeldPrivate></private></privateData></extensions></HeldEvent>Jun 6 22:36:47.898: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK731FB5To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 141 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:47.926: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
ACK sip:2807@192.0.2.7:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~26Max-Forwards: 70To: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489From: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 1 ACKContent-Length: 0Contact: <sip:2229@192.0.2.9:5060;transport=tcp>Jun 6 22:36:47.926: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
REFER sip:2807@192.0.2.7:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~27Max-Forwards: 70To: <sip:2807@192.0.2.7>;tag=4D31DE54-1489From: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 2 REFERContent-Length: 0Contact: <sip:2229@192.0.2.9:5060;transport=tcp>Referred-By: <sip:2229@192.0.2.7>Refer-To: <sip:2803@192.0.2.7:5060>Call-Info: <urn:x-cisco-remotecc:delayDisconnect>;reason=blind transferAllow: INVITE, BYE, CANCEL, ACK, NOTIFYUser-Agent: Cisco-CRS/4.6Cisco-Gcid: 39F2FFC7-13B5-11DC-833A-9790DDA32D45Jun 6 22:36:47.930: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
SIP/2.0 202 AcceptedVia: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~27From: <sip:2229@192.0.2.9>;tag=dsf8c9ed89To: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Date: Wed, 06 Jun 2007 22:36:47 GMTCall-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 2 REFERContent-Length: 0Contact: <sip:2807@192.0.2.7:5060;transport=tcp>Jun 6 22:36:47.930: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK74A67From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 112 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:47 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: referSubscription-State: pending;expires=180Contact: <sip:192.0.2.7:5060;transport=tcp>Content-Type: message/sipfragContent-Length: 22SIP/2.0 100 TryingJun 6 22:36:47.930: DestCheckTeleUnassBusy cvif OperStatus 5, Type 1A, status 40020Jun 6 22:36:47.934: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK75251AFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 142 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:47 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1272<?xml version="1.0" encoding="UTF-8"?><OfferedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/offered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><offeredConnection><callID>39F2FFC7-13B5-11DC-833A-9790DDA32D45</callID><deviceID>2803</deviceID></offeredConnection><offeredDevice><deviceIdentifier>NULL</deviceIdentifier></offeredDevice><callingDevice><deviceIdentifier>2807</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2803</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed>2229</numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:OfferedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID><originalCalledAddress></originalCalledAddress></cisco-csta-ext:OfferedPrivate></private></privateData></extensions></OfferedEvent>Jun 6 22:36:47.942: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK74A67To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 112 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:47.942: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK761AB9From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 113 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:47 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: referSubscription-State: activeContact: <sip:192.0.2.7:5060;transport=tcp>Content-Type: message/sipfragContent-Length: 23SIP/2.0 180 RingingJun 6 22:36:47.946: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK75251ATo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 142 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:47.946: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK771024From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 143 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:47 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1222<?xml version="1.0" encoding="UTF-8"?><DeliveredEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/delivered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><connection><callID>39F2FFC7-13B5-11DC-833A-9790DDA32D45</callID><deviceID>2803</deviceID></connection><alertingDevice><deviceIdentifier>NULL</deviceIdentifier></alertingDevice><callingDevice><deviceIdentifier>2807</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2803</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed>2229</numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:deliveredPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></cisco-csta-ext:deliveredPrivate></private></privateData></extensions></DeliveredEvent>Jun 6 22:36:47.982: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK761AB9To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 113 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:47.986: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK771024To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 143 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:49.690: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK78AD9From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 144 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:49 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1198<?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>39F2FFC7-13B5-11DC-833A-9790DDA32D45</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2807</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2803</cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>2803</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed>2229</numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></private></privateData></extensions></cisco-csta-ext:ActiveEvent>Jun 6 22:36:49.694: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK791F11From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 114 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:49 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: referSubscription-State: terminated;reason=noresourceContact: <sip:192.0.2.7:5060;transport=tcp>Content-Type: message/sipfragContent-Length: 18SIP/2.0 200 OKJun 6 22:36:49.698: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK78AD9To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 144 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:49.698: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK7AEB5From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 145 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:49 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 925<?xml version="1.0" encoding="UTF-8"?><EstablishedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/established-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><establishedConnection><callID>39F2FFC7-13B5-11DC-833A-9790DDA32D45</callID><deviceID>NULL</deviceID></establishedConnection><answeringDevice><deviceIdentifier>NULL</deviceIdentifier></answeringDevice><callingDevice><deviceIdentifier>2807</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2803</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed>NULL</numberDialed></lastRedirectionDevice><cause>normal</cause></EstablishedEvent>Jun 6 22:36:49.718: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK791F11To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 114 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:49.718: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK7AEB5To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 145 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:49.718: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
BYE sip:2229@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK7BA7BFrom: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489To: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Date: Wed, 06 Jun 2007 22:36:47 GMTCall-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7User-Agent: Cisco-SIPGateway/IOS-12.xMax-Forwards: 70Timestamp: 1181169409CSeq: 115 BYEContent-Length: 0Jun 6 22:36:49.718: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK7C1020From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 146 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:49 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1110<?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd " xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><droppedConnection><callID>39F2FFC7-13B5-11DC-833A-9790DDA32D45</callID><deviceID>2229</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>transfer</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2807</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2229</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent>Jun 6 22:36:49.742: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
BYE sip:2807@192.0.2.7:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~28Max-Forwards: 70To: <sip:2807@192.0.2.7>;tag=4D31DE54-1489From: <sip:2229@192.0.2.9>;tag=dsf8c9ed89Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 4 BYEContent-Length: 0Allow: INVITE, BYE, CANCEL, ACK, NOTIFYUser-Agent: Cisco-CRS/4.6Cisco-Gcid: 39F2FFC7-13B5-11DC-833A-9790DDA32D45Jun 6 22:36:49.742: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 481 Call Leg/Transaction Does Not ExistVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK7BA7BTo: <sip:2229@192.0.2.9>;tag=dsf8c9ed89From: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Call-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7CSeq: 115 BYEContent-Length: 0Jun 6 22:36:49.742: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
SIP/2.0 200 OKVia: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~28From: <sip:2229@192.0.2.9>;tag=dsf8c9ed89To: "Remote IP9" <sip:2807@192.0.2.7>;tag=4D31DE54-1489Date: Wed, 06 Jun 2007 22:36:49 GMTCall-ID: 3AEC0612-13B511DC-833F9790-DDA32D45@192.0.2.7Server: Cisco-SIPGateway/IOS-12.xCSeq: 4 BYEContent-Length: 0Jun 6 22:36:49.742: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK7C1020To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 146 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:36:49.746: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK7D2416From: <sip:2229@192.0.2.7>;tag=4D1FEE90-31BTo: <sip:CRS_controller@192.0.2.9>;tag=ds1e98edb8Call-ID: 11811688226563@192.0.2.9CSeq: 105 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:36:49 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: presenceSubscription-State: active;expires=1616Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/pidf+xmlContent-Length: 441<?xml version="1.0" encoding="UTF-8"?><presence xmlns="urn:ietf:params:xml:ns:pidf" entity="sip:2229@192.0.2.7" xmlns:e="urn:ietf:params:xml:ns:pidf:status:rpid" xmlns:rpid="urn:ietf:params:xml:ns:pidf:status:rpid" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"><dm:person><status><basic>Open</basic></status></dm:person><tupleid="cisco-cme"><status><basic>Open</basic><rpid:activeIdle>idle</rpid:activeIdle></status></tuple></presence>Jun 6 22:36:49.766: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK7D2416To: <sip:CRS_controller@192.0.2.9>;tag=ds1e98edb8From: <sip:2229@192.0.2.7>;tag=4D1FEE90-31BCall-ID: 11811688226563@192.0.2.9CSeq: 105 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventScenario 3: Call Forward
This scenario example displays message flow for the agent calling SCCP A but then the call is forwarded to SCCP B after ringing for ten seconds with no answer:
Jun 6 22:42:00.494: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK811925From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 150 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:42:00 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1084<?xml version="1.0" encoding="UTF-8"?><OriginatedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/originated-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><originatedConnection><callID>F92F4B44-13B5-11DC-8346-9790DDA32D45</callID><deviceID>2803</deviceID></originatedConnection><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier></deviceIdentifier></calledDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:originatedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></cisco-csta-ext:originatedPrivate></private></privateData></extensions></OriginatedEvent>Jun 6 22:42:00.502: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK811925To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 150 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:42:00.502: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK82A55From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 151 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:42:00 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1190<?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>F92F4B44-13B5-11DC-8346-9790DDA32D45</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>2803</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></private></privateData></extensions></cisco-csta-ext:ActiveEvent>Jun 6 22:42:00.514: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK82A55To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 151 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:42:02.150: DestCheckTeleUnassBusy cvif OperStatus 5, Type 1A, status 40020Jun 6 22:42:02.154: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK8317D7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 152 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:42:02 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1268<?xml version="1.0" encoding="UTF-8"?><OfferedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/offered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><offeredConnection><callID>F92F4B44-13B5-11DC-8346-9790DDA32D45</callID><deviceID>2807</deviceID></offeredConnection><offeredDevice><deviceIdentifier>NULL</deviceIdentifier></offeredDevice><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2807</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:OfferedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID><originalCalledAddress></originalCalledAddress></cisco-csta-ext:OfferedPrivate></private></privateData></extensions></OfferedEvent>Jun 6 22:42:02.162: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK8317D7To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 152 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:42:02.162: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK8413CFFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 153 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:42:02 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1218<?xml version="1.0" encoding="UTF-8"?><DeliveredEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/delivered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><connection><callID>F92F4B44-13B5-11DC-8346-9790DDA32D45</callID><deviceID>2807</deviceID></connection><alertingDevice><deviceIdentifier>NULL</deviceIdentifier></alertingDevice><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2807</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:deliveredPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></cisco-csta-ext:deliveredPrivate></private></privateData></extensions></DeliveredEvent>Jun 6 22:42:02.174: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK8413CFTo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 153 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:42:12.154: DestCheckTeleUnassBusy cvif OperStatus 5, Type 1A, status 40020Jun 6 22:42:12.158: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK858CDFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 154 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:42:12 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1276<?xml version="1.0" encoding="UTF-8"?><OfferedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/offered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><offeredConnection><callID>F92F4B44-13B5-11DC-8346-9790DDA32D45</callID><deviceID>2808</deviceID></offeredConnection><offeredDevice><deviceIdentifier>NULL</deviceIdentifier></offeredDevice><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2808</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed>2807</numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:OfferedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID><originalCalledAddress>2807</originalCalledAddress></cisco-csta-ext:OfferedPrivate></private></privateData></extensions></OfferedEvent>Jun 6 22:42:12.166: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK858CDTo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 154 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:42:12.170: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK863E2From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 155 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:42:12 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1222<?xml version="1.0" encoding="UTF-8"?><DeliveredEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/delivered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><connection><callID>F92F4B44-13B5-11DC-8346-9790DDA32D45</callID><deviceID>2808</deviceID></connection><alertingDevice><deviceIdentifier>NULL</deviceIdentifier></alertingDevice><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2808</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed>2807</numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:deliveredPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></cisco-csta-ext:deliveredPrivate></private></privateData></extensions></DeliveredEvent>Jun 6 22:42:12.182: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK863E2To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 155 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:42:12.182: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK87291From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 156 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:42:12 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1121<?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd " xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><droppedConnection><callID>F92F4B44-13B5-11DC-8346-9790DDA32D45</callID><deviceID>2807</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>callForwardNoAnswer</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2807</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent>Jun 6 22:42:12.194: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK87291To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 156 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:42:16.766: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK8829BFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 157 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:42:16 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1202<?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>F92F4B44-13B5-11DC-8346-9790DDA32D45</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>2808</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed>2807</numberDialed></lastRedirectionDevice><originalCalledAddress>2807</originalCalledAddress><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></private></privateData></extensions></cisco-csta-ext:ActiveEvent>Jun 6 22:42:16.774: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK8829BTo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 157 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:42:16.774: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK8916BFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 158 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:42:16 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 925<?xml version="1.0" encoding="UTF-8"?><EstablishedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/established-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><establishedConnection><callID>F92F4B44-13B5-11DC-8346-9790DDA32D45</callID><deviceID>NULL</deviceID></establishedConnection><answeringDevice><deviceIdentifier>NULL</deviceIdentifier></answeringDevice><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2808</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed>NULL</numberDialed></lastRedirectionDevice><cause>normal</cause></EstablishedEvent>Jun 6 22:42:16.794: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bK8916BTo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 158 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventScenario 4: Consult Transfer
This example scenario continues where scenario 2 left off. From this point, user agent (Ag) receives call, initiates consult transfer to SCCP endpoint B, and then commits transfer while endpoint B is ringing:
Note
Jun 6 22:50:25.514: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
REGISTER sip:192.0.2.7:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~44Max-Forwards: 70To: <sip:CRS_controller@192.0.2.7>From: <sip:CRS_controller@192.0.2.7>;tag=dsa8afec60Call-ID: 11811688223121@192.0.2.9CSeq: 26 REGISTERContent-Length: 0Contact: <sip:CRS_controller@192.0.2.9:5060;transport=tcp>;expires=160Allow: INVITE, BYE, CANCEL, ACK, NOTIFYUser-Agent: Cisco-CRS/4.6X-cisco-session-server: CRS1Jun 6 22:50:25.514: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
SIP/2.0 100 TryingVia: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~44From: <sip:CRS_controller@192.0.2.7>;tag=dsa8afec60To: <sip:CRS_controller@192.0.2.7>Date: Wed, 06 Jun 2007 22:50:25 GMTCall-ID: 11811688223121@192.0.2.9Server: Cisco-SIPGateway/IOS-12.xCSeq: 26 REGISTERContent-Length: 0Jun 6 22:50:25.514: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
SIP/2.0 200 OKVia: SIP/2.0/TCP 192.0.2.9:5060;branch=z9hG4bKl83.ZS9nz+P+iXsfLQiSMw~~44From: <sip:CRS_controller@192.0.2.7>;tag=dsa8afec60To: <sip:CRS_controller@192.0.2.7>;tag=4D3E71FC-21D5Date: Wed, 06 Jun 2007 22:50:25 GMTCall-ID: 11811688223121@192.0.2.9Server: Cisco-SIPGateway/IOS-12.xCSeq: 26 REGISTERX-cisco-referenceID: 48F1DB51Contact: <sip:CRS_controller@192.0.2.9:5060;transport=tcp>;expires=160Expires: 160Content-Length: 0Jun 6 22:50:29.402: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKA9B87From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 172 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:50:29 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1024<?xml version="1.0" encoding="UTF-8"?><HeldEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/held-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><heldConnection><callID>192BA764-13B7-11DC-8358-9790DDA32D45</callID><deviceID>2803</deviceID></heldConnection><holdingDevice><deviceIdentifier>NULL</deviceIdentifier></holdingDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:HeldPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2807</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2803</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:HeldPrivate></private></privateData></extensions></HeldEvent>Jun 6 22:50:29.414: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKA9B87To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 172 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:50:31.006: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKAA19B5From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 173 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:50:31 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1121<?xml version="1.0" encoding="UTF-8"?><OriginatedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/originated-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><originatedConnection><callID>29793E66-13B7-11DC-8361-9790DDA32D45</callID><deviceID>2803</deviceID></originatedConnection><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier></deviceIdentifier></calledDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:originatedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>consult</cisco-csta-ext:callType><cisco-csta-ext:parentGCID>192BA764-13B7-11DC-8358-9790DDA32D45</cisco-csta-ext:parentGCID></cisco-csta-ext:originatedPrivate></private></privateData></extensions></OriginatedEvent>Jun 6 22:50:31.010: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKAA19B5To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 173 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:50:31.014: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKAB26A5From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 174 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:50:31 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1227<?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>29793E66-13B7-11DC-8361-9790DDA32D45</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>2803</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>consult</cisco-csta-ext:callType><cisco-csta-ext:parentGCID>192BA764-13B7-11DC-8358-9790DDA32D45</cisco-csta-ext:parentGCID ></private></privateData></extensions></cisco-csta-ext:ActiveEvent>Jun 6 22:50:31.026: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKAB26A5To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 174 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:50:31.606: DestCheckTeleUnassBusy cvif OperStatus 5, Type 1A, status 40020Jun 6 22:50:31.614: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKAC1DB7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 175 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:50:31 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1305<?xml version="1.0" encoding="UTF-8"?><OfferedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/offered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><offeredConnection><callID>29793E66-13B7-11DC-8361-9790DDA32D45</callID><deviceID>2808</deviceID></offeredConnection><offeredDevice><deviceIdentifier>NULL</deviceIdentifier></offeredDevice><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2808</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:OfferedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>consult</cisco-csta-ext:callType><cisco-csta-ext:parentGCID>192BA764-13B7-11DC-8358-9790DDA32D45</cisco-csta-ext:parentGCID ><originalCalledAddress></originalCalledAddress></cisco-csta-ext:OfferedPrivate></private></privateData></extensions></OfferedEvent>Jun 6 22:50:31.622: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKAC1DB7To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 175 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:50:31.622: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKAD778From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 176 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:50:31 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1255<?xml version="1.0" encoding="UTF-8"?><DeliveredEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/delivered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><connection><callID>29793E66-13B7-11DC-8361-9790DDA32D45</callID><deviceID>2808</deviceID></connection><alertingDevice><deviceIdentifier>NULL</deviceIdentifier></alertingDevice><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2808</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:deliveredPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>consult</cisco-csta-ext:callType><cisco-csta-ext:parentGCID>192BA764-13B7-11DC-8358-9790DDA32D45</cisco-csta-ext:parentGCID ></cisco-csta-ext:deliveredPrivate></private></privateData></extensions></DeliveredEvent>Jun 6 22:50:31.634: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKAD778To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 176 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:50:33.430: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKAECBDFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 177 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:50:33 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1170<?xml version="1.0" encoding="UTF-8"?><TransferredEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/transferred-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><primaryOldCall><callID>192BA764-13B7-11DC-8358-9790DDA32D45</callID><deviceID>NULL</deviceID></primaryOldCall><secondaryOldCall><callID></callID><deviceID>NULL</deviceID></secondaryOldCall><transferringDevice><deviceIdentifier>2803</deviceIdentifier></transferringDevice><transferredToDevice><deviceIdentifier>2808</deviceIdentifier></transferredToDevice><transferredConnections><connectionListItem><newConnection><callID>29793E66-13B7-11DC-8361-9790DDA32D45</callID></newConnection><oldConnection><callID>192BA764-13B7-11DC-8358-9790DDA32D45</callID></oldConnection><endpoint><deviceID>2807</deviceID></endpoint></connectionListItem></transferredConnections><cause>normal</cause></TransferredEvent>Jun 6 22:50:33.466: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKAECBDTo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 177 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:50:33.466: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKAF394From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 178 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:50:33 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1110<?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd " xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><droppedConnection><callID>29793E66-13B7-11DC-8361-9790DDA32D45</callID><deviceID>2803</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>transfer</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent>Jun 6 22:50:33.474: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKAF394To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 178 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:50:33.474: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKB0BF1From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 179 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:50:33 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1110<?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd " xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><droppedConnection><callID>29793E66-13B7-11DC-8361-9790DDA32D45</callID><deviceID>2808</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>transfer</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent>Jun 6 22:50:33.482: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKB0BF1To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 179 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:50:33.486: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKB11ABCFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 180 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:50:33 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 876<?xml version="1.0" encoding="UTF-8"?><CallClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/call-cleared-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><clearedCall><callID>29793E66-13B7-11DC-8361-9790DDA32D45</callID><deviceID>NULL</deviceID></clearedCall><cause>transfer</cause><extensions><privateData><private><droppedPrivate><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber></droppedPrivate></private></privateData></extensions></CallClearedEvent>Jun 6 22:50:33.494: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKB11ABCTo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 180 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:50:33.494: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKB21433From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 181 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:50:33 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1110<?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd " xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><droppedConnection><callID>192BA764-13B7-11DC-8358-9790DDA32D45</callID><deviceID>2803</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>transfer</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2807</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2803</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent>Jun 6 22:50:33.502: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKB21433To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 181 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:50:33.502: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKB3D97From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 182 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:50:33 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1218<?xml version="1.0" encoding="UTF-8"?><DeliveredEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/delivered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><connection><callID>192BA764-13B7-11DC-8358-9790DDA32D45</callID><deviceID>2808</deviceID></connection><alertingDevice><deviceIdentifier>NULL</deviceIdentifier></alertingDevice><callingDevice><deviceIdentifier>2807</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2808</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:deliveredPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></cisco-csta-ext:deliveredPrivate></private></privateData></extensions></DeliveredEvent>Jun 6 22:50:33.514: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKB3D97To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 182 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:50:36.338: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKB425FBFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 183 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:50:36 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1194<?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>192BA764-13B7-11DC-8358-9790DDA32D45</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2807</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>2808</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></private></privateData></extensions></cisco-csta-ext:ActiveEvent>Jun 6 22:50:36.346: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKB425FBTo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 183 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:50:36.346: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKB5237EFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 184 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:50:36 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 925<?xml version="1.0" encoding="UTF-8"?><EstablishedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/established-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><establishedConnection><callID>192BA764-13B7-11DC-8358-9790DDA32D45</callID><deviceID>NULL</deviceID></establishedConnection><answeringDevice><deviceIdentifier>NULL</deviceIdentifier></answeringDevice><callingDevice><deviceIdentifier>2807</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2808</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed>NULL</numberDialed></lastRedirectionDevice><cause>normal</cause></EstablishedEvent>Jun 6 22:50:36.358: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKB5237ETo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 184 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventScenario 5: Call Conference
This example scenario continues where scenario 2 left off—call routed to user agent (Ag), Ag initiates consult call and connects with SCCP endpoint B, and then Ag commits the conference:
Jun 6 22:54:58.918: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKD514E9From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 198 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:54:58 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1024<?xml version="1.0" encoding="UTF-8"?><HeldEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/held-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><heldConnection><callID>BE95D856-13B7-11DC-836A-9790DDA32D45</callID><deviceID>2803</deviceID></heldConnection><holdingDevice><deviceIdentifier>NULL</deviceIdentifier></holdingDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:HeldPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2807</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2803</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:HeldPrivate></private></privateData></extensions></HeldEvent>Jun 6 22:54:58.926: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKD514E9To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 198 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:54:58.930: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKD611D1From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 199 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:54:58 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1121<?xml version="1.0" encoding="UTF-8"?><OriginatedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/originated-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><originatedConnection><callID>C929F81E-13B7-11DC-8372-9790DDA32D45</callID><deviceID>2803</deviceID></originatedConnection><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier></deviceIdentifier></calledDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:originatedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>consult</cisco-csta-ext:callType><cisco-csta-ext:parentGCID>BE95D856-13B7-11DC-836A-9790DDA32D45</cisco-csta-ext:parentGCID></cisco-csta-ext:originatedPrivate></private></privateData></extensions></OriginatedEvent>Jun 6 22:54:58.938: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKD611D1To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 199 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:54:58.942: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKD72045From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 200 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:54:58 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1227<?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>C929F81E-13B7-11DC-8372-9790DDA32D45</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>2803</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>consult</cisco-csta-ext:callType><cisco-csta-ext:parentGCID>BE95D856-13B7-11DC-836A-9790DDA32D45</cisco-csta-ext:parentGCID></private></privateData></extensions></cisco-csta-ext:ActiveEvent>Jun 6 22:54:58.946: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKD72045To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 200 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:55:00.358: DestCheckTeleUnassBusy cvif OperStatus 5, Type 1A, status 40020Jun 6 22:55:00.362: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKD81E04From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 201 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:55:00 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1305<?xml version="1.0" encoding="UTF-8"?><OfferedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/offered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><offeredConnection><callID>C929F81E-13B7-11DC-8372-9790DDA32D45</callID><deviceID>2808</deviceID></offeredConnection><offeredDevice><deviceIdentifier>NULL</deviceIdentifier></offeredDevice><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2808</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:OfferedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>consult</cisco-csta-ext:callType><cisco-csta-ext:parentGCID>BE95D856-13B7-11DC-836A-9790DDA32D45</cisco-csta-ext:parentGCID ><originalCalledAddress></originalCalledAddress></cisco-csta-ext:OfferedPrivate></private></privateData></extensions></OfferedEvent>Jun 6 22:55:00.370: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKD81E04To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 201 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:55:00.370: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKD9594From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 202 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:55:00 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1255<?xml version="1.0" encoding="UTF-8"?><DeliveredEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/delivered-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><connection><callID>C929F81E-13B7-11DC-8372-9790DDA32D45</callID><deviceID>2808</deviceID></connection><alertingDevice><deviceIdentifier>NULL</deviceIdentifier></alertingDevice><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2808</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:deliveredPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callType>consult</cisco-csta-ext:callType><cisco-csta-ext:parentGCID>BE95D856-13B7-11DC-836A-9790DDA32D45</cisco-csta-ext:parentGCID ></cisco-csta-ext:deliveredPrivate></private></privateData></extensions></DeliveredEvent>Jun 6 22:55:00.378: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKD9594To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 202 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:55:02.394: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKDADABFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 203 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:55:02 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1230<?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>C929F81E-13B7-11DC-8372-9790DDA32D45</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>2808</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>direct</cisco-csta-ext:callType><cisco-csta-ext:parentGCID>BE95D856-13B7-11DC-836A-9790DDA32D45</cisco-csta-ext:parentGCID ></private></privateData></extensions></cisco-csta-ext:ActiveEvent>Jun 6 22:55:02.402: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKDADABTo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 203 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:55:02.402: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKDB19D7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 204 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:55:02 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 925<?xml version="1.0" encoding="UTF-8"?><EstablishedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/established-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><establishedConnection><callID>C929F81E-13B7-11DC-8372-9790DDA32D45</callID><deviceID>NULL</deviceID></establishedConnection><answeringDevice><deviceIdentifier>NULL</deviceIdentifier></answeringDevice><callingDevice><deviceIdentifier>2803</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>2808</deviceIdentifier></calledDevice><lastRedirectionDevice><numberDialed>NULL</numberDialed></lastRedirectionDevice><cause>normal</cause></EstablishedEvent>Jun 6 22:55:02.414: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKDB19D7To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 204 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:55:05.762: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKDC1EC0From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 205 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:55:05 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1204<?xml version="1.0" encoding="UTF-8"?><ConferencedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/conferenced-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><primaryOldCall><callID>BE95D856-13B7-11DC-836A-9790DDA32D45</callID><deviceID>NULL</deviceID></primaryOldCall><secondaryOldCall><callID></callID><deviceID>NULL</deviceID></secondaryOldCall><conferencingDevice><deviceIdentifier>2803</deviceIdentifier></conferencingDevice><addedParty><deviceIdentifier>NULL</deviceIdentifier></addedParty><conferenceConnections><connectionListItem><newConnection><callID>C929F81E-13B7-11DC-8372-9790DDA32D45</callID><deviceID>2808</deviceID></newConnection><oldConnection><callID>BE95D856-13B7-11DC-836A-9790DDA32D45</callID><deviceID>2807</deviceID></oldConnection><endpoint><deviceID>2808</deviceID></endpoint></connectionListItem></conferenceConnections><cause>normal</cause></ConferencedEvent>Jun 6 22:55:05.766: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKDC1EC0To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 205 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:55:05.770: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKDD1998From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 206 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:55:05 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1064<?xml version="1.0" encoding="UTF-8"?><RetrievedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/retrieved-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><retrievedConnection><callID>BE95D856-13B7-11DC-836A-9790DDA32D45</callID><deviceID>2803</deviceID></retrievedConnection><retrievingDevice><deviceIdentifier>NULL</deviceIdentifier></retrievingDevice><cause>normal</cause><extensions><privateData><private><cisco-csta-ext:RetrievedPrivate><cisco-csta-ext:callDirection>TRUE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2807</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2803</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:RetrievedPrivate></private></privateData></extensions></RetrievedEvent>Jun 6 22:55:05.794: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKDD1998To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 206 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:55:05.794: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKDEF82From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 207 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:55:05 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1112<?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd " xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><droppedConnection><callID>C929F81E-13B7-11DC-8372-9790DDA32D45</callID><deviceID>2803</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>Conference</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent>Jun 6 22:55:05.830: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKDEF82To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 207 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:55:05.834: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKDF85From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 208 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:55:05 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1112<?xml version="1.0" encoding="UTF-8"?><ConnectionClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/connection-cleared-event.xsd " xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><droppedConnection><callID>C929F81E-13B7-11DC-8372-9790DDA32D45</callID><deviceID>2808</deviceID></droppedConnection><releasingDevice><deviceIdentifier>NULL</deviceIdentifier></releasingDevice><cause>Conference</cause><extensions><privateData><private><cisco-csta-ext:CallConnectionClearedPrivate><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber></cisco-csta-ext:CallConnectionClearedPrivate></private></privateData></extensions></ConnectionClearedEvent>Jun 6 22:55:05.838: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKDF85To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 208 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:55:05.838: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKE0BE1From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 209 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:55:05 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 878<?xml version="1.0" encoding="UTF-8"?><CallClearedEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/call-cleared-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><clearedCall><callID>C929F81E-13B7-11DC-8372-9790DDA32D45</callID><deviceID>NULL</deviceID></clearedCall><cause>Conference</cause><extensions><privateData><private><droppedPrivate><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber></droppedPrivate></private></privateData></extensions></CallClearedEvent>Jun 6 22:55:05.850: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKE0BE1To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 209 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventJun 6 22:55:05.850: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:
NOTIFY sip:CRS_controller@192.0.2.9:5060;transport=tcp SIP/2.0Via: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKE1BDDFrom: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6To: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7Call-ID: 11811688227034@192.0.2.9CSeq: 210 NOTIFYMax-Forwards: 70Date: Wed, 06 Jun 2007 22:55:05 GMTUser-Agent: Cisco-SIPGateway/IOS-12.xEvent: dialogSubscription-State: active;expires=2800Contact: <sip:2229@192.0.2.7:5060;transport=tcp>Content-Type: application/csta+xmlContent-Length: 1195<?xml version="1.0" encoding="UTF-8"?><cisco-csta-ext:ActiveEventxmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"xmlns:xsi="http://www.example.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ecma-international.org/standards/ecma-323/csta/ed3 http://www.ecma-international.org/standards/ecma-323/csta/ed3/private-event.xsd" xmlns:cisco-csta-ext="cisco-csta-ext.xsd"><monitorCrossRefID>48F1DB51</monitorCrossRefID><extensions><privateData><private><cisco-csta-ext:gcid>BE95D856-13B7-11DC-836A-9790DDA32D45</cisco-csta-ext:gcid><cisco-csta-ext:callDirection>FALSE</cisco-csta-ext:callDirection><cisco-csta-ext:callingDirectoryNumber>2803</cisco-csta-ext:callingDirectoryNumber><cisco-csta-ext:calledDirectoryNumber>2808</cisco-csta-ext:calledDirectoryNumber><connectionAddress><deviceIdentifier>2808</deviceIdentifier></connectionAddress><lastRedirectionDevice><numberDialed></numberDialed></lastRedirectionDevice><originalCalledAddress></originalCalledAddress><cisco-csta-ext:callType>consult</cisco-csta-ext:callType><cisco-csta-ext:parentGCID></cisco-csta-ext:parentGCID></private></privateData></extensions></cisco-csta-ext:ActiveEvent>Jun 6 22:55:05.862: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:
SIP/2.0 200 OkVia: SIP/2.0/TCP 192.0.2.7:5060;branch=z9hG4bKE1BDDTo: <sip:CRS_controller@192.0.2.9>;tag=dscdc4ede7From: <sip:2229@192.0.2.7>;tag=4D1FEEB0-1E6Call-ID: 11811688227034@192.0.2.9CSeq: 210 NOTIFYContent-Length: 0Allow-Events: referAllow-Events: telephone-eventCisco Unified CME Configuration Examples
The following examples provide sample configurations of the Unified CME for configuring and activating the call monitoring feature:
•
•
Minimum preconfiguration required before using the AXL interface
!
voice service voip
allow-connections sip to sip
sip
registrar server
!
voice register global
mode cme
source-address 192.0.2.254 port 5060
max-dn 100
max-pool 100
authentication presence
authentication register
create profile
!
ixi transport http
response size 64
no shutdown
request outstanding 1
!
ixi application cme
no shutdown
!
presence
presence call-list
watcher all
allow subscribe
!
sip-ua
presence enable
!
telephony-service
xml user axluser password cisco 15
Typical configuration of the Unified CME
!version 12.4service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname sb-sj1-3845-uut1!boot-start-markerboot system flash:c3845-ipvoice-mz.124-12.12.2.PIA1boot-end-marker!card type t1 0 2card type t1 0 3logging buffered 1000000no logging consoleenable password lab!no aaa new-modelnetwork-clock-participate wic 2network-clock-participate wic 3!ip cef!!no ip dhcp use vrf connectedip dhcp excluded-address 192.0.2.130 192.0.2.255!ip dhcp pool ephonesnetwork 192.0.2.0 255.255.255.0option 150 ip 192.0.2.254default-router 192.0.2.254!!no ip domain lookupmultilink bundle-name authenticated!isdn switch-type primary-5ess!voice-card 0no dspfarmdsp services dspfarm!!!voice service voipgcidcallmonitorallow-connections h323 to h323allow-connections h323 to sipallow-connections sip to h323allow-connections sip to sipno supplementary-service sip moved-temporarilysipregistrar server expires max 120 min 60!!voice class codec 1codec preference 1 g711ulawcodec preference 2 g729r8!!!!!!!!!!voice register globalmode cmesource-address 192.0.2.254 port 5060max-dn 720max-pool 240authenticate presencedialplan-pattern 1 511.... extension-length 4voicemail 9001create profile sync 0000260378327476!voice register session-server 1keepalive 300register-id SB-SJ1-UCCX1_1173482160000!voice register dn 1session-server 1number 8901allow watchrefer target dial-peer!voice register dn 2session-server 1number 8001allow watchrefer target dial-peer!voice register dn 3session-server 1number 8002allow watchrefer target dial-peer!voice register dn 4session-server 1number 8101allow watchrefer target dial-peer!voice register dn 5session-server 1number 8102allow watchrefer target dial-peer!voice register dn 11number 2011name ep-sip-1-11mwi!voice register dn 12number 2012name ep-sip-1-12mwi!voice register dn 13number 2013name ep-sip-1-13mwi!voice register dn 14number 2014name ep-sip-1-14mwi!voice register dn 15number 2015name ep-sip-1-15mwi!voice register dn 16number 5016name rp-sip-1-16label SIP 511-5016mwi!voice register dn 17number 5017name rp-sip-1-17label SIP 511-5017mwi!voice register dn 18number 5018name rp-sip-1-18label SIP 511-5018mwi!voice register dn 19number 5019name rp-sip-1-19label SIP 511-5019mwi!voice register dn 20number 5020name rp-sip-1-20label SIP 511-5020mwi!voice register dn 21number 5021name rp-sip-1-21label SIP 511-5021mwi!voice register dn 22number 5022name rp-sip-1-22label SIP 511-5022mwi!voice register pool 1session-server 1number 1 dn 1number 2 dn 2number 3 dn 3number 4 dn 4number 5 dn 5dtmf-relay sip-notifycodec g711ulaw!voice register pool 11id mac 1111.0511.2011type 7970number 1 dn 11dtmf-relay rtp-ntevoice-class codec 1username 5112011 password 5112011!voice register pool 12id mac 1111.0511.2012type 7960number 1 dn 12dtmf-relay rtp-ntevoice-class codec 1username 5112012 password 5112012!voice register pool 13id mac 1111.0511.2013type 7970number 1 dn 13dtmf-relay rtp-ntevoice-class codec 1username 5112013 password 5112013!voice register pool 14id mac 1111.0511.2014type 7970number 1 dn 14dtmf-relay rtp-ntevoice-class codec 1username 5112014 password 5112014!voice register pool 15id mac 1111.0511.2015type 7970number 1 dn 15dtmf-relay rtp-ntevoice-class codec 1username 5112015 password 5112015!voice register pool 16id mac 0013.1A10.7349type 7970number 1 dn 16dtmf-relay rtp-ntevoice-class codec 1username rp-sip-1-16 password cisco!voice register pool 17id mac 0016.9D99.2BFEtype 7941GEnumber 1 dn 17dtmf-relay rtp-ntevoice-class codec 1username rp-sip-1-17 password cisco!voice register pool 18id mac 0014.1C0F.0176type 7970number 1 dn 18dtmf-relay rtp-ntevoice-class codec 1username rp-sip-1-18 password cisco!voice register pool 19id mac 0011.9378.D1B5type 7960number 1 dn 19dtmf-relay rtp-ntevoice-class codec 1username rp-sip-1-19 password cisco!voice register pool 20id mac 0015.F9A2.CE5Etype 7940number 1 dn 20dtmf-relay rtp-ntevoice-class codec 1username rp-sip-1-20 password cisco!voice register pool 21id mac 0014.69E2.662Ctype 7940number 1 dn 21dtmf-relay rtp-ntevoice-class codec 1username rp-sip-1-21 password cisco!voice register pool 22id mac 0014.698C.5D9Ftype 7960number 1 dn 22dtmf-relay rtp-ntevoice-class codec 1username rp-sip-1-22 password cisco!voice logout-profile 1number 4034 type normalspeed-dial 1 4317 label SD_511-4317!voice logout-profile 2number 4035 type normalspeed-dial 1 4016 label SD_511-4016!voice user-profile 1user ad1 password ad1ad1number 4044,4046,4048 type normalspeed-dial 1 4017 label SD_511-4017!voice user-profile 2user ad2 password ad2ad2number 4045 type normalspeed-dial 1 4017 label SD_511-4017!voice user-profile 3user ad3 password ad3ad3number 4046 type normalspeed-dial 1 4018 label SD_511-4018!!!!!archivelog config!!controller T1 0/2/0framing esfclock source internallinecode b8zspri-group timeslots 1-4,24!controller T1 0/2/1framing esfclock source internallinecode b8zspri-group timeslots 1-4,24!controller T1 0/3/0framing esfclock source internallinecode b8zsds0-group 0 timeslots 1-4 type e&m-immediate-start!controller T1 0/3/1framing esfclock source internallinecode b8zsds0-group 0 timeslots 1-4 type e&m-immediate-start!!!!!interface GigabitEthernet0/0ip address 192.0.2.1 255.255.0.0duplex autospeed automedia-type rj45no keepalive!interface GigabitEthernet0/1ip address 192.0.2.254 255.255.255.0duplex autospeed automedia-type rj45no keepalive!interface Serial0/2/0:23no ip addressencapsulation hdlcisdn switch-type primary-5essisdn protocol-emulate networkisdn incoming-voice voiceno cdp enable!interface Serial0/2/1:23no ip addressencapsulation hdlcisdn switch-type primary-5essisdn protocol-emulate networkisdn incoming-voice voiceno cdp enable!interface Service-Engine1/0ip unnumbered GigabitEthernet0/0service-module ip address 192.0.2.250 255.255.0.0service-module ip default-gateway 192.0.2.1!ip route 192.0.0.0 255.0.0.0 192.0.2.1ip route 192.0.2.250 255.255.255.255 Service-Engine1/0ip route 172.16.2.0 255.255.255.0 192.0.2.2ip route 172.16.3.0 255.255.255.0 192.0.2.3ip route 223.255.254.0 255.255.255.0 192.0.2.1!!ip http serverip http authentication localip http path flash:!!ixi transport httpresponse size 64no shutdownrequest outstanding 1!ixi application cmeno shutdown!!!control-plane!!!voice-port 0/0/0!voice-port 0/0/1!voice-port 0/2/0:23!voice-port 0/3/0:0!voice-port 0/1/0!voice-port 0/1/1!voice-port 0/2/1:23!voice-port 0/3/1:0!!!sccp local GigabitEthernet0/1sccp ccm 192.0.2.254 identifier 100 version 4.0sccp!sccp ccm group 1associate ccm 100 priority 1associate profile 1 register confprof1!dspfarm profile 1 conferencecodec g711ulawcodec g711alawcodec g729ar8codec g729abr8codec g729r8codec g729br8maximum sessions 3associate application SCCPshutdown!!dial-peer voice 9000 voipdescription ==> This is for internal calls to CUEdestination-pattern 9...voice-class codec 1session protocol sipv2session target ipv4:192.0.2.250dtmf-relay rtp-nte sip-notify!dial-peer voice 9001 voipdescription ==> This is for external calls to CUEdestination-pattern 5119...voice-class codec 1session protocol sipv2session target ipv4:192.0.2.250dtmf-relay rtp-nte sip-notify!dial-peer voice 521 voipdestination-pattern 521....voice-class codec 1max-redirects 5session protocol sipv2session target ipv4:192.0.2.2dtmf-relay sip-notify rtp-nte!!presencepresence call-listwatcher allallow subscribe!sip-uamwi-server ipv4:192.0.2.250 expires 3600 port 5060 transport udppresence enable!!telephony-servicesdspfarm conference mute-on B11 mute-off B22sdspfarm units 1sdspfarm tag 1 confprof1conference hardwareno auto-reg-ephonexml user axluser password cisco 15max-ephones 240max-dn 720ip source-address 192.0.2.254 port 2000system message sb-sj1-3845-uut1url services http://192.0.2.252:6293/ipphone/jsp/sciphonexml/IPAgentInitial.jspurl authentication http://192.0.2.252:6293/ipphone/jsp/sciphonexml/IPAgentAuthenticate.jspcnf-file perphonedialplan-pattern 1 511.... extension-length 4voicemail 9001max-conferences 8 gain -6call-forward pattern .Ttransfer-system full-consulttransfer-pattern .Tcreate cnf-files version-stamp Jan 01 2002 00:00:00!!ephone-dn 1 dual-linesession-server 1number 1001name ag-1-1allow watchmwi sip!!ephone-dn 2 dual-linesession-server 1number 1002name ag-1-2allow watchmwi sip!!ephone-dn 3 dual-linesession-server 1number 1003name ag-1-3allow watchmwi sip!!ephone-dn 4 dual-linesession-server 1number 1004name ag-1-4allow watchmwi sip!!ephone-dn 5 dual-linesession-server 1number 1005name ag-1-5allow watchmwi sip!!ephone-dn 11 dual-linenumber 3011name ep-sccp-1-11mwi sip!!ephone-dn 12 dual-linenumber 3012name ep-sccp-1-12mwi sip!!ephone-dn 13 dual-linenumber 3013name ep-sccp-1-13mwi sip!!ephone-dn 14 dual-linenumber 3014name ep-sccp-1-14mwi sip!!ephone-dn 15 dual-linenumber 3015name ep-sccp-1-15mwi sip!!ephone-dn 16 dual-linesession-server 1number 4016label SCCP 511-4016name rp-sccp-1-16allow watchmwi sip!!ephone-dn 17 dual-linesession-server 1number 4017label SCCP 511-4017name rp-sccp-1-17allow watchmwi sip!!ephone-dn 18 dual-linenumber 4018label SCCP 511-4018name rp-sccp-1-18mwi sip!!ephone-dn 19 dual-linenumber 4019label SCCP 511-4019name rp-sccp-1-19mwi sip!!ephone-dn 20 dual-linesession-server 1number 4020label SCCP 511-4020name rp-sccp-1-20allow watchmwi sip!!ephone-dn 21 dual-linenumber 4021label SCCP 511-4021name rp-sccp-1-21mwi sip!!ephone-dn 22 dual-linenumber 4022label SCCP 511-4022name rp-sccp-1-22mwi sip!!ephone-dn 23 dual-linenumber 4023label SCCP 511-4023name rp-sccp-1-23mwi sip!!ephone-dn 24 dual-linenumber 4024label SCCP 511-4024name rp-sccp-1-24mwi sip!!ephone-dn 25 dual-linesession-server 1number 4025label SCCP 511-4025name rp-sccp-1-25allow watch!!ephone-dn 26 dual-linesession-server 1number 4026label SCCP 511-4026name rp-sccp-1-5114026allow watch!!ephone-dn 27 dual-linesession-server 1number 4027label SCCP 511-4027name rp-sccp-1-5114027allow watch!!ephone-dn 34 dual-linesession-server 1number 4034label SCCP 511-4034name rp-sccp-1-5114034allow watch!!ephone-dn 35 dual-linesession-server 1number 4035label SCCP 511-4035name rp-sccp-1-5114035allow watch!!ephone-dn 44 dual-linesession-server 1number 4044label SCCP 511-4044name rp-sccp-1-5114044allow watch!!ephone-dn 45 dual-linesession-server 1number 4045label SCCP 511-4045name rp-sccp-1-5114045allow watch!!ephone-dn 46 dual-linesession-server 1number 4046label SCCP 511-4046name rp-sccp-1-5114046allow watch!!ephone-dn 121 dual-linenumber A000conference ad-hocpreference 1no huntstop!!ephone-dn 122 dual-linenumber A000conference ad-hocpreference 2no huntstop!!ephone-dn 123 dual-linenumber A000conference ad-hocpreference 3no huntstop!!ephone-dn 124 dual-linenumber A000conference ad-hocpreference 4no huntstop!!ephone-dn 125 dual-linenumber A001conference ad-hocpreference 1no huntstop!!ephone-dn 126 dual-linenumber A001conference ad-hocpreference 2no huntstop!!ephone-dn 127 dual-linenumber A001conference ad-hocpreference 3no huntstop!!ephone-dn 128 dual-linenumber A001conference ad-hocpreference 4no huntstop!!ephone 1mac-address 1111.0511.1001type 7970keep-conference endcallbutton 1:1!!!ephone 2mac-address 1111.0511.1002type 7970keep-conference endcallbutton 1:2!!!ephone 3mac-address 1111.0511.1003type 7970keep-conference endcallbutton 1:3!!!ephone 4mac-address 1111.0511.1004type 7970keep-conference endcallbutton 1:4!!!ephone 5mac-address 1111.0511.1005type 7970keep-conference endcallbutton 1:5!!!ephone 11mac-address 1111.0511.3011type 7960keep-conference endcallbutton 1:11!!!ephone 12mac-address 1111.0511.3012type 7960keep-conference endcallbutton 1:12!!!ephone 13mac-address 1111.0511.3013type 7960keep-conference endcallbutton 1:13!!!ephone 14mac-address 1111.0511.3014type 7960keep-conference endcallbutton 1:14!!!ephone 15mac-address 1111.0511.3015type 7960keep-conference endcallbutton 1:15!!!ephone 16mac-address 0002.4BCC.D6D4type 7960keep-conference endcallbutton 1:16!!!ephone 17mac-address 0011.9350.8030type 7960keep-conference endcallbutton 1:17!!!ephone 18mac-address 0016.9D99.29CEtype 7941keep-conference endcallbutton 1:18!!!ephone 19mac-address 0015.F9A2.CC64type 7940keep-conference endcallbutton 1:19!!!ephone 20mac-address 0011.9378.D1FAtype 7960keep-conference endcallbutton 1:20!!!ephone 21mac-address 0011.93B6.C547type 7905keep-conference endcallbutton 1:21!!!ephone 22mac-address 0011.5C0E.550Dtype 7970keep-conference endcallbutton 1:22!!!ephone 23mac-address 0011.216E.158Btype 7970keep-conference endcallbutton 1:23!!!ephone 24mac-address 0015.6389.AF1Etype 7931keep-conference endcallbutton 1:24!!!ephone 25mac-address 0050.BF97.30EBtype CIPCkeep-conference endcallbutton 1:25!!!ephone 26mac-address 0018.F3F1.CD5Ftype CIPCkeep-conference endcallbutton 1:26!!ephone 27mac-address 0050.DAB2.67B9type CIPCkeep-conference endcallbutton 1:27!!line con 0exec-timeout 0 0stopbits 1line 66no activation-characterno exectransport preferred nonetransport input alltransport output pad telnet rlogin lapb-ta mop udptn v120line aux 0stopbits 1line vty 0 4password lablogin!scheduler allocate 20000 1000!endCCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0705R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
Posted: Tue Sep 11 18:58:18 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
