Re: [sr-dev] [kamailio/kamailio] Problem parsing content-type with numbers in multipart INVITE (#1053)
OK Thx for quick feedback! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1053#issuecomment-291439676___ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Problem parsing content-type with numbers in multipart INVITE (#1053)
Fixed by @camilleoudot and it will be backported. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1053#issuecomment-291246788___ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Problem parsing content-type with numbers in multipart INVITE (#1053)
Closed #1053 via #1055. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1053#event-1027108975___ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
[sr-dev] [kamailio/kamailio] Problem parsing content-type with numbers in multipart INVITE (#1053)
### Description When sending a multipart INVITE with a part having the following content type **application/vnd.3gpp.mcptt-info+xml** there is a parse error on content type header causing for eg we can't force rtpproxy to replace ports on a call leg. >From **parse_content.c** implementation It seems numbers are not accepted >inside a content type header. >(https://github.com/kamailio/kamailio/blob/master/src/core/parser/parse_content.c) > This might cause issues with MCPTT Rel 13 3GPP specs (http://www.arib.or.jp/english/html/overview/doc/STD-T63V12_20/5_Appendix/Rel13/24/24381-d20.pdf) or other content type defined by 3gpp ( eg of other content types defined in iana like https://www.iana.org/assignments/media-types/application/3gpp-ims+xml , etc.) See attached conversation in user-list http://lists.sip-router.org/pipermail/sr-users/2017-April/096594.html ### Troubleshooting See below attached logs generated by Kamailio when processing that INVITE and a sample of INVITE message causing the issue (cut from wireshark) Reproduction See attached INVITE or just send a multipart INVITE with a body part that has content type application/vnd.3gpp.mcptt-info+xml Log Messages See log messages generated when trying to force rtpproxy Apr 3 18:31:21 mcptt /usr/sbin/kamailio[3232]: INFO: