Summary: | ASTERISK-27487: MESSAGE | ||
Reporter: | Slava Bendersky (volga629) | Labels: | |
Date Opened: | 2017-12-18 11:50:52.000-0600 | Date Closed: | 2017-12-18 11:55:05.000-0600 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | Applications/app_sms |
Versions: | 14.7.4 15.1.4 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | fedora server 27 x86_64 | Attachments: | |
Description: | Hello Everyone,
I would like ask add support for application/im-iscomposing+xml for MESSAGE method. Right now asterisk reply 415 which correct, but as example messages from desktop clients are never reach destination. Trace <--- Received SIP request (1280 bytes) from UDP:10.30.100.41:5060 ---> MESSAGE sip:8426-10@domain.tld;transport=TLS SIP/2.0 Via: SIP/2.0/UDP 10.30.100.41;branch=z9hG4bK9488.c0ec4c3ef4f1e6faa7d81e571616c317.0;i=5141 Via: SIP/2.0/TLS client_pub_ip:41989;received=client_pub_ip;branch=z9hG4bK-524287-1---1e014acadf548d74;rport=41989 Max-Forwards: 69 To: <sip:8426-10@domain.tld;transport=TLS> From: "User2"<sip:8422-10@domain.tld;transport=TLS>;tag=fe0d2110 Call-ID: UK5cCTtripL4PaLkL8w8Tg.. CSeq: 3 MESSAGE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/im-iscomposing+xml User-Agent: Z 5.1.7 r406dc01 Authorization: Digest username="8422-10",realm="asterisk",nonce="1513619362/9cf1a22b370ee177dd2f44a25d361b2f",uri="sip:8426-10@domain.tld;transport=TLS",response="a4cbe850f94d4e000a39c38a570f1d1f",cnonce="298ab8d05d3bba03084b21098f338df1",nc=00000001,qop=auth,algorithm=md5,opaque="7f1617a87efbff78" Allow-Events: presence, kpml, talk Content-Length: 321 <?xml version="1.0" encoding="UTF-8"?> <isComposing xmlns="urn:ietf:params:xml:ns:im-iscomposing" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ietf:params:xml:ns:im-composing iscomposing.xsd"> <state>idle</state> <refresh>120</refresh> </isComposing> <--- Transmitting SIP response (512 bytes) to UDP:10.30.100.41:5060 ---> SIP/2.0 415 Unsupported Media Type Via: SIP/2.0/UDP 10.30.100.41;rport=5060;received=10.30.100.41;branch=z9hG4bK9488.c0ec4c3ef4f1e6faa7d81e571616c317.0;i=5141 Via: SIP/2.0/TLS client_pub_ip:41989;rport=41989;received=client_pub_ip;branch=z9hG4bK-524287-1---1e014acadf548d74 Call-ID: UK5cCTtripL4PaLkL8w8Tg.. From: "User2" <sip:8422-10@domain.tld>;tag=fe0d2110 To: <sip:8426-10@domain.tld>;tag=z9hG4bK9488.c0ec4c3ef4f1e6faa7d81e571616c317.0 CSeq: 3 MESSAGE Server: Asterisk PBX 15.1.4 Content-Length: 0 | ||
Comments: | By: Asterisk Team (asteriskteam) 2017-12-18 11:50:53.395-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Slava Bendersky (volga629) 2017-12-18 11:52:49.722-0600 I think it rfc https://www.ietf.org/rfc/rfc3994.txt By: Joshua C. Colp (jcolp) 2017-12-18 11:54:57.169-0600 Features requests without patches are not accepted through the issue tracker. Features requests are openly discussed on the mailing lists, forums, and IRC [1]. Please see the Asterisk Issue Guidelines [2] for more information on feature request and patch submission. [1] http://asterisk.org/community/discuss [2] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines |