Acme Packet (MOSC)

MOSC Banner

Session Constraints issue on SIP Interface

edited Oct 12, 2015 8:17AM in Acme Packet (MOSC) 3 commentsAnswered

Hello,

I have an issue with the session-constraints limit in an interconnect scenario:

Each carrier that we connect to the SBC (Oracle AP4500/6300 running SCZ7.2m5p3) has an own core and peer realm and SIP interface. We have configured a session constraints profile on the peer SIP interface of each carrier in order to limit the incoming and outgoing traffic to the carrier. An example for this session-constraints profile is as follows:

session-constraints

        name                                    Constraints_Carrier-X

        state                                   enabled

        max-sessions                            5000

        max-inbound-sessions                    700

        max-outbound-sessions                   4300

        max-burst-rate                          0

        max-inbound-burst-rate                  0

        max-outbound-burst-rate                 0

        max-sustain-rate                        0

        max-inbound-sustain-rate                0

        max-outbound-sustain-rate               0

        min-seizures                            5

        min-asr                                 0

        cac-trap-threshold                      0

        time-to-resume                          60

        ttr-no-response                         0

        in-service-period                       0

        burst-rate-window                       0

        sustain-rate-window                     0


Our expectation is the following:

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center