[OpenSIPS-Devel] PROTO numbers

[Donat Zenichev]

Hi Ben!
Sure I tried to find out any parameters that store TLS as a value. But,
unfortunately I haven't found it yet, that's strange.
I trust you and the documentation/ code you referred to, in your last
message, so I have to finish searching of needed packets that beget it.

Until that, this looks as mysterious case for me, since nor I have an IPv6
working in my network, nor we have systems that could require TLS as a
transport.
But that's a nice challenge for me and I will let you know when I finish it.

Have a nice day.

пн, 8 апр. 2019 г. в 17:50, Ben Newlin <Ben.Newlin at genesys.com>:

> You may not have any TLS in your network, but the error is about sending,
> not receiving. Have you checked the Request-URI, Route headers, and Contact
> headers to ensure there is no “transport=tls” parameters that would make
> OpenSIPS believe the request should be sent via TLS?
>
>
>
> Proto 3 is TLS, unless I am very confused:
> https://github.com/OpenSIPS/opensips/blob/master/ip_addr.h#L52
>
>
>
> Ben Newlin
>
>
>
> *From: *Devel <devel-bounces at lists.opensips.org> on behalf of Donat
> Zenichev <donat.zenichev at gmail.com>
> *Reply-To: *OpenSIPS devel mailling list <devel at lists.opensips.org>
> *Date: *Monday, April 8, 2019 at 10:17 AM
> *To: *OpenSIPS devel mailling list <devel at lists.opensips.org>
> *Subject: *Re: [OpenSIPS-Devel] PROTO numbers
>
>
>
> That's a good explanation, I believe they use socket.h for socket(),
> bind(), connect(), recv(), send() etc.
>
> In this case it's definitely, that AF just sticks with numbers defined by
> the IANA.
>
>
>
> " I think that proto 3 in OpenSIPS is TLS, but I don’t have a reference
> for that one." - I have doubts regarding this, since I don't have any TLS
> in my network.
>
> To be honestly it's almost impossible that TLS would appear within it.
>
> But that's a good thought, I hope some of OpenSIPS project developers will
> clear our this for me.
>
>
>
> пн, 8 апр. 2019 г. в 16:46, Ben Newlin <Ben.Newlin at genesys.com>:
>
> I believe Address Family (AF) 2 is IPv6 [1].
>
>
>
> The protocol number is not the index of the listener, it refers to the
> actual protocol being used. I think that proto 3 in OpenSIPS is TLS, but I
> don’t have a reference for that one.
>
>
>
> So the error is saying you are attempting to send a message to an IPv6
> address using TLS, but you have no listener defined for that combination.
>
>
>
> [1] -
> https://www.iana.org/assignments/address-family-numbers/address-family-numbers.xhtml
>
>
>
> Ben Newlin
>
>
>
> *From: *Devel <devel-bounces at lists.opensips.org> on behalf of Donat
> Zenichev <donat.zenichev at gmail.com>
> *Reply-To: *OpenSIPS devel mailling list <devel at lists.opensips.org>
> *Date: *Monday, April 8, 2019 at 8:39 AM
> *To: *"devel at lists.opensips.org" <devel at lists.opensips.org>
> *Subject: *[OpenSIPS-Devel] PROTO numbers
>
>
>
> Hi there.
>
> Lately I came across such messages in opensips logs:
>
> "ERROR:tm:update_uac_dst: failed to fwd to af 2, proto 3 (no corresponding
> listening socket)"
>
>
>
> The error is pretty descriptive and says that certain request is unable to
> be forwarded, since of absence of needed socket. But I cannot get what
> means:
>
>
>
> "to af 2" - I found, that it's a member of this structure
> uac->request.dst.to.s.sa_family   ,
>
> but still no wonder what means number "2".
>
>
>
> And "proto 3" - does it correlate to a number of a listener defined in my
> openips configuration file? And if yes, does the count starts at 0 or at 1 ?
>
>
>
> Thanks for help in advance!
>
>
>
>
>
>
>
>
> --
>
> --
> BR, Donat Zenichev
>
> _______________________________________________
> Devel mailing list
> Devel at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>
>
>
> --
>
> --
> BR, Donat Zenichev
> _______________________________________________
> Devel mailing list
> Devel at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>


-- 
-- 
BR, Donat Zenichev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20190409/5a262064/attachment.html>