PDF(40.7 KB) View with Adobe Reader on a variety of devices
ePub(81.0 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(65.8 KB) View on Kindle device or Kindle app on multiple devices
Updated:April 21, 2021
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes the reason for the ims-authorization-revoked disconnect. The show session disconnect-reasons command shows the internal disconnect reason that is currently overserved in the system.
When the ims-authorization-revoked Disconnect Reason is Pegged?
The most common scenario is the PGW receives Re-Auth-Request (RAR) from PCRF to release the session. To understand the exact scenario the monitor subscriber (verbosity 3 and Multi-Call Trace options) and/or packet capture should be collected. Here is a snippet of monitor subscriber trace where the PCRF releases the session with ims-authorization-revoked disconnect reason by sending RAR with UNSPECIFIED_REASON at Session-Release-Cause.
“If the PCRF decides to terminate an IP CAN session due to an internal trigger or trigger from the SPR, the PCRF shall send a RAR command including the Session-Release-Cause AVP to the PCEF. The PCEF shall acknowledge the command by sending an RAA command to the PCRF.”
Monday April 12 2021 ***CONTROL*** 20:06:25:139 Eventid:10285 .... Disconnect Reason: ims-authorization-revoked Last Progress State: GTP-PDN-IPv4-Connected
Cisco Internal Information Logging monitor configured for the imsi with filters below showed the following sessmgr events logging monitor msid <imsi> logging display pdu-verbosity 5 loggin display event-verbosity full