The AutoCallType subcommand is used to select a method for establishing autocalls between selected voice channels. Specifically, it allows the user to choose between the normal (standard) method, and Hoot-and-Holler.
When this option is selected, going off-hook causes the local Voice Application (VA) to initiate a search for the device network address (DNA) of the destination voice channel. Once resolved, the local (calling) VA establishes a network connection with the destination (called) VA. Finally, the two voice channels use the network connection to establish a voice connection. The connection is terminated when the user at either end hangs up the phone. While a connection is in place, both channels are in a busy state to any other network station. Once the connection is terminated, and provided there are no other restrictions (e.g., outgoing calls only), either side is free to receive calls from another channel. Note that network connection, as used in this context, applies to a connection established either over a frame relay link or between channels located within the same physical unit.
This feature refers to a permanent SVC connection between two voice channels designated as master and slave, respectively. It is the responsibility of the master to establish and maintain the network connection. It does so upon power up, following a reset, or through link failures.
By definition, the master is a voice channel whose switching profile autocallType is configured for masterHootHoller. Its autoCallIndexNum is an index number pointing to an extension number in the ingress table. That extension number is an egress table phone number entry in its designated slave channel.
The slave is a voice channel whose switching profile autocallType is configured for slaveHootHoller. Its autoCallIndexNum is an index number pointing to an extension number in the ingress table. That extension number is an egress table phone number entry in its designated master channel. It can accept calls from its designated master channel, but cannot initiate calls.
At start-up, master and slave behave differently; the master attempts to establish a network connection. Once a network connection has been made, master and slave behave the same way. While so designated, neither can accept calls from another network channel.
Like other Passport 4400 voice circuits, Hoot-and-Holler incorporates bandwidth-on-demand, a feature designed to optimize bandwidth utilization. Even though the connection is semi permanent, bandwidth is used only when there is voice traffic present, and then only in the direction of the voice traffic. To enable this bandwidth saving feature, the bandwidth parameter of the voice profile must be set to voiceActivated.
|
Note: In networks containing Release 3.x and Release 4.x software, the Release 4.x software should be set to Master, not Slave. |
To set the AutoCallType, enter:
CLI> set voice switchingProfile autoCallType
  |
|