Answer Tab

Usage: Click the Help button at any time to get online help for the settings in the current tab.

This opens a World Wide Browser, such as Netscape Navigator or Internet Explorer, and displays information about the settings.

To close the help display, close the browser as you would any other program. For example, in Windows 95, click the X button at the upper right of the window or choose Exit from the File menu.

With some browsers, a new window will open each time you click the Help button. If this happens, simply close each window when you're done with it.

Finding setting descriptions: At the beginning of each help window is a table of contents for the window. To go information about a particular setting, click the hyperlink (the underlined text in most browsers) for that setting in the contents. To return to the contents, use the control in your browser for going back, such as the Back button in Netscape Navigator or Internet Explorer 3.0.

Usage: Click this button to send the settings shown in the Java-Based Pipeline Configurator to the Pipeline.

These new settings replace the previous settings in the Pipeline. You can use this button at any time; you do not have to enter values for all settings before updating the Pipeline.

Usage: Click this to save the settings shown in the Java-Based Pipeline Configurator in a file on your computer.

You then use your operating system's facility for specifying a name and location for the file, such as the Save To dialog box in Windows 95.

You can later open a file in which you've saved settings by clicking the Open a Configuration File button in the first window that appears when you run the Java-Based Pipeline Configurator.

You can use this button at any time; you do not have to enter values for all settings before saving settings.

Usage: Choose one of the following:

• General
  This displays general settings for controlling incoming data calls. These settings are described in the General settings section.

• Bridging/Routing
  This displays settings that control whether routing or bridging is used for incoming data calls. These settings are described in the Bridging/Routing settings section.

• Bandwidth
  This displays settings that control how the data-carrying capacity of the ISDN line is used for incoming data calls. These settings are described in the Bandwidth settings section.

Usage: If the checkbox is checked, the Pipeline rejects incoming calls for which it can find no Connection Profile and no entry on a remote authentication server. If the checkbox is not checked, the Pipeline does not require a Connection Profile or a remote authentication entry. By default, the checkbox is not checked.

If Require Connection Profile is checked, one of the following must be true for each incoming data call for the connection to be made:

• The source IP address of the caller matches the IP Address setting in a local Connection Profile.

  In this case, the Encapsulation setting is MPP or PPP.

• The source name of the caller matches the Station setting in a local Connection Profile.

  In this case, the Encapsulation setting is PPP or MPP, and the Authentication setting is PAP or CHAP.

• The source MAC address of the caller matches the Station setting in a local Connection Profile.

Usage: Check the box to allow multiple incoming calls to share a Connection Profile.

Dependencies: The Pipeline must first authenticate each caller using the caller's name and password. If an incoming call has an IP address that conflicts with the IP address of another caller, the Pipeline rejects the call.

Usage: Choose one of the following:

• None
  This setting specifies that the Pipeline does not use an authentication protocol to validate incoming calls.

  None is the default.

• PAP (Password Authentication Protocol)
  This is a PPP authentication protocol.

  PAP provides a simple method for a host to establish its identity in a two-way handshake. Authentication takes place only upon initial link establishment, and does not use encryption.

  If you choose PAP, the Pipeline uses this protocol for authentication. The remote device must support PAP.

• CHAP (Challenge Handshake Authentication Protocol)
  This is a PPP authentication protocol.

  CHAP is more secure than PAP. CHAP provides a way to periodically verify the identity of a host using a three-way handshake and encryption. Authentication takes place upon initial link establishment; the Pipeline can repeat the authentication process any time after the connection is made.

  If you choose CHAP, the Pipeline uses this protocol for authentication. The remote device must support CHAP.

• Either
  This setting specifies that the Pipeline can use either PAP or CHAP.

  When you select Either, the Pipeline first requests authentication using CHAP, the more secure protocol. If the dial-in call rejects the request (or doesn't acknowledge it), the Pipeline then requests PAP authentication. If the dial-in call rejects the PAP request, the Pipeline terminates the link and drops the call.

• The link must use PPP or MPP encapsulation (Encapsulation setting is PPP or MPP).

• If you choose PAP or CHAP, you must also specify a password using Password in a Connection Profile, or Auth Host on an authentication server.

• When the Authentication setting is PAP, CHAP, or Either, the Pipeline can determine the IP address of a caller, even if the caller does not specify an address; the Pipeline derives the IP address from the Connection Profile.

Usage:

• If this box is checked, the Pipeline does not shut down cleanly, but simply hangs up a PPP connection on a RADIUS timeout.

• If this box is not checked, the Pipeline shuts down a call gracefully on a RADIUS timeout.

Usage: Enter a number between 0 and 65535. If you specify 0 (zero), Pipeline does not enforce a limit; an idle connection stays open indefinitely.

The default setting is 120 seconds.

Dependencies: Keep this additional information in mind:

• In a Connection Profile, Idle Timeout does not apply to nailed-up links; that is, the Idle Timeout setting is dimmed when the Call Type setting is Nailed.

• If MP+ encapsulation is in use and the bandwidth utilization on both sides of the connection drops below the value entered in the Idle % field, the Pipeline clears the call, regardless of the value you enter for the Idle Timeout setting.

• Idle Timeout in the Answer tab applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its Idle Timeout setting takes precedence.

• If the Require Connection Profile setting is checked in the Answer tab, Idle Timeout does not apply (Idle Timeout setting is dimmed) in the Answer tab.

• Because the Idle % is setting is dependent on traffic levels on both sides of the connection, we recommend that you use the Idle Timeout setting in preference to it.

Usage: Choose one of the following:

• None
  This setting turns off data compression.

• Stac
  This setting turns on data compression.

  The Pipeline applies the STACKER LZS compression/decompression algorithm. STAC is the default.

• Microsoft-Stac
  This setting turns on Microsoft LZS Coherency Compression for Windows95, a proprietary compression scheme for Windows 95 only (not for Windows NT).

  Both sides of the link must set the Compression setting to Stac or MS-Stac to turn on data compression.

• Stacker LZS Compression (as defined in the Internet Draft of November 1995) and Microsoft LZS Coherency Compression for Windows 95 both use the same PPP option to indicate that their compression scheme is in use.

  Therefore, a router can have difficulty determining exactly which compression method a caller is requesting. Ascend units handle this ambiguity in the call by always using the compression scheme specified in the Connection Profile; if there is no Connection Profile, the Ascend unit uses the compression scheme specified in the Answer tab.

  If the caller requests MS-Stac and the profile does not specify MS-Stac compression, the connection seems to come up correctly, but no data is routed. If the profile is configured with MS-Stac and the caller does not acknowledge that compression scheme, the Pipeline attempts to use standard Stac compression. If it cannot use standard Stac compression, it uses no compression at all.

• Both sides of the link must set the Compression setting to Stac or MS-Stac to turn on data compression.

• The Compression setting applies only if the link uses PPP encapsulation (Encapsulation setting is PPP or MPP). When the Encapsulation setting is MPP, both the dialing side and the answering side of the link must support MP+. If only one side supports MP+, the connection uses MP or standard single-channel PPP. When the Encapsulation setting is PPP, the connection uses only PPP.

• Compression in the Answer tab applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its Compression setting takes precedence.

• If the Require Connection Profile setting is checked, Compression does not apply (Compression setting is dimmed) in the Answer tab.

Usage: The default setting is 1524; you should accept this default unless the device at the remote end of the link cannot support it.

If the administrator of the remote network specifies that you must change this value, enter a number between 1 and 1524.

Dependencies: Keep this additional information in mind:

• The Max PPP Packet Size setting applies to any link using PPP encapsulation (Encapsulation setting is MPP or PPP).

  When the Encapsulation setting is MPP, both the dialing side and the answering side of the link must support MP+. If only one side supports MP+, the connection uses MP or standard single-channel PPP. When the Encapsulation setting is PPP, the connection uses only PPP.

• Max PPP Packet Size in the Answer tab applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its Max PPP Packet setting takes precedence.

• If the Require Connection Profile setting is checked in the Answer tab, Max PPP Packet Size does not apply (Max PPP Packet setting is dimmed) in the Answer tab.

Usage: Click the Data Filter button. In the window that appears, select a data filter and then click OK.

If you choose None, the Pipeline forwards all data packets. None is the default.

Dependencies: Keep this additional information in mind:

• The Pipeline applies a Call Placement Filter after applying a data filter; only those packets that the data filter forwards can reach the Call Placement Filter.

• If IPX client bridging is in use (Discard RIP, SAP setting is Client), set Data Filter to None.

• Do not confuse this Data Filter setting with the Data Filter setting in the Connections tab.

  This Data Filter setting filters data packets on the Pipeline unit's local LAN interface; the Data Filter setting in the Connections tab filters data packets on the Pipeline unit's WAN interface. The WAN interface is the port on the Pipeline that is connected to a WAN line.

• This Data Filter setting applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its Data Filter setting takes precedence.

• If the Require Connection Profile setting is checked in the Answer tab, Data Filter does not apply (Data Filter setting is dimmed) in the Answer tab.

LQM is a feature that enables the Pipeline to monitor the quality of a link. LQM counts the number of packets sent across the link and periodically asks the remote end how many packets it has received. Discrepancies are evidence of packet loss and indicate link quality problems.

LQM causes the generation of periodic link quality reports. Both ends of the link exchange these reports.

Usage:

• If the checkbox is checked, the Pipeline requests LQM.

• If the checkbox is not checked, the Pipeline does not request LQM.

  This is the default.

• Both sides of the link negotiate the interval between periodic link quality reports; however, the interval must fall between the minimum interval (as set by Minimum LQM) and the maximum interval (as set by Maximum LQM).

• If LQM is turned off (Request Link Monitoring (LQM) is not checked), the Maximum LQM and Minimum LQM settings do not apply (Maximum LQM setting is dimmed and Minimum LQM setting is dimmed).

• LQM applies only if the Encapsulation setting is PPP.

• Request Link Monitoring (LQM) in the Answer tab applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its Request Link Monitoring (LQM) setting takes precedence.

• If the Require Connection Profile setting is checked in the Answer tab, LQM does not apply (Request Link Monitoring (LQM) setting is dimmed) in the Answer tab.

Usage: Enter a number between 0 and 600. The default is 600.

Dependencies: Keep this additional information in mind:

• If the Request Link Monitoring (LQM) setting is not checked, the Minimum LQM setting does not apply (Minimum LQM setting is dimmed).

• Minimum LQM in the Answer tab applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its Minimum LQM setting takes precedence.

• If the Require Connection Profile setting is checked in the Answer tab, Minimum LQM does not apply (Minimum LQM setting is dimmed) in the Answer tab.

Usage: Enter a number between 0 and 600. The default is 600.

Dependencies: Keep this additional information in mind:

• If the Request Link Monitoring (LQM) setting is not checked, the Maximum LQM setting does not apply (Maximum LQM setting is dimmed).

• Maximum LQM in the Answer tab applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its Maximum LQM setting takes precedence.

• If the Require Connection Profile setting is checked in the Answer tab, Maximum LQM does not apply (Maximum LQM setting is dimmed) in the Answer tab.

Usage: Check the box to enable bridging.

This is unchecked by default.

Dependencies: The effect of the Enable Bridging setting depends upon how you set the Enable IP Routing and Enable IPX Routing settings.

Enable Bridging and Enable IP Routing

• If both the Enable Bridging setting and Enable IP Routing settings are checked, the Pipeline routes IP packets and bridges all other packets.

• If the Enable Bridging setting is checked and Enable IP Routing setting is not checked, the Pipeline bridges all packets.

• If the Enable Bridging setting is not checked and the Enable IP Routing setting is checked, the Pipeline routes only IP packets.

• If the Enable Bridging setting is not checked and the Enable IP Routing setting is not checked, an error occurs and you cannot save the profile.

  You must enable bridging or routing, or both.

• If both the Enable Bridging and Enable IPX Routing setting are checked, the Pipeline routes IPX packets and bridges all other packets.

• If the Enable Bridging setting is checked and the Enable IPX Routing setting is not checked, the Pipeline bridges all packets.

• If the Enable Bridging setting is not checked and the Enable IPX Routing setting is checked, the Pipeline routes only IPX packets.

• If the Enable Bridging setting is not checked and the Enable IPX Routing setting is not checked, an error occurs and you cannot save the profile.

  You must enable bridging or routing, or both.

• Bridging must be enabled on both the dialing and answering sides of the link.

  The Enable Bridging setting must be checked in both the Connection Profile on the dialing side and the Answer tab on the answering side. Otherwise, the Pipeline does not bridge the packets.

• Enable Bridging in the Answer tab applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its Enable Bridging setting takes precedence.

• Do not confuse the Enable Bridging setting with the Bridging setting.
  • The Enable Bridging setting in the Answer tab applies only to connections that the Pipeline answers.

  • The Enable Bridging setting in the Connection Profile applies only to a specific connection.

  • The Bridging setting globally enables or disables bridging.

Usage: If checked, the Pipeline requests IPX routing.

By default, this is not checked.

Dependencies: Keep this additional information in mind:

• If the link supports PPP or MP+ (Encapsulation setting is PPP or MPP), both sides of the connection must check the Enable IPX Routing setting for IPX routing to take place.

• In addition, the effect of the Enable IPX Routing setting depends upon how you set the Enable Bridging setting:
  • If both the Enable Bridging and Enable IPX Routing settings are checked, the Pipeline routes IPX packets and bridges all other packets.

  • If the Enable Bridging setting is checked and the Enable IPX Routing setting is not checked, the Pipeline bridges all packets.

  • If the Enable Bridging setting is not checked and the Enable IPX Routing setting is checked, the Pipeline routes only IPX packets.

  • If the Enable Bridging setting is not checked and the Enable IPX Routing setting is not checked, an error occurs and you cannot save the profile.

    You must enable bridging or routing, or both.

• IPX SAP Input filters
  These filters apply to all SAP packets that the Ascend unit receives.

  Input filters screen advertised services and exclude them from its service table as specified in the filters.

• IPX SAP Output filters
  These filters apply to SAP response packets that the Ascend unit transmits.

  If the Ascend unit receives a SAP request packet, it applies Output filters before transmitting the SAP response, and excludes services from the response packet as specified in the filters.

If you select None, all SAP data is included in the service table. None is the default.

Use this feature when you place calls to European or Pacific Rim countries and the complete path cannot distinguish between the Switched-56 and Switched-64 data services. This feature is not required if you are placing calls only within North America.

Usage: Check the box to use only the 56-Kbps portion of a channel.

If the box is not checked, the Pipeline can use 64 Kbps, if available. By default, it is not checked.

The Pipeline uses the historical time period specified by the Sample Time setting as the basis for calculating ALU. It then compares ALU to the amount specified in the Target % setting. When ALU exceeds the threshold defined by Target % for a period of time greater than the value of the Add Time setting, the Pipeline attempts to add a channel. When ALU falls below the threshold defined by Target % for a period of time greater than the value of the Sub Time setting, the Pipeline attempts to remove the a channel.

MP+ supports Dynamic Bandwidth Allocation.

Usage: Choose one of the following:

• Constant
  This setting gives equal weight to all samples taken during the historical time period specified by the Sample Time setting.

  When you select this option, older historical samples have as much impact on the decision to change bandwidth allocation as do more recent samples.

• Linear
  This setting gives more weight to recent samples of bandwidth usage than to older samples taken during the historical period specified by the Sample Time setting; the weighting grows at a linear rate.

• Quadratic
  This setting gives more weight to recent samples of bandwidth usage than to older samples taken during the historical period specified by the Sample Time setting; the weighting grows at a quadratic rate.

  Quadratic is the default for MP+ calls (Encapsulation setting is MPP).

Dependencies: Keep this additional information in mind:

• To dynamically allocate bandwidth by tracking line usage, you must specify the DBA Algorithm, Sample Time, Min Channels, Max Channels, Add Time, Sub Time, Target %, and Idle % settings.

• DBA Algorithm in the Answer tab applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its DBA Algorithm setting takes precedence.

• If the Require Connection Profile setting is checked in the Answer tab, DBA Algorithm does not apply (DBA Algorithm setting is dimmed) in the Answer tab.

When ALU exceeds the Target % threshold for a period of time greater than the value of the Add Time setting, the Pipeline attempts to add a channel.When ALU falls below the Target % threshold for a period of time greater than the value of the Sub Time setting, the Pipeline attempts to remove a channel.

The number of seconds you choose for the Sample Time setting depends on your device's traffic patterns. For example, if you want to average spikes with normal traffic flow, you may want the Pipeline to establish a longer historical time period. If, on the other hand, traffic patterns consist of many spikes that are short in duration, you may want to specify a shorter period of time; doing so assigns less weight to the short spikes.

Usage: Enter a number between 1 and 300. The default value is 15 seconds.

Dependencies: Keep this additional information in mind:

• The Sample Time setting applies only to dynamic MP+ calls (Encapsulation setting is MPP).

• If you specify a small value for the Sample Time setting, and increase the values of the Add Time setting and the Sub Time setting relative to the value of Sample Time, the system becomes less responsive to quick spikes.

• The easiest way to determine the proper values for Sample Time, Add Time, and Sub Time is to observe usage patterns; if the system is not responsive enough, the value of Sample Time is too high.

Usage: Enter a number between 1 and the maximum number of channels your Pipeline supports. The default setting is 1.

Dependencies: This setting applies only to MP+ calls (Encapsulation setting is MPP). For optimum MP+ performance, both sides of a connection must set these settings to the same values:

• Base Channels (in the Connection Profile)

• Min Channels (in the Answer Tab and the Connection Profile)

• Max Channels (in the Answer Tab and the Connection Profile)

Usage: Enter a number between 1 and the maximum number of channels your Pipeline supports.

Dependencies: Keep this additional information in mind:

• The Max Channels setting applies only to dynamic MP+ calls (Encapsulation setting is MPP).

• If the Require Connection Profile setting is checked in the Answer tab, Max Channels does not apply (Max Channels setting is dimmed) in the Answer tab.

• For optimum MP+ performance, both sides of a connection must set these settings to the same values:
  • Base Channels (in the Connection Profile)

  • Min Channels (in the Answer tab and the Call Profile)

  • Max Channels (in the Answer tab and the Connection Profile)

• Max Channels in the Answer tab applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its Max Channels setting takes precedence.

When utilization exceeds the threshold for a period of time greater than the value of the Add Time setting, the Pipeline attempts to add a channel. Using the Add Time and Sub Time settings prevents the system from continually adding and subtracting bandwidth, and can slow down the process of allocating or removing bandwidth.

Usage: Enter a number between 1 and 300.

When the Pipeline is using MP+ (Encapsulation setting is MPP), the default value is 5.

Dependencies: Keep this additional information in mind:

• Additional channels must be available, and the number of channels added cannot exceed the amount specified by the Max Channels setting.

• Add Time in the Answer tab applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its Add Time setting takes precedence.

• If the Require Connection Profile setting is checked in the Answer tab, Add Time does not apply (Add Time setting is dimmed) in the Answer tab.

• Add Time and Sub Time have little or no effect on a system with a high Sample Time value.

  If the value of Sample Time is low, the Add Time and Sub Time settings provide an alternative way to ensure that spikes must persist for a certain period of time before the system responds.

When utilization falls below the threshold for a period of time greater than the value of the Sub Time setting, the Pipeline attempts to remove a channel. Using the Add Time and Sub Time settings prevents the system from continually adding and subtracting bandwidth, and can slow down the process of allocating or removing bandwidth.

Usage: Enter a number between 1 and 300.

When the Pipeline is using MP+ (Encapsulation setting is MPP), the default value is 10.

Dependencies: Keep this additional information in mind:

• One channel must be up at all times.

• Removing bandwidth cannot (a) cause the ALU to exceed the threshold specified by the Target % setting or (b) cause the number of channels to fall below the amount specified by the Minimum Channels setting.

• Sub Time in the Answer tab applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its Sub Time setting takes precedence.

• If the Require Connection Profile setting is checked in the Answer tab, Sub Time does not apply (Sub Time setting is dimmed) in the Answer tab.

• Add Time and Sub Time have little or no effect on a system with a high Sample Time value.

  However, if the value of Sample Time is low, the Add Time and Sub Time settings provide an alternative way to ensure that spikes persist for a certain period of time before the system responds.

Usage: Enter a number between 0 and 65535. If you specify 0 (zero), Pipeline does not enforce a limit; an idle connection stays open indefinitely.

Dependencies: Keep this additional information in mind:

• If MP+ encapsulation is in use and the bandwidth utilization on both sides of the connection drops below the value entered in the Idle Pct field, the Pipeline clears the call, regardless of the value you enter for the Idle setting.

• Idle in the Answer Profile applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the Idle setting takes precedence.

This setting specifies the target percentage of bandwidth utilization for an MP+ call (Encapsulation setting is MPP).

The Pipeline uses the historical time period specified by the Sample Time setting as the basis for calculating average line utilization (ALU) of transmitted data. It then compares ALU to the amount specified in the Target % setting.

When ALU exceeds the threshold defined by Target % for a period of time greater than the value of the Add Time setting, the Pipeline attempts to add a channel. When ALU falls below the threshold defined by Target % for a period of time greater than the value of the Sub Time setting, the Pipeline attempts to remove a channel.

Usage: Enter a number between 0 and 100.

The default is 70. When the value is 70%, the device adds bandwidth when it exceeds a 70 percent utilization rate, and subtracts bandwidth when it falls below that number.

Dependencies: When selecting a target utilization value, keep these guidelines in mind:

• Monitor how the application behaves when using different bandwidths.

  For example, an application might be able to use 88% of a 64-Kbps link, but only 70% of a 256-Kbps link.

• Monitor the application at different loads.

Usage: Enter a number between 0 and 99. The default value is 0; this setting causes the Pipeline to ignore bandwidth utilization when determining whether to clear a call.

Dependencies: Keep this additional information in mind:

• MP+ must be the selected encapsulation method (Encapsulation setting is MPP) in a Connection Profile.

• If the device at the remote end of the link enters an Idle % setting lower than the value you specify, the Pipeline does not clear the call until bandwidth utilization falls below the lower percentage.

• If either end of a connection sets the Idle % setting to 0 (zero), the Pipeline ignores bandwidth utilization when determining when to clear a call.

• If the time set by the Idle Timeout setting expires, the call disconnects whether or not bandwidth utilization falls below the Idle % setting.

• When bandwidth utilization falls below the Idle % setting, the call disconnects regardless of whether the time specified by the Idle Timeout setting has expired.

• Because the Idle % setting is dependent on traffic levels on both sides of the connection, we recommend that you use the Idle Timeout setting in preference to it.

• Idle % in the Answer tab applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its Idle % setting takes precedence.

• If the Require Connection Profile setting is checked in the Answer tab, Idle % does not apply (Idle Timeout setting is dimmed) in the Answer tab.

By default, any packet destined for the WAN causes the Pipeline to place a call. In addition, by default, every packet resets the idle timer, the indicator that the Pipeline uses to know when to clear a call. When you set up a Call Placement Filter, only those packets that the Call Placement Filter forwards can initiate a call or reset the Preempt or Idle Timeout settings.

Usage: Click the Call Placement Filter button. In the window that appears, select a filter or None and then click OK.

If you select None, the Pipeline forwards all packets. None is the default.

Dependencies: Keep this additional information in mind:

• If all channels of a link are nailed up (Call Type setting is Nailed in the Connection Profile), the Call Placement Filter setting does not apply (Call Placement Filter setting is dimmed) in both the Answer tab and Connection Profiles.

• The Pipeline applies a Call Placement Filter after applying a data filter; only those packets that the data filter forwards can reach the Call Placement Filter.

• If IPX client bridging is in use (Discard RIP, SAP setting is Client), set Call Placement Filter to None.

• Call Placement Filter in the Answer tab applies to incoming calls for which no Connection Profile exists; if a Connection Profile exists, the setting of its Call Placement Filter setting takes precedence.

• If the Require Connection Profile setting is checked in the Answer tab, Call Placement Filter does not apply (Call Placement Filter setting is dimmed) in the Answer tab.