Freeswitch's `mod_dingaling` Google Voice authentication failure - freeswitch

Does anyone currently have a working setup of Google Voice calling with Freeswitch? I have had one working before for many years (as per https://wiki.freeswitch.org/wiki/Google_Voice) but now am receiving following error message:
[CRIT] libdingaling.c:1675 sasl authentication failed

Google dropped xmpp support, for more details please check following link:
http://nerdvittles.com/?p=9286

Related

Websocket Connection ErrorERR_CONNECTION_REFUSED

I am currently developing a tizen app using a web app.
I have a problem with web socket communication, but I can not tell which part is the problem.
Is there anybody who can help with this?
try port number 9000,3000,8080
WebSocket connection to 'ws://localhost:3000/' failed: Error in
connection establishment: net::ERR_CONNECTION_REFUSED
Could you check this guide page for Tizen Websocket?
https://developer.tizen.org/ko/development/guides/web-application/w3chtml5supplementary-features/communication/websocket
I think.. If you add some codes, it will be helpful to others.

Custom Microsoft Teams Connector doesn't communicate with an external service at all

Common description
First, my goal is sending notifications from my service using an internal API to a MT channel and having an option to answer it transmitting one to internal API.
I've found a Connector has such functionality. Good example which i've tried to use StackOverflowConnector. It was a good point to start that is exactly what i need(Bot has inappropriate UI behaviour) , but i've decided to do it by small steps from creating a Bot just to understand things better. In short i had success, the bot and a mt channel communicted well both directions. Next point was Connector. I explored all information here:
https://learn.microsoft.com/en-us/microsoftteams/platform/index
https://learn.microsoft.com/en-us/azure/bot-service/?view=azure-bot-service-3.0
https://learn.microsoft.com/en-us/outlook/
What i have taken to create a Connector
registered a Connector in the Connectors Developer Dashboard with followed fields:
Connector name: connector
Logo: contoso96x96.png
Short description of your app (10 words or less): sd
Detailed description of what your Connector does (3-5 sentences): dd
Company website: https://external.service
List the events supported by your Connector: all
Do you want to enable actions on your Connector cards?: Yes
Actions URL: https://external.service/api/messages
Does your service support login using subdomain?: No
Landing page for your users for Inbox: https://external.service
Landing page for your users for Groups or Teams: https://external.service
Redirect URLs: https://external.service/api/messages
Ran the external service to communicate with a Connector. Checked service works
took a manifest.json file is generated by Connectors Developer Dashboard and uploaded it to a Microsoft Team(MT) team. Uploading was successful. There was no network requests(monitored nginx logs) to the external service
selected a channel in MT and clicked the Connectors dialog option. Found the created connector in the list Sideloaded group and clicked Configure. Got such window and clicked Done. Nothing happened
ran nodejs code from the [github connector example][3](it didn't have meaning because of total lack of the requests)
What i expected:
Any activity in the external service, other nodes of integration i can't monitor. I compare this failed result with ones of StackOverflowConnector and my bot experience, both works as needed.
Question:
How to set up the connector to work, to send network requests? At least to have echo logic.
Upd:
I have noticed a weird report of deleting a MT app of the connector.
I believe you might have some confusion between a Bot and a Connector. Based on your post description you should be looking to create a Bot and not a Connector. Please let us know if you have further queries.
Update:
Could you please give a try with C# sample code? Here is the basic flow for your understanding:
When user clicks on Visit Site to install the Setup endpoint is hit.
When user clicks on Connecto to Office 365 the Register endpoint is hit with webhook information.
When new task is created in your system you can post the message to registered channels using webhook url.

Reg: Socket Connection in Ionic3

I am having an issue with the socket connection with my ionic3 application. I am using socket for implementing chat. Please find the below work flow.
I have configured the socket.io in my dashboard moudule (Not on app.module.ts) because I have to pass user token while connection which is obtained only after login. I have added screenshot below. Here I am getting success socket connection with the server.
When I import the socket in my chat page, I am getting the below error.
Is there any mistake in my approach? If my question is not clear to you please comment below before downvoting.

SSL Handshake with Cloud Code HTTP Request

I'm trying to see if it's possible to do an SSL handshake through cloud code. So far all I have found is https://parse.com/questions/is-it-possible-to-attach-a-certificate-to-httprequest
But I was hoping to get a more clear answer regarding whether this is possible or not.

IBM Worklight 6.0.0.1 - Error during hourly process for push notifications

We're getting an error in WebSphere's SystemOut log approximately every hour on our Worklight Server.
It seems to be trying to validate push notification configuration. We currently have working notifications, using Apple push notifications only. Errors are:
com.notnoop.apns.internal.ApnsFeedbackConnection getInactiveDevices
Failed to retreive invalid devices ava.lang.RuntimeException:
javax.net.ssl.SSLHandshakeException
Our notifications are working, but, what is this hourly process? I don't see anything in the docs regarding a batch process that's run by Worklight Server.
Our setup: Worklight Server 6.0.0.20130909-1459, WAS 8.0.0.6, JDK 1.6.
Worklight uses notnoop open source library to push notification to APNS. This is a known harmless bug in notnoop.
https://github.com/notnoop/java-apns/issues/29
I believe this check is part of the way APNS's feedback service works.
From: Provider Communication with Apple Push Notification Service
Section: General Provider Requirements
Connect regularly with the feedback service and fetch the current list
of those devices that have repeatedly reported failed-delivery
attempts. Then stop sending notifications to the devices associated
with those applications. See “The Feedback Service” for more
information.
As for what it means, it looks to me like your exception quote is cut. Is that all of it?

Resources