Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DrachtIO and Homer #61

Closed
haeferer opened this issue Nov 28, 2018 · 11 comments
Closed

DrachtIO and Homer #61

haeferer opened this issue Nov 28, 2018 · 11 comments

Comments

@haeferer
Copy link

Hi,

we are trying to get get HEP running. We had installed Homer5-Docker and the HEP3 Packages are reaching the container (port 9060).
But it seems homer does not even recognize these packages

Do you have a defined a enviroment in which homer integration does work?

@davehorton
Copy link
Collaborator

I want to make sure I understand the current state. You have configured the drachtio server to send HEP to your homer instance, and when you take a wireshark trace you can see that the drachtio server is in fact sending HEP to the expected IP:port. Yet you do not see the SIP transactions in homer.

Is that correct?

@haeferer
Copy link
Author

Yep exactly (using ngrep within kamailio instance)

@haeferer
Copy link
Author

Package starts with "HEP3.........................." and ends with the SIP Package content

@haeferer
Copy link
Author

We tried the Single Instance Version (docker run) and the Multi Instance Version (docker-compose). Result ist the same
Homer WebApp is working, but every panel is empty except a few stating : "Could not resolve all promises"

PS we are running docker for windows on windows 10

@davehorton
Copy link
Collaborator

It sounds like a homer problem. I'm not a homer expert, but one of the problems I faced in the past was that the cron job that needs to run to rotate the mysql tables that homer writes to, had not run / was not running. Thus the tables that homer wanted to write sip transactions to did not exist, and the writes failed.

Note sure if this is your problem, but I suggest logging into the mysql database, and listing the tables in the 'homer_data' database to see if you get what's expected. For instance, there should be a table named sip_capture_call_20181128. This is incoming HEP messages for sip invites would be written.

Here are the commands I used....note I was running homer in kubernetes, so the commands are different for pure docker

kubectl -n homer exec -ti homer-complete-163319440-kp88c -c homer-kamailio -- /bin/bash

mysql -u homer -p3DZcYXeyGLCY -h cloudsql.default.svc.cluster.local homer_data

mysql> show databases;
+---------------------+
| Database            |
+---------------------+
| information_schema  |
| homer_configuration |
| homer_data          |
| homer_statistic     |
+---------------------+
4 rows in set (0.00 sec)

mysql> use homer_data;

Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> show tables;
+-----------------------------------+
| Tables_in_homer_data              |
+-----------------------------------+
| isup_capture_all_20180115         |
| isup_capture_all_20180116         |
| isup_capture_all_20180117         |
| logs_capture                      |
| report_capture                    |
| rtcp_capture                      |
| rtcp_capture_all_20180115         |
| rtcp_capture_all_20180116         |
| rtcp_capture_all_20180117         |
| sip_capture_call_20180115         |
| sip_capture_call_20180116         |
| sip_capture_call_20180117         |
| sip_capture_registration_20180115 |
| sip_capture_registration_20180116 |
| sip_capture_registration_20180117 |
| sip_capture_rest_20180115         |
| sip_capture_rest_20180116         |
| sip_capture_rest_20180117         |
| webrtc_capture                    |
| webrtc_capture_all_20180115       |
| webrtc_capture_all_20180116       |
| webrtc_capture_all_20180117       |
+-----------------------------------+
22 rows in set (0.01 sec)

@haeferer
Copy link
Author

Thx a lot we will check this

@davehorton
Copy link
Collaborator

I recall around this time I opened this issue with homer-cron

https://github.com/sipcapture/homer-docker/issues/61

@ttitze2
Copy link

ttitze2 commented Nov 28, 2018

I just had a look at the database (after struggling with the Password until I realized that it is void). The tables "Capture_all_" are empty.

@davehorton
Copy link
Collaborator

are there any date-stamped tables, like the ones I show above? If not, you need to run the homer cron job. That is supposed to run daily, and creates the next 3 days worth of tables...

@ttitze2
Copy link

ttitze2 commented Nov 29, 2018

Yes! Tables
"logs_capture_all_20181127", … 30,
"sip_catpture_call_20181127",.. 30,
"sip_capture_rest_20171127",...30, etc. -- beginning from day before yesterday until tomorrow --
do not contain any records at all although when listening at port 9060 we can watch this sip-data arriving at the docker box running "heplify-service".

@haeferer
Copy link
Author

It seems that sipcapture/homer-docker:latest is very old (9 Months)
we have changed to sipcapture/homer-docker:master, and magically it works :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants