cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
924
Views
4
Helpful
4
Replies

SoHo/behind firewall systems can't be added to TMS

ken.tucker
Level 1
Level 1

I've got automatic discovery on for soho, using a known good template. This has worked in the past, and works for internal clients. External clients show up as "Preregistered not added" when they first hit the external TMS IP. These used to automatically go into Discovered Systems and work great. Now they don't show anywhere other than Add Systems/From List, I see it and can add it, but then it shows as "Not Yet Activated" and I can't get it to talk to TMS. More importantly, it can't get phone books.


I can't find anything that has changed - from TMS config, firewall rules, etc. Unless it's a codec firmware issue, I've tested EX60 v5.1.4 and v6.0.0. TMS is 13.2.1.

Any ideas?


Ken

4 Replies 4

Magnus Ohm
Cisco Employee
Cisco Employee

Hi, are you sure the endpoints can reach the tms server? The bot yet activated message means that tms has not got any alive messages from the system. Can you login as root to the endpoint and try the curl command: curl http://

/magnus


Sent from Cisco Technical Support iPhone App

Thanks Magnus,

Yes, curl works. Although the html returned does say access is denied. I get the same thing in a web browser though, so I suspect that's normal.

Port 80/443 are allowed into TMS. I've looked through TMS logs and the only items from that endpoint's IP are related to phone book denies (since the endpoint isn't fully in TMS).

Any other thoughts?

Ken

Ken: did you find a fix? Do you use http or https?

I have some similar case as well. TMS13.2.2 and TC5.1.8. It rarely happened before and if

purging and readding the system helped, but not this time.

Btw, there seems to be an additional issue with TC6.2

https://supportforums.cisco.com/thread/2236458?tstart=0

Please remember to rate helpful responses and identify helpful or correct answers.

Please remember to rate helpful responses and identify

Martin,

I did find a fix... But for the life of me, I can't remember what it was. I remember testing with http and https, didn't make a difference while it was broken. I think it was network related though and wasn't on the endpoint or TMS.

I don't have any TC6.2, especially behind a firewall. I'll be mindful of upgrading!

Ken