Acme Packet (MOSC)

MOSC Banner

SAG Hunt strategy

edited Jul 25, 2019 5:04AM in Acme Packet (MOSC) 3 commentsAnswered

Hi there!

Sorry in advance for my english,

I have incorrect behavior or misunderstand of how AcmePacket session agent group Hunt strategy's working.

I have following SAG settings:

session-group

        group-name                     trunksag

        description                   

        state                          enabled

        app-protocol                   SIP

        strategy                       Hunt

        dest                          

                                       Trunk2

                                       Trunk1

                                       Trunk3

                                       Trunk4

                                       Trunk5                       

        trunk-group                   

        sag-recursion                  enabled

        stop-sag-recurse               486,502

and following constraints

            Max-outbound-sessions

Trunk1            100

Trunk2            100

Trunk3            500

Trunk4            200

Trunk5            200

In my example Trunk 1 and Trunk 2 exceeds their constraints.

So I have following choice of next route from sipd logs:

Jan 21 11:17:35.263 [SIP]   redirects: 1/5

Jan 21 11:17:35.263 [SIP]   =>1=[Trunk3|Trunk3|defaultsag]sip:9999999999@Trunk3:5060(rt) q=done lpStage=0

Jan 21 11:17:35.263 [SIP]     2=[Trunk|Trunk2|defaultsag]sip:9999999999@Trunk2:5060(rt) lpStage=0

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