Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

TMS Phonebook Server Configuration

Hello Forum,

 

I have a simple question about phonebook configuration in TMS14.3.0.

When I push a phonebook from TMS to a SX20 (TC7.1.1) the PhoneBook server Configuration is provisionned with

https://IP@_TMS//tms/public/external/phonebook/phonebookservice.asmx

It is correct but in my environment, everything is secured with Certificates so when I press the phonebook button on the SX20 remote the Phonebook does not appear. Indeed my certificates are made of FQDN and not IP address (PKI Policy, no choice !)

 

So I created a template in TMS wiht PhoneBook server Configuration for SX20 as

https://FQDN_TMS/tms/public/external/phonebook/phonebookservice.asmx

Then I get the PhoneBook. Great. But when I do a change on the phonebook and I push it back immediatly from Set on Systems in PhoneBook, TMS provisions back its IP Address instead of the FQDN.

 

I configured In Network my IPv4 address as well as FQDN of TMS. My systems are tracked by Hostname and added to TMS with their FQDN.

 

Does anyone know where to configure the provisioning of Phonebook Server field and replace it by TMS FQDN instead of TMS IP Address ?

In the meantime, I upgrade to 14.3.2 to see if it changes anything, and I am even ready to try 14.4.

 

Thanks for any reply that could be provided.

Cécile

8 REPLIES
Cisco Employee

Hi Cécile,If you have

Hi Cécile,

If you have populated the "TMS Server Fully Qualified Hostname" field in the Network Settings, TMS should use that value when building phonebook configuration URLs, not the IP address. Nothing has changed (deliberately at least!) between 14.3 and 14.4, so upgrading is unlikely to help.

I'll see if I can reproduce the problem in my lab.

Regards,
Kjetil

 

Cisco Employee

Works fine for me in 14.3,

Works fine for me in 14.3, the phone book URL stays on a FQDN format after I make phone book changes:

 

Not sure what to suggest, but do you have your Network Settings like I do above? Do the endpoint logs show anything about the URL change?

 

-Kjetil

New Member

Hello Kjetil, Thanks for your

Hello Kjetil,

 

Thanks for your reply and testing.

 

Did you push from TMS the phonbook to the SX20 ? I do agree that any entry in a phonbook would be updated instantly in the SX20 when you recall for the phonebook but when you add a new phonebook and then push it from TMS (Set on System > Save) then the fqdn swaps to IP Address.

 

 

I picked up the logs from the codec (extended logging) :

 

Reference : TMS is 249 and codec is 108

 

May 13 17:58:01.781 a8 appl[1659]: 97733.31 CuilApp   User admin(1001) about to execute command '/Logging/ExtendedLogging/Start Duration: 600' from 10.x.x.101.
May 13 17:58:01.867 a8 appl[1659]: 97733.39 APPL_Addons W: Diagnostics enabled, dumping status and configuration
May 13 17:58:20.034 a8 appl[1659]: 97751.56 CuilApp   User admin(1001) successfully changed configuration 'Config/NetworkServices[1]/NTP[1]/Mode[1]' to 'Manual' from 10.xx.xx.249.
May 13 17:58:20.079 a8 appl[1659]: 97751.61 CuilApp   User admin(1001) successfully changed configuration 'Config/NetworkServices[1]/NTP[1]/Address[1]' to '10.x.x.233' from 10.xx.xx.249.
May 13 17:58:20.091 a8 appl[1659]: 97751.62 CuilApp   User admin(1001) successfully changed configuration 'Config/Phonebook[1]/Server[1]/URL[1]' to 'https://srvcgs-tms1.domain.com/tms/public/external/phonebook/phonebookservice.asmx' from 10.xx.xx.249.
May 13 17:58:20.139 a8 appl[1659]: 97751.67 CuilApp   User admin(1001) successfully changed configuration 'Config/Phonebook[1]/Server[1]/Type[1]' to 'TMS' from 10.xx.xx.249.
May 13 17:58:20.145 a8 appl[1659]: 97751.67 CuilApp   User admin(1001) successfully changed configuration 'Config/Provisioning[1]/Mode[1]' to 'TMS' from 10.xx.xx.249.
May 13 17:58:20.186 a8 appl[1659]: 97751.71 CuilApp   User admin(1001) successfully changed configuration 'Config/Provisioning[1]/ExternalManager[1]/Address[1]' to 'srvcgs-tms1.domain.com' from 10.xx.xx.249.
May 13 17:58:20.191 a8 appl[1659]: 97751.72 CuilApp   User admin(1001) successfully changed configuration 'Config/Provisioning[1]/ExternalManager[1]/Protocol[1]' to 'HTTPS' from 10.xx.xx.249.
May 13 17:58:20.232 a8 appl[1659]: 97751.76 CuilApp   User admin(1001) successfully changed configuration 'Config/Provisioning[1]/ExternalManager[1]/Path[1]' to 'tms/public/external/management/systemmanagementservice.asmx' from 10.xx.xx.249.
May 13 17:58:20.238 a8 appl[1659]: 97751.77 CuilApp   User admin(1001) successfully changed configuration 'Config/Provisioning[1]/ExternalManager[1]/Domain[1]' to 'domain.com' from 10.xx.xx.249.
May 13 17:58:20.279 a8 appl[1659]: 97751.81 CuilApp   User admin(1001) successfully changed configuration 'Config/Provisioning[1]/HttpMethod[1]' to 'POST' from 10.xx.xx.249.
May 13 17:58:20.285 a8 appl[1659]: 97751.81 CuilApp   User admin(1001) successfully changed configuration 'Config/Provisioning[1]/Connectivity[1]' to 'Internal' from 10.xx.xx.249.
May 13 17:58:22.979 a8 appl[1659]: 97754.51 CuilApp   User admin(1001) about to execute command '/SystemUnit/MenuPassword/Validate Password: Input Hidden' from 10.x.x.101.
May 13 17:58:28.899 a8 appl[1659]: 97760.43 SipPacket   PacketDump: Proto: SIP, Direction: Outgoing, Name: REGISTER, CSeq: 61625 REGISTER, RemoteAddress: 10.x.x.81:5060, CallId: 5cbdc1f305d1f1fe5138aba126119ce8, Time: 97760427
May 13 17:58:28.900 a8 appl[1659]: 97760.43 SipPacket   REGISTER sip:domain.com SIP/2.0
May 13 17:58:28.901 a8 appl[1659]: 97760.43 SipPacket   Via: SIP/2.0/TCP 10.x.x.108:5060;branch=z9hG4bK5baf190db2d888e3d50b0102305d5bf8.1;rport
May 13 17:58:28.901 a8 appl[1659]: 97760.43 SipPacket   Call-ID: 5cbdc1f305d1f1fe5138aba126119ce8
May 13 17:58:28.902 a8 appl[1659]: 97760.43 SipPacket   CSeq: 61625 REGISTER
May 13 17:58:28.902 a8 appl[1659]: 97760.43 SipPacket   Contact: <sip:8794@10.x.x.108:5060;transport=tcp>;+sip.instance="<urn:uuid:865844be-9892-5ea7-9727-b692cde652d7>"
May 13 17:58:28.903 a8 appl[1659]: 97760.43 SipPacket   From: <sip:8794@domain.com>;tag=fe41af22f7385cba
May 13 17:58:28.904 a8 appl[1659]: 97760.43 SipPacket   To: <sip:8794@domain.com>
May 13 17:58:28.904 a8 appl[1659]: 97760.43 SipPacket   Max-Forwards: 70
May 13 17:58:28.904 a8 appl[1659]: 97760.43 SipPacket   Route: <sip:10.x.x.81;lr>
May 13 17:58:28.904 a8 appl[1659]: 97760.43 SipPacket   Allow: INVITE,ACK,CANCEL,BYE,UPDATE,INFO,OPTIONS,REFER,NOTIFY
May 13 17:58:28.904 a8 appl[1659]: 97760.43 SipPacket   User-Agent: TANDBERG/520 (TC7.1.1.168aadf)
May 13 17:58:28.905 a8 appl[1659]: 97760.43 SipPacket   Expires: 3600
May 13 17:58:28.905 a8 appl[1659]: 97760.43 SipPacket   Supported: replaces,100rel,timer,gruu,path,outbound
May 13 17:58:28.905 a8 appl[1659]: 97760.43 SipPacket   Content-Length: 0
May 13 17:58:28.905 a8 appl[1659]: 97760.43 SipPacket   
May 13 17:58:28.911 a8 appl[1659]: 97760.44 SipPacket   PacketDump: Proto: SIP, Direction: Incoming, Name: 200 OK, CSeq: 61625 REGISTER, RemoteAddress: 10.x.x.81:5060, CallId: 5cbdc1f305d1f1fe5138aba126119ce8, Time: 97760438
May 13 17:58:28.912 a8 appl[1659]: 97760.44 SipPacket   SIP/2.0 200 OK
May 13 17:58:28.912 a8 appl[1659]: 97760.44 SipPacket   Via: SIP/2.0/TCP 10.x.x.108:5060;branch=z9hG4bK5baf190db2d888e3d50b0102305d5bf8.1;received=10.x.x.108;rport=59023
May 13 17:58:28.913 a8 appl[1659]: 97760.44 SipPacket   Call-ID: 5cbdc1f305d1f1fe5138aba126119ce8
May 13 17:58:28.913 a8 appl[1659]: 97760.44 SipPacket   CSeq: 61625 REGISTER
May 13 17:58:28.914 a8 appl[1659]: 97760.44 SipPacket   Contact: <sip:8794@10.x.x.108:5060;transport=tcp>;+sip.instance="<urn:uuid:865844be-9892-5ea7-9727-b692cde652d7>";pub-gruu="sip:8794@domain.com;gr=urn:uuid:865844be-9892-5ea7-9727-b692cde652d7";expires=60
May 13 17:58:28.914 a8 appl[1659]: 97760.44 SipPacket   From: <sip:8794@domain.com>;tag=fe41af22f7385cba
May 13 17:58:28.914 a8 appl[1659]: 97760.44 SipPacket   To: <sip:8794@domain.com>;tag=cb680cd1ca51d581
May 13 17:58:28.915 a8 appl[1659]: 97760.44 SipPacket   Server: TANDBERG/4129 (X8.1.1)
May 13 17:58:28.915 a8 appl[1659]: 97760.44 SipPacket   Date: Sun, 13 May 2014 15:58:29 GMT
May 13 17:58:28.916 a8 appl[1659]: 97760.44 SipPacket   Supported: com.tandberg.sdp.extensions.v1,gruu,outbound,path
May 13 17:58:28.916 a8 appl[1659]: 97760.44 SipPacket   Content-Length: 0
May 13 17:58:28.917 a8 appl[1659]: 97760.44 SipPacket   

On TMS I went to Systems > Navigator I selected the system and went to Phonebook and clicked on Save : Results TMS replaces the FQDN by its IP Address

May 13 17:58:30.301 a8 appl[1659]: 97761.83 CuilApp   User admin(1001) about to execute command '/SystemUnit/MenuPassword/Validate Password: Input Hidden' from 10.x.x.101.
May 13 17:58:43.150 a8 appl[1659]: 97774.68 CuilApp   User admin(1001) successfully changed configuration 'Config/Phonebook[1]/Server[1]/ID[1]' to 'default' from 10.xx.xx.249.
May 13 17:58:43.194 a8 appl[1659]: 97774.72 CuilApp   User admin(1001) successfully changed configuration 'Config/Phonebook[1]/Server[1]/Type[1]' to 'TMS' from 10.xx.xx.249.
May 13 17:58:43.214 a8 appl[1659]: 97774.74 CuilApp   User admin(1001) successfully changed configuration 'Config/Phonebook[1]/Server[1]/URL[1]' to 'https://10.xx.xx.249/tms/public/external/phonebook/phonebookservice.asmx' from 10.xx.xx.249.
May 13 17:58:44.341 a8 appl[1659]: 97775.87 CuilApp   User admin(1001) about to execute command '/SystemUnit/MenuPassword/Validate Password: Input Hidden' from 10.x.x.101.
May 13 17:58:52.260 a8 appl[1659]: 97783.79 CuilApp   User admin(1001) about to execute command '/Logging/ExtendedLogging/Stop' from 10.x.x.101.
May 13 17:58:52.263 a8 appl[1659]: 97783.79 APPL_Addons W: Diagnostics disabled

New Member

Hello back Forum, I digged a

Hello back Forum,

 

I digged a little bit more further into TMS ans SX20 interaction. The problem of fqdn versus IP address can be extended to upgrade function in TMS.

 

Indeed, once more TMS pushes its ip address instead of fqdn for the url where to download the package meanwhile I specifically configured in Network Settings : fqdn of tms/...

 

More over, I had to disable :No otherwise, once the :1 (hour) is over, TMS pushes its IP address back to all the field where fqdn is configured or expected.

 

If anybody can do the test, I would be delighted to confront my results.

Thanks for any help.

Cecile

Cisco Employee

Yes, it would apply to all

Yes, it would apply to all features where the endpoint needs to be told the location of TMS

 

- Phonebooks

- feedback registration

- upgrades

- external manager

 

It all would use the same logic to determine what TMS address to use in URLs configured on the endpoint...  the IPv4 address, the IPv6 address, or the FQDN address.  All the values to use are taken from the Network Settings page under Configuration in Admin Tools in TMS.

The intended behavior is TMS would determine if the system supports DNS, and if so, use the FQDN if available.  If not available, or if DNS support is non-deterministic, use IPv4 or IPv6 address.

Unfortunately I do not have the capacity at the time to simulate and debug your situation myself.  But I would recommend calling TAC and getting a case open to investigate.

If you have the network address fields configured properly under Admin Tools -> Configuration, the expectation is the hostname will be used in the URLs provisioned to the devices.

Cisco Employee

There is/was (can't look up

There is/was (can't look up right now) logic where TMS would determine if an endpoint supported DNS or not before deciding if hostname or IP should be used in URLs

Obviously you must have the FQDN of the server defined in the Network Settings in Administrative Tools (which it sounds like you do)

But make sure TMS thinks the device supports DNS...  have both a DNS server and the DNS domain name defined in the endpoint.

New Member

Hello Steve, Thanks for Reply

Hello Steve,

 

Thanks for Reply.

I added a snasphot of SX20 in TMS. I believe TMS is aware that SX20 is able to do DNS resolution.

But while pushing the phonebook it would configure the Phonebook server address with its ip address.

 

Cecile

New Member

Hi I have a similar issue but

Hi

 

I have a similar issue but it's mainly that I don't want the external IP address pushed to some devices outside the network. These devices are on a separate private network and use a different external IP address to talk back to the phonebook server. I can set the phonebook URL to the new address in TMS (via templates) and all works fine, however, after the 4 hour polling period it appears some central management settings get enforced on the endpoint and the units phonebook address is changed back to the centrally set external one (that most of the existing endpoints are using). Is there any way to stop TMS from updating these endpoints phonebook URL's? Also - it seems odd that TMS overwrites the phonebook URL that is set in the configured persistent template set on the endpoint..

 

Any ideas greatly appreciated.

 

thanks

Anthony

1575
Views
0
Helpful
8
Replies
CreatePlease to create content