cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
790
Views
0
Helpful
3
Replies

TMS Phonebook design

Rod.Blackie
Level 1
Level 1

HI Netpro's

I have a VCS-C AND TMS located inside a DMZ. The VCS-E is located on the public internet.

All internal clients are registered to the VCS-C and pull the phone books from TMS - OK.

I would like to publish the TMS phonebooks to devices that are registerd with the VCS-E

Our compnay is a global organisaiton and we have external companies with internet only C20 endpoints that are registered to our VCS-E.

My goal is this - I'd like to have one global phone book that all systems have access to via VCS /TMS registration

Is the only way to achieve this goal to create two TMS servers that query the same DB? One TMS server on the DMZ with a NAT translation to a public address and one TMS server on the inside network for all WAN / LAN clients?

Or is there another way to achieve my goal?

Thanks

Rod                

1 Accepted Solution

Accepted Solutions

Magnus Ohm
Cisco Employee
Cisco Employee

Well, the phonebook is transferred using http(s) which means that the endpoint need to reach the tms over http or https to be able to get it. An alternative would be to open port 80 or 443 so that the tms can be reached on the public internet which is what you ultimately have to do. If you use a double tms pointing at the same database where one server is public you anyway comprimise the tms server to the public internet since the info you get would be the same regardless what tms server you connect to because of the shared db. The c20s needs to be added into tms as well (but not reachable by the tms if its a soho system) in order to get permission to access the phonebooks you set on the system. It does not need to be very complex as long as the endpoints can reach the tms server from the internet.

/Magnus

Sent from Cisco Technical Support iPhone App

View solution in original post

3 Replies 3

Magnus Ohm
Cisco Employee
Cisco Employee

Well, the phonebook is transferred using http(s) which means that the endpoint need to reach the tms over http or https to be able to get it. An alternative would be to open port 80 or 443 so that the tms can be reached on the public internet which is what you ultimately have to do. If you use a double tms pointing at the same database where one server is public you anyway comprimise the tms server to the public internet since the info you get would be the same regardless what tms server you connect to because of the shared db. The c20s needs to be added into tms as well (but not reachable by the tms if its a soho system) in order to get permission to access the phonebooks you set on the system. It does not need to be very complex as long as the endpoints can reach the tms server from the internet.

/Magnus

Sent from Cisco Technical Support iPhone App

Magnus

Thanks for the quick reply.

To confirm:

I can use a public IP that has a NAT translation to the TMS server located on the inside network. I can then configure the external C20 system to access the TMS system using the public NAT address within the phone book configuraiton option.

Rod

Magnus Ohm
Cisco Employee
Cisco Employee

Correct, but the endpoints need to be added to the tms servers systems (system navigator) because its not enough to just point the phonebook url to the tms server. You need to assign the pb to the system in TMS but im sure you are aware if this, but just in case.

/Magnus

Sent from Cisco Technical Support iPhone App