[OpenSIPS-Users] Problem with presence_xml module Opensips 1.9

[Estefania figueroa buitrago]

Hi,

At the moment I'm working in a project, in which I need to use OpenIMSCore with 
a presence server, so I decided to use Opensips (version 1.9).

When I tried to start it I get two errors. The first one is due to the script 
generated by the tool ./osipsconfig, specifically in this line:


modparam("presence|presence_xml", "db_url",
"mysql://opensips:opensipsrw@localhost/opensips")


As you can see in the documentation, the presence_xml module doesn't include 
the db_url parameter anymore. It would be great if you could fix it, so the 
./osipsconfig tool would not generate the script this way :).

The second error is due to the presence_xml module. I want a presence server 
WITHOUT XCAP and my configuration script looks like:


 PRESENCE modules
loadmodule "presence.so"
loadmodule "presence_xml.so"

modparam("presence", "db_url",
"mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE ME
modparam("presence", "server_address", "sip:x.x.x.x:5065") # CUSTOMIZE ME
modparam("presence_xml", "force_active", 1)


Here I'm just following the documentation:

force_active: Should be set to 1 if not using an xcap server

But every time I try to start Opensips I get this error:


ERROR:presence_xml:mod_init: Can't bind xcap
ERROR:core:init_mod: failed to initialize module presence_xml
ERROR:core:main: error while initializing modules


It doesn't make any sence if you read the documentation. I commented the lines 
involving the presence_xml module and everything worked fine, but sadly I DO 
need this module.

What is that due to? It's there a bug? 

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

Re: [OpenSIPS-Users] OpenSIPS mhomed=yes and shared IP address using corosync

[Remco .]

Hi Bogdan,

Thanks for your reply. The feature of setting the probe interface for DR
would be great. In the meantime, I studied the exact behavior of the
IPaddr2 resource agent a bit more. It turns out it uses iproute2 to bind
the address. The VIP is added as a secondary IP address to the interface -
no wonder the kernel picks the primary. I will see if I can modify the
resource agent a bit so it will add the VIP as the primary IP (swap the IP
addresses round). That way, the mhomed=yes option will work. I will report
back my findings.

Thanks,

Remco.


On Fri, Nov 1, 2013 at 12:27 PM, Bogdan-Andrei Iancu wrote:

>  Hello Remco,
>
> In mhomed, yes you let the kernel to pick the source IP based on the
> routing table - so this approach delegate the logic from OpenSIPS to the
> kernel. And it is up to ho well the network part is set.
>
> In the future I would like to add to the DR module the possibility to set
> the probing interface (as you have now in the dispatcher module). For now,
> what you can do is to use the local_route to catch the DR pings and use
> force_send_socket() to change the outgoing interface.
>
> Best regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
>
> On 11/01/2013 10:39 AM, Remco . wrote:
>
>   Hi all,
>
>  I have a clustered OpenSIPS setup (using corosync with a virtual IP
> address). This has been working great over the last couple of years. I now
> want to add an extra IP address to the boxes, again floating a VIP over
> these interfaces. These interfaces will be used to communicate with PSTN
> gateways. I noticed however upon enabling these interfaces, the drouting
> module starts to ping the gateways using the wrong source address, i.e
>
>  1.1.1.1 = VIP on eth0
>  2.2.2.2 = VIP on eth1
>
>  OpenSIPS is configured to listen on the the two VIPs with a listen
> directive.
>
> According to the kernel's routing table, it should use 2.2.2.2 but it uses
> 1.1.1.1 which results in failure. As I understood, mhomed=yes should
> achieve just this behavior by asking the kernel for the appropriate source
> address on sending out a packet. However, when I enable the mhomed option,
> OpenSIPS starts to complain about not having a socket to send out the
> packets. I assume this is caused by the kernel returning the real IP from
> the interfaces (first) instead of the VIPs.
>
>  Just because of the dynamic nature of the interface selection, I won't
> be able to use force_send_socket().
>
>  I know this question has come up on the list on several occasions, but
> nothing recent and I was still wondering if someone has a workaround or
> solution for this. I can imagine when using OpenSIPS as a load-balancer
> with two interfaces (in and out) you might encounter this problem as well
> if you try to add high availability (in which you often cannot avoid the
> Virtual IP scenario).
>
>  Thanks,
>  Remco.
>
>
> ___
> 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

Re: [OpenSIPS-Users] High CPS Media Solution

[Alex Ionescu]

Hi Doc,

What exactly do you mean when you say "high CPS" ? Give us some numbers 
and also explain a bit the way you have set up your scenario.
If you can also attach your opensips config file, or at least part of it 
we would be able to tell if you are using OpenSIPS in the best way.
Also, same for RTP Proxy, how do you start it ? Have you check it's 
logs, are you sure that OpenSIPS is the bottle neck and not the RTPProxy 
? Because usually the media proxy is the bottle neck, not the signalling.


So, give us some more information.

Regards,
Alex Ionescu

On 11/02/2013 07:41 AM, capn crunch wrote:
Has anyone in the community experimented with proxying media on high 
CPS type traffic? We have experimented with mediaproxy and rtp-proxy, 
but the dispatcher module on both is too slow to setup the media, and 
the opensips children eventually hang, effectively blocking traffic.


Would be interested if anyone is performing such a task and what works 
for them.


--
Sincerely,

Doc Draper
capncrunch...@gmail.com 



___
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