If I run the command "list measurements route-pattern 102 today" we can see that there are 9662 calls offered and 216 calls blocked.
Regarding the calls blocked, reading the CM reporting guide (albeit very old) it suggests that:
The number of offered outgoing calls that found all trunk groups in
the pattern busy. If the queue overflows, then the call is still
blocked. Specifically, a blocked call is a call that:
■ Arrives when there are no available resources
■ Arrives and gets queued
■ Arrives when the queue is full
■ Arrives and cannot queue because the queue length is set to
zero
■ Cannot queue because the Automatic Callback (ACB) button is
busy
■ Cannot queue because there is no ACB button
If I run a trunk summary report I can see that various trunks within the route list have had hardly any traffic, I fail to see how a call would get blocked because of a trunk availability issue.
Anyone any thoughts, this issue doesn't just relate to today, it is like it each day?
Regarding the calls blocked, reading the CM reporting guide (albeit very old) it suggests that:
The number of offered outgoing calls that found all trunk groups in
the pattern busy. If the queue overflows, then the call is still
blocked. Specifically, a blocked call is a call that:
■ Arrives when there are no available resources
■ Arrives and gets queued
■ Arrives when the queue is full
■ Arrives and cannot queue because the queue length is set to
zero
■ Cannot queue because the Automatic Callback (ACB) button is
busy
■ Cannot queue because there is no ACB button
If I run a trunk summary report I can see that various trunks within the route list have had hardly any traffic, I fail to see how a call would get blocked because of a trunk availability issue.
Anyone any thoughts, this issue doesn't just relate to today, it is like it each day?
Comment