An update to this ticket. It has now been fixed after reaching out to tac. The behaviour is known with Oracle Session monitor version 5.1 patch 3 and a fix was provided on patch 4 to resolve this. The Minor update was done and the issue is now fixed

Hi Experts,

I have two local-policy configured on OCSBC AP6350 as follows. The SBC is running software version SCZ920p5.

Local-Policy A:

local-policy
from-address *
to-address 100.200.100.1
source-realm Core
description Outbound to SBC1
activate-time
deactivate-time
state enabled
parallel-forking disabled
policy-priority none
policy-attribute
next-hop SAG:SBC1
realm SBC1_Access
action none
terminate-recursion disabled
carrier
start-time 0000
end-time 2400
days-of-week U-S
cost 0
state enabled
app-protocol
methods
media-profiles
lookup single
next-key
auth-user-lookup
eloc-str-lkup disabled
eloc-str-match

Local-Policy B:

local-policy
from-address +441171234567
+441171234578
+441171234589

    to-address             *
    source-realm                            Core
    description                             
    activate-time
    deactivate-time
    state                                   enabled
    parallel-forking                        disabled
    policy-priority                         none
    policy-attribute
            next-hop                                                      SAG:SBC2
            realm                                   SBC2_Access
            action                                  none
            terminate-recursion                     disabled
            carrier
            start-time                              0000
            end-time                                2400
            days-of-week                            U-S
            cost                                    0
            state                                   enabled
            app-protocol
            methods
            media-profiles
            lookup                                  single
            next-key
            auth-user-lookup
            eloc-str-lkup                           disabled
            eloc-str-match

Please note that both local-policy has the same source-realm named Core.

When +441171234567 calls 08000123456, and the call gets routed to the SBC from the Core Network, the SBC uses local-policy A to route the call to SAG:SBC1 instead of local-policy B which should route the call to SAG:SBC2.

How do we configure the SBC to always use local-policy B instead of local-policy A for this type of call scenario where a number in the from-field of local-policy B calls any destination number?

Thanks.

Hello

in local-policy A what 100.200.100.1 in To-address field is ? is that address present in incoming To or RURI ? if yes probably is the reason why it is matching LP-A , since To-address has priority over From-address .

as general rules below the routing preferences and priority , from top to down :

1. Cost (cost in local policy attributes) is always given preference.
2. Matching media codec (media profiles option in local policy attributes).
3. Longest matching To address (to address list in local policy).
4. Shortest matching To address (to address list in local policy).
5. Longest matching From address (from address list in local policy).
6. Shortest matching From address (from address list in local policy).
7. Narrowest/strictest day of week specification (days of week option in local policy attributes).
8. Narrowest/strictest time of day specification (start time and end time options in local policy attributes).
9. Wildcard matches (use of an asterisk as a wildcard value for the from address and to address lists in local policy).
10. Wild card matches are given the least preference. A prefix value of 6 is given a higher preference than a prefix value of * even though both prefix values are, in theory, the same length.

Cheers

Antonio