Have upgraded to v2.2.3, added a hep udp listener and still having problems.
Also tried adding a hep tcp listener and changing the protocol to tcp.
My edited opensips.cfg file is now like this:
# LAN interface
listen=udp:192.168.0.118:5060
listen=tls:192.168.0.118:5061
listen=hep_udp:192.168.0.118:5656
listen=hep_tcp:192.168.0.118:5656
loadmodule "proto_udp.so"
loadmodule "proto_tcp.so"
loadmodule "tls_mgm.so"
loadmodule "proto_tls.so"
loadmodule "proto_hep.so"
loadmodule "mi_fifo.so"
loadmodule "mi_datagram.so"
loadmodule "cfgutils.so"
loadmodule "db_mysql.so"
loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "signaling.so"
loadmodule "sipmsgops.so"
loadmodule "siptrace.so"
loadmodule "sipcapture.so"
loadmodule "registrar.so"
loadmodule "auth.so"
loadmodule "auth_db.so"
loadmodule "acc.so"
loadmodule "uri.so"
loadmodule "domain.so"
loadmodule "dialog.so"
loadmodule "nathelper.so"
loadmodule "rtpproxy.so"
loadmodule "textops.so"
loadmodule "avpops.so"
loadmodule "permissions.so"
loadmodule "group.so"
...
modparam("siptrace", "trace_on", 1)
modparam("siptrace", "trace_id",
"[tid]uri=hep:xx.yy.zz.234:9060;transport=tcp;version=3")
route[REGISTER] {
sip_trace("tid", "t");
...
I am testing it by registering a phone over tls onto a test server behind NAT
(external address aa.bb.80.225). I want it to send hep data to the capture node
at xx.yy.zz.234.
Now getting the following errors when sip_trace is called during registration:
2017-03-15 11:27:13 ERROR:proto_hep:tcpconn_async_connect: poll error: flags 1c
2017-03-15 11:27:13 ERROR:proto_hep:tcpconn_async_connect: failed to retrieve
SO_ERROR [server=xx.yy.zz.234:9060] (111) Connection refused
2017-03-15 11:27:13 ERROR:proto_hep:hep_tcp_send: async TCP connect failed
2017-03-15 11:27:13 ERROR:siptrace:msg_send: send() for proto 9 failed
2017-03-15 11:27:13 ERROR:siptrace:trace_send_hep_duplicate: cannot send
duplicate message
2017-03-15 11:27:13 ERROR:siptrace:save_siptrace: Failed to duplicate with hep
to <:>
The capture node at xx.yy.zz.234 is running Kamailio v4.2. Could the above
errors be caused by incompatibility with Kamailio or do they look more
fundamental than that?
If I change the capture node to OpenSIPS, will it have to be v2.2.3? (I
already have v1.11 installed on that server and didn't want to have to upgrade).
The capture node did receive some traffic from my test server, but nothing
appeared on the homer dashboard.
Here is the iptables output for the listening port 9060 on the server at
xx.yy.zz.234:
]# iptables -L -nv | grep 9060
0 0 ACCEPT udp -- * * aa.bb.80.128/25 0.0.0.0/0
udp dpt:9060
16 960 ACCEPT tcp -- * * aa.bb.80.128/25 0.0.0.0/0
tcp dpt:9060
John Quick
Smartvox Limited
Tel: 01727-221221
-----Original Message-----
From: Ionut Ionita [mailto:[email protected]]
Sent: 15 March 2017 09:00
To: [email protected]; OpenSIPS devel mailling list
<[email protected]>
Subject: Re: [OpenSIPS-Devel] siptrace hep "hit a programming bug"
That should be fixed in 2.2.3 . You have to define a hep udp listener in order
to work.
Regards,
Ionut Ionita
OpenSIPS Developer
On 03/14/2017 11:41 AM, John Quick wrote:
> Hi,
>
> I'm trying to configure opensips v2.2.2 to send hep data to a homer
> capture server.
> Here are a few lines from my opensips.cfg that might be relevant:
> loadmodule "proto_udp.so"
> loadmodule "proto_hep.so"
> loadmodule "siptrace.so"
>
> modparam("siptrace", "trace_on", 1)
> modparam("siptrace", "trace_id",
> "[tid]uri=hep:xx.yy.zz.234:9060;transport=udp;version=2;")
>
> The following message is being written to the logs frequently:
> 2017-03-14 09:32:13 CRITICAL:siptrace:msg_send: #012>>> using proto 8
> which is not init!#012#012It seems you have hit a programming
> bug.#012Please help us make OpenSIPS better by reporting it at
> https://github.com/OpenSIPS/opensips/issues
> 2017-03-14 09:32:13 ERROR:siptrace:trace_send_hep_duplicate: cannot
> send duplicate message
> 2017-03-14 09:32:13 ERROR:siptrace:save_siptrace: Failed to duplicate
> with hep to <:>
>
> John Quick
> Smartvox Limited
>
>
>
> _______________________________________________
> Devel mailing list
> [email protected]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
