Local policy - longest match ?

Hi everybody !

 

I have a situation where I have a customer with 2 configured SA's

One SA is for production traffic, and one SA is for LAB/Testing.

LAB SA is using a 10 digit number seies.

 

I was thinking I could use 2 local policys on traffic from core (towards customer) like this :

 

from-address *

to-addess *

source-realm ic_core_customer

policy-attribute

next-hop production-SA

 

from-address *

to-addess 471122334*

source-realm ic_core_customer

policy-attribute

next-hop LAB-SA

 

Problem is that SD4250 (I use currently ver 6.1) always selects the first production-SA, even if the request uri from core is sip:+4711223340@some-ip-address

I also tried to use cost=0 on the lab-SA policy and cost=1 on the production-policy .. But still no traffic was hitting the lab SA.