SIP CSRV - Timeout

Description

Indicates that the ONT attempted to retrieve its configuration from the TConfig server, but the request timed out indicating it was unable to communicate with the TConfig server.

Pre-Conditions(s)

The line must be in Softswitch mode for this alarm to occur.

Trouble Clearing

The probable causes of this alarm are: 

• The network to the TConfig server is down and the TConfig server on the EMS is not reachable.
• Tconfig server is not reachable: The most common cause of this alarm is that the network between the ONT and the TConfig server resident on the EMS has gone down. This can be verified by obtaining the ONT IP address from the ONT > Properties > VoIP tab > DHCP Address(es) and then pinging that IP address from the EMS command line interface. If the IP address is not pingable, then find and fix the problem with the network. If the IP address is pingable, it is likely the TConfig server is down.
• The IP address specified for the EMS TConfig IP address is incorrect. This configuration can be found at the NE > Properties > VoIP tab in the Config Server Address field.
• TConfig Server is down: Some certificate activities and maintenance functions can take down the TConfig server. You can bring up the tconfig server can be restarted by going to the bbmgr/server subdirectory of the EMS installation and running runHttpServer.ksh, Solaris, or runHttpServer.bat, Windows.
• Tconfig Server is not set up: For the TConfig server to operate properly, it must be installed as part of the EMS installation (refer to Panorama PON EMS Installation and System Administrator Guide for the EMS TConfig server installation instructions.
• ONT does not have an IP: In some cases this can occur if the ONT has not been able to obtain an IP address. Verify that the ONT shows an IP address on the ONT > Properties > VoIP tab > DHCP Address(es). If it does not, then there should be a DHCP alarm, which should be corrected first using the appropriate procedure.

Previous   |