Provisioning a public SIP server to Jabber user doen't appear to work

[Chris Swinney]

Hey,

We are running TMS 14.2.1, TMSPE 1 and VCS x7.1

Although I have added the schema and templates for the relevant Jabber versions (such as 4.5, 4.6 etc) and assigned them the the relevant user groups, if I make a change in the "Public SIP Server Address" (or indeed the normal configuration item, "SIP Server Address", it makes no difference to the settings in the Jabber video client.

I have another question relating to old Jabber/Movi version, but I think this is best left to another discussion.

Any ideas?

Chris

[ahmashar]

check on VCS, whether the new template is downloaded from TMS. if not, click on force synchronize now button. make sure the template is there (i.e. on VCS). now logout of jabber client and sign in again, you should have the new provisioning paramter for jabber client.

[Chris Swinney]

Yes - the VCS shows the correct template for the User + the correct info for the internal and external SIP Server address.

In addation, I know that the template is being applied as I can make other changes such as the download URL which is applied correctly.

However, the SIP server does not change on the client (in this case the external server remains blank).

[Martin Koch]

For the public sip server to be used the request have to

come via the external server configured on the jabber video client,

the internal one is tried first and has to fail (you can for example remove the

internal server setting to see if it works afterwards).

A debug session on the Jabber Client and/or the VCS can also show you more,

there are a couple of postings regards that in the forum, please search for it.

[Chris Swinney]

Hi Martin,

Apologies for the delay in responding, I have been on holiday.

Ah, I see - I think.  I was expecting that the text in the External and Internal server addresses in the Jabber client to be overwritten, however this does not appear to happen - correct?

So, if I MANUALLY add either of the the VCS addresses to the the Jabber Video client, does this override any provisioning information that is hidden, or does the provisioning information take precedence? What I was expecting was that a user will enter the internal VCS address, connect the Jabber Video client, and the Public VCS address will then be provisioning from TMS populating the external server address.

Problem is this doesn't seem to hold true. Just for giggles, I removed BOTH the internal and external server addresses from the Jabber Video client settings, and the client continued to connect successfully to the internal address. However, setting the internal address to something random (thus trying to force it NOT to connect to the internal server) simply resulted in a failure to connect. If I manually overrode the external server setting with the internal address still set to something random, I connect successfully.

I had thought about creating modified installation scripts for new Jabber video installation, but as we maintain many different organisations, the current method is unworkable for us.

I will look for other posts, but didn't come up with much prior to posting.

[Zac Colton · Accepted solution]

THe SIP server values configured in the client do not get over written by the provisioning data. I think this was already explained, but let me try to clarify. In the TMS, there are 2 values for SIP server, one is "SIP Server Address" and "Public SIP Server Address." These are used to identify an internal and external SIP server for the client to register to. If only "SIP Server Address" is used, this is used for both internal and external. On the Jabber client, you have 2 field available for server, "Internal Server" and "External Server". With these configured, the Jabber client will first try to connect to the internal server, and then the external server. For which ever one that it connects to, it will send a SUBSCRIBE for provisioning data. Within that SUBSCRIBE, it will identify itself and its connection (either internal or external). The Provisioning service on the VCS will process this, and is the client is "internal", the provisioning data returned will contain the value for the "SIP Server Address". If the client sees itself as external, the "Public SIP Server Address" is returned. If the "Public SIP Server Address" is not configured in the profisioning template in TMS, the value for "SIP Server Address" is returned. When the Jabber client receives this data, it will then attempt to register to that server. To better understand this, you need to look at the Jabber client logon process as 2 separate processes. One is the subscription for provisioning data. The second process is the registration of itself as a SIP client to a server.

I hope this clarifies thing.

Zac Colton

[Chris Swinney]

Thanks Zac, that are really good answer and does indeed clarify the situation. It would be great to see this kind of information in the Jabber Video administration guide. Apologies to Martin for not fully understanding his answers.

Sometime when asking a question, you later realise that the question your asking doesn't necessarily follow the correct form of thinking, and so searching for answers becomes awkward.

So the only way populate the fields Internal and External server in the actual Jabber client is to either get the user to manually enter them, or apply them during installation using parameters passed into the setup exe?

Just out of curiosity, am I correct in thinking that the Jabber client somehow stores the provisioning information on a per SIP domain basis, and will use the last stored provisioning information for that SIP domain to register to the VCS if both the Internal and External server fields in the Jabber client are left blank? It appears that I can change the SIP domain on the client, leave both server field blank, and the Jabber client will still be able to register to the correct VCS.

[Zac Colton]

There are multiple ways have having the internal server, external server, and SIP domain pre-populated for the user. Please take a look at chapter 4 in the admin guide:

http://www.cisco.com/en/US/docs/telepresence/endpoint/Jabber_Video/4_6/CJAB_BK_C89F6C9E_00_cisco-jabber-video-for-telepresence.pdf

- Zac Colton

[Chris Swinney]

Thanks again Zac. I have indeed read these pages. Pushing  configurations is a non starter for us as we manage many organisations  without having full access to their domains or software management  applications.

Even creating unique installers  might be a bit of a bind as potentially we would manage many domains -  50 off the bat but this could rise significantly if sub domains are  included. However, if this is the only method open to us, then it is  something I will explore. I could create unique BAT files that contain a  simple line to launch the Jabber Video Setup EXE with the various configuration options

One of the issue I had with pre-configureing the  installer was the setion on page 13 of the admin in the "Installer  Pre-configureation" section that stated:

When installers are preconfigured, these configurations:
     will be replaced or removed during upgrades.

I  wasn't sure if I could then configure an upgrade via the provisioning  (using a the Software URL/Software version) to use the pre-configuration install options via a BAT file or some such. I did think this I could take a snapshot an re-create an MSI, but this would be even more tedious, and in any case, pointing to an MSI in the Software URL in the provisioning template doesn't appear to work.