[OpenSIPS-Users] Proto_hep listeners

Bogdan-Andrei Iancu bogdan at opensips.org
Thu Feb 15 02:11:01 EST 2018


Hi Ben,

Even if you do not actually act a HEP traffic receiver (so no need for 
listening), you *need* to define a HEP listener in the config file. This 
constrain comes from the generic TCP stack in OpenSIPS (which also 
re-used to implement the HEP protocol)  - this stack work only in a 
symmetric way (sending and receiving).

So, just add a listener to make it happy :)

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
OpenSIPS Summit 2018
   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/14/2018 08:55 PM, Ben Newlin wrote:
>
> Hi,
>
> I’m trying to upgrade from 1.11 to 2.3.3. We use the siptrace module 
> to replicate messages via HEP, so I had to load in the proto_hep 
> module as well. On startup, I’m getting the following errors:
>
> ERROR:proto_hep:mod_init: No HEP listener defined, neither TCP nor UDP!
>
> ERROR:core:init_mod: failed to initialize module proto_hep
>
> It is intentional that I have not defined any listeners as I do not 
> wish to listen for HEP messages. I am only using the proto_hep module 
> to enabling **sending** HEP messages via siptrace. Why are listeners 
> required for the proto_hep module to start successfully?
>
> Thanks,
>
> Ben Newlin
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20180215/bdca7aef/attachment.html>


More information about the Users mailing list