Paul Donald

All airplay versions (i.e. the specs) assume a 2 second realtime buffer. The apparent reason for this is backwards compatibility with the airport express: the device has limited memory, that...

I wanted to add something to this idea: namely, the ability to use key-files that can specify which sectors they apply to, which should accelerate, or obviate key-mapping. The idea...

https://copr.fedorainfracloud.org/coprs/ibotty/prometheus-exporters/

> In which versions of EPEL is this available? Didn't really understand your question but "all" seems an appropriate answer

Yes. I ran the upgrade on both 7 and 8 systems

Here's a few more: ``` heplify-server | [102649YWNlMjdiNTYyMjgyMmM3Yjg2NGM1OTE3MjRlYjk3ZTc 2020-03-11T13:10:27.432521Z {"protocolFamily":2,"protocol":17,"srcIp":"10.48.88.2","dstIp":"10.48.254.82","srcPort":64683,"dstPort":58043,"timeSeconds":1583932227,"timeUseconds":432521,"payloadType":5,"captureId":"101","capturePass":"asdf","correlation_id":"102649YWNlMjdiNTYyMjgyMmM3Yjg2NGM1OTE3MjRlYjk3ZTc"} {"node":"101","proto":"rtcp"} {"report_count":0,"type":200,"ssrc":925155192,"sender_information":{"ntp_timestamp_sec":3792921027,"ntp_timestamp_usec":1805565597,"rtp_timestamp":1347440,"packets":1539,"octets":240000},"report_blocks":[]}] heplify-server | heplify-server | 2020/03/11 13:10:30.084516 postgres.go:294: DBG [sql] COPY hep_proto_35_default(sid,create_date,protocol_header,data_header,raw) FROM STDIN heplify-server | heplify-server | [102649YWNlMjdiNTYyMjgyMmM3Yjg2NGM1OTE3MjRlYjk3ZTc...

To clarify: refactoring code is not a bad idea, but at this stage, I have in mind only the variables in logging output.

Well, partially, but here: #365 Will have to tackle the internal names at a later stage. Requires transitioning things that the Homer GUI may depend on.

Same assumption goes for: https://github.com/sipcapture/heplify/blob/1b2a80825bf4ef051337a8a746285346c7d992c3/decoder/correlator.go#L42

These standards do not mandate port ranges or string lengths for the `m=` or `a=` row: https://tools.ietf.org/html/rfc4566#section-5.14 https://tools.ietf.org/html/rfc2327#page-19 Also, the assumption is that the media type is `audio`. Possible types...