Limitations

Static Link feature limitations

Here comes limitation directly related to the static link feature itself

Dynamic Ringdown Place only

The static link feature is limited to RingdownDynamic DDI places that only have DDI slots with attached properties. No link can be made to another place type, or to a RingdownDynamic place that has one or several slots with no property.

No multi-layer indirection

The static link feature is limited to one level of indirection. In other words, we can have place@TPO2 pointing to place@TPO1 but we CANNOT have place@TPO3 pointing to place@TPO2 which in turn points to place@TPO1. However, we can have several slave places (of different TPO groups) that are linked to the same master place.

The static link feature is not bi-directional. In other words, we CANNOT have place@TPO1 pointing to place@TPO2 and place@TPO2 pointing to place@TPO1 at the same time. Such a configuration wouldn’t make any sense.

Up to 10 slave places pointing the same master place

The system is limited to 10 slave places pointing the same master place. This limitation is theoretical. Even if the system doesn’t avoid operator to create more than 10 slave places, there is no guaranty system remain stable in such configuration. IP Trade would not provide support if this limitation isn’t respected.

Up to 200 R-links for a single TPO

The system is limited to 200 R-Link calls in total for a single TPO. This limitation is theoretical. Even if the system doesn’t avoid operator to create more than 200 R-links, there is no guaranty system remain stable in such configuration. IP Trade would not provide support if this limitation isn’t respected.

Restricted edition capability on Distributed places

•A slave place, once created, cannot be modified (except for few properties). E.g. it cannot be linked to another master place. IT Administrator must delete and re-create it in order to link it to another master place.

•A master place cannot be deleted as long it is referenced by at least one slave place. IT Administrator must delete the slave(s) place(s) before being able to delete the master place.

•A master place type cannot be changed as long it is referenced by at least one slave place. IT Administrator must delete the slave(s) place(s) before being able to change the master place type.

•A master place cannot be modified as long as all referencing slave places have not been stopped. IT Administrator must stop the slave(s) place(s) before being able to edit the master place properties.

•A slave place cannot be started while its master counterpart is not.

•A master place cannot be stopped while all its slave counterparts are not stopped.

•It is not possible to provision slave places using Bulk Administration & Provisioning.

Same cluster redundancy mode

The static link feature is only supported between clusters of the same redundancy mode.

Example  : A cluster in "Session Persistency" can connect to an other cluster in "Session Persistency", but it can't connect to a cluster configured in a different redundancy mode (DNS, VIP, failover).

In addition of that, clusters configured for Skype For Business can't connect to non-SFB clusters (Alcatel for example), and non-SFB clusters can't connect to SFB clusters. Even if both clusters are using the DNS redundancy mode.

ARD from Slave place

In case of distributed place usage, ARD would only work from slave places if MRD is set to Yes in TPO place definition. If MRD is set to No, ARD would not be generated when a user gets connected on a slave place.

Outlying features limitations

Here comes static link limitation that impact other outlying features

Unavailable telephony functions

Some telephony functions that might be used on ARD slots are not available with R-Link. Following functions are not available on places that are involved in Static Link:

•Pickup/Group Pickup

•Call forwarding

•Call park

•Do not disturb

•Video call

•Conference **

•Transfer **

** Conference and transfer feature are not available due to lack of dynamic slots. Both those features require an additional free slot that hosts the second call (either transfer target or conference next participant). As those features are commonly used to link standard telephony users with radio and PW remote parties, an alternative might be using PBX Phone access from all locations.

Different instant replay behaviors

Depending on user is connected to a master or a slave place, instant replay provides different results.

•On master places, the behavior is conform the classical instant replay and behaves as on place that are not R-Linked: the replayed sound only contains remote party voice (radio, ARD, MRD, multicast,…)

•On slave places, the behavior is quite different as the replayed sound contains remote party voice as well as voice of all the users connected to the place slot through another TPO

Different FlexGo voice activity notifications behavior

Depending on FlexGo user is connected to a master or a slave place, voice activity notifications are raised differently.

•On master places, the behavior is conform the classical instant replay and behaves as on place that are not R-Linked: notifications are raised when activity is detected in remote party voice streams (radio, ARD, MRD, multicast,…)

•On slave places, the behavior is quite different as notifications are raised when activity is detected in remote party voice streams as well as voice streams of all the users connected to the place slot through another TPO

DDI Line Coverage limitations

The only properties that a user is able to change on his turret are the value of Subscribe To Notifications, RingtoneSetUId and RingtoneVolume. The user is not able to change the forward, DND (and so on) states.

There is no restriction for R-Linked places to be part of User group lines shared profile.

Geographical Conference Mode limitations

This feature is decentralized on each slave place. That implies that turrets connected to different TPOs are always considered as infinitely distant from each other, and thus, always hear to each other.

Consider 4 turrets ABCD configured not to hear each other. If A & B are connected on the master place slot while C & D are connected to the corresponding slave place slot:

•“A” cannot hear “B” but hears “C” & “D”

•“B” cannot hear “A” but hears “C” & “D”

•“C” cannot hear “D” but hears “A” & “B”

•“D” cannot hear “C” but hears “A” & “B”

Recording beep tone behavior

This is not a key feature in static link context. As all slots have properties, the recording beep tone is probably going to be generated by a third party system. IP Trade recommends not to activate recording beep tone on slot having properties when using TPO Static link.

Waiting message indicator

Waiting message indicator doesn't work properly on turret connected to Slave TPO.

Consistent Exclusive / Exclusive conference configuration

Exclusive conference mode must be deactivated or activated on all TPOs. Mixing both modes might lead to inconsistent behaviors.

Potential inconsistent behavior on specific features

Using following features may lead to unexpected and inconsistent behavior:

•Barge on DDI slots

•Mute/Unmute/Eject remote parties

•Slot Bridge

•Trader Call Reinjection