[OpenSIPS-Users] Opensips 3.4 Not sending hep to homer server
Vincent Horst
vincent.horst at ehvc.nl
Tue Sep 26 10:27:56 UTC 2023
Thanks @Michel,
hep socket is indeed the local host.
step I missed, installing heplify agent on the opensips system.
Forward the received packets towards Homer :)
case closed.
Vincent
Op di 26 sep 2023 om 08:21 schreef Michel crans <mcrans at gmail.com>:
> If you're not seeing any packets received on the Homer server, there could
> be several reasons for this issue. Let's go through some troubleshooting
> steps:
>
> 1.
>
> Check Network Connectivity:
> - Ensure that there is network connectivity between your OpenSIPS
> server and the Homer server. You should be able to ping the Homer server
> from the OpenSIPS server.
> 2.
>
> Homer Server Configuration:
> - Verify that your Homer server is correctly configured to receive HEP
> packets on the specified IP and port (in this case, 127.0.0.1:6061).
> Check Homer's logs for any incoming connection attempts or errors.
> 3.
>
> Socket Configuration:
> - It seems you are using 127.0.0.1 as the IP address in your socket
> configuration (socket=hep_udp:127.0.0.1:6061). This means OpenSIPS
> will send HEP packets to localhost (the same server it's running on).
> Ensure that this is the correct configuration. If Homer is on a different
> server, you should use the Homer server's IP address instead.
> 4.
>
> Firewall and Security Rules:
> - Make sure that there are no firewall rules or security policies
> blocking traffic on the specified HEP port (6061) or the network interface
> being used for communication.
> 5.
>
> Logging and Debugging:
> - Enable verbose logging in OpenSIPS to see if there are any error
> messages related to HEP. You can do this by setting the log_level
> parameter in your OpenSIPS configuration file.
>
> cfgCopy code
> modparam("log", "log_level", 3)
>
> This will increase the logging verbosity, and you can check the
> OpenSIPS logs for any relevant error messages.
> 6.
>
> Verify Route Execution:
> - Ensure that your route[to_homer] block is being executed when you
> expect it to. You can add additional log messages in this block to verify
> that it's being triggered.
> 7.
>
> Check HEP Configuration:
> - Review your HEP configuration parameters, such as hep_id and trace_id,
> to ensure they are correctly set. Make sure they match the configuration on
> the Homer server.
> 8.
>
> Firewall on Homer Server:
> - Check if there is any firewall or security software running on the
> Homer server that might be blocking incoming HEP packets.
> 9.
>
> Homer Server Logs:
> - Examine the logs on your Homer server to see if there are any error
> messages or indications of failed connections.
> 10.
>
> Packet Capture:
> - You can use tools like Wireshark to capture network traffic on the
> OpenSIPS server and check if the HEP packets are actually being sent. This
> can help you confirm whether the issue is with OpenSIPS or the network.
>
> By systematically going through these troubleshooting steps, you should be
> able to identify the root cause of why OpenSIPS is not sending HEP packets
> to your Homer server. Remember to make configuration adjustments as needed
> to match your specific network setup and requirements.
>
> Op ma 25 sep 2023 om 22:34 schreef Vincent Horst via Users <
> users at lists.opensips.org>:
>
>> Hi All,
>>
>> I have a issue where opensips is not sending the hep files towards homer.
>> I have used a manual and have add below to the .cfg file.
>>
>> Sockets: (It is unclear for my why I should put here the local adres,
>> when I put the remote IP of homer, I get an error in the config:
>> socket=hep_udp:127.0.0.1:6061
>> socket=hep_tcp:127.0.0.1:6061
>> If I remove them from the config the hep module gives an error.
>>
>> Second part in the .cfg:
>> ### Configure an HEP Endpoint
>> loadmodule "proto_hep.so"
>> modparam("proto_hep", "hep_id", "[hid]10.0.0.216:9060
>> ;transport=udp;version=3")
>> #### Configure Tracer module to use the HEP Protocol instance id [hid]
>> loadmodule "tracer.so"
>> modparam("tracer", "trace_on", 1)
>> modparam("tracer", "trace_id", "[tid]uri=hep:hid")
>>
>> And then the third part,
>> I noticed that it make no different when I put it above in the route
>> logic or below.
>>
>> route[to_homer] {
>> $var(trace_id) = "tid";
>> if (!has_totag()) {
>> if (is_method("INVITE")) { $var(trace_type) = "dialog"; }
>> else if (!is_method("CANCEL")) { $var(trace_type) = "transaction"; }
>> } else { $var(trace_type) = NULL; }
>> switch ($var(trace_type)) {
>> case "dialog":
>> trace("$var(trace_id)", "d", "sip|xlog|rest");
>> break;
>> case "transaction":
>> trace("$var(trace_id)", "t", "sip|xlog");
>> break;
>> }
>> }
>>
>> I'm not getting an error, but I'm also not seeing any packets received on
>> the homer server.
>> Can someone point me in the right direction or explain how I can add
>> details to trouble shoot?
>>
>> Cheers,
>> Vincent
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
--
Met vriendelijke groet,
Vincent Horst
EHVC Zakelijk
www.ehvc.nl
VincentHorst at EHVC.nl
Tel: 06 518 218 48
DISCLAIMER
Dit bericht is uitsluitend bestemd voor de geadresseerde. Als u dit bericht
per abuis heeft ontvangen, wordt u verzocht het te vernietigen en de
afzender te informeren. EHVC Zakelijk wijst elke aansprakelijkheid af die
voortvloeit uit elektronische verzending.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20230926/383df9d6/attachment-0001.html>
More information about the Users
mailing list