- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-03-2013 07:30 AM - edited 03-18-2019 01:55 AM
Hello,
Have an issue where a handful of endpoints experience a flapping up/down TMS HTTP connection issue. They are up, and then go down for 5-7 minutes. Then, they come back up and the TMS "no HTTP connection" alert clears. Then they go down again.....
- SIP and H.323 registrations are not impacted.
- Web interface access is OK.
- Just visibility to TMS service is issue.
Seems a segment of the network route is the culprit blocking/unblocking TMS visibility. What tools can I use to best prove to customer where he should instruct his network team to investigate?
Would this be Wireshark from one of the network ports in the conference room designated for this endpoint? If so, identifying what exactly?
Thank you,
JL
Solved! Go to Solution.
- Labels:
-
Room Endpoints
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-03-2013 02:39 PM
Another option would be to install Wireshark on the TMS server, (assuming it is not one of the old appliances), and do a packet trace looking for http traffic on port 80 (if https port 443) between TMS and one of the end-points in question.
/jens
Please rate replies and mark question(s) as "answered" if applicable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2013 11:54 PM
Actually, thinking about it, assuming these are SNMP capable systems, they could also try increasing the scan interval and number of missed responses before it sets the system(s) as "unreachable".
/jens
Please rate replies and mark question(s) as "answered" if applicable.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-03-2013 02:39 PM
Another option would be to install Wireshark on the TMS server, (assuming it is not one of the old appliances), and do a packet trace looking for http traffic on port 80 (if https port 443) between TMS and one of the end-points in question.
/jens
Please rate replies and mark question(s) as "answered" if applicable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2013 11:54 PM
Actually, thinking about it, assuming these are SNMP capable systems, they could also try increasing the scan interval and number of missed responses before it sets the system(s) as "unreachable".
/jens
Please rate replies and mark question(s) as "answered" if applicable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2013 07:02 AM
Thank you, Jens. These are both excellent. JL
