Need RAD solution for Mxe server!!

[Virtualman9000]

Can anyone recommend an IP-based RAD solution for an MXe server besides the iQueue? I have several hunt groups that need a RAD. Is SIP an option?

Thanks

 

[kwbMitel]

Don't you have a gateway for your trunks?

Can't you enable embedded Mail RAD ports on the gateway?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Virtualman9000]

I was under the impression that networked RAD hunt groups are not supported.

 

[kwbMitel]

Not sure about supportability.

Not sure if the description Networked RAD Group applies.

As far as the MXE server is concerned the Rad is an external device. On the Gateway it is local.

I can't think of a logical reason it would not work.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[IrwinMFletcher]

If you mean the RADs supported by EMEM, then you are correct. The MXe Server doesn't support it.

 

[kwbMitel]

Irwin, My suggestion was to use the EMEM ports on the gateway, not the server.

Are you saying you know for certain that this is not possible?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[IrwinMFletcher]

No, I missed the 'on the gateway' part. I was referring to EMEM on the MXe Server. However I'm not saying it will work either . One thing to look at is the E2T usage. You'll use up an extra channel (or is it two) on the gateway for each port.

 

[kwbMitel]

To clarify your question regarding Networked Rads.

It is the Hunt Group that has the restiction over whether "Networking" is possible or not.

Only Voice Huntgroups can be networked.

A Hunt group is considered networked when phones from a remote system are members of a local hunt group.

None of the above applies in this case.

The Hunt Group is created on the Gateway
The Members of the hunt group are local to the gateway

The suggestion therefore is valid.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[LoopyLou]

Are the hunt groups ACD by any chance. If so put the path on the gateway and run the agents of the server. That way the RADs are on the same controller as the paths.

 

[Virtualman9000]

If I try to add either a RAD hunt group or individual RAD extension from the trunking gateway MXe to a hunt group in the MXe server I get "The RAD directory number must be for a station (non-mixed) or RAD hunt group". The gateway directory numbers only exist in the MXe server as a remote directory number, so it will not allow it.

 

[kwbMitel]

Virtualman9000:

Please read More Carefully!

Huntgroup on gateway
Rad on gateway
voicemail on gateway.

The only thing on the MXE server is a Remote Directory entry pointing to the RAD (On the Gateway)

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[mitelmitel]

I successfully program the following regularly:-

Agents/Users on the MXe Server [User gateway]
Paths/RAD HG/RAD Ports on the Gateway

Agent groups are created on the server and referenced in paths ass on the gateway.

 

[Mitelmike2010]

You would be better of using a 6160 (Or IQ if you use the latest names!!)

Best regards

 

[kwbMitel]

MitelMike2010: Please respond to the original posters question.

Can anyone recommend an IP-based RAD solution for an MXe server [highlight]besides the iQueue?[/highlight]

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[IrwinMFletcher]

Just curious, can someone who has this setup take a look at the E2T consumption, I have a feeling that for every incoming call you'd be using 2 or maybe even 3 E2T channels on the gateway.