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.

If a matching Server Flow is found, the SIP routing system performs Policy Invocation and Route Resolution using the matched Server Flow.

• You can configure multiple Server Flows for a single Server Configuration.

• The URI Group field can be configured with the wild card entry (*) that matches any incoming SIP request.

• The Signaling Interface configuration contains the Avaya SBC SIP communication IP Address and Port for each configured transport to receive SIP signaling traffic from the network. The SIP routing system can select a different SIP connect port from Port Ranges for communication with external SIP entities based on configuration.

• The Received Interface field must not be confused with the Signaling interface and is not used as part of inbound call processing.

If there is no matching Server Flow, the call is refused and the incoming SIP request is dropped. The SIP routing system stops the call processing for the incoming SIP request after an appropriate SIP error response (403 Forbidden) is sent to the SIP entity for rejecting the call.