The following is the process of configuring and reverting TNs on an 1140 endpoint when the ProVision configuration is completed and the data is migrating to the Avaya Aura® system.
-
The endpoint TN is 4 0 0 0. It is currently registered to node 2000 on an existing CS 1000 system.
-
The endpoint is transferred from CS 1000 to Device Adapter. Device Adapter uses node 3500, however there is another endpoint that is already configured on Device Adapter with TN 4 0 0 0.
-
ProVision maps this endpoint to TN 252 0 0 0.
-
The administrator uploads the remapping file generated by the ProVision tool to the Avaya Breeze® platform master node using FTP and runs the adaSetReconfigure enable /home/cust/<provisionmapfile>.txt command.
-
The DHCP server is reconfigured to have S1 as the Avaya Breeze® platform master node instead of the CS 1000 TPS.
-
The endpoint restarts.
-
The endpoint tries to register with the Avaya Breeze® platform node as node 2000 and TN 4 0 0 0, which it has in memory.
-
Device Adapter with the relocation feature enabled recognizes the endpoint in the map and sends it a message to change the node and TN, and then restarts the endpoint.
-
The endpoint registers to Device Adapter with node 3000 and TN 252 0 0 0. Registering is mandatory for the reverting functionality to work correctly.
-
The adaSetReconfigure revert command reads the map and detects that endpoint with TN 252 0 0 0 and node 3000 is registered. Then the endpoint receives a command to change the TN and node back to the original data: node 2000 and TN 4 0 0 0.
-
After the DCHP server is reverted and the S1 of this endpoint is changed back to CS 1000, the endpoint can register back to CS 1000.
