You can use the WebAdmin Interface to configure the Signal component. Open the Real-Time pages in the Settings realm, then open the Signals page:
Log: Use this setting to specify the type of information the Signal component should put in the Server Log. Usually you should use the Failure (unrecoverable problems only), Major (Signal progress reports), or Problems (failures, progress reports, and non-fatal errors) levels. When you experience problems with the Signal component, you may want to set the Log Level setting to Low-Level or All Info: in this case the signal processing internals will be recorded in the System Log. When the problem is solved, set the Log Level setting to its regular value, otherwise your System Log files will grow in size very quickly. The Signal component records in the System Log are marked with the SIGNAL tag.
Processors: The Signal component uses several simultaneous processors (threads) to process Signal "tasks". One processor can handle several Signal tasks. If you use many time-consuming Automated Rules, you should allow the component to use more processors for signal processing.
Object Limit: This setting specifies how many Signal "tasks" the component can handle at any given time. If this limit is exceeded, new Signals are rejected, and an error is returned to the Signal sender.
Event Limit: This setting specifies the critical number of unprocessed events sent to all active Signal "tasks". If this number is exceeded, the component is overloaded (the component Processors cannot handle events as they appear), new Signals are rejected, and an error is returned to the event sender.
Use the Signal Task panel to configure Signal processing by Signal Tasks.
AOR Limit: This setting limits the number of AORs that can be processed for a single operation. It limits the total number of forks, redirects, etc. for a single request.
Active Fork Limit: This setting limits the number of concurrent forks for a single request.
Time Limit: This setting specifies the default time limit for request processing.
Authenticate All outgoing calls: The CommuniGate Pro Server requires user authentication for certain Requests: