Hello,
I'm checking the imc module and it appears that imc sends all messages with hard-coded content type header so if client sends an application/im-iscomposing+xml message, other clients receives the message with content-type text/plain which is very confusing.
I think the right behavior is to take the content-type header from the original message and use it in the messages imc sends.
Is there a workaround that might help me achieve that?
Hello,
there seems to be no configuration parameter to achieve this. Of course, the module can be extended e.g. with a pull request. Probably worth to check also what the RFCs say in this regard, but in all cases if could be extended if its configurable for example by a module parameter.
Cheers,
Henning
-- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.comhttps://gilawa.com/
From: sr-users sr-users-bounces@lists.kamailio.org On Behalf Of Joey Golan Sent: Sunday, November 27, 2022 10:31 AM To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org Subject: [SR-Users] imc sends all messages with Content-Type: text/plain
Hello,
I'm checking the imc module and it appears that imc sends all messages with hard-coded content type header so if client sends an application/im-iscomposing+xml message, other clients receives the message with content-type text/plain which is very confusing.
I think the right behavior is to take the content-type header from the original message and use it in the messages imc sends.
Is there a workaround that might help me achieve that?
Hello,
IMC does not implement any rfc, is kind of custom implementation for a instant messaging conferencing room, inspired from IRC, with /command-like control. From IETF, I think that only MSRP has specs about group chatting, nothing that is defined for MESSAGE requests.
Anyhow, makes sense to propagate the content type, the IMC did not get proper attention for long time, no much interest around. It defaulted to text/plain because of the control commands. But it can be updated to propagate content type, the module is open for contributions/enhancements.
Cheers, Daniel
On 28.11.22 09:12, Henning Westerholt wrote:
Hi,
I did that and added few more enhancements. 1. propagate content-type header 2. add the option to modify member role 3. added support to db_mode. all changes are synch to db in case db_mode is set to 2.
pull request #3291 was created.
Thanks, Joey.
On Mon, Nov 28, 2022 at 11:44 AM Daniel-Constantin Mierla miconda@gmail.com wrote:
-
Daniel-Constantin Mierla -
Henning Westerholt -
Joey Golan