Hi asterisk-users,
We have recently moved to the 13.x branch of Asterisk from 11.x, and we're
trying to correlate CDR records from multiple-legs for billing purposes.
As part of this change we have added 'linkedid' to our CDR table schema in an
attempt to join the multiple records into one
Thanks for sharing this, Alex. It sounds like TURN, as a media repeater,
wouldn't work if the media must be secured (via SRTP). Is that right?
On Wed, 3 Oct 2018, 3:17 pm alex epshteyn, wrote:
> WebRTC requires a few specific things to be in place. We have blog posts
> that talk about WebRTC
WebRTC requires a few specific things to be in place. We have blog posts that
talk about WebRTC based Thirdlane Connect, but most of the information applies
to WebRTC applications in general.
https://www.thirdlane.com/blog/get-up-and-running-with-thirdlane-connect
@Olivior
I agree that seting up WebRTC is hard, however when done it is smooth to
use. For replication you can build RPMs with working configurations.
Regarding stability, it is not being used widly, so can't say it is mature.
However we have no complain so far regarding audio or connectivity.
All;
A few years back, we put a heck of a lot of effort into developing a
software package to analyze call queue data that we want to open source.
It's a pretty good package and I would like to dust it off and resurrect it.
What I need to do that is have sample call queue data to test with.
@Nasir:
Thanks for replying here.
Did you met in your deployments, the kind of stability issues Carlos
reported earlier ?
Le sam. 29 sept. 2018 à 13:32, Nasir Iqbal a
écrit :
> Hi Olivior,
>
> We have recently worked on a WebRTC based agent panel. As based on my
> experience I think that
