-
-
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
HEP relay/forwarder not working #111
Comments
Could you try adding |
Do I add to the input{} or udp{} section? I have tried both and it doesn't seem to have made a difference, I have not done a capture yet to see the contents. Also, as a comparison, the following udp forwarder solution using socat seems to work as expected:
|
With input as:
The output UDP packet contents is the same JSON formatted contents:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm trying to set up paStash as a HEP relat/forwarder so that it will send HEP packets (from rtpproxy 2.2.0) to two separate Homer servers.
I am following this guide:
https://github.com/sipcapture/paStash/wiki/Example:-HEP-Relay
and have configured it to run as a service, as per:
https://github.com/sipcapture/paStash/wiki/pastash-service#running-as-systemd-service
I am using the following paStash config:
Note that I'm using UDP as:
My node version is
v16.14.1
running on a CentOS 7.9 machine.pastash seems to be working in that it receives the input and sends an output to both Homer server IPs.
The original UDP HEP packet contents is:
However, the format of the output does not seem correct. When I capture the packets and view the output UDP stream, the contents are:
So it seems that paStash is converting the message and encoding it in a JSON format.
I expect paStash to be relaying/forwarding the HEP UDP contents untouched and relay it on to the destination Homer server IP.
The text was updated successfully, but these errors were encountered: