Acme Packet (MOSC)

MOSC Banner

ext-policy-server via diameter: How to avoid call release after Re-Auth-Req?

in Acme Packet (MOSC) Question

Hi all,

 

one of our customers (cable provider) uses external policy server connected via diameter to the SBC.

The ext-policy-server object in SBC is configured with permit-conn-down and permit-on-reject enabled to ensure that calls are established also in the case of policy server unavailability or rejection of bandwidth reservation requests (in these cases only with media transmission "best effort" of curse).

 

Due to a missbehavior in the interworking of eMTA/CM and CMTS we experienced that the policy server sends a diameter Re-Auth request with "Specific-Action: INDICATION_OF_LOSS_OF_BEARER (2)" (triggered by a COPS message sent by the CMTS) to the SBC.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center