[OpenSIPS-Users] Conflicting information from commands 'opensipsctl ul show' and ' opensipsctl fifo list_tcp_conns '.

[Răzvan Crainea]

Hi, Rodrigo!

Before removing A from the user location, did you do an opensips ul show 
to see what registrations OpenSIPS knows? Are there multiple 
registrations? Are you deleting all of them?
Opening a TCP connection to opensips doesn't necessarily mean that the 
client also sent a REGISTER message, and therefore the client is not yet 
registered from SIP perspective. What you might see there (with port 
48695) might be an old (bogus) registration. After a while, when the 
client registers, you see the correct info.

Best regards,

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 11/29/2016 10:33 PM, Rodrigo Pimenta Carvalho wrote:
> Hi.
>
>
> I have peer A and peer B online on my OpenSIPS.
>
> After removing peer A from table location and reseting peer A, I have:
>
>
> Connection::  ID=29 Type=tcp State=0 Source=127.0.0.1:*52887*
> Destination=127.0.0.1:5060 Lifetime=1970-01-01 08:44:41
>
> It means that peer A is online on OpenSIPS via TCP socket with port
> 52887. This is the result of command '/opensipsctl fifo list_tcp_conns/'.
>
>
> However, the commad '/opensipsctl ul show/' gives me:
>
>
>     AOR:: intercomA_5dtUWgwgqzR6
>         Contact::
> sip:intercomA_5dtUWgwgqzR6 at 127.0.0.1:*48694*;transport=TCP;ob Q=
>             Expires:: 479
>             Callid:: 5694778c-6178-4e80-bf2e-7a4dc0deb5d1
>             Cseq:: 37504
>             User-agent:: n/a
>             State:: CS_SYNC
>             Flags:: 0
>             Cflags::
>             Socket:: tcp:127.0.0.1:5060
>             Methods:: 8063
>             Attr:: in_same_network
>             SIP_instance:: <urn:uuid:00000000-0000-0000-0000-0000fe2ea41d>
>
> It means that peer A is online on OpenSIPS via TCP socket with port
> 48694. So, I have a kind of conflict here. How can it be possible?
>
> So, if peer A calls peer B, when B answers I can see the following log:
>
>
> Jan  1 08:36:14 [435] ERROR:core:tcpconn_async_connect: failed to
> retrieve SO_ERROR [server=127.0.0.1:*48694*] (111) Connection refused
>
>
> Why such behavior does exist in OpenSIPS? How to avoid it?
>
> And after a while a new TCP connection appered in port 52887. Like this:
>
>
>         Contact::
> sip:intercomA_5dtUWgwgqzR6 at 127.0.0.1:52887;transport=TCP;ob Q=
>             Expires:: 236
>             Callid:: 96672dc5-a98c-468e-a07a-aca27748791a
>             Cseq:: 25094
>             User-agent:: n/a
>             State:: CS_SYNC
>             Flags:: 0
>             Cflags::
>             Socket:: tcp:127.0.0.1:5060
>             Methods:: 8063
>             Attr:: in_same_network
>             SIP_instance:: <urn:uuid:00000000-0000-0000-0000-0000fe2ea41d>
>
> Could it be a problem in OpenSIPS?
>
>
>
> Any hint will be very helpful!
>
>
> Best regards.
>
>
>
>
>
> RODRIGO PIMENTA CARVALHO
> Inatel Competence Center
> Software
> Ph: +55 35 3471 9200 RAMAL 979
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>