[asterisk-bugs] [JIRA] (ASTERISK-25470) SDP version increased when no change in SDP on 183 session progress retransmit

Rusty Newton (JIRA) noreply at issues.asterisk.org
Wed Oct 21 09:29:33 CDT 2015


     [ https://issues.asterisk.org/jira/browse/ASTERISK-25470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-25470:
------------------------------------

    Assignee: Morten Tryfoss  (was: Unassigned)
      Status: Waiting for Feedback  (was: Triage)

Many reporters attempt to provide information on how to reproduce an issue. Often, probably more often than not the information does not lead us to being able to reproduce the issue.

Often a debug log can provide us further detail about how Asterisk got into the problematic situation. It can help a developer understand the chain of events involved.

As simple as your suggested fix is - we can't accept inline patches due to licensing. You must submit a patch marked contribution after having signed the submission agreement.

Please submit the patch on here  and post it to Gerrit if you will - then others can review it and help verify the fix is appropriate. Thanks!

[Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]

> SDP version increased when no change in SDP on 183 session progress retransmit
> ------------------------------------------------------------------------------
>
>                 Key: ASTERISK-25470
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25470
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.5.0, 13.6.0
>         Environment: Centos 6
>            Reporter: Morten Tryfoss
>            Assignee: Morten Tryfoss
>            Severity: Minor
>
> 183 is retransmitted by Asterisk every 60 seconds. The version is bumped even if there are no change in the SDP.
> Some equipment terminates the call because of this.
> We had a similar error like this earlier, but then asterisk bumped the version on the 200 OK after a 183 session progress.
> Reproduce like this:
> {noformat}
> progressinband=yes
> {noformat}
> {noformat}
> exten => 200,1,Progress
> exten => 200,n,Wait(65)
> {noformat}
> First SDP:
> {noformat}
> v=0 
> o=root 179570363 179570363 IN IP4 192.168.1.50 
> s=Nordicom 
> c=IN IP4 192.168.1.50 
> t=0 0 
> m=audio 12914 RTP/AVP 8 97 
> a=rtpmap:8 PCMA/8000 
> a=rtpmap:97 telephone-event/8000 
> a=fmtp:97 0-16 
> a=ptime:20 
> a=maxptime:150 
> a=sendrecv 
> {noformat}
> Second:
> {noformat}
> v=0 
> o=root 179570363 179570364 IN IP4 192.168.1.50 
> s=Nordicom 
> c=IN IP4 192.168.1.50 
> t=0 0 
> m=audio 12914 RTP/AVP 8 97 
> a=rtpmap:8 PCMA/8000 
> a=rtpmap:97 telephone-event/8000 
> a=fmtp:97 0-16 
> a=ptime:20 
> a=maxptime:150 
> a=sendrecv 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list