[asterisk-bugs] [JIRA] (ASTERISK-26860) Upon RTCP reception, netsock2.c:210 ast_sockaddr_split_hostport: Port missing in (null)

[Joshua Colp (JIRA)]

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

Joshua Colp commented on ASTERISK-26860:
----------------------------------------

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. 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



> Upon RTCP reception, netsock2.c:210 ast_sockaddr_split_hostport: Port missing in (null)
> ---------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26860
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26860
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.14.0
>         Environment: CentOS7
>            Reporter: Evers Lab
>            Assignee: Evers Lab
>            Severity: Minor
>      Target Release: 13.16.0, 14.5.0
>
>         Attachments: conf_and_verbose.txt
>
>
> When the call arrives to the Queue and listens to music on hold, the console continually gives an error. When the agent answers the call, the error stops
> [Edit by Rusty - adding Sean Bright's reproduction guide below]
> This is fairly easy to duplicate with Asterisk 13 from git:
> {{extensions.conf:}}
> {noformat}
> [just-moh]
> exten => 1234,1,Answer()
> exten => 1234,n,MusicOnHold()
> {noformat}
> {{Asterisk CLI:}}
> {noformat}
> *CLI> channel originate PJSIP/some-endpoint extension 1234 at just-moh
> {noformat}
> Answer {{some-endpoint}} and place the call on hold. Every time Asterisk receives an RTCP packet, you'll see this error.



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