Yealink Forums

Full Version: Confirm current details of VQ RTCP-XR sendings
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello,

As other threads show it, I'm currently digging in VQ RTCP-XR feature.

For my very first tests, I was a bit surprised to capture that when a phone is registered to a SIP B2BUA, it would sent to this B2BUA its VQ RTCP-XR reports: I expected those reports to be directly sent to whatever host I configured.

Let me rephrase this:
My phone is registered to a B2BUA.
A collector is alive and waiting for reports, on the same network but a different address.
At the end of a call, my phone sends to its B2BUA, a PUBLISH message like this
PUBLISH sip:foo@1.2.3.4 SIP/2.0
where:
foo is account.X.vq_rtcpxr.collector_name
1.2.3.4 is account.X.vq_rtcpxr.collector_server_host.

I expected this very same message to be directly sent to Collector (my B2BUA does not support incoming unsollicited PUBLISH messages).

Is it correct behaviour ?
My testing where done with firmware 46.81.0.25.

Best regards
(02-16-2017 03:24 PM)oliv Wrote: [ -> ]Hello,

As other threads show it, I'm currently digging in VQ RTCP-XR feature.

For my very first tests, I was a bit surprised to capture that when a phone is registered to a SIP B2BUA, it would sent to this B2BUA its VQ RTCP-XR reports: I expected those reports to be directly sent to whatever host I configured.

Let me rephrase this:
My phone is registered to a B2BUA.
A collector is alive and waiting for reports, on the same network but a different address.
At the end of a call, my phone sends to its B2BUA, a PUBLISH message like this
PUBLISH sip:foo@1.2.3.4 SIP/2.0
where:
foo is account.X.vq_rtcpxr.collector_name
1.2.3.4 is account.X.vq_rtcpxr.collector_server_host.

I expected this very same message to be directly sent to Collector (my B2BUA does not support incoming unsollicited PUBLISH messages).

Is it correct behaviour ?
My testing where done with firmware 46.81.0.25.

Best regards

May I add the following:
From a very old habit, I configure my phones with:
account.1.outbound_proxy_enable = 1
account.1.outbound_host = 4.5.6.7

where 4.5.6.7 is my B2BUA address.
Maybe chosen destination address (for PUBLISH messages) comes from this specific setting which somehow "overwrites" vq_rtcpxr settings ?

I add the opportunity to test and disabling SIP outbound proxy restored expected behaviour.
Sorry for the noise
The collector address only up to the account.X.vq_rtcpxr.collector_server_host.
Never mind which parameter configured in account.x.outbound_host string, it don't influence the collector's address.
Reference URL's