Refer to the exhibit.
Company ABC has just implemented Rendezvous conference using Cisco Meeting Server (CMS) and Unified CM. However, all calls to CMS space URI 5000 failed. Based on the snippets from the CMS event logs, which two configuration issues caused the calls to fail? (Choose two.)
A. Incoming rules to match vceguide.com domain is not configured in CMS
B. Incoming rules to match cms.vceguide.com domain to target Spaces is not configured in CMS
C. No route pattern configured in Unified CM to route the call to CMS Space
D. SIP trunk between Unified CM and CMS is down
E. No SIP route pattern configured in Unified CM to route the calls to CMS
F. There is no Space with URI [email protected] in CMS
A,B
It checks if the domain part of the incoming URI matches the incoming matching table or not. If it does match, it is able to route the call to space, user, IVR or do a Lync conference lookup (on-prem or off-prem) as per your configuration for this dialplan rule. The table does not allow for wildcard domains, it requires a full match.
If the forwarding table does not have any rule or a reject rule, then the event log does not explicitly show this. It just informs you that the SIP call did not match (any space, user, IVR or Lync meeting) and that you miss the forwarding rule (or it is set to reject) to move to the outbound rules section.
2018-10-04 06:47:12.482 Info call 790: incoming SIP call from “sip:[email protected]” to local URI “sip:[email protected]”
2018-10-04 06:47:12.495 Info call 790: ending; local teardown, destination URI not matched – not connected after 0:00
BF
I think the right answer is : BF