3102 無料問題集「Avaya Aura Session Manager and System Manager Implementation and Maintenance」

（A）the registration state of the destination

（B）the SIP domain of the called party

（C）the origination or termination application sequences that will be applied to call, ignoring what the applications themselves may do

（D）the location of the calling party

（A）A SIP entity must be specified as both a destination and as an origination point. You must provide the times of day that the policy applies, and a dial pattern or regular expression that the call URI must match.

（B）The destination SIP entity can either be chosen specifically, or it may be selected implicitly using a matching expression. Multiple times of day the policy is active can be chosen. The policy must have either a dial pattern or regular expression.

（C）A SIP Entity must be specified as a destination.

（D）A dial pattern must be specified which the called party in the SIP message is matched against. Inclusion of a time range, or regular expression, is optional but recommended since it makes the policy more specific.

（A）Create a new Non-SIP User Application Sequence Policy.
Define the address and location of the non-SIP user.
Select appropriate Originating and Terminating Sequences for the non-sip user from the
given options.

（B）Create a new Implicit User rule.
Define a number pattern that can be compared with dialed numbers.
Select appropriate Originating and Terminating Sequences to be applied when a match
occurs.

（C）Navigate to the list of Application Sequences and select the sequence to apply to the
non-SIP user.
Add the user's extension number to the list of associated users.
Select appropriate check box options to determine if the sequence should be applied In
originating mode, terminating mode or both.

（D）Add an Avaya-SIP Communication Address to the user's User Profile.
Add a Session Manager Profile to the user's User Profile.
Select appropriate Originating and Terminating Sequences for the user from the options in
the new Session Manager Profile.

（A）Whether SMGR will abort and rollback the operation or continue processing records is entirely configurable.

（B）Whether SMGR will abort or continue processing records is entirely configurable; but you cannot rollback successfully imported users.

（C）It will abort the operation and roll back any successfully imported records from the import file.

（D）It will continue processing the rest of the import file and collate the failures into a single XML document that can be retrieved following the import.

（A）Messaging Profile

（B）Endpoint Profile

（C）Communication Address

（D）Session Manager Profile

（A）Run traceSM100 to capture SIP MONITOR message from the entity to determine if there is a delay in the network.

（B）Run SIP Entity Performance on the Entity to determine id SIP OPTIONS messages are being blocked on the network.

（C）Run traceSM to capture SIP INVITE message from the entity to determine if there is a display in the network.

（D）Run SIP monitoring diagnostics along with ICMP ping to the Entity to verify its connectivity.

（A）The IP of the remote server providing High Availability

（B）Network Time Protocol (NTP) settings.

（C）Subnet network mask

（D）SMGR IP address

（E）Default Gateway IP