Execution of Follow Me

All incoming new calls to the diverted/controlling position are diverted to the divertee position. A call origin message is sent to the calling party.

For network calls to a party with the divertee in the same PBX as the diverted party the call is treated as above, and the identity of the divertee is returned to the originating party, to be displayed.

In the case where the divertee position is in another PBX than the diverted party, the diversion case and the identity of the divertee are sent back to the originating PBX.

When set up from the originating PBX the original connection is released and the diverted call is set up. As above the originating party is informed of the divertee’s identity. In the terminating (first called) PBX a time supervision (10s) is started to supervise the release message from the originating PBX. On expiry of the timer the connection will be released from terminating PBX.

If the originating PBX doesn’t support the network diversion feature (e.g. ISDN in a PBX not supporting network diversion), no diversion information is sent back to the originating PBX and if the divertee position is in another PBX, a new call is set up from the first PBX, seen from the originating PBX, supporting network diversion.

If follow me cannot be executed due to internal barring, nominated position is vacantor class of service barred, a NO PROGRESS message is sent.

If the divertee position is a generic extension and follow me has been successfully executed, if the terminal becomes ’not available’ while ringing, the calling party receives ‘NOT AVAILABLE’. The actual message is dependent on the originator type.

For more information on where the diverted call is routed with respect to the different states of the divertee position, Internal Diversion followed by internal Diversion.