Refer to the exhibit. A new neighbor zone is added for a new Cisco Meeting Server, but the zone is showing a SIP status of failed from the time the zone it was created. What should be done to…

Question

Exhibit

Options

• AThe search rule must be changed to continue on match
• BThe existing zone using ID 7 must be deleted
• CMore bandwidth must be added to the appropriate pipes
• DThe underlying DNS issue must be resolved

• A
  5% (1)
• B
  10% (2)
• C
  10% (2)
• D
  76% (16)

Explanation

A zone status of 'failed' that appears immediately upon creation-before any calls have been attempted-strongly indicates that Expressway cannot resolve the hostname configured for the neighbor zone. Expressway performs a DNS lookup to establish the SIP OPTIONS keep-alive connection that determines zone status. If DNS resolution fails, the zone goes directly to 'failed' state. Other options are not relevant here: search rule configuration does not affect zone status (A), deleting zone ID 7 would not fix the new zone's DNS problem (B), and bandwidth (C) does not affect the signaling status check. Resolving the DNS record for the Cisco Meeting Server's FQDN is the correct fix.

No community discussion yet for this question.