Limitations and known issues

•If the phone’s user enters an unknown slot, TPO drops the call

•There is no notification (bip or vocal message) announcing that the PBX Phone has properly reached the slot and is now in conference

•If the phone’s user does not finish the DTMF sequence by enter ‘#’ in default timeout 30 s, TPO drops the call. This parameter can be changed by setting the key application.TPO.accesspoint.nofinishtimeout in TPO settings

Location: TPO Shared Settings, TPO Private Settings, TPO Boot Settings
Global	PBX Phone access point - no finish timeout Key: application.tpo.accesspoint.nofinishtimeout Description: Define the timeout for the receive of the DTMF end sequence "#", TPO closes the call on the PBX phone access line

•If the phone’s user does not enter any DTMF in the default timeout 5 min, TPO drops the call. This parameter can be changed by setting the key application.TPO.accesspoint.nodtmftimeout in TPO settings

Location: TPO Shared Settings, TPO Private Settings, TPO Boot Settings
Global	PBX Phone access point - no dtmf timeout Key: application.tpo.accesspoint.nodtmftimeout Description: Define the timeout for PBX Phone Access Point; After the timeout, TPO closes the call on the PBX phone access line.

•Hot Backup only saves phone “Joined” calls.

Example:

TLAB01 has an established call with Remote party RP on slot 101. Slot 101 is in public talking; TLAB01 and RP can hear and speak each other.

A phone user 1120 calls the PBX phone access line 5042; if a failure happens at this moment, Hot Backup will not save this call.

After the call to 5042, user enters DTMF “101#” to joins the slot 101. If a failure happens at this moment, Hot Backup will save this call.

•DDI Slot Bridging has some limitations related to this feature.