A SIP RA entity provides the following limiter endpoints for use with Rhino platform rate limiting:

 inbound_initial_requests

This limiter endpoint can be used to control the rate that incoming initial requests received from the network are accepted for processing by the SIP RA.

The SIP RA requests one unit of work from this limiter endpoint for each initial request that it receives. If the request is granted then initial request processing proceeds normally. If, however, the work request is rejected by a rate limiter connected to the endpoint, then the SIP RA stops processing the initial request and returns a 503 error response with a Retry-After value determined by the RetryAfterInterval config property.

 inbound_initial_invites

This limiter endpoint can be used to control the rate that incoming initial INVITE requests received from the network are accepted for processing by the SIP RA.

This limiter endpoint is a "sub-endpoint" of the inbound_initial_requests endpoint. For each initial INVITE, the SIP RA requests one unit of work from the inbound_initial_requests endpoint, and if that is granted, another unit of work is requested from the inbound_initial_invites endpoint.

By configuring the inbound_initial_requests endpoint with a rate limiter of higher capacity than inbound_initial_invites, the SIP RA can throttle initial INVITEs while still allowing other initial requests to proceed.

If the initial INVITE is rejected by a rate limiter connected to the endpoint, then the SIP RA stops processing the initial request and returns a 503 error response with a Retry-After value determined by the RetryAfterInterval config property.

Previous page Next page