Ask Your Question

Revision history [back]

SIP register timeout

Hi all,

I have a fax server running on a Windows Server 2019 machine. The fax server communicates via VoIP and registers itself on a PBX in the local network.

Problem: the fax server sends regularly SIP REGISTER requests which results in a time out.

I recorded a trace from the fax server (192.168.73.150) and the PBX (192.168.73.1).

An example:

  • in 192.168.73.150 a REGISTER request is sent (packet no. 310)
  • in 192.168.73.1 I am not able to find the correspondig request. It seems that it didn't even reach it's destination.

Am I missing something? Can you witness my observation?

SIP register timeout

Hi all,

I have a fax server running on a Windows Server 2019 machine. The fax server communicates via VoIP and registers itself on a PBX in the local network.

Problem: the fax server sends regularly SIP REGISTER requests to the PBX which results in a time out.

I recorded a trace from the fax server (192.168.73.150) and the PBX (192.168.73.1).

An example:

  • in 192.168.73.150 a REGISTER request is sent (packet no. 310)
  • in 192.168.73.1 I am not able to find the correspondig request. It seems that it didn't even reach it's destination.

Am I missing something? Can you witness my observation?

SIP register timeout

Hi all,

I have a fax server running on a Windows Server 2019 machine. The fax server communicates via VoIP and registers itself on a PBX in the local network.

Problem: the fax server sends regularly SIP REGISTER requests to the PBX which results in a time out.

I recorded a trace from the fax server (192.168.73.150) and the PBX (192.168.73.1).

An example:

  • in 192.168.73.150 a REGISTER request is sent (packet no. 310)
  • in 192.168.73.1 I am not able to find the correspondig request. It seems that it didn't even reach it's destination.

Am I missing something? Can you witness my observation?

EDIT There is a successful registration in the fax server trace at 13:46:45 (Packat no. 88). The next registration at 13:47:40 fails as the PBX sends a tcp ack but no SIP response code.