[Home]

Summary:ASTERISK-26251: "400 Bad Request" error on Siemens C470ip SMS via pjsip
Reporter:Dmitriy Serov (Demon)Labels:
Date Opened:2016-07-29 07:09:09Date Closed:2016-07-29 07:29:39
Priority:MajorRegression?
Status:Closed/CompleteComponents:Resources/res_pjsip
Versions:13.7.2 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) c470ip.txt
Description:Siemens C470IP sending SMS.
Asterisk answered "SIP/2.0 400 Bad Request"
Warning: 399 SIP "Unknown error 220030"

Similar ASTERISK-24242, but SDP too short.
Logs attached.
Comments:By: Asterisk Team (asteriskteam) 2016-07-29 07:09:10.403-0500

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: Joshua C. Colp (jcolp) 2016-07-29 07:29:39.366-0500

This is a bug in the device itself. It has provided the following SDP:

{noformat}
v=0
o=- 5010 9 IN IP4 109.60.xxx.xxx
s=Mapping
c=IN IP4 109.60.xxx.xxx
t=0 0
m=audio 5010 RTP/AVP 8 0 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
{noformat}

This is offering payloads 8, 0, and 101.
8 is ulaw.
0 is alaw.

101 is a dynamic payload that has no defined value, it is up to the rtpmap to provide what it actually is. It's likely telephone-event for DTMF but as the payload is dynamic it could be something else in practice. The device should be sending an rtpmap for it to say it is telephone-event.