Description

Looks like Jitsi don't manage SIP/INFO messages from IPBX server https://tools.ietf.org/html/rfc6086

Current behavior

On Jitsi desktop. If IPbx sends SIP/INFO message, jitsi reply with 501 Error "Not implemented" So Ipbx sends a BYE request and close communication

Expected Behavior

Allow reply with "Status-code 200" and permit continuing discussion

Possible Solution

Accept SIP/INFO messages

Steps to reproduce

Call from Aastra SIP Phone 6755i To Jitsi deskTop 2.10.5550

Environment details

Mitel IPBX MV5000-R6.5 SP2 /AN00 FRA jitsi0.pcap.txt

As this is good to have, this is not a mandatory thing.

I don't see why the PBX will reply with BYE in this situation, do you see such thing describe in the RFC? I would say contact and the PBX opening issue on their side as this should be fixed there.

We already support receiving INFO for content application sub types dtmf-relay and media_control+xml.

If those INFO messages are just pings whether client is alive, even an error reply is and indication that the client is alive.

Hi, Not sure what I read in RFC. In section 4.2.2 :

Otherwise, if the INFO request is syntactically correct and well structured, the UA MUST send a 200 (OK) response.

As my English comprehension is not perfect, I found this in french : http://www.efort.com/r_tutoriels/SIP2_EFORT.pdf section 5.5

Une des réponses suivantes est retournée par le destinataire de la requête INFO :

• 200 OK si la requête INFO est applicable à une session,
• 481 Call Leg/Transaction Does Not Exist, si la requête INFO ne correspond à aucunesession en cours,
• 415 Unsupported Media Type message si la requête INFO contient un corps demessage que le récepteur n'a pas su interpréter faute de disposer des règles detraitement correspondantes.
• 4xx, 5xx et 6xx comme pour les autres méthodes SIP.

Ekiga replies with : "Status 415 Unsupported Media Type" X-lite replies with : ""Status 200 OK"

PBx isn't opensource and I can try to contact them but we are talking about mitel .... Thanks

The PBX is broken. See: https://tools.ietf.org/html/rfc3261#section-12.2.1.2

Since the error is not a 481 nor a 408 there is no reason to tear down the dialog.

Yes, Jitsi should probably send a 415 instead of a 501, since it's a client error, but I'll invoke POstel's principle: be gentle in what you accept.

Yep, I agree with that ;)

https://tools.ietf.org/html/rfc3261#section-12.2.1.2 https://tools.ietf.org/html/rfc2976#section-2.2

These 2 sections are talking about UAC (so client I guess) sending SIP/INFO requests and what UAServer should do but I can't see anything about Packets send by server.... Could you give me a link which explain that it shouldn't ? this would help me to open a TAC with Mitel. Thanks

The UAC / UAS roles are interchangeable, they are used in the context of the transaction, not in the sense of a server and a client application.

So when the PBX sends an INFO transaction, it is the UAC, because it's the one sending it. When it received an INVITE, for example, is acting as the UAS.

Hi all, Comming back on this subject. I a call conf yesterday with mitel's integrator. They said me that the UAs should answer on every SIP/INFO and that and 501 response isn't a valid one...

Recieved message contains a valid CALL-ID so sip client has to answer to it as explained in rfc :

"A 200 OK response MUST be sent by a UAS for an INFO request with no message body if the INFO request was successfully received for an existing call."

Do add this feature take lot of work ? Thanks

This project is currently community maintained, which means nobody is actively working on it on dedicated time. If you can fix it, send a PR and drop a line here so it can be reviewed, otherwise you'll have to wait for someone with the skills and time to do it.

Hi all,

I have the same issue. Using the same PBX ... I just want to up this issue ... Hoping someone could do something ... Should be great.

Regards,

I saw, that some that have had the same issue had found a way so that work. The thread is dated of 2013, So i think that Mitel won't do anything. Unfortunately, I'm don't know how to do so. If It can help someone who wan't to work on this issue, here is the link to this issue ; https://community.jitsi.org/t/jitsi-users-sip-info-501-not-implemented/6452