Troubleshooting

This section offers suggestions for handling problems with SIP sessions.

System running but does not receive calls

• Check the audio.sip.UserAgentPort service property setting.

  If calls are coming from an external network to an internal one, make sure the address is visible externally. Internal networks may use a private addressing scheme.

• Call the application using a SIP softphone on the same LAN. The syntax is: sip:app@vbs_hostname[:port]. The port is the value specified by audio.sip.UserAgentPort, by default, 5060.

  If calling with a SIP softphone is successful, the problem might be the Gateway or proxy server configuration (if any). Try to capture the SIP messages coming out the system using any network protocol analyzer. Some are available for free on the intranet.

  If calling with a SIP softphone is unsuccessful:

  • Make sure the port assigned to the SIP application is not being used by another application
  • Make sure the port number used for SIP is higher than 5000, to avoid using a port usually designated for other applications (such as port 80, which is for HTTP only).

System running but cannot place calls

Place a call directly to a SIP softphone on the same LAN from an application.

If calling the SIP softphone is successful, the problem may be with the Gateway or proxy (if any) configuration.

If calling the SIP softphone is unsuccessful, there may be a problem with Voice Platform’s configuration or the application.

• Try to capture the SIP messages coming out the system using any network protocol analyzer. Some are available for free on the intranet.
• Make sure the port assigned to the SIP application is not being used by another application.

  Make sure the port number used for SIP is higher than 5000, to avoid using a port usually designated for other applications (such as port 80, which is for HTTP only).