<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12pt">Great. Thanks for answering all my questions.<br>I've become a huge spce fan in just a few days.<br><div><span><br></span></div><div style="display: block;" class="yahoo_quoted"> <br> <br> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> On Monday, November 25, 2013 1:43 PM, Andreas Granig <agranig@sipwise.com> wrote:<br> </font> </div> <div class="y_msg_container">Hi,<br clear="none"><br clear="none">On 11/25/2013 11:25 AM, Miguel Rios wrote:<br clear="none">> I've been looking into the IM features in latest spce 3.1, specifically<br clear="none">>
the SIP SIMPLE messaging support.<br clear="none">> I see that SIP messages are indeed passed between registered endpoints,<br clear="none">> but I'm not sure about store and forward for endpoints that are offline.<br clear="none">> Kamailio has the msilo module which would take care of this requirement,<br clear="none">> but I'm not sure if installing it would break something in the spce<br clear="none">> framework. Any thoughts?<br clear="none"><br clear="none">You can create a customtt for your impresence.cfg.tt2 and/or <br clear="none">proxy.cfg.tt2. We're happily receiving patches and will review them also.<br clear="none"><br clear="none">> Also, in xmpp land, spce currently uses prosody which is a great<br clear="none">> lightweight xmpp solution. I believe there is also a smack module for<br clear="none">> prosody that will inform users if their recipient is online or off.<br clear="none">> Again, would installing
other Prosody modules, like MUC, break spce? Are<br clear="none">> there some docs or guidelines I should follow so as not to break spce?<br clear="none"><br clear="none">We're using MUC on top of prosody internally, works perfectly fine. <br clear="none">Again, add a customtt for the config files, so if something breaks, you <br clear="none">can always just reuse the original ones.<br clear="none"><br clear="none">> Lastly, I see that 3.1 has both apache and nginx running. Being a nginx<br clear="none">> man myself, why not get rid of apache completely? It seems that having 2<br clear="none">> webservers is not very efficient, no?<br clear="none"><br clear="none">Currently, SOAP is quite deeply integrated into apache/mod-perl, so we <br clear="none">haven't migrated that yet. If you don't need the API, you can safely <br clear="none">stop apache.<br clear="none"><br clear="none">Andreas<div class="yqt1844998101" id="yqtfd38592"><br
clear="none"><br clear="none">_______________________________________________<br clear="none">Spce-user mailing list<br clear="none"><a shape="rect" ymailto="mailto:Spce-user@lists.sipwise.com" href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br clear="none"><a shape="rect" href="http://lists.sipwise.com/listinfo/spce-user" target="_blank">http://lists.sipwise.com/listinfo/spce-user</a><br clear="none"></div><br><br></div> </div> </div> </div> </div></body></html>