Resilency of a trusted app Phone

[augustD2]

MiVoice Business and MiCollab both at the latest release and in synk with SDS.

I have a phone configure as a trusted app and call reroute always to the voicemail. This way, the user and phone are create in MiCollab and I don't use a license. I then only have to add a callflow mailbox to the user and everythings is working fine.

The problem is that resiliency of the trusted phone does not work. Has someone already have a success with resiliency of a trusted app phone?

I know I can create a Hunt Group or a single line key on a phone, but it does not create the user in MiCollab. I need to add it manually as a Phantom phone in MiCollab.

Thanks.

 

[kwbMitel]

What type of device did you choose for the Trusted device.

Resiliency is not available for all device types.

I know for certain that resiliency can work with trusted device types that support resiliency.

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

 

[augustD2]

I have try with a 5360.

It seem that it does not support resiliency if not an application like MiCollab or MICC.

 

[kwbMitel]

Incorrect,

I make my nupoint ports resilient all the time
I also create resilient phones with Key appearances of DSS keys for Console purposes all the time
I also make pilot numbers for groups resilient to allow failover routing to work.

Are any of your licensed devices successfully set to be resilient? I feel your issues might be more general.

Have you checked your logs on both system? there might be reasons you are not aware of.

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

 

[augustD2]

I have no problem with resilience of all the phones, hunt group, MiCollab and MICC port setup as trusted.

The only problem is when I create a "dummy" phone with licence trusted. Then I call reoute always the phone to the voicemail hunt group to a callflow mailbox.

In normal mode everything is working fine, except in resiliency the dummy phone won't go to the 2nd controller.

I know I can create a hunt groupe or single line on a phone and it would work, but that way, I have to manually create the user in MiCollab with a type of phone Phantom. That is why I want to used a trusted licence to do it. That way, the user is create in MiCollab and in synk with SDS.

 

[kwbMitel]

Is the issue that you can't do it with Milollab creating the phone?

Have you tried manually creating a 5360 as trusted and making it resilient?

I have done both of these with a 5312 so I can't imagine why you would have difficulty with a 5360.

Something is wrong in your environment, what you are trying to do is possible.

You never answered about checking the logs either

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

 

[Billz66]

I agree

we now use trusted devices as the starting point for call flows - we generally use 5312's as those stand out nicely in the user database
We have nt had any issues creating these on the Mivb and making them resilient

i normally make them there and then they will be pushed to the micollab database

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

 

[augustD2]

I don't have a problem to create the phone, but when we test the resiliency, everything work, except the phone setup as trusted.

I will do more test.

 

[kwbMitel]

Maybe read those logs (3rd time)

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

 

[jpruder]

I usually make my trusted 5020, don't know if you can assign a pseudo mac to trusted, might try it?