Mitel 3300 in a Citrix Enviroment

[PrinceEvans]

All our users use Citrix via our LAN. We are looking to purchase the Mitel 3300 phone system but we are concerned that the UC Advanced software may not fully work in Citrix.

Does anyone know if the UC Advanced software is compatible with Citrix and if yes, are there restrictions to the features available?

Thanks
Lee

 

[libellis]

See the following thread that recently addressed this. Note that at the time of posting the responder hadn't implemented anything yet, but had done his homework.

http://www.tek-tips.com/viewthread.cfm?qid=1564079&page=2

 

[PrinceEvans]

The info in the previous thread is very useful.

Has anyone gone as far as implementing UC Advanced in Citrix? If yes, what have been your experiences with it in this environment?

 

[mitelmmaniac]

I have attended a site with Citrix. It wasnt one of my customers so i have never been back. They used UC Advanced with it and it worked fine.

sorry there isn't much more info just thought i would tell you it was working.

Desk Jockey Lunacy

 

[mitelmitel]

I have a customer with 2 x 3300's, Enterprise Manager, Ops Manager, Teleworker, UC - All based on a Citrix network.

It has worked flawlessly.

If you download the Engineering Guidelines for all Mitel solutions then you will find that Citrix is supported.

 

[PrinceEvans]

Thanks for the replies.

I have been informed by a reseller that:

"Call recording is not possible as this is only supported on the softphone and softphones are not supported in a Citrix environment.

The other features are supported providing that the information (Outlook contacts, calendar, and any other information that is referenced) is held on the Citrix server and not the local PC."

Call recording not working was a bit of a surprise to me as I did not think you needed a softphone to do it.

 

[james1982]

hmmmmm regarding record a call im not so sure????
You can record a call on standrd IP Phones / dont believe you need softphones:--

Record-A-Call
Description:
Record-A-Call allows extension users to record a two-party call when one party is connected to a trunk. The recorded conversation is stored in the users' voice mail mailbox. You have the option of using the ports that store voice mail messages for Record-A-Call, or you can set up ports exclusively for recorded messages.

Conditions and Feature Interactions
Record-A-Call should only be used in conjunction with the laws of the jurisdiction where the call is placed from and/or the laws of the jurisdiction of the place being called. Mitel is not liable for misuse of this feature in a manner that does not conform with the applicable law. for example: laws involving wiretapping, eavesdropping, electronic surveillance, call recording etc. Dealers should warn the customer in writing that they are responsible for the use of this feature in accordance with the law, and that in many jurisdictions both parties must be made aware that the call is being recorded.

Record-A-Call requires the Advanced Voice Mail purchasable option.

Record-A-Call is only available on some phones; see Feature Availability below for more information. It is not supported on the 5550 IP Console.

Record-A-Call is supported for the 5230 IP Phone and the OpenPhone 27 in Auto-record mode only (see Programming Note).

Record-A-Call functionality has the following constraints:

Record-A-Call can only be used in two-party calls when one party in the call is a trunk.

Record-A-Call can interoperate with Auto-record or user invoked recording.

The 5230 IP Phone and the OpenPhone 27 handset can only use the Auto-record mode.

On a SUPERSET 4015 set, you can use Auto-record mode, or you can press a pre-programmed Feature Access Key to start recording. In both cases (Auto Record or pre-programmed Feature Access Key) you MUST set COS Option "Save Recording on Hang-up" to YES. On a SUPERSET 4015 set, you cannot save recordings by pressing softkeys. To use Auto Record, set COS Option "Start Recording Automatically" to YES in the Class of Service of the set. To program a "Record-A-Call" Feature Access Key, see Feature Keys.

Record-A-Call prompts are only displayed on supported devices when the device is connected to a trunk.

Record-A-Call Feature Access Keys are only functional when the device is connected to a trunk.

An IP networking trunk party is permissible.

Phones are Record-A-Call-enabled using COS option programming.

The features Intrude, Group Page, Directed Page, Silent Monitor are rejected by devices in Record-A-Call conference.

Use of Record-A-Call preempts any existing Silent Monitor.

The "COV/ONS/E&M Voice Mail Port" feature must not be enabled in the Class of Service of the incoming trunk. If the "COV/ONS/E&M Voice Mail Port" feature is enabled for the trunk of the incoming call, the Record Call feature key will not function.

A 3300 ICP supports a maximum of:

12 concurrent Record-A-Call sessions on systems with a 300 or 450 MHz processor controller.

6 concurrent Record-A-Call sessions on systems with a 133 MHz processor controller. Note that 12 concurrent sessions can be programmed and used on systems with a 133 MHz processor, but the system may experience performance problems if more than six concurrent sessions are permitted, and the system is running at the standard business traffic levels (6 ccs per user).

Each Record-A-Call session uses one three-party conference resource, and one voice mail port.

Tones are not given to any party to indicate that the call is being recorded.

A voice mailbox must be programmed against the extension's prime directory number.

The voice mailbox and set must be on the same network node.

Unlike regular voice mail sessions, Record-A-Call sessions do not time out after five minutes. However, 60 seconds of silence in the conversation will cause automatic termination of the Record-A-Call session.

Record-A-Call recordings DO NOT activate the Message Waiting Indicator. When the user accesses the mailbox, the Voice Mail prompts, "You have 'N' new message, 'N' saved messages and 'N' recorded conversations." The recorded conversations is stored in order of arrival and interspersed with any new/saved messages.

If the system goes out of service while a message is being recorded (that is, before the user saves the message), the message will not be available after the system is rebooted.

The message "Recorder Unavailable" appears under the following conditions:

a Record-A-Call session has already been initiated by one of the participants

a caller attempts a session during a conference call

no voice mail ports are available

If the Start Recording Automatically COS option is set to YES and you wish to save the recording, you must set Save Recording on Hang-up COS option to YES, or you must manually press the save button before you hang up.

Inbound trunk calls to an extension in auto-record mode cannot be placed on Hold, parked, or transferred by the extension user.

During the recording, if you place the call on hold, the recording stops. The recording is not continued when you retrieve the call from hold. If you wish to continue recording, you must manually re-start the recording; in this case, you will have two recordings for this call.

An extension in Auto-record mode that is placed on hold does not receive Music on Hold as would be expected when the holding party is on another cluster element.

Parking a call ends any Record-A-Call session in progress at the set. The recording automatically restarts when the call is retrieved if the retrieving party has the "Record-A-Call—Start Recording Automatically" option enabled in their COS. The same applies to parked calls when they recall or are forwarded after a timeout: if the recalled party or forwarding destination has the option enabled, recording automatically restarts when the call is answered.

During the recording, if the person you called places you on hold or park, the recording still continues.

During the recording, if either you or the person you called, pressed the Trans/Conf button, the recording stops.

Recording will only start automatically on an inbound trunk call, providing that the required Class of Service options have been enabled. For outbound calls recording must be manually started.

If you have Record-A-Call enabled, the Record-A-Call prompt takes precedence over the Add Held prompt. To use the Add Held feature, you must disable the Record-A-Call feature.

Campon is supported, but without indications and softkey prompts (call waiting display, trade softkey, campon tone) for parties that are involved in a Record-A-Call conference. Camped on calls mature when the call completes (or when another member of a busy multicall/key group including a prime currently in Record-A-Call conference goes idle).

The Intrude, Group Page, Directed Page, and Silent Monitor features are not supported while a device is in a Record-A-Call conference.

During a Record-A-Call conference, the Trade soft key is not available. If the user stops the recording by pressing Stop&Save or Stop&Erase softkeys, then the Trade prompt is displayed automatically.