SBC URI groups 1

[mattKnight]

Hi

I need to apply a URI group to an inbound server flow and I'm using a regex to do this!

Except that the regexp doesn't match, so the calls drop through to the next flow - which fortunately still routes ok.

Is there a way of testing the URI group regex actually in-situ prior to binding it to the flow, or even a log that would show me why the expression doesn't match. The expression I'm using matches the header when I test it on an online regex tester (so its syntactically correct)

Or even any decent documents?

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[kyle555]

It's quirky to get your head around, but all SBCs are basically the same - they provide some sort of ingress processing on the interface being used inwards, then it goes to the SBCs brain for thinking, then it goes to the outward interface with outward processing possible.

The SBC for URI groups, upon ingress, from a Trunk Server or from a Call Server is different.

Took me a while when I was trying to build a URI group to block calls TO a number but had it on a inward flow and was pulling my hair out and just for kicks put my originating number on the URI group on the inward flow and got it to block.

Had to read a few times and let it sink in. Maybe putz around with a test uri group with a flat number to make sure it's your SBC config and not your regex!

https://downloads.avaya.com/css/P8/documents/101026873

p72
Server flow matching
The routing system uses the URI Group and SIP Received Interface fields of the Server Flow
configuration as an additional matching criterion to determine a Server Flow match.
The SIP routing system uses the SIP To header URI of the incoming request for comparison with
the provisioned URI Group to decide a match. If URI Group is matched, the SIP routing system
then validates if the destination IP address of the incoming SIP request matches the provisioned IP
Address field of the Received Interface configuration. If either of the URI Group or Received

Interface fields does not match, the SIP routing system skips to the next Server Flow. The SIP
routing system looks for a match from the set of Server Flows associated with Server Configuration.
If no matching Server Flow is found, the SIP routing system rejects the registration as there is no
outbound server flow configured.


p74:
Server flow matching for calls originated from the server
The routing system uses the URI Group and SIP Signaling Interface fields of the Server Flow
configuration as an additional matching criterion to determine a Server Flow match.
The SIP routing system uses the SIP From header URI of the incoming request for comparison with
the provisioned URI Group to decide a match. If URI Group is matched, the SIP routing system then
validates if the destination IP address of the incoming SIP request matches the provisioned IP
Address field of Signaling Interface configuration to decide a match. If either of the URI Group or
Signaling Interface fields does not match, the SIP routing system skips to the next Server Flow,
looking for a match from the set of Server Flows associated with the Server Configuration.

 

[mattKnight]

On first read through - Ithink I have found my issue!

The SIP routing system uses the SIP To header URI

Design error - I was setting my match to match on the SIP From header

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.