Summary:	ASTERISK-28550: SDP maxptime
Reporter:	Gant Liu (Gant)	Labels:
Date Opened:	2019-09-23 01:49:12	Date Closed:	2019-09-30 08:44:16
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Resources/res_pjsip_sdp_rtp
Versions:	16.5.0	Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I have found that when the asterisk send an outbound message,in the SDP will add a media attribute "maxptime", this will cause some devices to behave incorrectly when sending RTP. Can we add one more parameter to control whether to carry it?
Comments:	By: Asterisk Team (asteriskteam) 2019-09-23 01:49:13.334-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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: George Joseph (gjoseph) 2019-09-23 06:22:48.881-0500 Can you give more details on the device that's behaving incorrectly and what the effect on the call is? By: Gant Liu (Gant) 2019-09-24 03:39:24.464-0500 Sorry, I am not very clear about the specific device model. It seems to be ZTE's device, and the result is that asterisk received repeated DTMF event. For example, if the user presses  DTMF key 123, we may received like this: 1112233 By: George Joseph (gjoseph) 2019-09-26 07:15:08.743-0500 Your issue is in the queue. Your patience is appreciated as a developer may work the issue when time and resources become available. Asterisk is an open source project and community members work the issues on a voluntary basis. You are welcome to develop your own patches and submit them to the project.[1] If you are not a programmer and you are in a hurry to see a patch provided then you might try rallying support on the Asterisk users mailing list or forums.[2] Another alternative is offering a bug bounty on the asterisk-dev mailing list.[3] Often a little incentive can go a long way. [1]: https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process [2]: http://www.asterisk.org/community/discuss [3]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties By: Gant Liu (Gant) 2019-09-29 20:37:31.572-0500 Thanks, I will be try to submit some patches for this project in future. By: Sean Bright (seanbright) 2019-09-30 08:44:16.343-0500 It is highly unlikely that this issue will be looked in to given the lack of information in the report. In order to move this along, we will need (at minimum): # A more detailed description of what is actually occurring # The relevant Asterisk configuration ({{pjsip.conf}}, {{rtp.conf}}, etc.) # PCAP files that capture both the SIP and the problematic RTP # The manufacturer, model and firmware version of the affected device. I am closing this issue until this additional information is available. Once you have the additional information, you can comment on this issue and it will automatically re-open. By: Julio Cesar Casullo (jccasullo) 2022-09-15 14:36:26.492-0500 I'm also having problems with maxptime=150. I couldn't make any calls to iPhone devices that had VoLTE enabled. By disabling the option on the devices, I was able to make calls normally. However, it is not always possible to deactivate, because we call distant customers. Apparently the problem is due to the value maxptime = 150. If you set maxptime = 120 the problem is solved. However, we were not able to do this natively on the system, just changing the source code and recompiling, something difficult to perform on running business systems.