SIP IP gateway “%1” did not respond within %2 seconds to the Session Initiation Protocol (SIP) option request that was sent by the Unified Messaging server. Make sure that the IP gateway has no performance bottleneck. Also, make sure that there are no network connectivity issues between the IP gateway and the Unified Messaging server.

Details
Product: Exchange
Event ID: 1089
Source: MSExchange Unified Messaging
Version: 8.0
Symbolic Name: PeerDidntRespondTimely
Message: SIP IP gateway “%1” did not respond within %2 seconds to the Session Initiation Protocol (SIP) option request that was sent by the Unified Messaging server. Make sure that the IP gateway has no performance bottleneck. Also, make sure that there are no network connectivity issues between the IP gateway and the Unified Messaging server.
   
Explanation

This Warning event indicates that the expected Session Initiation Protocol (SIP) options status code 200 response was received by the computer that has the Unified Messaging server role installed. This response occurs after the Unified Messaging (UM) server issues an SIP Option request to the SIP peers (VoIP gateway or IP/PBX). However, there was a delay between the request and the response. The SIP request is sent periodically as a mechanism to obtain the operational status of the SIP peers. After the UM server issues the request, the UM server waits for an SIP options response. If the server receives a status code 200 response within 2 seconds, the SIP peers are considered functional and without a connection delay between the UM server and the SIP peers. This event may be caused by performance issues at the SIP peers or by network connectivity issues between SIP peers and the UM server.

   
User Action

To resolve this warning, do one or more of the following:

  • Contact the vendors who support the VoIP gateway or IP/PBX hardware. Run diagnostic test to make sure that the device is operational and without a performance bottleneck when it responds to an SIP Option request.

  • Use the Ping or PathPing command-line tools to test basic connectivity. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems.

  • Review the Application log and System log for network-card-related entries or connectivity-related events. Check the Application log for MSExchangeADAccess and MSExchange Topology events. Use the information in those events to determine the root cause of this warning.

  • Check to see whether other computers that use the same default gateway and are plugged into the same hub or switch also experience connectivity problems. If the other computers connected to the same default gateway do not experience network connectivity problems, a network adapter issue on a single computer may be the cause of the problem. If this is the case, try to resolve this issue by doing one or more of the following:

    • Replace the network adapter with a network adapter that has been tested and proven reliable.

    • Update the driver for the network adapter driver to the latest version.

    • Replace the network cable between the failing system and the hub or switch.

  • Check the settings on the network adapter and uplink hardware. The uplink hardware is the hub or switch that is used by the computer that has the Unified Messaging server role installed. Make sure that all network hardware is correctly configured by doing the following:

    • Use the same speed and duplex-level settings on all hardware.

    • If the media type is set to autosense, autosensing, autodetect, or Auto Select, make sure that all components autosense correctly.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Leave a Reply