[asterisk-bugs] [JIRA] (ASTERISK-28265) PJSIP chow channelstats incorrect information output

Asterisk Team (JIRA) noreply at issues.asterisk.org
Mon Jan 28 07:28:47 CST 2019


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

Asterisk Team commented on ASTERISK-28265:
------------------------------------------

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.

> PJSIP chow channelstats incorrect information output
> ----------------------------------------------------
>
>                 Key: ASTERISK-28265
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28265
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 16.1.1
>         Environment: CentOS 7 (7.6.1810)
> Kernel (4.20.3-1.el7.elrepo.x86_64)
> Asterisk 16 (16.1.1)
>            Reporter: Vyrva Igor
>              Labels: pjsip
>
> There are problems when using the "pjsip show channelstats" command in CLI
> While we making first call (222->666), this command displays
> pjsip show channelstats
>                                              ...........Receive......... .........Transmit..........
>  BridgeId ChannelId ........ UpTime.. Codec.   Count    Lost Pct  Jitter   Count    Lost Pct  Jitter RTT....
>  ===========================================================================================================
>           222-00000047       00:00:02 alaw       90       0    0   0.000     53       0    0   0.000   0.000
>  PJSIP/666-00000048 not valid
> Objects found: 2
> After the recipient is answer (picked up the phone):
> pjsip show channelstats
>                                              ...........Receive......... .........Transmit..........
>  BridgeId ChannelId ........ UpTime.. Codec.   Count    Lost Pct  Jitter   Count    Lost Pct  Jitter RTT....
>  ===========================================================================================================
>  37805376 222-00000047       00:00:13 alaw      464       0    0   0.000    428       0    0   0.000   0.000
>  37805376 666-00000048       00:00:13 alaw        4       0    0   0.000      1       0    0   0.002   0.000
> Objects found: 2
> After that we make the second call (333 → 555), before recipient picked up the phone:
> pjsip show channelstats
>                                              ...........Receive......... .........Transmit..........
>  BridgeId ChannelId ........ UpTime.. Codec.   Count    Lost Pct  Jitter   Count    Lost Pct  Jitter RTT....
>  ===========================================================================================================
>           333-00000049       00:00:03 ulaw      135       0    0   0.000    125       0    0   0.016   0.000
>  PJSIP/555-0000004a not valid
> Objects found: 4
> After the 555 is answer:
> pjsip show channelstats
>                                              ...........Receive......... .........Transmit..........
>  BridgeId ChannelId ........ UpTime.. Codec.   Count    Lost Pct  Jitter   Count    Lost Pct  Jitter RTT....
>  ===========================================================================================================
>  37805376 222-00000047       00:03:41 alaw      464       0    0   0.000    428       0    0   0.000   0.000
>  37805376 666-00000048       00:03:41 alaw        4       0    0   0.000      1       0    0   0.002   0.000
>  baf1c888 333-00000049       00:00:10 ulaw      502       0    0   0.000    459       0    0   0.015   0.019
>  baf1c888 555-0000004a       00:00:10 alaw      109       0    0   0.000    142       0    0   0.000   0.000
> Objects found: 4
> As seen above, we do not see in the response of the command the conversations currently active. 
> With two simultaneous calls (222 → 666, 333 → 555), we don't see all the information:
> pjsip show channelstats
>                                              ...........Receive......... .........Transmit..........
>  BridgeId ChannelId ........ UpTime.. Codec.   Count    Lost Pct  Jitter   Count    Lost Pct  Jitter RTT....
>  ===========================================================================================================
>           222-00000052       00:00:06 alaw      279       0    0   0.000    236       0    0   0.000   0.000
>           333-00000050       00:00:08 ulaw      411       0    0   0.000    401       1    0   0.015   0.019
>  PJSIP/555-00000051 not valid
> Objects found: 4
> It is more correct if this command will always output information on all current channels, similarly "sip chow channelstats"



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



More information about the asterisk-bugs mailing list