Author Message
sercanoztorun
Joined: Feb 14, 2018
Messages: 31
Offline
Hi everybody,

i deployed javascript breeze client code to server
i work on only CommunicationPackage from source code.

i have access all components(aawg,amm,aads) from "localhost". (Everything is fine in localhost)
if we can access the another computer with server ip then we can connect (aawg,amm) but can not connect AADS(i can see call and messaging tabs but cannot see Contacts tab.)

i cannot reach AADS server and got error like,

ACSContactsProvider: Subscription confirmation was not received in time https://aads.xxx.xxx.xxx.xx:443/acs/bsid/7a553228-5493-4dfc-832e-66efe899f6e8/resources/contacts/users/self/searches

WebSocket connection to 'wss://aads.xxx.xxx.xxx.xx/notification/bsid/7a553228-5493-4dfc-832e-66efe899f6e8/notificationChannel/websocket' failed: WebSocket opening handshake was canceled

ACSContactsProvider: Notification provider connection failed

ACSContactsProvider: Start notification channel failed

AMMMessagingProvider: Start notification channel failed

i think about the problem is certificate error. i create keystore and i reach the application link from "https" but problem is not resolved.

you can see more detail about error from below attachment.
Please help about this error.
  • [Thumb - error.png]
[Disk] Download
sercanoztorun
Joined: Feb 14, 2018
Messages: 31
Offline
Hi everyone ,

i notice that if i can go to the aads page (ex : https://aads.xxx.xxx.xxx.xx/acs/bsid/e822ad01-1ffc-4b67-af06-917baeb2eba1/resources/contacts/users/self/searches ) , it ask me login name and password . (you can see the attachment)

If i login the credentials then Contacts page is appear after next login

i really didn't clarify the problem.

Please help me why this is happening.

  • [Thumb - error2.png]
[Disk] Download
Rumata
Joined: Dec 20, 2016
Messages: 133
Offline
Hi,

Thank you for your question,

Our technical team is working on your issue.
Rumata
Joined: Dec 20, 2016
Messages: 133
Offline
Server team reports that the error seems to indicate that the websocket connection could not be established. It could be that the certificate is not trusted, but it’s not clear what the real problem is without more AADS logs.
You can also try using SSE instead of WebSockets by replacing the URL:
wss://aads.xxx.xxx.xxx.xx/notification/bsid/7a553228-5493-4dfc-832e-66efe899f6e8/notificationChannel/websocket
With:
https://aads.xxx.xxx.xxx.xx/notification/bsid/7a553228-5493-4dfc-832e-66efe899f6e8/notificationChannel/sse

Go to:   
Mobile view