
Related topics:
Deleting Adaptations on page 267
Installed vendor adapters
Cisco Adapter (CiscoAdapter)
The Cisco Adapter provides two basic header manipulations: converting between Diversion
and History-Info headers and converting between P-Asserted-Id and Remote-Party-Id
headers. The Diversion and Remote-Party-Id headers have not been accepted by the IETF.
They are replaced by History-Info and P-Asserted-Identity respectively, but are still used in the
Cisco products. The Cisco Adapter also performs all the conversions available by the Digit
Conversion Adapter.
Note:
DiversionTypeAdapter performs all the conversions similar to Cisco adapter.
Diversion to History-Info Header Adaptation
Cisco requires the use of the Diversion header, rather than the History-Info header to provide
information related to how and why the call arrives to a specific application or user. The
following examples illustrate the adaptations.
Example 1:
Communication Manager user 66600001 forwards to Cisco user 60025.
Communication Manager’s outgoing INVITE has this history-info:
Reason=SIP%3Bcause%3D302%3Btext%3D%22Moved%20Temporarily%22
&Reason=Redirection%3Bcause%3DCFI>;index=1.1
In the message sent to Cisco this is converted to:
answer;privacy=off;screen=no
Example 2:
Communication Manager user calls Cisco user 60025. The call is routed to Modular Messaging
at extension 688810.
The INVITE message from the Cisco server contains the Diversion Header:
busy;privacy=off;screen=no
The message is adapted and the outgoing INVITE to MM replaces the Diversion header with
the following:
Managing Session Manager routing
268 Administering Avaya Aura
®
Session Manager November 2010
Komentáře k této Příručce