Sip plugin often fails when toggeling between sip-connections

Hi everyone,

We use the Janus Sip Plugin to make an audio connection
between a browser and some legacy hardware.

Sometimes a user can switch every 2 seconds to listen to another sipconnection.
Often Janus repsonse with a confirmation but there is no sound.
Inspecting Janus logging shows:
[WARN][User-name] Leaving thread, no pipe file descriptor…

Has anyone experience with the same situation and
know how to fix this?

What do you mean by that?

1 Like

A user can make an audio-connection to a sip-source based on an alert in the system.
He can evaluate the audio in 2 seconds and decide to stop the audio connection and
make a new audio connection to another sip-source.
This proces continues.

Again, I don’t understand what you mean by that. Is there SIP involved? Stopping audio connection means a BYE? A re-INVITE? Something else?

All right in more detail:
We use the Janus Sip Plugin to make an audio connection between a browser and some legacy hardware. The proces is:

  • User makes audio connection with sip-source A, sending ‘Invite’;
  • User listens to audio for 2 seconds;
  • User breaks audio connection with Sip-source A by sending 'Bye;
  • User makes audio connection with sip-source B, sending ‘Invite’;
  • User listens to audio for 2 seconds;
  • User breaks audio connection with Sip-source B by sending 'Bye;
  • etc;

Then the problem might be you’re doing new calls too quickly after the previous one ended. An easier way to alternate these calls is using helper sessions: like you create a handle as you’re doing now, and then add a helper, and you alternate the two (1st call on master session, 2nd call on the helper, 3rd one on the master, etc etc), which would ensure the thread always has time to cleanup. You can refer to the documentation for what I mean by helper: the demo has examples of it too.

Thanx for quick response.