nametag huntgroups and resiliency

[veenstrahiem]

Anyone with thoughts about nametag huntgroups and resiliency.
I have a customer with 2 MBGs ans sip-trunks, going to 2MCDs as a resilient pair.
Currently all users are on 1 controllers, and failover to the 2nd. This all works.
But I also want to have several numbers with a nametag-huntgroup, to give a name on the display of the Phone.

However, I cannot make a nametag-huntgroup resilient. So when the primary mcd fails, these calls are not working.

Any suggestions would be appreciated

 

[Supernova99]

Nametag hunt groups are not resilient (perhaps they should be)
I would change them to standard voice hunt groups if you want them to work when resilient
You could front the call with an ACD path with a teldir name that interflows to the voice hunt group, that way the name should still be displayed
Or Resilient Hunt group routed always to a new nametag hunt group, but you will need to program them on each system, and allocate different DN's on each system with the name you require.

e.g.
system 1 incoming voice hunt group is 1000 this is resilient on system 2
Call re-route always 1000 to nametag hunt group 1001 on system 1 and nametag hunt group 1002 on system 2
Make sure the call reroute is not shared between systems

Share what you know - Learn what you don't

 

[kwbMitel]

My thinking is that if your system is in resilient mode, you have bigger issues than what shows up on the display. My 2 bits.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[Billz66]

Can you program the name tags as as local only numbers on both controllers ( same number on each)

We have done something similar for a resilient site that used acd paths interflowing to nametags and then rr to vmail.
We duplicated anything that was not resilient on both controllers with same ext numbers as local ( including vmail pilots and ports ).
This meant that when resilient , any rads worked and interflows to vmail worked.

If I never did anything I'd never done before , I'd never do anything.....

 

[veenstrahiem]

I allready tried nametag huntgroup as local-only dn, but, a local-only cannot have a name in the tel.directory, therefore this is not functioning

 

[Supernova99]

Yes local number nametag hunt group is not possible,
Have you tried the method suggested above?

Share what you know - Learn what you don't

 

[veenstrahiem]

call reroute is already being shared on the cluster, I really dont want to change this.
I have been thinking about this for some time now, and I think I wil have to use some sort of ARS digits dialled going to a route list, where the first route goes to the 1st vmcd and the second route to the 2nd vmcd.
I can also use this for making ACD paths kind-off resilient on both vmcds

dialling 360xxx to routelist 100 -> 1st route with digit mod. makes: 361xxx
-> 2nd route with digit mod. makes: 362xxx
Then the 361xxx are numbers on vmcd1, and 362xxx are numbers on vmcd2

 

[Supernova99]

That should work but it does require more programming on both systems.
BTW you can select individual entries to not share in SDS so if you don't want to share CRA 250 then just select All Records with Exceptions then specify route 250

Share what you know - Learn what you don't

 

[veenstrahiem]

Oke, I will look at that, now that you say this, looks familiar. At first I thought ALL callreroute is shared: YES/NO, but if I can use this with exception, that could work. Thanks.