Last night, I tried replacing some of our shared lines with blast groups. Currently, our UC520 is set up with hunt groups that first ring a single phone, then ring a shared line and finally ring the original person, forwarding to voicemail if not picked up.
This system is inefficient as only 1 call can be on the shared line at one time.
I created a blast group last night with 3 phones added (using the CCA v2) which added the following code,
"voice hunt-group 1 parallel
That works fine. I then created a hunt group which would ring a single phone then end on a blast group (it seems like hunt groups can't do Single phone->Blast group-> single phone in a single hunt) which gave me this,
ephone-hunt 5 sequential
preference 0 secondary 7
Ringing the blast group directly works fine but when we tested ringing 805, it failed when it was supposed to ring the blast group. We checked over the settings for a good few hours, trying to work out why this didn't work but we didn't get anywhere.
This seemed like the logical way to me but is there another way I should be going about this?
Are you suggesting that I create a dummy ephone to forward all calls for the hunt group?
Why is my current hunt group not working though? 'No Answer Forward to" is set to "Blast Group:1(507)" within CCA and I am able to call the blast group directly. Why does it fail when it tries to forward to the blast group?
That is a limitation in CME and we need better error checking in CCA, which we will be adding.
Will it be a permanent limitation?
Also, if the dummy ephone is an applicable workaround, can you provide a link to a tutorial to get that happening please?
We will probably fix it, but there are no estimates as to when that will happen.
To implement the workaround, please do this:
1) Identify an available out of band ephone-dn. OOB rules for CCA can be found on:
2) Enter this CLI. Notice "XX" corresponds to the DN you identified in step 1.
call-forward all 900
In this example, the first hunt group points to 800, which will hit ephone-dn XX, and the call will be forwarded to 900, which corresponds to the pilot number of the second hunt group.
Let me know how this goes.
Even using this method, it seems I can't get a hunt group to successfully forward a call to the blast group. Set up ephone-dn 166 which a number of 998 with forwards all to the blast group. Ringing 998 works fine but i added 998 as 'other' in the no answer forward to section and that had the same issue as forwarding directly to the blast group.
Is there any other way to produce the same effect (i.e. hunt group ending up at a blast group)
Tried a new method of adding a new line with the number 997. When it is unanswered, it forwards to the blast group. Using this method, was bypassing the hunt group problem but it also failed transferring to the blast group.
I think I get the issue now. Cannot forward to a blast group at all =(
Can you post your full configuration and version? Don't forget to hide the passwords. Forwarding to a blast group is supported.
My previous statement was backwards (sorry, I am sleepy). The timeout needs to be lower than the call forward settings of the ephone-dn's in the group. Again, sorry for the mess.
Time for debugs. For a failed call, please provide a "debug voip ccapi inout"
Please remove this command from under telephony-service (just negate it):
call-forward system redirecting-expanded
Ran the command,
and-ucncle02(config-telephony)#no call-forward system redirecting-expanded
and it still had issues. Tried remaking the blast group(508) and hunt group(808) but it didn't work here. Also didn't work ringing a line (997&998) that was set to forward to it. Attached the current running config.
Let's try one more thing before we send you to TAC. Try to increase "max-redirecct" under telephony-service to 10.
After the redirect from the ephone-hunt, the call gets disconnected with cause code 1, which is unallocated number. The weird thing i that your patterns are all dialable...
The following doesn't solve the hunt-group nuances however it may give you the fuctionality that you are looking for.
Keep your current call flow, but reconfigure your shared line as an octal line. Octal lines have an 8 call limit, so your users will now be able to field multiple calls on the shared line.
I am sorry if I wasn't clear. You need to open a TAC case and have one of our support engineers work with you directly.