Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2337090.1
Update Date:2017-12-08
Keywords:

Solution Type  Problem Resolution Sure

Solution  2337090.1 :   SBC media release is not working properly  


Related Items
  • Acme Packet 4500
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Session Delivery Network>SN-SND: Acme Service Provider
  •  


SBC is not managing media properly on 7.2 and above
mm-in-realm/mm-in-network parameter act different in 6.3.0 vs 7.2.0

In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-13345479281>

Applies to:

Acme Packet 4500 - Version S-Cz7.3.0 and later
Information in this document applies to any platform.

Symptoms

MM-in-realm/mm-in-network parameter act different in 6.3.0 vs 7.2.0/7.3.0

Normally, Customer wants media to be released for calls in the same access realm. 

To achieve this they have mm-in-realm and mm-in-network disabled in the realm configuration.

In some cases where they want to manage media they will enable mm-in-realm and keep mm-in-network disabled.

This used to work perfectly on 6.3.

But in release 7.2, in the same situation, putting mm-in-realm to enabled is not
enough. They have to configure also mm-in-network enabled, in order to have
the media managed by the SBC.
All the other mm parameters are always enabled.

Changes

 Upgrade from 6.3 to 7.2/7.3

Cause

 This is a bug and code needs to be changed.

Reference Bug# 24702886 - mm-in-realm/mm-in-network parameter act different in 6.3.0 vs 7.2.0

Solution

This issue is resolved in SCZ730m2p3 and later

 


 

References

<BUG:24702886> - MM-IN-REALM/MM-IN-NETWORK PARAMETER ACT DIFFERENT IN 6.3.0 VS 7.2.0

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback