-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Unable to see paStash messages (AudioCodes plugin) in Homer 10 #240
Comments
Today I found that one REGISTER message was recorded in Homer. Just one and subsequent REGISTERES were no longer recorded. |
@myrcinos Could you add a stdout {} to your output {} and check if you see any messages before the hep output? The log you see indicates that app_audiocodes was unable to find a 'complete' SIP message to send onward and process. |
@Dletta This is now my config file:
Here is what I got in the console:
If I set debug to true in the config file I can see SIP messages in the console, just part of it below:
Does it make any sense? |
Hi,
This is my second try with the following setup AudioCodes via Syslog to paStash -> Homer 10 (last time I tried with Homer 7). I installed a fresh Debian 12 VM with Docker and Homer 10 inside a container. I used docker compose as recommended. Homer and Grafana work fine, I can see test HEP messages from hepgen in Homer. Then I installed the AudioCodes filter plugin. It was installed in the global folder location:
I use basic config file copied from Github:
When I start paStash it seems to be fine. If I turn on Debug log level it complains about the missing plugin but it was already discussed in another issue and can be safely ignored.
When I make a test call, I get the following output in the console:
tcpdump shows that SYSLOG messages are being received on port UDP 514 from AudioCodes. However, if I run tcpdump withing the heplify-server container there is nothing on the destination port 9060:
The AudioCodes firmware version is:
7.40A.500.781
What am I doing wrong? Could you please help me troubleshoot this issue? I am happy to provide more details. Thank you.
The text was updated successfully, but these errors were encountered: