Existing Session Status Changed To Orphan Due To Nas-Port Not Coming In Radius Packet (Doc ID 1357634.1)

Last updated on SEPTEMBER 02, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.1.0.1 and later   [Release: 7.3.1 and later ]
Information in this document applies to any platform.

Symptoms

We are receiving RADIUS account packets from network element without NAS-Port attribute, but default BRM searching for duplicate sessions is based on NAS-Identifier (PIN_FLD_TERMSERV_ID) and NAS-Port (PIN_FLD_TERMSERV_PORT). Due to this, any existing session with that same NAS-Identifier is getting closed as orphan session by default BRM RADIUS Manager.

As per RFC2139, "Either NAS-IP-Address or NAS-Identifier MUST be present in a RADIUS Accounting-Request. It SHOULD contain a NAS-Port or NAS-Port-Type attribute or both, unless the service does not involve a port or the NAS does not distinguish among its ports." , they are receiving NAS-Identifier and NAS-Port-Type in the packets.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms