[asterisk-bugs] [JIRA] (ASTERISK-20806) Strange values reported by CHANNEL(rtpqos, audio, all) - outbound call

[Leonard Andre (JIRA)]

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

Leonard Andre updated ASTERISK-20806:
-------------------------------------

    Status: Waiting for Feedback  (was: Waiting for Feedback)

1) Does this occur on all outbound calls? --> YES

2] Is SIP RTT populated appropriately on all inbound calls? --> YES

4] Can you explain how to reproduce this, and do you know if it happens on any other version?
--> I'm using asterisk via freepbx distro
--> issue also after an upgrade to version 1.18.19
--> code use in extensions_override_freepbx.conf:
[macro-hangupcall]
exten => s,1,System(echo "Call Ended at ${STRFTIME(,,%c)} to {CALLERID(num)} ${CHANNEL(rtpqos,audio,all)}" >> /var/spool/asterisk/tmp/callended.log)
...

5] What SIP endpoint is in use and what model/firmware version are you using? --> Internal phones are SNOM 300 & Snom 320

                
> Strange values reported by CHANNEL(rtpqos,audio,all) - outbound call 
> ---------------------------------------------------------------------
>
>                 Key: ASTERISK-20806
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20806
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.18.0
>         Environment: CentOS 6.2
>            Reporter: Leonard Andre
>            Assignee: Leonard Andre
>            Severity: Minor
>
> the reported rtt value is "strange" for outbound calls.
> (measures logged from [macro-hangupcall])
> Example: 
> ssrc=1888837987;themssrc=2540558895;lp=0;rxjitter=0.001343;rxcount=6207;txjitter=0.000000;txcount=6220;rlp=0;rtt=65535.005000
> ssrc=1533549072;themssrc=399931211;lp=0;rxjitter=0.001413;rxcount=20608;txjitter=0.000000;txcount=20627;rlp=0;rtt=65535.389000

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira