SalesForce timeout and need to re-register client

Status
Not open for further replies.

boomschtick

Free User
Joined
Sep 11, 2012
Messages
49
Reaction score
8
I'm having the same issue that is referenced here.

My users are having to re-register their 3cxPhone in order to get the SalesForce integration to start working again.

The log is showing a timeout:


6/5/2018 8:17:40 AM - Error: System.Web.Services.Protocols.SoapException: INVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session hash: +R6DI/UMOSukjWtXdcFtXeFBvIgxLToYMttp/m0mZVY=
This error usually occurs after a session expires or a user logs out.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.InvokeAsyncCallback(IAsyncResult result)

Once the client is re-registered, it starts to work as expected. The linked thread says that the client should automatically start a new SalesForce session, but I'm not seeing that kind of functionality happening.

What can I do so that my users are not having to deal with this issue on a daily basis?

Thanks in advance!
 
Hello @boomschtick,

In first place, it is recommended that you change your Salesforce configuration to allow larger sessions. Salesforce has a setting for this, so you can make sessions expire after 6 hours, 12 hours, 24 hours, etc. I would change the setting to use a larger value.

The automatic reconnection only happens on inbound calls. If you use Salesforce for outbound dialing, then this will not happen and you will have to restart 3CXPhone.

Kind regards.
 
Hello @boomschtick,

In first place, it is recommended that you change your Salesforce configuration to allow larger sessions. Salesforce has a setting for this, so you can make sessions expire after 6 hours, 12 hours, 24 hours, etc. I would change the setting to use a larger value.

The automatic reconnection only happens on inbound calls. If you use Salesforce for outbound dialing, then this will not happen and you will have to restart 3CXPhone.

Kind regards.

@edossantos, I have bumped up the timeout on SalesForce. My users are still having to re-register their 3cx for Windows client every morning. Seems like a bug that could use squashing.
 
Have you tried the server side integration? We are not making fixes to the client side plugins, that approach will be deprecated at some point and you should move to server side.
 
Have you tried the server side integration? We are not making fixes to the client side plugins, that approach will be deprecated at some point and you should move to server side.

My understanding is that server side does not pop up the contact page on inbound calls, which is functionality that my sales people like. What other functionality is lost by going server side?
 
Actually, with the server side integration you have that functionality. But you need to use the 3CX Web Client. In that case you will see a button on the upper right corner of the caller card when you receive an inbound call, and if you click on the button you will see the contact in Salesforce.

Call journaling is not available at the moment in the server side integration, but it will be added shortly.
 
Status
Not open for further replies.

Forum statistics

Threads
112,148
Messages
590,962
Members
165,168
Latest member
Stephan Eusebe