Cisco Cisco Expressway 维护手册
■
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:
■
H.323 calls, and interworked H.323 to SIP calls: the Disconnect command will actually disconnect the call.
■
SIP to SIP calls: the Disconnect command will cause the Expressway to release all resources used for the call
and the call will appear on the system as disconnected. However, SIP calls are peer-to-peer and as a SIP
proxy the Expressway has no authority over the endpoints. Although releasing the resources may have the
side-effect of disconnecting the SIP call, it is also possible that the call signaling, media or both may stay up
(depending on the type of call being made). The call will not actually disconnect until the SIP endpoints
involved have also cleared their resources.
and the call will appear on the system as disconnected. However, SIP calls are peer-to-peer and as a SIP
proxy the Expressway has no authority over the endpoints. Although releasing the resources may have the
side-effect of disconnecting the SIP call, it is also possible that the call signaling, media or both may stay up
(depending on the type of call being made). The call will not actually disconnect until the SIP endpoints
involved have also cleared their resources.
■
SIP calls via the B2BUA: as the B2BUA can control the state of a call, if you disconnect the leg of the call that
is passing through the B2BUA (where the Type is B2BUA), the call will fully disconnect. Note that the call may
take a few seconds to disappear from the Call status page — you may have to refresh the page on your
browser.
is passing through the B2BUA (where the Type is B2BUA), the call will fully disconnect. Note that the call may
take a few seconds to disappear from the Call status page — you may have to refresh the page on your
browser.
B2BUA Calls
The B2BUA calls page (Status > Calls > Calls or Status > Calls > History, then click View for a particular B2BUA call)
provides overview information about a call routed through the B2BUA.
provides overview information about a call routed through the B2BUA.
Calls are routed through the B2BUA if:
297
Cisco Expressway Administrator Guide
Overview and Status Information