Revision history [back]

Hello Wireshark-Community, we have a challenge with our proxy server, because after a random time period it closes the control TCP session of our cloud-based videoconferencing system which causes the UDP traffic to stop flowing (conference interrupted). Can you name some options why a proxy would do so?

VC Participant: 192.168.0.1 Proxy: 10.10.10.1 VC-System: 172.16.0.1

Client to to Proxy: image:

Proxy to VC: image:

Thanks for helping

Hello Wireshark-Community, we have a challenge with our proxy server, because after a random time period it closes the control TCP session of our cloud-based videoconferencing system which causes the UDP traffic to stop flowing (conference interrupted). Can you name some options why a proxy would do so?

VC Participant: 192.168.0.1 Proxy: 10.10.10.1 VC-System: 172.16.0.1

Client to to Proxy: image:link text

Proxy to VC: image:link text

Thanks for helping

Hello Wireshark-Community, we have a challenge with our proxy server, because after a random time period it closes the control TCP session of our cloud-based videoconferencing system which causes the UDP traffic to stop flowing (conference interrupted). Can you name some options why a proxy would do so?

VC Participant: 192.168.0.1 Proxy: 10.10.10.1 VC-System: 172.16.0.1

Client to to Proxy: link textProxy:

Proxy to VC: link textVC:

Thanks for helping

Hello Wireshark-Community, we have a challenge with our proxy server, because after a random time period it closes the control TCP session of our cloud-based videoconferencing system which causes the UDP traffic to stop flowing (conference interrupted). user kicked out). Can you name some options why a proxy would do so?

VC Participant: 192.168.0.1 Proxy: 10.10.10.1 VC-System: 172.16.0.1

Client to to Proxy:

Proxy to VC:

Thanks for helping

Hello Wireshark-Community, we have a challenge with our proxy server, because after a random time (minutes to hours) period it closes the control TCP session of our cloud-based videoconferencing system which causes the UDP traffic to stop flowing (conference user kicked out). out). Connection is not closed by client/server, but from proxy (Screenshots). Can you name some options why a proxy would do so?

VC Participant: 192.168.0.1 Proxy: 10.10.10.1 VC-System: 172.16.0.1

Client to to Proxy:

Proxy to VC:

Thanks for helping

Hello Wireshark-Community, we have a challenge with our proxy server, because after a random time (minutes to hours) period it closes the control TCP session of our cloud-based videoconferencing system which causes the UDP traffic to stop flowing (conference user kicked out). Connection is not closed by client/server, but from proxy (Screenshots). (TCP control session inside screenshots). Can you name some options why a proxy would do so?

VC Participant: 192.168.0.1 Proxy: 10.10.10.1 VC-System: 172.16.0.1

Client to to Proxy:

Proxy to VC:

Thanks for helping

Hello Wireshark-Community, we have a challenge with our proxy server, because after a random time (minutes to hours) period it closes the control TCP session of our cloud-based videoconferencing system which causes the UDP traffic to stop flowing (conference user kicked out). Connection is not closed by client/server, but from proxy (TCP (VC control session inside screenshots). Can you name some options why a proxy would do so?

VC Participant: 192.168.0.1 Proxy: 10.10.10.1 VC-System: 172.16.0.1

Client to to Proxy:

Proxy to VC:

Thanks for helping

Hello Wireshark-Community, we have a challenge with our proxy server, because after a random time (minutes to hours) period it closes the control TCP session of our cloud-based videoconferencing system which causes the UDP traffic to stop flowing (conference user kicked out). Connection is not closed by client/server, but from proxy (VC control session inside screenshots). (Screenshots). Can you name some options why a proxy would do so?

VC Participant: 192.168.0.1 Proxy: 10.10.10.1 VC-System: 172.16.0.1

Client to to Proxy:Proxy:

Proxy to VC:VC:

Thanks for helping