Hot Backup Limitations

Top  Previous  Next
Trading and C&C > Turret Proxy To Open communication (TPO) > TPO Clusters > Hot Backup

This chapter discuss limitations and restrictions inherent to TPO Hot Backup.  

 

•The cluster is restricted for 7 nodes.

•TPO cluster is not compatible with Fail-Over and Fail-Over Linesbackup options.

•TPO cluster uses TCP port 9500 for internal communication. This port must be free for TPO usage. You can change it if necessary by setting the key application.cluster.connection.port in TPO configuration on TSS.

•If a TPO node is linked or unlinked in an active cluster, a restart of TPO services of all nodes is required.

 

 

DDI Sharing Places

 

•Forward and DND lines are not restored

•Only established outgoing calls are restored. If the failure of an active node occurs   during an outgoing call is in ringing state, the slot is free on the TPO side but it is only notified on the turrets on the next action on this DDI line.

•Music on hold on Cisco PBX; the failure of an active node happens when the remote party put the call on hold. Then the PBX does not send sometimes the Music on Hold. In this case, there is not input stream on the restored call. Then the RTP timeout terminates the call after the timeout delay (5 min).

•Video streams and video state of the calls are not preserve in case of failure.

oOngoing video may freeze in case of TPO failure

oUser is capable to hide frozen video as easily as hiding normal video

•Ongoing internal DDI calls may not be maintained during the hot backup procedure if both the caller and receiver are using lines that terminate on the same TPO Group ID involved in the hotbackup.

 

BuildInJoin place

•Only established calls are restored.