Welcome to the RingCentral Community

I'm hitting a similar issue. Node.js env.

Not picking up on any call action after successful subscription.

My Code:

function setSubscription() {
    const platform = rcsdk.platform()
    platform.login({
        username: '+14706150273',
        extension: '101',
        password: '********'
    }).then(response => {
        const subscription = rcsdk.createSubscription().setEventFilters(['/account/~/telephony/sessions']);
        subscription.on(subscription.events.notification, function (msg) {
            console.log(msg);
        });
        subscription.register().then(function (response) {
            console.log(response.json());
            console.log('Success: Subscription is listening');
        }).catch(function (e) {
            console.log('Subscription Error: ' + e.message);
        });
    }).catch(e => {
        console.error(e)
    })
}

Console output after run showing successfully subscribed (but nothing after) - Calls are showing in the sandbox call log:

[nodemon] starting `node index.js`
Server is running on port: 5000
{
  uri: 'https://platform.devtest.ringcentral.com/restapi/v1.0/subscription/edde4bf6-1563-4263-94c7-247954e3ac68',
  id: 'edde4bf6-1563-4263-94c7-247954e3ac68',
  creationTime: '2021-11-16T22:52:03.946Z',
  status: 'Active',
  eventFilters: [ '/restapi/v1.0/account/307128004/telephony/sessions' ],
  expirationTime: '2021-11-16T23:07:03.946Z',
  expiresIn: 899,
  deliveryMode: {
    transportType: 'PubNub',
    encryption: false,
    address: '4174641560134678_4a93035d',
    subscriberKey: 'sub-c-b8b9cd8c-e906-11e2-b383-02ee2ddab7fe'
  }
}
Success: Subscription is listening

Hi,

1. You are using the old C-sharp SDK (deprecated). It still should work correctly but I recommend you to use the latest one.

2. Watching the video I could see that you tested correctly for sandbox and production environments. However, I could not see the notification filter you specified in your code so I don't know if it is a notification at the extension level or at the company level.

• Account level: /account/{accountId}/telephony/sessions
• Extension level: /account/{accountId}/extension/~/telephony/sessions

A. If the filter was set at the extension level, then the problem is that you login the app with the main company number with the extension 101, but in your test, you make a call from your own extension (605 3706083) => no notification for your extension

B. If the filter was set at the account level, then the problem is still unknown to me => Either open a support ticket with our developer support team or send me an invite for a meeting at phong.vu@ringcentral.com

Hi Mindy,

Sorry for the delayed response.

The question is a little bit confusing so I will have to ask you to try to test again as follows:

1. Keep testing with PubNub notification which worked for you when you placed a RingOut call. But with a direct call. If your PubNub app works with both type of calls, then your application permissions and testing account are correct.

2. Test your Webhooks application with the same app's and user's credentials (as you tested on your PubNub app). If this does not work, then the problem is with the Webhooks implementation, NOT the server notification. In this case, make sure your Webhooks implementation is correct by checking if it is set up correctly.

Let me know