Move RADs To Another Controller

[RAMitel]

I have an upcoming task to convert a physical Mxe to Virtual but the controller is using 29 ports as RADs and 1 port for admin MB access. The system uses the RADs for ACD paths. Version 7.2SP1 PR1

The Mxe will remain as a gateway for the remaining ISDN circuits so I was planning on moving the RADs to this controller because a virtual instance can only have 12 ports for VM/RADs. (Obviously the Mxe will be formatted and then added to the cluster as a new node)

I will re-program the RADs onto the physical controller but can I simply move the recordings from the vmail directory? Also I remember something about not being able to use RADs on a remote node for ACD?

 

[kwbMitel]

==> can I simply move the recordings from the vmail directory?

Yes

==> not being able to use RADs on a remote node

Correct


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

 

[Billz66]

virtual instance can only have 12 ports for VM/RADs ?

we have plenty of vMiVB's with 30 Vm ports , usually use up to 24 for rads

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

 

[RAMitel]

@kwbmitel- I thought this was the case but I had a look at the engineering guidelines over the weekend and pages 20-22 state that "External IP RAD in 3300" will work, I may speak with Mitel to double check.

@Billz66- Yes only 12 ports are supported on virtual installations, the latest vMCD eng guidelines (Granted the latest is still 7.0) page 24. I have also confirmed this with Mitel in the past.

 

[kwbMitel]

I've tested using a remote system EMEM for RADs and ACD and it did not work - I did this last around 7.0 SW

The 12 port limit on virtual comes as a surprise to me (Yes I checked, with REL 8.0 Eng Guide). The system lets you program 30 and I've never had an issue but it is entirely possible that no more than 12 were in use at any one time.

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

 

[RAMitel]

Thanks kwb,

I won't be using the remote node on advice received! Also I don't want to risk setting up 13+ RADs only to find that only 12 or less will actually work as I have a limited window to do the migration. I can setup a RAD workflow via IVR to get around this so not a big issue. If I ever get chance I will set this up to see what actully happens as yourself and Billz66 clearly have done this.

 

[kwbMitel]

Keep in mind that RADs and ACD are very efficient. If you have more callers than RAD ports available, then the system will create a listen only conference when a port becomes available and ALL waiting lines will hear the RAD simultaneously.

I recently set up a College with over 2000 calls a day and a 45 second Auto-Att greeting (via ACD) and 5 ports handle the traffic without issue.

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

 

[Billz66]

kwb , can you screenshot that capacity statement , I must be getting old as i cant find it in 7.2 or 8.0 eng guidelines

I'm going to fire up a vMiVb and configure 24 acd paths with short delay to a rad hunt and short repeat timers and see if i can get them all to work at once


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

 

[Billz66]

search for capacities found it

From memory we haven't used 24 RADS on a large traffic call centre , more for ring group and ACD delays in lower volume call centres and general businesses
This means that we are possibly below the limit of 12 at once.


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