That is exactly the issue here - missing Message-ID header in Linphone and using Call-ID instead. Thank you for detailed answer and notes about the possible IMDN looping issue. Best regards, Marko ----- Original Message ----- From: "Sergey Safarov" <s.safarov@gmail.com> To: "freeswitch-users" <freeswitch-users@lists.freeswitch.org> Sent: Wednesday, November 15, 2017 7:07:39 PM Subject: Re: [Freeswitch-users] mod_sms chat messages delivery notification Let me guess - you are using linphone with [ http://www.linphone.org/news/54/26/IM-Delivery-status-now-available-in-Linph... | not fully implemented RFC5438 ] RFC requires to use Message-ID for such purpose [ https://tools.ietf.org/html/rfc5438#section-6.3 | https://tools.ietf.org/html/rfc5438#section-6.3 ] The IM Sender MUST include the Message-ID header field in the IM for which he wishes to receive an IMDN. [ https://tools.ietf.org/html/rfc5438#section-7.1.1.1 | https://tools.ietf.org/html/rfc5438#section-7.1.1.1 ] If the IM Sender requests the reception of IMDNs, the IM Sender MUST include a Message-ID header field. On one project customer already have issue with IMDN looping because linphone non RFC compliant. Customer resolved issue by implemented RFC compliant IMDN in linphone. Sergey ср, 15 нояб. 2017 г. в 14:52, Marko Djuric < [ mailto:Marko.Djuric@amphinicy.com | Marko.Djuric@amphinicy.com ] >: Looping should be avoided by checking the X-FS-Sending-Message header. Still, changing the Call-ID may present another set of issues. Is it possible to read the Call-ID from the chatplan, in the similar manner how it's done in dialplan, other than parsing it from SIP trace? Thank you for response, Marko
-----Original Message----- From: Sergey Safarov [mailto: [ mailto:s.safarov@gmail.com | s.safarov@gmail.com ] ] Sent: Tuesday, November 14, 2017 4:24 PM To: FreeSWITCH Users Help < [ mailto:freeswitch-users@lists.freeswitch.org | freeswitch-users@lists.freeswitch.org ] > Subject: Re: [Freeswitch-users] mod_sms chat messages delivery notification
My experiance say that Call-ID change is required to prevent message loops. Looks like need to use other header or field to correlate messages.
вт, 14 нояб. 2017 г., 13:44 Marko Djuric < [ mailto:Marko.Djuric@amphinicy.com | Marko.Djuric@amphinicy.com ] <mailto: [ mailto:Marko.Djuric@amphinicy.com | Marko.Djuric@amphinicy.com ] > >:
Hi all,
We're using mod_sms for SIP SIMPLE messaging with delivery notifications (message/imdn+xml). The Call-ID is changed in the chatplan, and this causes issues with matching the delivery notifications to the original message.
Changing the Call-ID itself is not an issue, but I'm wondering if it is possible to read the original Call-ID and/or manually set the Call-ID in the chatplan.
The message:getHeader("sip_call_id") does not contain the Call-ID. My understanding is that this is due to skip_global_process=false variable set by mod_sms. Setting the sip_call_id variable also does not produce a desired effect, as it is added as another header instead of setting the Call-ID one.
The question is - how to match the messages before and after the chatplan?
Any help is appreciated.
Thank you! Marko
__________________________________________________________ _______________ Professional FreeSWITCH Consulting Services: [ mailto:consulting@freeswitch.org | consulting@freeswitch.org ] <mailto: [ mailto:consulting@freeswitch.org | consulting@freeswitch.org ] > [ http://www.freeswitchsolutions.com/ | http://www.freeswitchsolutions.com ]
Official FreeSWITCH Sites [ http://www.freeswitch.org/ | http://www.freeswitch.org ] [ http://confluence.freeswitch.org/ | http://confluence.freeswitch.org ] [ http://www.cluecon.com/ | http://www.cluecon.com ]
FreeSWITCH-users mailing list [ mailto:FreeSWITCH-users@lists.freeswitch.org | FreeSWITCH-users@lists.freeswitch.org ] <mailto: [ mailto:FreeSWITCH- | FreeSWITCH- ] [ mailto:users@lists.freeswitch.org | users@lists.freeswitch.org ] > [ http://lists.freeswitch.org/mailman/listinfo/freeswitch-users | http://lists.freeswitch.org/mailman/listinfo/freeswitch-users ] UNSUBSCRIBE: [ http://lists.freeswitch.org/mailman/options/freeswitch- | http://lists.freeswitch.org/mailman/options/freeswitch- ] users [ http://www.freeswitch.org/ | http://www.freeswitch.org ]
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: [ mailto:consulting@freeswitch.org | consulting@freeswitch.org ] [ http://www.freeswitchsolutions.com/ | http://www.freeswitchsolutions.com ] Official FreeSWITCH Sites [ http://www.freeswitch.org/ | http://www.freeswitch.org ] [ http://confluence.freeswitch.org/ | http://confluence.freeswitch.org ] [ http://www.cluecon.com/ | http://www.cluecon.com ] FreeSWITCH-users mailing list [ mailto:FreeSWITCH-users@lists.freeswitch.org | FreeSWITCH-users@lists.freeswitch.org ] [ http://lists.freeswitch.org/mailman/listinfo/freeswitch-users | http://lists.freeswitch.org/mailman/listinfo/freeswitch-users ] UNSUBSCRIBE: [ http://lists.freeswitch.org/mailman/options/freeswitch-users | http://lists.freeswitch.org/mailman/options/freeswitch-users ] [ http://www.freeswitch.org/ | http://www.freeswitch.org ] _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org