Blocked call - conflicting reports?

[underwoj]

I am running a measurements report in the CM for a Route Pattern and it's showing blocked calls. I run a CMS Trunk Summary Daily on all the Trunk Groups (TG) in the RP and it shows no blocked calls. How can this be?

In addition - I am showing re-hunts on a TG (188) that appears to tie up and equal the amount of blocked calls in this RP...so I am thinking these are the blocked calls that have re-hunted back to the same TG? What is odd is there are 230 channels in TG 188 and it never gets more than 10 calls at a time...so there is no way that TG is full. Please help?

I have attached a couple of pics.

thanks!
Robert

 

[underwoj]

adding another pic

 

[underwoj]

adding final pic

 

[kyle555]

I don't play with those reports very much. And yknow what, I've never actually tried to see what happens if choice 1 has FRL 5 and choice 2 has FRL 2 whether my FRL3 station would be allowed out...

But, could it just be that it correlates with "blocking" as per FRL and not because of all trunks busy?

 

[underwoj]

gotcha...I was definitely thinking it could be some with the FRL station vs the RP. Is there a measurement/report that I can run for blocked calls per station/FRL?

 

[AvayaTier3]

cm5.2
Avaya Aura Communication
Manager Reports
555-233-505
Issue 8
May 2009

Table 13 Page 75
Calls
Blocked
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

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[kyle555]

Cool. So, if blocked calls aren't because of FRL, and you obviously had no availability across trunks in that route pattern, what if...

You had a routing loop? A call to a number out that route is call forwarded at the CO to a DID that goes to a coverage path/vector/whatever that routes out to the same number. You'd only hit "all trunks busy" on the last attempt out, which would tear down every other 'leg' of that call, so you technically only had 'all trunks busy' for the amount of time it took you to send a SETUP message for the last trunk until the carrier sent another SETUP message to loop again and everything tore down with 'normal call clearing'.

 

[underwoj]

wow - a lot to digest here...thanks for the info guys!