[asterisk-bugs] [JIRA] (ASTERISK-28966) chan_pjsip: Interaction with provider re-INVITE and RTP causes codec flip-flop

Asterisk Team (JIRA) noreply at issues.asterisk.org
Wed Jul 15 12:00:26 CDT 2020


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

Asterisk Team commented on ASTERISK-28966:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> chan_pjsip: Interaction with provider re-INVITE and RTP causes codec flip-flop
> ------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28966
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28966
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 16.10.0
>         Environment: ubuntu 18.04, docker, asterisk 16.10
>            Reporter: Robert Sutton
>            Assignee: Robert Sutton
>            Severity: Minor
>              Labels: fax, webrtc
>
> we had rtp_symmetric set to "no" on the trunk endpoint
> It seems that asterisk and our up stream sip provider got into a feed back loop as can be seen below. 
> This is just a small snippet of this, in 90 seconds this line was logged 600+ times across 3 channels.
> This was detected because the system was failing to bridge channels, it may not be the cause of failing to bridge, but either way it is a problem.
> {noformat}
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of ulaw on channel 'PJSIP/trunk-00000f60' when we're sending 'alaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of alaw on channel 'PJSIP/trunk-00000f60' when we're sending 'ulaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of ulaw on channel 'PJSIP/trunk-00000f60' when we're sending 'alaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of alaw on channel 'PJSIP/trunk-00000f60' when we're sending 'ulaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of ulaw on channel 'PJSIP/trunk-00000f60' when we're sending 'alaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of alaw on channel 'PJSIP/trunk-00000f60' when we're sending 'ulaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of ulaw on channel 'PJSIP/trunk-00000f60' when we're sending 'alaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of alaw on channel 'PJSIP/trunk-00000f60' when we're sending 'ulaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of ulaw on channel 'PJSIP/trunk-00000f60' when we're sending 'alaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of alaw on channel 'PJSIP/trunk-00000f60' when we're sending 'ulaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of ulaw on channel 'PJSIP/trunk-00000f60' when we're sending 'alaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of alaw on channel 'PJSIP/trunk-00000f60' when we're sending 'ulaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of ulaw on channel 'PJSIP/trunk-00000f60' when we're sending 'alaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of alaw on channel 'PJSIP/trunk-00000f60' when we're sending 'ulaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of ulaw on channel 'PJSIP/trunk-00000f60' when we're sending 'alaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of alaw on channel 'PJSIP/trunk-00000f60' when we're sending 'ulaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of ulaw on channel 'PJSIP/trunk-00000f60' when we're sending 'alaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of alaw on channel 'PJSIP/trunk-00000f60' when we're sending 'ulaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of ulaw on channel 'PJSIP/trunk-00000f60' when we're sending 'alaw', switching to match
> Jun 29 10:11:34 chan_pjsip.c:878 chan_pjsip_read_stream: Oooh, got a frame with format of alaw on channel 'PJSIP/trunk-00000f60' when we're sending 'ulaw', switching to match
> {noformat}



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



More information about the asterisk-bugs mailing list