[asterisk-bugs] [JIRA] (ASTERISK-20650) Asterisk resets ptime value in 200 OK response

Mark Michelson (JIRA) noreply at issues.asterisk.org
Tue Feb 5 17:15:59 CST 2013


    [ https://issues.asterisk.org/jira/browse/ASTERISK-20650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202606#comment-202606 ] 

Mark Michelson commented on ASTERISK-20650:
-------------------------------------------

I think the renaming of this issue is not correct.

The incoming leg into Asterisk is negotiated to have a ptime of 30. The outgoing leg from Asterisk is negotiated to have a ptime of 10. On the incoming call leg, the audio from the far end comes in 30 ms segments (good). Asterisk, however, sends the RTP in 10 ms segments (bad). On the outgoing leg, Both Asterisk and the far end send their audio in 10 ms segments (good). The issue is that Asterisk, despite claiming a ptime of 30 on the incoming leg, is sending audio in 10 ms segments.

I'm going to set up some local tests and see if I can reproduce the issue and come up with a fix.
                
> Asterisk resets ptime value in 200 OK response
> ----------------------------------------------
>
>                 Key: ASTERISK-20650
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20650
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General, Resources/res_fax
>    Affects Versions: 1.8.17.0
>            Reporter: Maciej Krajewski
>            Severity: Critical
>         Attachments: ast_config.zip, Asterisk_1_4_26_RTP_packetization.pcap, debug_5-autoframing_yes.cap.gz, debug_5-autoframing_yes.log, tmptk_20121102_1527_g02_editcap.cap, tmptk_20121105_1155_g03_edit_filtr.cap
>
>
> Today I have found a problem concerning asterisk 1.8.X
> I've migrated one of my servers from old version of asterisk 1.4 branch to the newest 1.8.
> Everything works fine, but faxes has stopped working.
> I've made some research and what I have found is that asterisk 1.8 has some problems with transcoding ptime, it simply does not do this, Astersik 1.4 was coping with this.
> I've attached the cap file where one of my legs is negotiating connection with ptime 10, the other one with ptime 20.
> However if you look at the payload of RTP packets it is 10 ms every where.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list