Just two cents - <div><br></div><div>We make such a product already - and it's very tricky to get it working. We have real-time routing decisions based on user-provided variables such as location and presence. We can automatically direct calls based on inactivity on the keyboard and mouse over a period of say 1 minute, kicking on FindMe rules or routing in almost any other way you can imagine through Asterisk-based dial plans. Users can choose their own location and all inbound calls will immediately be directed to this end-point, and all outbound calls will reflect accurately in the CDRs that this user made a call - regardless of the end-point where the call originated.</div>
<div><br></div><div>UC is really cool stuff - and I would love to see what you come up with. Our product is 6 years in the making and doesn't do everything that I wish it would do. Lots of tricky logic when you're supporting a theoretically unlimited user base through a SaaS model. Add-in mobile devices and web-based clients for environments where installable applications are neither realistic nor preferred, and it's quite the beast.</div>
<div><br></div><div>If you have any questions - I would be happy to answer them within the limits of what my internal NDA allows. <br><br><div class="gmail_quote">On Thu, Feb 17, 2011 at 5:16 AM, Duane Larson <span dir="ltr"><<a href="mailto:duane.larson@gmail.com">duane.larson@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>I guess one option could be to have an XCAP server and an XCAP IP Phone (Snom) that can publish its PIDF info. Then you would need to somehow search the XCAP table and parse that xml code to see the persons status. That is what comes to my mind first but I am not sure if it will work or be a dead end. Another question Carlo is how the persons status will be updated if we are not talking about Dialog Status. Would they manually update it (like you would with a Snom phone with PIDF) or are you wanting something really cool like Outlook/Exchange Calendar integration to show if the person has a meeting or is on vacation? That would be really sweet, but then you get into compatibility issues when you upgrade Exchange.</div>
<div><div></div><div class="h5">
<div><br> </div>
<div class="gmail_quote">On Wed, Feb 16, 2011 at 11:34 AM, Adrian Georgescu <span dir="ltr"><<a href="mailto:ag@ag-projects.com" target="_blank">ag@ag-projects.com</a>></span> wrote:<br>
<blockquote style="border-left:#ccc 1px solid;margin:0px 0px 0px 0.8ex;padding-left:1ex" class="gmail_quote">
<div style="word-wrap:break-word">Hi Carlo,
<div><br></div>
<div>Such powerful feature would deserve some module of its own. Routing based on end-user provided preferences using presence is something fresh and cool nobody has tried it before. Make something that uses published presence and xcap policy in a meaningful way for the end-user!
<div><br></div>
<div>We will help you if want to implement such feature if something is missing on the server side.</div>
<div><br></div>
<div>Regards,</div>
<div>Adrian</div>
<div><br></div>
<div>
<div>
<div>
<div><br></div>
<div>
<div>
<div>
<div>
<div>
<div></div>
<div>
<div>On Feb 16, 2011, at 5:20 PM, Carlo Dimaggio wrote:</div><br></div></div>
<blockquote type="cite">
<div>
<div></div>
<div>
<div text="#000000" bgcolor="#ffffff"><font size="-1"><font face="Arial">Dear all,<br><br></font></font><font size="-1"><font face="Arial">I'm thinking about a design of an unified communication system based on presence status.</font></font><br>
<font size="-1"><font face="Arial"><br>I would like to know if the presence status of a subscriber could be used to define the routing logic. <br>An example is routing the call to voicemail when Alice's status is "meeting" or to a cell phone when she is on "holiday".<br>
<br><br>Thanks,<br>Carlo<br></font></font></div></div></div>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br></blockquote></div><br></div></div></div></div></div></div></div></div><br>
_______________________________________________<br>Users mailing list<br><a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br><br clear="all"><br></div></div>-- <br>--<br>*--*--*--*--*--*<br>Duane<br>*--*--*--*--*--*<br><font color="#888888">--<br>
</font><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>