Cisco Cisco Expressway Maintenance Manual
Field
Description
Destination
The alias dialed from the device. This may be different from the alias to which the call was placed,
which may have been transformed (due to pre-search or zone transforms).
which may have been transformed (due to pre-search or zone transforms).
Type
Indicates either a traversal or non-traversal call.
Protocol
Shows whether the call used H.323, SIP, or both protocols. For calls passing through the B2BUA, this
may show "Multiple components"; you can view the call component summary section to see the
protocol of each individual call component.
may show "Multiple components"; you can view the call component summary section to see the
protocol of each individual call component.
Status
The reason the call ended (completed calls only).
Peer
Identifies the cluster peer through which the call is being made.
Actions
Click View to see further information about the call, including a list of all of the call components that
comprise that call.
comprise that call.
Call components summary information
After selecting a call from the primary list (as described above) you are shown further details of that call, including a
list of all of the call components that comprise that call.
list of all of the call components that comprise that call.
Each call component may be one of the following types:
■
Expressway: a standard Expressway call
■
B2BUA: a call component that is routed through the B2BUA to apply a media encryption policy or ICE
messaging support
messaging support
■
Microsoft Lync B2BUA: a call component that is routed through the Microsoft Lync B2BUA
You can view full details of each call component by clicking on the Local call serial number associated with each
component. This will open the Call details page which lists full information about that component, including all call
legs and sessions. It also provides further links to the Call media page which lists the individual media channels
(audio, video, data and so on) for the most relevant session for a traversal call.
component. This will open the Call details page which lists full information about that component, including all call
legs and sessions. It also provides further links to the Call media page which lists the individual media channels
(audio, video, data and so on) for the most relevant session for a traversal call.
If the Expressway is part of a cluster and the call passes through two cluster peers, you can click View associated
call on other cluster peer to see the details of the other leg of the call.
call on other cluster peer to see the details of the other leg of the call.
Mobile and remote access calls have different component characteristics depending on whether the call is being
viewed on the Expressway-C or Expressway-E:
viewed on the Expressway-C or Expressway-E:
■
On an Expressway-C, a Unified CM remote session will have 3 components (as it uses the B2BUA to enforce
media encryption). One of the Expressway components will route the call through one of the automatically
generated neighbor zones (with a name prefixed by either CEtcp or CEtls) between Expressway and Unified
CM.
media encryption). One of the Expressway components will route the call through one of the automatically
generated neighbor zones (with a name prefixed by either CEtcp or CEtls) between Expressway and Unified
CM.
■
On an Expressway-E, there will be one component and that will route the call through the
CollaborationEdgeZone.
CollaborationEdgeZone.
Note that if both endpoints are outside of the enterprise (i.e. off premises), you will see this treated as 2 separate
calls.
calls.
Rich media sessions
If your system has a rich media session key installed and thus has been extended to support business-to-business
calls, and interworked or gatewayed calls to third-party solutions and so on, those calls are also listed on the call
status and call history pages.
calls, and interworked or gatewayed calls to third-party solutions and so on, those calls are also listed on the call
status and call history pages.
Disconnecting Calls
Click Disconnect to disconnect the selected calls. Note that if your Expressway is part of a cluster you have to be
logged into the peer through which the call is associated to be able to disconnect the call.
logged into the peer through which the call is associated to be able to disconnect the call.
Call disconnection works differently for H.323 and SIP calls due to differences in the way the protocols work:
223
Cisco Expressway Administrator Guide