05-19-2015, 09:10 AM
Hello,
We are testing the new RTCP collector option in v73, and are having a conflict with a previous change made to correct BLF issues when using DNS-SRV.
The DNS-SRV issue with BLF was that it would not fail back to the primary server for the BLF subscription, unless we added in our registration server as the outbound proxy as well.
When using the outbound proxy, the PUBLISH messages sent by the phone are directed at the 'proxy' as well, but we need them to be sent out to a totally separate server. While this does seem like correct behavior, it puts in a position of either choosing between RTCP or BLF, or creating a whole new layer to our infrastructure that actually provides a true proxy service.
Has anyone else worked with the RTCP collector and\or outbound proxies that can provide some input? I will be testing the BLF failback with DNS-SRV on the new v73 firmware to see if the original problem is resolved, and will report back here with results.
Thanks!
We are testing the new RTCP collector option in v73, and are having a conflict with a previous change made to correct BLF issues when using DNS-SRV.
The DNS-SRV issue with BLF was that it would not fail back to the primary server for the BLF subscription, unless we added in our registration server as the outbound proxy as well.
When using the outbound proxy, the PUBLISH messages sent by the phone are directed at the 'proxy' as well, but we need them to be sent out to a totally separate server. While this does seem like correct behavior, it puts in a position of either choosing between RTCP or BLF, or creating a whole new layer to our infrastructure that actually provides a true proxy service.
Has anyone else worked with the RTCP collector and\or outbound proxies that can provide some input? I will be testing the BLF failback with DNS-SRV on the new v73 firmware to see if the original problem is resolved, and will report back here with results.
Thanks!