sipcapture / homer-view Goto Github PK

Adding a new URL filter for whitelisting multiple IP addresses will help show only the traffic for a specific segment of the call.

The heplify server is receiving RTCP messages for both streams, and we can see both of them on the Messages tab, but only one of them is showing up on the QoS tab.
We suspect there might be something that homer-view doesn't like from the second stream which is preventing it from showing up.
Note: this issue happens also on the QoS tab of the homer app.
I'm sending attached screenshots from both tabs as well as the exported pcaps.
Can you please review and confirm why is it not showing up?

Thanks

export_96616646.zip

Hi guys,

We have noticed that the new version of Homer-View, the one using Angular 10, is not working properly when run as prod.

The same software, with only a change in host URLs runs fine when run as Dev, but when run with --prod switch, it fails to load the JS files:

The JSON with data gets loaded correctly, as inspected through explorer, but the main issue seems to be with the above files.

We have tried tweaking this in a few ways, without success. Have you seen this before?

Adding new homer-view URL filters for capture_id and capture_agent_id will help isolate traffic to a specific capture node and avoid seeing duplicate messages.

When navigating to the Export section of homer-view, what should appear as images are showing as text instead of the intented images, e.g.

file_copy
cloud_download
share

Attached is a comparison between Chrome and Safari (no issues with Safari)

Scroll left or right, and the header row remains fixed while the vertical lines pointing to them scroll away to the left or right.....

It would be great if the "Session Info" that's seen in Homer 7.10.x could be incorporated in to homer-view. Here's a screenshot from a 7.10.16 instance for better clarification. Thanks!

... in three displayed fields taken from within a SIP packet.

e.g. for an OPTIONS packet which displays as follows:

These fields display correctly, they are derived from the HEP packet (I think):

We are trying to deploy the latest version of the View, with the proxy residing in the same container where View is running, but we get a 404 for /api/v3/auth

The installation was done from source, based on the README guide, and the View is started with:
ng serve --host=0.0.0.0 --disable-host-check

Recommend a new regex here.

https://regexr.com/3hpvt