[OpenSIPS-Users] [Release] OpenSIPS 3.2.0 major release, beta version

[Matthew Schumacher]

nevermind,  $socket_out fixed my issue.

Looks like 3.2.0 is running fine for my limited use case.

On 5/27/21 12:33 PM, Matthew Schumacher wrote:
> I was able to compile the software without any issue and it loaded my 
> config and seems to work with only changing the listen to socket, 
> however an issue that I was having with the old version (and the 
> reason to try the new one) is not resolved.
>
> The issue is that I have two instances of opensips running on the same 
> host with different sets of public and private addresses (4 total).
>
> Instance one (3.0.2) has
>
> listen=udp:a.a.a.a:5060
> listen=udp:b.b.b.b:5060
>
> Instance two (3.2.0-beta) has
>
> socket=udp:x.x.x.x:5060
> socket=tcp:x.x.x.x:5060
> socket=udp:y.y.y.y:5060
> socket=tcp:y.y.y.y:5060
>
> On instance two, when relaying with UDP I get:
>
> May 27 11:24:59 [7095] ERROR:core:get_out_socket: outbound IP b.b.b.b 
> not found as listener
> May 27 11:24:59 [7095] ERROR:core:get_out_socket: failed to find route 
> to <sip dest>
> May 27 11:24:59 [7095] ERROR:tm:update_uac_dst: failed to fwd to af 2, 
> proto 1  (no corresponding listening socket)
> May 27 11:24:59 [7095] ERROR:tm:t_forward_nonack: failure to add branches
>
> But this only happens on UDP traffic, not TCP traffic.  So, instance 
> two is trying to send the UDP packet with a source address it's not 
> listening on, probably because it's the host's first IP address.
>
> If this a known or unknown issue?  Can I define for instance two which 
> IP to source from?
>
> Thanks,
> Matt
>
>
> On 5/27/21 9:45 AM, Bogdan-Andrei Iancu wrote:
>> Hi there !!
>>
>> One more year, one more ambitious roadmap 
>> <https://www.opensips.org/Development/Opensips-3-2-Planning>, one 
>> more OpenSIPS major release.
>>
>> So, we are all happy to announce the beta release of OpenSIPS 3.2.0 
>> major version - and this 3.2 version is all about Clustering, 
>> Integration, Security and IMS. But here is the shortest possible 
>> description 
>> <https://blog.opensips.org/2021/05/27/opensips-3-2-here-it-is/> of 
>> this release; and be aware that it's actually not so short as nothing 
>> is short about 3.2 !
>>
>> Please keep in mind that 3.2.0 is still a beta release, targeting mid 
>> July to become fully stable. So, we still have some testing ahead of 
>> us :).
>>
>> Many thanks to our awesome community for contributing with ideas, 
>> code, patches, tests and reports!
>>
>> Looking for downloading it? See the tarball 
>> <http://opensips.org/pub/opensips/3.2.0>or the GIT repo 
>> <https://github.com/OpenSIPS/opensips/tree/3.2>. Packages (rpms 
>> <https://yum.opensips.org/> and debs <https://apt.opensips.org/>) are 
>> also already available!
>>
>> Enjoy it,
>> -- 
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>    https://www.opensips-solutions.com
>> OpenSIPS Bootcamp 2021 online
>>    https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> 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/20210527/c5db2576/attachment-0001.html>