This read-write field indicates whether this node is responsible for actively initiating the backup-trunk call setup for this primary trunk, true, versus passively waiting to receive an incoming backup call from the other end. An admin sets this correctly on exactly one side of a backup relationship, since having both ends configured to initiate, or neither, would break the intended call-setup flow for a switched backup path. For example, on a backup trunk that uses a dial or switched connection, one node's lportInitCallSetup would be set to true(1) so it is the one that places the call, while the far-end node is configured to wait for that incoming call rather than also trying to initiate.