Dear RE Mobile Team,
Currently I working on RE Mobile deployment with UCCX.
I am using restricted Client Access mode, So I can define the caller with the SIP calling line ID.
Unfortunately, when I used restricted client acess then co browse feature on finesse gadget is not working.
The pop up message is "this call not through from Remote Expert Mobile Server", then button "Start Co Browse" become disabled.
Is the co browse feature supported with restricted client access?
Restricted Client Access mode is supported. If you are providing your own CorrelationID it should start with "assist-".
If you are still having issues can you provide:
1. The json you are using to create your own session token
2. The server logs by using the logcapture.sh script as outlined in the feature guide: ./logcapture.sh -c -p -f example.tar run as root on the REAS should be enough
3. The browser console logs.
Thanks for your response.
My latest update is I already solve the error above with add addtional attributes on my JSON script, like below :
I have sucessfully made call and do cobrowse session with Web SDK client.
In other case, Unfortunately another error comes up when I'm using Android SDK Client.
The error occur when the agent press the "start co-browse" button in Finesse Gadget.
The cobrowse session won't start, then I capture the logs from my android deveice. Here is the log :
An error occured when sending screen image
java.lang.NullPointerException: Attempt to invoke interface method 'void com.alicecallsbob.assist.aed.AEDTopic.sendMessage(byte)' on a null object reference
It seems there is a null object called AEDTopic.
For your information, I already succeed making a cobrowse session using Android Client with Anonymous Client Access.
The Log error above occur when I change into Restricted Client Access.
Do you have similiar case?
Here is my JSON script that used to obtain SessionID :
$json = '
This is the same issue reported yesterday in CoBrowse showing blank grey screen Is this the same project?
If so please let us know how you resolved the issue.