csharp sdk Telephony sample login remain in connecting status
Répondu
I'm tryng to test Telephony csharp sdk sample but when I click login the connection status remain in 'connecting'.
I've also try with Instantmessage of csharp sdk sample and with this the connection it's ok.
In addition I've created a new application copying the code from instant message sample but also in this case che login remain in connecting status.
In both application i've set the same parameter of application id, secret key, user and password.
Can someone help me to solve the login problem ?
Here the log for thelephony:
2020-04-25 11:06:10,788 INFO 1 Rainbow.Application: 0 - ================================================================
2020-04-25 11:06:10,811 INFO 1 Rainbow.Application: 0 - [Application] Using INI file - path:[C:\Users\fdoss\AppData\Local\Temp\Rainbow.CSharp.SDK\configuration.ini]
2020-04-25 11:06:10,817 INFO 1 Rainbow.Application: 0 - Rainbow.CSharp.SDK: [1.10.0.0]
2020-04-25 11:06:10,817 DEBUG 1 Rainbow.Application: 0 - [GetTimeoutFromIniFile] Debugger mode detected - Double the timeout based on INI file - Timeout:[4000]
2020-04-25 11:06:13,374 DEBUG 1 Rainbow.Application: 0 - [Login] Start
2020-04-25 11:06:13,384 DEBUG 1 Rainbow.Application: 0 - [RaiseConnectionStatus] - ConnectionStatus:[connecting]
And this is the log for instant message:
2020-04-25 11:39:20,790 INFO 1 Sample_Contacts.SampleInstantMessagingForm: 76 - ==============================================================
2020-04-25 11:39:20,804 INFO 1 Sample_Contacts.SampleInstantMessagingForm: 77 - SampleInstantMessaging started
2020-04-25 11:39:20,811 INFO 1 Rainbow.Application: 0 - ================================================================
2020-04-25 11:39:20,813 INFO 1 Rainbow.Application: 0 - [Application] Using INI file - path:[C:\Users\fdoss\AppData\Local\Temp\Rainbow.CSharp.SDK\configuration.ini]
2020-04-25 11:39:20,819 INFO 1 Rainbow.Application: 0 - Rainbow.CSharp.SDK: [1.10.0.0]
2020-04-25 11:39:20,821 DEBUG 1 Rainbow.Application: 0 - [GetTimeoutFromIniFile] Debugger mode detected - Double the timeout based on INI file - Timeout:[4000]
2020-04-25 11:39:24,641 DEBUG 1 Rainbow.Application: 0 - [Login] Start
2020-04-25 11:39:24,642 DEBUG 1 Rainbow.Application: 0 - [RaiseConnectionStatus] - ConnectionStatus:[connecting]
2020-04-25 11:39:24,684 DEBUG 3 Rainbow.Private.Rest: 0 - [Login] Set timeout value:[4000]
2020-04-25 11:39:25,106 DEBUG 10 Rainbow.Application: 0 - [Login] REST login with login/pwd successfull - contactId:[5ea2a8fadab8af573119688a]
2020-04-25 11:39:25,109 DEBUG 10 Rainbow.Application: 0 - [Login] IpEndPoint:[] - Proxy:[]
2020-04-25 11:39:25,169 DEBUG 7 Rainbow.Application: 0 - [CommonLoginProcessInit] - nb features:[48]
2020-04-25 11:39:25,204 DEBUG 7 Rainbow.Application: 0 - [CommonLoginProcessInit] - nb profiles:[1]
2020-04-25 11:39:25,205 DEBUG 10 Rainbow.Application: 0 - [CommonLoginProcessInit] - All info has been asked in correct delay
2020-04-25 11:39:25,292 INFO 10 Rainbow.Application: 0 - [SetUserCapability] Name:[UserNameUpdate] - Available:[enabled]
2020-04-25 11:39:25,293 INFO 10 Rainbow.Application: 0 - [SetUserCapability] Name:[FileDownload] - Available:[enabled]
....... and more ......
Regards,
Flavio
-
Hi,
I just check the Telephony sample on my side without any trouble
Double check to ensure you have specified correctly APP_ID, APP_SECRET_KEY and a valid HOSTNAME. Since you are blocked on the "connecting" step, it's generally due to an error on these data.
If the login/pwd are incorrect, you have a specif error. "invalid login/pwd"
Now if you are sure of all of this are correct, list all Nuget packages versions you use and provide me the list ( name + version). I will check if you are using them with the correct version. Since one the sample is working on your side you can first compare on your side.
Regards,
Christophe -
Thank you for your suggestion. In fact in the Telephony project I had updated the references of the nuget components. I reset the original references and the login works. Surely there is something in the nuget references dll that is not compatible.
Thank you and good day.
Flavio
Vous devez vous connecter pour laisser un commentaire.
Commentaires
3 commentaires