404 after receiving call and not accepting it about janus-gateway

[lminiero]

Caching may be involved in Sofia (the SIP stack used in the plugin), as I do remember some similar issue when failing an authenticated registration as well.

Are you using redirects for the purpose? Can you share the SIP interaction (without the SDP not to clog the issue) highlighting what's going wrong?

[ibrahimab]

Okay, I have changed a few things in the logs to protect my server:

XXX.XXX.XXX.XXX => server ip
XXXX-YYYYYYYYYYYYY => SIP account
YYYY-XXXXXXXXXXXXXX => Janus SIP Plugin user
ZZZZZZZZZZZ => incoming context
XXXX => extension that is called from Janus SIP Plugin, this is the same as the XXXX in the SIP account.

SIP log: https://gist.github.com/anonymous/48f43105b02bf3d26548

[lminiero]

Sorry if this took so long...

I've just been able to reproduce the issue. You're right, the plugin is not sending the INVITE to the extension that is passed to it but the actual username of the peer. Looking at the SIP messages, I don't see the extension anywhere, though, which makes me think it's not any caching that is involved (there would be no mapping to make), but a bug in the plugin itself. In fact, the original INVITE has the username as part of the calling address (e.g., sip:caller@ip:5060), which is what is called by the plugin later on. Most likely there's a variable that is not cleaned as it should, which results in the plugin calling the last caller instead of who's requested.

I'll look into it right away.

[lminiero]

It should be fixednow. It was not an issue with variables and the like, but a wrong reuse of libsofia's nua_handles. I just pushed the commit, let me know if that fixes it for you as well and I'll close the issue.