Hmm.... that is strange.
Could you send me (off list) your cfg to give it a try - I
see you use the 2.3.3 version , right ?
Regards,
Nothing
root@dus-appsrv01:/etc/opensips#
opensipsctl fifo ps
Process:: ID=0 PID=14966 Type=attendant
Process:: ID=1 PID=14967 Type=MI FIFO
Process:: ID=2 PID=14968 Type=time_keeper
Process:: ID=3 PID=14969 Type=timer
Process:: ID=4 PID=14970 Type=SIP receiver
udp:1.2.3.4:5060
Process:: ID=5 PID=14975 Type=SIP receiver
udp:1.2.3.4:5060
Process:: ID=6 PID=14976 Type=SIP receiver
udp:1.2.3.4:5060
Process:: ID=7 PID=14977 Type=SIP receiver
udp:1.2.3.4:5060
Process:: ID=8 PID=14978 Type=SIP receiver
udp:1.2.3.4:5060
Process:: ID=9 PID=14979 Type=TCP receiver
Process:: ID=10 PID=14982 Type=TCP
receiver
Process:: ID=11 PID=14984 Type=TCP
receiver
Process:: ID=12 PID=14985 Type=TCP
receiver
Process:: ID=13 PID=14986 Type=TCP
receiver
Process:: ID=14 PID=14987 Type=TCP
receiver
Process:: ID=15 PID=14988 Type=TCP
receiver
Process:: ID=16 PID=14989 Type=TCP
receiver
Process:: ID=17 PID=14991 Type=Timer
handler
Process:: ID=18 PID=14992 Type=TCP main
root@srv01:/etc/opensips# netstat -tlnp |
grep opensips
root@srv01:/etc/opensips#
Thanks,
Xaled
If
you do "netstat -tlnp | grep opensips", what do you
get ?
The TCP layer
automatically enable itself if a TCP-based protocol is
used from the OpenSIPS config (as listener), like SIP
TCP/TLS/WS/WSS , HEP or BIN.
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/26/2018 05:53 PM, xaled wrote:
Hi
Bogdan,
nope,
non of them.
Greetings,
Xaled
Hi
Xaled,
Do you use HEP
for tracing or BIN for replication ?
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/26/2018 01:36 PM, xaled
wrote:
Hi Callum,
that helped thanks.
I have 8 TCP receivers and one TCP main
process that I did not expected as I only listen on
udp.
Will have to understand the TCP spawn
logic.
Greetings,
Xaled