This is a wrapper around callstats.io to encapsulate common logic used in jvb and jigasi.
To use it AbstractStatsPeriodicRunnable needs to be extended passing to the constructor:
- o: Conference or Call
- period: the reporting interval
- statsService: the stats service created using the StatsServiceFactory
- conferenceJid: A jid of the conference name@conference.domain.com or name@conference.tenant.domain.com
- conferenceIDPrefix: The conference prefix, this is the domain of the deployment.
- initiatorID: The initiator for these stats, a string representing either the bridge or jigasi. And later this is seen in callstats.io dashboard.
When reporting to callstats.io we will report sideId as tenant in case of jid of type name@conference.tenant.domain.com or / in case of name@conference.domain.com
and all this if conferenceIDPrefix is domain.com.
There is a conference identification (conferenceId), which is the string used to search in callstats.io dashboard.
- The conferenceId will be
domain.com/tenant/nameif we use jid:name@conference.tenant.domain.comandconferenceIDPrefixisdomain.com. - If there is no
conferenceIDPrefixpassed we will set conference identification to be justnameand siteId will be/; - If there is
conferenceIDPrefixbut the jid does not contain this configure prefix,name@someother.d.comthen conference identification will be justdomain.com/name.