
Reason=SIP%3Bcause%3D486%3Btext%3D%22Busy%20Here%22
&Reason=Redirection%3Bcause%3DNORMAL%3Bavaya-cm-reason%3D%22
cover-busy%22%3Bavaya-cm-vm-address-digits%3D81080000%3Bavaya-cm-vm-address-
handle%3Dsip:80000%40avaya.com>;index=1.1
Remote-Party-Id to P-Asserted-Identity Header Adaptation
Cisco requires information in the P-Asserted-Identity (PAI) header to be received in the
Remote-Party-Id (RPI) header. Any incoming message containing a P-Asserted-Identity
header being routed to Cisco will replace that header with the Remote-Party-Id header.
Similarly, calls from Cisco containing the Remote-Party-Id header will be converted to a P-
Asserted-Identity header when routed to non-Cisco entities.
Example 3:
A call is placed from 12345 at Communication Manager and routed to the Cisco PBX.
The INVITE from Communication Manager contains:
This header is converted to RPI when the request is sent to the Cisco PBX:
Remote-Party-Id: “Ryan”
Example 4:
A call is placed from 23456 at Cisco PBX and routed to Communication Manager.
The INVITE from Cisco PBX contains:
Remote-Party-Id: “Ryan”
This header is converted to PAI when the request is sent to Communication Manager:
Verizon Adapter (VerizonAdapter)
The Verizon adapter requires the same History-Info to Diversion adaptations that the Cisco
Adapter uses. The Verizon Adapter also performs all the conversions available by the Digit
Conversion Adapter.
AT&T Adapter (AttAdapter)
AT&T does not handle the History-Info header. The adaptation module removes, on egress to
AT&T, any History-Info headers in a request or response. Messages from AT&T do not change.
The AT&T Adapter also performs all the conversions available by the Digit Conversion
Adapter.
Adaptations
Administering Avaya Aura
®
Session Manager November 2010 269
Kommentare zu diesen Handbüchern