Script

If a user cannot make calls to federated users or receive calls from federated users, you can troubleshoot the issue as follows:

1. Verify that the Access Edge service is running and connected.
   
   
2. Verify, on the Edge Server, that the external interface of the A/V Edge service that is shown on the Edge Interfacestab of Microsoft Office Communications Server 2007R2 Propertiesis configured with a publicly routable IP address. For details, see Configuring the External Interface of the A/V Edge Servicein the Administering Office Communications Server 2007 R2 documentation.
   
   
3. Verify the configuration of the A/V Edge service on the Generaltab of the pool-level A/V Conferencing Server Propertiesdialog box, including the configuration of the FQDN, IP address, SIP listening port, and media port range. For details, see Configuring the Listening Address for A/V Conferencing Serversin the Administering Office Communications Server 2007 R2 documentation.
   
   
4. Verify that the external firewall is configured to allow traffic over the configured media port range.
   
   
5. In Office Communications Server 2007 R2, run the Validation Wizardon the following:
   
   
   • The Edge Server running the Access Edge service. Use the Validate Local Server Configurationand Validate Connectivityoptions.
     
     
   • Internal servers, such as the Director or Front End Server. Use the Validate Local Server Configurationand Validate Connectivityoptions. You can also use the Validate SIP Logonoption and the option to verify connectivity with a federated user.
     
     

The Validation Wizard indicates configuration errors or warnings, and recommends specific solutions that you can try. If you cannot resolve the issue by using the errors and warnings posted by the Validation Wizard, do the following:

1. On the Edge Server:
   
   
   • Review the Office Communications Server log in Event Viewerto determine whether there are any specific events related to connectivity or domain validation. For details about relevant Office Communications Server events, see Appendix A: Enterprise Voice-Related Events.
     
     
   • Verify that federation is enabled.
     
     
   • Check the Allowlist of the Access Edge services (that is, for your organization and federated partners) to ensure the domain and Access Edge service FQDNs are correct. For details, see Configuring Access for Federated Partnersin the Administering Office Communications Server 2007 R2 documentation.
     
     
   • Check the list of internal domains to ensure that all internal SIP domains are listed.
     
     
   • Verify that the next hop server is correctly configured for the Director or pool.
     
     
   • Ensure that the IP addresses of the internal and external interfaces are correct for your Access Edge service and for those of your federated partners.
     
     
   • Verify connectivity with federated partners by entering the domain and FQDN of the federated server on the Allowlist and then running the Validation Wizard with the Check Connectivityoptions. If the connection attempt fails, an error message appears.
     
     
2. In Global Properties(forest level):
   
   
   • On the Federationtab, verify that federation is enabled and that the FQDN is correct for the Director (if deployed) or the Edge Server (if no Director is deployed). For details, see Enabling Federation and Public IM Connectivity and Configuring Routing of Inbound and Outbound SIP Trafficin the Administering Office Communications Server 2007 R2 documentation.
     
     
3. On the Edge Serverstab, in the list of Access Edge services and Web Conferencing Edge services, verify the FQDNs. In the list of A/V Edge services, verify the internal FQDNs and ports. For details, see Specifying Trusted Edge Servicesin the Administering Office Communications Server 2007 R2 documentation.
   
   
4. On the Director (if deployed):
   
   
   • On the Federationtab, verify the internal FQDN of the Access Edge service.
     
     

See Also