The following needs to be done in the Aura network:
-
The Communication Manager, Session Manager, and any other devices must be deployed and configured to communicate.
-
The desired digit translations must be entered in the System Manager. This downloads the information as applicable to route the calls through the Session Manager and Communication Manager. In addition, the call may route through a media gateway or IP connection to the external environment. This must be set up correctly.
-
The Device Adapter must be deployed and configured.
-
The Device Adapter endpoints must be deployed and configured on the Session Manager and Communication Manager.
No routing decisions are configured in the Device Adapter. Effectively, the Device Adapter converts the endpoints it services into “96x1-like” endpoints registering through the Session Manager to the controlling Communication Manager. Once the endpoints can register with the Session Manager, the endpoints should be able to place calls successfully, provided all the translations and destinations are correctly configured.
However, the Device Adapter has three timer values administered:
-
Dialtone: Determines how long dialtone is to be played without the user entering a digit. On expiry, the call attempt is failed.
-
Interdigit: Determines how long to wait for another digit before attempting the call. On expiry, if the number has no conflicts in the PPM Dial Plan data, the call is attempted. Otherwise the call is rejected.
Note:
As soon as there is a valid match (prefix to the digit string matches one entry, and the total length matches the expected length), the call is attempted.
-
Busy/overflow: Busy tone and call failure tone are played out for a specific maximum duration. If the user does not disconnect before the timer expires, the Device Adapter completes call clearing anyway.
These are included in the Attributes of the Device Adapter in the System Manager.
