eSpace U1911 - Hunting group is not working

Publication Date:  2015-07-07 Views:  423 Downloads:  4
Issue Description
Customer is conflict about the hunting group. Customer provide 3 number which are 3230, 3231 and 3131. Customer wanted all three numbers to ring at the same time. If one is engaged, the other two will ring. If two are engaged, the last one will ring. If all are engaged, 4th call and above will be in the waiting line (queue). But the final result is, when we dial either one number, the entire internal phone which starts with number 3 will ring. This is because the prefix 3 is for the inter call.
Solution

Firstly, I do a remote access with the customer and see what the request that the customer is needed.

Secondly, create a hunting group for the company and add in 3 users into the hunting group. Below is the command line to create a hunting group:
config add huntinggroup huntno 0 huntgroupname Addon ifstaticgroup yes allbusymanage queuethenredirect allofflinemanage redirect allquitmanage redirect pwdauth no ringtype serial ifnoanswerredirect yes redirectdn 3230

For the sign in and sign out mode, we change the ifstaticgroup from no to yes, it will automatic sign in.
Below is the command line to create the hunting member to the hunting group:
config add huntmember huntno 0 memberdn 3230
config add huntmember huntno 0 memberdn 3231
config add huntmember huntno 0 memberdn 3131

After that, add in the prefix into the hunting group:
config add prefix dn 3 callcategory sin callattribute huntercall cldpredeal no huntgroupno 0

Last step, type in the command to show the hunting group:
show huntinggroup huntno 0

After configure all the command to create a hunting group, we start to test is the solutions are working.

Unfortunately, customer already adds a prefix 3 as inter prefix, so when we dial the number 3131, the entire internal phone which start with number 3 is ringing.

So we suggest customer to change the hunt member number start with 4xxx and add a prefix 4.

Customer agrees with the solution we gave and we configure again with the number 4230, 4231 and 4131.

 At the end, the testing is successful.

END