I have an application for Android based on Voximplant platform. I need to know when the destination side rejects the call. How do I find that it was the other side who rejected the call?
If the call on Android rejects via the ICall.reject() method, the caller side will receive the OnCallFailed event with the 480 or 603 error code, depending on the RejectMode.
Related
EXPO SDK Version: 42.0.01
Developing for: iOS
Our goal: successfully send a test notification from Test Send tool in Azure Notification Hub to a registered physical iPhone which is running a local instance of an EXPO app.
Progress: we're able to successfully register a physical iPhone with Azure Notification Hub without using a 3rd party library. We can see that registration in the Hub.
Issues: when using the Azure's Test Send tool we're getting an error "The Push Notification System handle for the registration is invalid" and the test notification does not get delivered.
Debugging:
we're using EXPO's Notifications.getDevicePushTokenAsync() API to obtain the push token.
Azure support team analysed the logs and concluded that the problem is the PNS handle i.e. Apple's ID of the phone registered for notifications.
the phone's PNS handle remains the same at all times.
by using "expo credentials:manager" I've added a new Push Notification Key using KeyID, TeamID and .p8 certificate - the PNS handle didn't change after doing that and notifications were failing too.
I haven't found any tools to validate the APNS handle. I'm currently awaiting a .p12 certificate from our corporate team to test notifications by using https://pushtry.com/.
How do we validate the APNS handle and if found that it's invalid - how do we cycle it / request another?
The PNS Handle from APNs does not change that often as it is tied to the device and app installation. See this answer for more details Does the APNS device token ever change, once created?
Pardon me if this question has been asked before, I just couldn't find the answer.
I have an react native application, it has calling feature using .Net Core SignalR (For signalling) and webRTC for actual calling. There are three scenarios out of which my application works fine in two scenarios:
Application is in foreground: For this I simply inform other client that X is calling you (using signals from SignalR).
Application is in background: For this I send push notification to the client which is read by the application (notification listener) which in turns opens up the call accept/decline window.
I am struggling with scenario 3:
Application has been killed (from recent apps etc.) and is now not in background in this scenario I only receive the push notification but call windows doesn't open but if I open up that notification I can see the calling window as intended. I need a solution which will open up the calling window automatically just like it does in scenario 1 & 2. How can I listen to push notifications when the application is dead? So that I can show the call window?
I am looking for a solution that would preferably work both on Android and iOS and I am using FCM Push notifications. I am also open to solutions other than push notifications as long as they work correctly.
For supporting to android and iOS you can use
import messaging from "#react-native-firebase/messaging";
messaging().setBackgroundMessageHandler(async (remoteMessage) => {
// handle your notification message here
}
I am using gcm with appodeal in my app and when I am sending the push notification the for the first push was successful but phone is not receiving the notification and after that error is there while sending push that device is not register. What to do in this situation please help me.
Is it iOS or Android ? I had the exact same issue just yesterday with iOS and all I had to was to create a development provisioning profile and set it up properly in xCode. I hope that helps you.
I think for you to verify that your app can send and receive messages, client apps must register with GCM.
To register with GCM:
1.The client app obtains a registration token using the Instance ID API. The call to this API must have the authorized entity set to your app server's sender ID, and the scope set to the appropriate value for GCM (depending on your platform). Refer to the API reference for full detail on this API.
2.The client app passes the registration token to the app server.
3. The app server saves the registration token and acknowledges to the client app that the process completed successfully.
This thread may also provide further insight as to why you are receiving the device not registered error.
I have a problem with my application. About sending notifications via GCM. My application saves on my server the user register_id, notifications work perfect, but after an hour I get error NotRegistered.
I have reviewed the documentation and in theory the REQUEST should return me a new register_id, but this does not happen.
Can I get help?
Based on your Manifest file, I suppose that you are using https://github.com/infobip/push-plugin-cordova-phonegap insted of https://github.com/phonegap-build/PushPlugin.
Here is a documentation for Infobip Push Library. Let's try to integrate it from scratch, but first of all, don't forget to register on Push Platform and get necessary credentials.
I'm having problems receiving toast notifications for a Windows Phone 8 application. I did all the steps required:
For the client side, I did this:
Get the channelUri from MPNS
Open the channel
Bind to toast notifications
For the server side, I did this:
Server is written in PHP using this code
Hard-coded the Channel Uri I got in the client app into the PHP code (for testing purposes)
However, when I send the notification from the server, the phone doesn't seem to receive it. Everything runs correctly on the server side and the curl library loads without problems.
I got this!
The problem was in my constructor of the channel. I was doing this to create a new channel:
httpChannel = new HttpNotificationChannel("MyChannel","www.foobar.com");
This constructor should only be called in case of "Authenticated Mode" of push notifications, which requires registering your website and having a certificate.
Obviously, this wasn't my case as I was just testing the push system.
The solution was to create the channel using this:
httpChannel = new HttpNotificationChannel("MyChannel");
It's so misleading as the the official documentation of Windows Phone didn't mention this.