call rate limiting
2 posters
Page 1 of 1
call rate limiting
Hi,
in logs we can find information that call rate limiting was triggered.
08th, 18:08:04.844+0200 TBMSG ENGI: WARNING: 22 calls dropped by call rate limiting in the last 60 seconds (598813 total)
How can I find which NAP entered call rate limiting? It's not in log message and I didn't find anything useful in GUI.
in logs we can find information that call rate limiting was triggered.
08th, 18:08:04.844+0200 TBMSG ENGI: WARNING: 22 calls dropped by call rate limiting in the last 60 seconds (598813 total)
How can I find which NAP entered call rate limiting? It's not in log message and I didn't find anything useful in GUI.
AndrzejP- Number of Messages : 12
Point : 22
Registration Date : 2019-09-11
Re: call rate limiting
You need to set the gateway application log level to 1 to see which NAP is dropping the call. Also in the call trace you can see it.
Re: call rate limiting
Thank you.
We have to high volume of traffic to set gataway log to level 1 so I'll try with call trace.
What call termination Reason should I look for?
Or maybe there is a list of possible reasons that appear in call trace, somewhere in documentation?
We have to high volume of traffic to set gataway log to level 1 so I'll try with call trace.
What call termination Reason should I look for?
Or maybe there is a list of possible reasons that appear in call trace, somewhere in documentation?
AndrzejP- Number of Messages : 12
Point : 22
Registration Date : 2019-09-11
Re: call rate limiting
Hi
You can check 218-TOOLPACK_LOCAL_CONGESTION error from the Call Trace search.
You can check 218-TOOLPACK_LOCAL_CONGESTION error from the Call Trace search.
Similar topics
» Call Rate Limit Settings
» Call Drops
» SYNC_DROP call logs
» Inbound call no ringing
» How can I trace a call in FreeSBC?
» Call Drops
» SYNC_DROP call logs
» Inbound call no ringing
» How can I trace a call in FreeSBC?
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum