lazedo

@adubovikov Hello, tried 1.3.19 with same results. capture is being done by `heplify` in a freeswitch server and sent to a `heplify-server` i noticed that [homer-ui restricts the types](https://github.com/sipcapture/homer-ui/blob/master/src/app/qos.worker.ts#L349) it...

@adubovikov noticed no diff in the way homer-ui handles the rtcp packets. [type 207 is still not handled](https://github.com/sipcapture/homer-ui/blob/master/src/app/workers/qos.worker.ts#L360)

@adubovikov thanks for looking into this. [check previous comment](https://github.com/sipcapture/homer-app/issues/400#issuecomment-807849147) where i posted what was received from freeswitch and sent to heplify-server by heplify-client, the payload is from homer-app (using chrome...

@adubovikov this issue is related https://github.com/sipcapture/heplify/issues/197 the same packet contains `200`, `202` and `207`. `200` is overridden by `207` and that's why its not selected .

@adubovikov it is inserted in the db and retrieved but the type is 207 (the last in the packet). what's inserted in the db is not the `real` packet but...

changed decoder ProcessHEPPacket to this, seems to be working. ```code golang func (d *Decoder) ProcessHEPPacket(data []byte) { if config.Cfg.DiscardMethod != "" { h, err := DecodeHEP(data) if err == nil...

`org: 123free` also fails to get the groups and needs to be set as `org: '123free'` which might be not obvious to everybody, maybe adding a `note` about that.

@mihovilkolaric this is by design. your possible fix only allows the publishing of the routing key which in this case is useless. however, this will be taken in consideration when...

@arentrue i think the initial external validators may not be fully explained. we have draft3/draft4 schemas that validate data, and.., for business extensions (validate a customer in a database, ....)...

@arentrue thanks for the reply, but how would you validate a draft4+(custom for a single field)?