Your question title and the details are so confused. Duration of a supervised call has nothing to do with PubNub notification expiration.

PubNub notification is for you to receive push notification event, which you used to receive telephony session event notification and use the info to subscribe for call supervision.

Once you subscribed for a call supervision successfully, the voice data stream will come via a WebSocket channel, NOT via the PubNub notification channel!

Hi @Phong Vu,
Thanks for your answer, but we are not using a websocket to receive the data stream. Because we are limited to use .net framework 4.7 we are using RingCentral.Net and RingCentral.Net.PubNub nuget packages to establish subscription. My question is because we are maintaining the subscription on every 15mins, does this can cause a call supervise to break (stop)?

And another question, do we have limitation for call supervise regarding the duration of a subscription session?

Why do you keep mentioning about this "The session is keep-alive every 15mins from the SDK"? There is nothing to do with the PubNub notification in your call supervision. So what you try to tell me is your SIP call supervision session is closed after 15 mins?

Correct, the call supervision session is closed after exactly 15mins or 900seconds. My doubt is that we receive a BYE (SIP) message from the PBX but I'm not sure why, cause we never initiated one. Any idea why this might happen?

I agree with Phong that when you are already supervising the call, it has nothing to do with PubNub any more. You can do an experiment: as soon as the supervision starts, delete your PubNub subscription. I doubt that it will have any effect on the supervision call.

Call supervision session is closed after exactly 15mins or 900seconds. My doubt is that we receive a BYE (SIP) message from the PBX but I'm not sure why, cause we never initiated one. Any idea why this might happen?

This needs some deep investigation and inputs from you which should not be exposed in the public domain. Can you create a support request and provide the details.

What device endpoint do you receive the supervise call ? Softphone / Hardphone ?

Also , I a looking at the ticket for your support case. Can you share Wireshark / Sip Logs to investigate this further ? What i need is the callID , Session ID and timestamp of the latest calls.

Dear @Vyshakh Babji,
Thanks for the support. We are using softphone implementation. Here are some details from the wireshark we have. If it's not helpful i will try to record new wireshark from this week and post new results.

Call information:

User: Izabela Kucharska

time_started: 1614680319000 Tuesday, March 2, 2021 11:18:39 AM GMT+01:00

time_connected: 1614680319000 Tuesday, March 2, 2021 11:18:39 AM GMT+01:00

time_ended: 1614681220000 Tuesday, March 2, 2021 11:33:40 AM GMT+01:00

Session-id: s-796f493849be457eae0f5d7e99f90907

Party-id: p-796f493849be457eae0f5d7e99f90907-1

Sip call-id: 3e002a1a-c954-4f5f-82d4-ec02cecfe980

Usefull sip data:

p-rc-api-ids: party-id=p-796f493849be457eae0f5d7e99f90907-3;session-id=s-796f493849be457eae0f5d7e99f90907

p-rc-api-monitoring-ids: party-id=p-796f493849be457eae0f5d7e99f90907-1;session-id=s-796f493849be457eae0f5d7e99f90907

Endpoints: 104.245.57.180:54606 (Local)

Endpoints: 172.30.132.43:17186 (Remote)

Wireshark trace: https://drive.google.com/file/d/1c4h9PkMLGSBwyH2RxqOw7oTUO8QImeZG/view?usp=sharing

The details above are the first call from the wireshark.
Please let me know if we need to record new pcap. We have more than 2000 calls like this that are cut after 900 seconds.

I just test on my demo app and it works well after 15 mins.

Dear @Vyshakh Babji ,

Here are call information from today:

Call information:

User: James Selway

time_started: 1632388375000 Thursday, September 23, 2021 11:12:55 AM GMT+02:00 DST

time_connected: 1632388375000 Thursday, September 23, 2021 11:12:55 AM GMT+02:00 DST

time_ended: 1632396475000 Thursday, September 23, 2021 1:27:55 PM GMT+02:00 DST

Session-id: s-b247c60103694d19b4d51884e880154c-1

Party-id: p-b247c60103694d19b4d51884e880154c-1

Sip call-id: 2243557a-3693-47fa-9519-aca8f302967d

Usefull sip data:

p-rc-api-ids: party-id=p-b247c60103694d19b4d51884e880154c-3;session-id=s-b247c60103694d19b4d51884e880154c

p-rc-api-monitoring-ids: party-id=p-b247c60103694d19b4d51884e880154c-1;session-id=s-b247c60103694d19b4d51884e880154c

INVITE sip:441159004000*6500@172.30.132.43:63229=104.245.57.27:43730

Wireshark data: https://drive.google.com/file/d/1pG2NWHIo_oyvhvJxEPZtHgDHQ5aC5_0v/view?usp=sharing