nerdexam
Cisco

300-820 · Question #97

Refer to the exhibit. Mobile and remote access is being added to an existing B2B deployment and is failing. When the administrator looks at the alarms on the Expressway-C, the snippets are shown…

The correct answer is C. The listening port on the Cisco UCM for the Expressway-C SIP trunk must be changed to. When Mobile and Remote Access (MRA) is added to an existing Business-to-Business (B2B) deployment, the Expressway-C must connect to Cisco Unified Communications Manager (CUCM) via a SIP trunk. The alarm on the Expressway-C typically indicates an 'address already in use' or…

Mobile and Remote Access

Question

Refer to the exhibit. Mobile and remote access is being added to an existing B2B deployment and is failing. When the administrator looks at the alarms on the Expressway-C, the snippets are shown. Which configuration action should the administrator take to fix this issue?

Exhibit

300-820 question #97 exhibit

Options

  • AThe listening port on the Expressway-C for SIP TCP must be changed to a value other than
  • BThe listening port on the Expressway-C for SIP TLS must be changed to a value other than
  • CThe listening port on the Cisco UCM for the Expressway-C SIP trunk must be changed to
  • DThe listening port on the Cisco UCM for the Expressway-C SIP trunk is set to something other

How the community answered

(42 responses)
  • A
    7% (3)
  • B
    17% (7)
  • C
    71% (30)
  • D
    5% (2)

Explanation

When Mobile and Remote Access (MRA) is added to an existing Business-to-Business (B2B) deployment, the Expressway-C must connect to Cisco Unified Communications Manager (CUCM) via a SIP trunk. The alarm on the Expressway-C typically indicates an 'address already in use' or binding conflict, meaning the port that the Expressway-C is trying to use to reach CUCM is already occupied by the existing B2B SIP trunk configuration. The fix is to change the listening port on the CUCM side for the Expressway-C SIP trunk so it does not conflict with the existing B2B zone port assignments. Options A and B are incorrect because changing the Expressway-C's own SIP TCP/TLS listening ports would disrupt existing registrations and B2B calls. Option D describes the problem, not the fix.

Topics

#Mobile and Remote Access (MRA)#Expressway-C#Cisco UCM SIP Trunk#Port Troubleshooting

Community Discussion

No community discussion yet for this question.

Full 300-820 Practice