J4W

[Sumit Bhargava]

Hi,

Customer-X has the entire UC 10.x  infrastructure based out of HQ.

There is a Remote site with 500 users

80% of the entire workforce including users at Remote Site are provisioned with SoftClient: Jabber for Windows  10.x version (SoftPhone mode)

I understand Scenario-I. However, not sure about Scenario-2.Please share your inputs on Scenario2 and if possible with Call Flow:

Scenario-I: When the IP connectivity between HQ & Remote Site goes down

1. Remote Site users with Jabber Windows Client10.x can connect to CUCM through  internet via VCS C/E or Exp-C/E and Authentication takes place using UDS.

Scenario-2: When CUCM/LDAP is not accessible, how will the Users at Remote Site with Jabber Windows10.x Client (SoftPhone mode) login and get provisioned?

Like to know if the below understanding is correct. If not, please share your inputs on the correct recommendation:

1. Jabber Windows Client10.x which is in SoftPhone mode gets into DeskPhone mode when CUCM/LDAP/UDS is down and only voice call would be supported.

The Jabber  windows client10.x  that are already logged in remain logged in but the new Jabber Windows client 10.x client will not be able to login when CUCM/UDS is down since authentication is not possible.

2. Need to use E-SRST concept wherein the SRST Manager will be installed as a separate Virtual Machine in HQ. It will take the configuration from CUCM and do auto synchronization with Voice Gateway running CME in SRST mode at Remote Site. So,  when the  CUCM goes down or IP WAN is down, the Jabber Windows Client 10.x will get the required configuration but how will the authentication takes place even in this scenario.?

Thanks & Regards

Sumit

[Jaime Valencia]

Scenario 1 authentication takes place wherever your users are, if they are LDAP, then LDAP, if local, then UDS.

Scenario 2 This is really a no brainer, if you don't have LDAP, no authentication, if you don't have CUCM, no phone registration. If both are down...

Nooo, if there's no CUCM, there's no CTI, thus no deskphone control. And if CUCM is down, no softphone either.

Assuming your CUCM is up and running, and UDS fails, then yes, no logins, if your CUCM is down... see above.

J4W works the same as it would be EM when it goes to SRST.

[Sumit Bhargava]

Hi Jaime,

  Is it correct to conclude that-

  (i)  If at the Branch Site, you have both IP Phone users and users with Soft Client: J4W

  (ii) CUCM at HQ goes down, IP Phones will get into Fallback mode, but J4W client be it DeskPhone mode or SoftPhone Mode can not get into fallback mode the way IP Phones does. 

 So, in nutshell....J4W doesn't support SRST concept and the CUCM/UDS has to be up for J4W client to authenticate and get provisioned with the respective user's Service Profile.

Thanks

Sumit

[Jaime Valencia · Accepted solution]

SRST DOES support J4W, that's in the SRST documentation. Again, it would be the same as if you were using EM.

And yes, if CUCM is down, and you just started J4W, you cannot get anything. You have to be already connected before something fails, to go to SRST.