| Summary: | ASTERISK-28265: PJSIP show channelstats incorrect information output | ||||
| Reporter: | Vyrva Igor (vigor1710) | Labels: | pjsip | ||
| Date Opened: | 2019-01-28 07:27:51.000-0600 | Date Closed: | 2019-02-18 06:27:57.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Resources/res_pjsip | ||
| Versions: | 16.1.1 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | CentOS 7 (7.6.1810) Kernel (4.20.3-1.el7.elrepo.x86_64) Asterisk 16 (16.1.1) | Attachments: | |||
| Description: | 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" | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2019-01-28 07:27:52.640-0600 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. By: George Joseph (gjoseph) 2019-02-15 09:20:12.010-0600 Being addressed in the linked issue. By: Vyrva Igor (vigor1710) 2019-02-18 06:22:00.363-0600 Why did you close my Task as a duplicate if the link goes to a task that was created Later? By: Asterisk Team (asteriskteam) 2019-02-18 06:22:01.049-0600 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Joshua C. Colp (jcolp) 2019-02-18 06:27:57.804-0600 sungtae has put a review up which fixes this already under that issue, so it was kept instead | ||||