An adaptation module can be used only once. An Adaptation can be used many times.
An adaptation module is a container extension. An Adaptation is a database record within the Adaptations collection.
An adaptation module references an Adaptation. An Adaptation does not reference an adaptation module.
An adaptation module is configured by the administration. An Adaptation is pre-built and is loaded as a container extension.
Create a Time Range. Select Saturday and set the start and end time for morning. Select Sunday and set start and end time for afternoon. Add Time Range to Routing Policy
Create a Time Range. Select Saturday and select morning. Select Sunday and select afternoon. Add Time Range to Routing Policy
Create a Time Range. Create a Routing Policy for Saturday Morning. Create a second Routing Policy for Sunday afternoon. Add both Routing Policies to the Time Range.
Create a Time Range. Select Saturday and set start and end time for morning. Create another Time Range. Select Sunday and set start and end time for afternoon. Add both Time Ranges to Routing Policy.
The request is rejected
The request is processed as normal, including NRP routing
The un-known domain is resolved and the request is proxied downstream
Session Manger crashes
It adds a route header to the request, addressed to the feature server
It changes the request URI of the request, and sends it to the feature server
It never addresses a feature server
It changes the to header of the request, and send it to the feature server SM100
Primary Session Manager and Secondary Session Managers are installed using the same installer
Primary Session Managers and Branch Session Managers are installed using the same installer
After installation Session Manager instances are configured to be either Primary Session Managers or Secondary Session Managers
An adaptation module is a pluggable component that is deployed in the Service Host container as a container extension
Adaptation modules are typically designed to cater for the needs of equipment from particular vendors.
Using pluggable adaptations help make Session Manager future proof
Adaptation modules are deployed through the SM 100 configuration pages
PPM stands for Personal Profile Manager policy
PPM is the process through which CM synchronized phone settings with Session Manager
PPM is the repository of phone settings from which SIP stations retrieve their settings when a user logs in
PPM is the process through which behaviors and settings are dynamically downloaded to the phone dependent on the specific user logging in
The 'Redundant devices' check box in the SIP Entity record is checked
The IP address of each redundant device is entered in the SIP entity record
The address of the combined Entity is entered as a FQDN in the SIP Entity record
It is not possible for SIP Entities to be redundant
IP address pattern
It is used to carry a Free-Pass token used to authenticate the caller
It is used to carry a Free-Pass token that signifies this call should not be billed
It tells Avaya's Session Manager which transport protocol is to be used as the request is routed toward the destination
There is no such header. The P-Avaya-Transport header does not exist
They both actively receive network traffic, providing an active / active model of server redundancy
One is for signaling traffic and the other is for management traffic
One belongs to the SM 100 and the other to the server box
The primary adapter receives all network traffic, whilst the secondary is on 'hot stand bye', ready to take over if anything goes wrong with the first
An Entity Link is the network connection between Session Manger and one of its SIP Entities
An Entity Link is the relationship between Session Manager and one of its SIP Entities
An Entity Link is another word for a SIP Trunk or a VPN tunnel
An Entity Link is another word for a SIP Entity
If the number of packets sent over a given period from a source exceeds a defined acceptable limit, then drop all packets from that source
If the number of packets sent over a given period from a source exceeds a defined acceptable limit, then drop some packets from that source
If the number of packets sent over a given period from a source exceeds a defined acceptable limit, then drop any packets from that source that exceed the threshold
If the number of packets sent over a given period from a source exceeds a defined acceptable limit, then add the source address to the Black list
If the White list is activated, no packets are allowed through the firewall unless the source is listed on the white list
If the source is listed on the White List, allow all packets through without further checks, regardless of other conditions
If the source is listed on the White List, block all packets without further checks
If the source is listed on the White List, mark the packet as having priority and send it to the front of the queue for processing
Session Manager combines data from the collections to determine routing of signaling requests
Session Manager queries data from the collections to validate a SIP Entity
Session Manager queries data from the collection to determine how much bandwidth is allocated to a location
Session Manager queries adaptation patterns from a collection to determine how a SIP message should be adapted
A Routing Policy references one or more SIP Entities and one or more Time Ranges
A Routing Policy references one Time Range and one or more Dial Patterns
A Routing Policy references one Dial Pattern and one SIP Entity
A Routing Policy references one SIP Entity and one or more Time Ranges
ASM checks the received Register request for a valid password. Only if it exists is the registration data written to the registry and the User Profile updated.
After checking that a User Profile exists, ASM returns an error response to the initial Register request, prompting the user for log on credentials. Only when received and validated against details in the User Profile is the user authenticated.
Users ensure that all requred log on credentials are included in the Register request. ASM compares the users details with those recorded in the Registry. If they match, the user is authenticated and the registration completes.
A Register request must contain the user's identifier (handle or extension ID) and the actual location of the SIP phone on which he would like to make his calls. If correct, the user is authenticated and the data is written to the registry.
A reference to an Entity Link
A time zone
An IP Address or FQDN
A reference to an Adaptation