GVP MCP:sip:call rate period
m (1 revision imported: converting [ and ] characters to HTML-friendly code) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
|valid=sip.call_rate_period should be non-negative integer. | |valid=sip.call_rate_period should be non-negative integer. | ||
|takeseffect=At start/restart | |takeseffect=At start/restart | ||
| − | |shortdesc=Specify the call rate period in milliseconds for overload control. It works along with parameter call_rate. For example, if call_rate is set to 10 and call_rate_period is set to 500 (ms), then SIP line manager can accept at most 10 incoming calls every 500 milliseconds. If there are more than 10 incoming calls within 500 milliseconds, the excess calls will be rejected with response 486 Busy Here. By default, call_rate_period is set to 0, which means no overload control at all. | + | |shortdesc=Specify the call rate period in milliseconds for overload control. It |
| + | works along with parameter call_rate. For example, if call_rate is set | ||
| + | to 10 and call_rate_period is set to 500 (ms), then SIP line manager | ||
| + | can accept at most 10 incoming calls every 500 milliseconds. If there | ||
| + | are more than 10 incoming calls within 500 milliseconds, the excess calls | ||
| + | will be rejected with response 486 Busy Here. By default, | ||
| + | call_rate_period is set to 0, which means no overload control at all. | ||
}} | }} | ||
{{DraftOption}} | {{DraftOption}} | ||
Latest revision as of 15:35, June 29, 2020
View in ref guide.
Edit this option Publish this option Clear draft content
Published Option
Draft Option
No draft option
This page was last edited on June 29, 2020, at 15:35.
Comments or questions about this documentation? Contact us for support!