7230X 試験問題を無料オンラインアクセス

Considering the message flow to an Avaya Aura Contract Centre (AACC) Agent Desktop, which protocol is used to communicate between AACC, CCT, and the Agent Desktop PC?

• A.WCF
• B.CSTA
• C.TSAPI
• D.SIP

Which statement about Network Routing Policies in Avaya Aura Session Manager (SM) is true?

• A.A dial pattern and routing policy are necessary in SM to call from an AST device to an H323 device on the same Avaya Aura Communication Manager (CM).
• B.A dial pattern and routing policy are necessary in SM to call from an H323 device to a Basic/Native SIP device (without an Avaya Aura Communication Manager profile).
• C.A dial pattern and routing policy are necessary in SM to call from an H323 device to an AST device on the same Avaya Aura Communication Manager (CM).
• D.A dial pattern and routing policy are necessary in SM to call from a Basic/Native SIP device (without a CM profile) to an H323 device on Avaya Aura Communication Manager (CM).

A customer reports that remote worker users cannot see their feature buttons. Their Avaya Session Border Controller for Enterprise (SBCE) was recently damaged and replaced due to a lightning strike. After doing some troubleshooting, support was able to see that PPM was misconfigured in the SBCE.
Which tool was used, and which symptoms were visible that pointed to this issue?

• A.traceSM; SIP requests were going to Avaya Aura Session Manager instead of SBCE
• B.List trace; PPM requests were going to Avaya Aura Session Manager instead of the PPM server
• C.traceSBC with PPM debugging enabled; PPM requests were seen to be going to the Utility Server instead of Session Manager
• D.traceHTTP; all HTTP requests were going to SBCE instead of Avaya Aura Communication Manager

A customer called is stating they cannot place WebRTC calls. You discover that Avaya Breeze T has not been configured to allow Cross-origin Resource Sharing (CORS).
How would you allow cross-origin resource sharing for all?

• A.Use Avaya Aura System Manager (SMGR) web GUI to access Breeze > Configuration > HTTP Security > HTTP CORS tab, the check the box Allow Cross-origin Resource Sharing for all.
• B.Use SSH to Avaya Breeze and edit the /etc/config.properties file.
• C.Use Avaya Aura System Manager (SMGR) web GUI to access the Inventory > Manage Elements.
  Edit
  the Avaya Breeze element, and check the box Allow Cross-origin Resource Sharing.
• D.Use Avaya Aura System Manager (SMGR) web GUI to access the Breeze > Configuration > Attributes, then select the webRTC attributes and check the box Allow Cross-origin Resource Sharing.

When a customer calls voicemail to retrieve their messages they hear "Hello, to access your mailbox..." instead of the users named followed by "please enter your password...".
After troubleshooting you discover that the Caller ID is not being sent correctly, therefore Avaya Aura Messaging (AAM) is not able to identify the correct mailbox associated with the station number calling into AAM.
How can this problem be fixed?

• A.Change clid-numbering 0 SAT form to send the correct CLID.
• B.In Session Manager, configure a DigitConversionAdapter with 'fromto=true' to update the 'Form' header as well as the P-asserted-identity, and link it to the AAM SIP Entity.
• C.Having identified the trunk group from Avaya Aura Communication Manager (CM) to AMM is public, change public-unknown-numbering 0 SAT form, to send the correct CLID.
• D.Using AAM web GUI access Administration > Messaging > Telephone Integration, write a caller ID modification rule to correct the incoming CLID format.