Re: [OpenSIPS-Users] [OpenSIPS-Devel] New MediaProxy Release version 2.6.6

[Abdul Basit]

Nice. Let's test.

On 8 May 2017 20:22, "Adrian Georgescu"  wrote:

> Hello,
>
> There is a new Mediaproxy software available
>
> Changelog mediaproxy (2.6.6)
>
>* Updated list of non-routable IP addresses and the corresponding RFC
>
> The software is packaged for latest Debian and Ubuntu versions.
>
> To update or install the software follow the instructions at
>
> http://mediaproxy.ag-projects.com
>
> Regards,
> Adrian
>
>
> ___
> Devel mailing list
> de...@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] InterProxy messaging

[SamyGo]

Hi Razvan,
I can for sure open up a feature request for this. Like I mentioned already
this is achievable via other modules but each have their own issues. Plus,
I personally don't want to deploy additional layers of tools and experience
their own difficulties. I am even willing to cut RabbitMQ out of the
picture if Clusterer Module shows some additional functions to send/get
data from other node(s).

Here is the ticket: https://github.com/OpenSIPS/opensips/issues/1119


Regards,
Sammy.




On Mon, May 8, 2017 at 11:28 AM, Răzvan Crainea  wrote:

> Hi, Sammy!
>
> Unfortunately there currently is no way to wait for a rabbitmq reply as
> you want. However, I also think it would be nice to have this feature in
> the next versions. Can you please open a feature request for this[1]?
> For now, you can only use REST, DB or CacheDB queries to achieve this.
>
> [1] https://github.com/OpenSIPS/opensips/issues/
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Solutionswww.opensips-solutions.com
>
> On 05/03/2017 06:51 PM, SamyGo wrote:
>
> Hi All,
>
> I'm toying with the idea of having a cluster of opensips sending events
> between each other and also capable of "querying" other servers in the
> cluster to retrieve the required data.
>
> This idea is not any different than having a shared Redis sentinel between
> the cluster to set/get data but I want to use event_routing,
> event_rabbitmq, or rabbitmq modules to achieve the same.
>
> The RabbitMQ as I've read it can only send data and can not listen for
> incoming bcast/mcast messages, let me know if I'm wrong here.
>
> The event_rabbitMQ can send some data to the RabbitMQ server again but
> only based on some event.
>
> The event_routing (EBR, new module) can wait for events to happen OR
> notify if an event happens.
>
> Now, the Question: How can I send a query(RPC) to the RabbitMQ server;
> wait for the reply event, and route my calls accordingly?
>
>
> OpenSIPS1 --data--->>RabbitMQ
> ..
> 
> OpenSIPS2-query->>RabbitMQ
> OpenSIPS2
>
> Thanks,
> Sammy
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] TLS opensips 2.2.3 on Debian 8

[Răzvan Crainea]

Hi, William!

Did you figure out what was the mode the tls_mgm was conflicting with? 
Can you let us know the modules you're using?


Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 05/04/2017 07:22 PM, William Simon wrote:

Can someone specify the version of openssl that works for TLS on Debian 8?

Debian 8 standard packaging comes with openssl 1.0.1t. I have also tried the 
Debian 8 backport of openssl 1.0.2k. In both cases, opensips fails to start 
with the following error:

Please disregard. I found that loading the tls_mgm module earlier in the script 
solves the problem. openssl 1.0.1t standard for Debian 8 works fine.


“The information transmitted is intended only for the person or entity to which 
it is addressed and may contain proprietary, business-confidential and/or 
privileged material. If you are not the intended recipient of this message you 
are hereby notified that any use, review, retransmission, dissemination, 
distribution, reproduction or any action taken in reliance upon this message is 
prohibited. If you received this in error, please contact the sender and delete 
the material from any computer.”
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] REG::Opensips V1.11.5 & V1.11.10 Duplicate TCP Conections

[Răzvan Crainea]

Hi, Ravitez!

You are right - if opensips gets multiple messages in parallel that need 
to get to a single destination, each process will open a different 
connection to that destination. However, all sequential messages will 
use a single TCP connection.
Synchronizing all the TCP actions to ensure you will have a single 
connection might be a bit overkill in terms of performance.


May I ask if this is a problem for you? Can you detail a bit why?

Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 05/04/2017 04:11 PM, Ravitez Ravi wrote:

Hi All,
Good Day,
I have been seeing opensips creating mutiple(duplicate) TCP 
connections to the same destination if hit with heavy call load.


*What do i mean?*
opensips ip : 10.10.10.1
Destination  : 10.10.10.2
Tcp Children : 32
Ideally opensips will create only one tcp connections and reuses 
it,if there's a heavy call load i see there are several tcp 
connections which are created to the same destination.

I believe here's the root cause :
- When a child tries to find a connection to the destination it 
calls _tcpconn_find() (assuming we are using ip and not id) system 
checks tcpconn_aliases_hash for the connection info.
  this map is maintained by the parent process and each child lock 
its while reaing tcpconn_get().in order to simulate the scenario lets 
assume a->parent->state is BAD this method
  will return null and so the child tries to create a new 
connections,assuming there's a second child trying to find the same 
connections and goes through the same process


  - Now each child thinks there's no connection to the destination and 
calls tcpconn_connect() this will create a socket to the destination 
and passes over the fd to the

main process to update the has map.

  - Not sure if tcp_connect() should have locking mechanism as in 
tcpconn_get().




Please correct me if my understanding is wrong,please share your thoughts.
Thank you.



Regards,
Ravitez.D


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users