Im Reciving a normal hangup event from janus but none of the part cut the call manually then what might be reason to recive hangup event

General
1

{

janus: ‘event’,

session_id: 4047086102650442,

sender: 4621504694568962,

plugindata: {

plugin: 'janus.plugin.sip',

data: {

  sip: 'event',

  result: { event: 'hangup', code: 200, reason: 'Session Terminated' },

  call_id: '4120d1980011a99a25c3886a1d5afffa@14.97.53.78:5060'

}

}

}

2

Check the Janus core hangup event, as it may give more info (e.g., a DTLS alert or an ICE failure).

3 
const janusWs = new WebSocket(`ws:${JANUS_IP}:${JANUS_PORT},"janus-protocol");

janusWs.on(“message”, async (data) => {

const message = JSON.parse(data);

// here im logging message
}

so, where can i find Janus core hangup event,

4

Please refer to the documentation for how the Janus API works.

5

sir, i already read the documentation and understood that hangup event comes with reason either session terminated or bye im getting that…but sometimes even if neither of the party cuts the call also im reciving hangup event
this im actually reciving as u mentioned to check in janus core hangup event but as per my understaing below is only message im reciving in onMessage event. is there any other hangup core event will come or am i suppose to see somewhere else ? to recive full reason like dtls or ice failed?

{

janus: ‘event’,

session_id: 4047086102650442,

sender: 4621504694568962,

plugindata: {

plugin: 'janus.plugin.sip',

data: {

  sip: 'event',

  result: { event: 'hangup', code: 200, reason: 'Session Terminated' },

  call_id: '4120d1980011a99a25c3886a1d5afffa@14.97.53.78:5060'

}


}

}
6

As I said, you need to check the core hangup event: the one you’ve shared is the plugin hangup event, which is a different thing entirely. You need to check the documentation for the Janus API, not the SIP plugin.

7

okay got this log Thank u sir, Just confirm is this correct or not

Received Janus message: {
“janus”: “hangup”,
“session_id”: 50211324421077,
“sender”: 1313627792057469,
“reason”: “Close PC”
} may be this is the issue

8

That means the plugin closed the connection, so something in the SIP signalling caused that.