21 jan 2010 kl. 10.03 skrev Daniel-Constantin Mierla: I'm sorry, can't attend this year. Daniel will just have to drink my beer too. /O ;-)

Hi again, I'm still in the process of testing and adding features in my newly installed sip router. I'm now trying to add presence support in my setup. I'm using the ser-advanced.cfg as a start for my configuration. I didn't found any howto dedicated to sip router for this. If you have any pointer, let me know. Here are the question: In former ser, "pa" module was responsible for presence information? I guess the old "pa" module from ser has been removed because in sip-router, the presence should be now handled with kamailio modules: "presence" "presence_xml"? I used ser_msysql.sh to prepare my defaut database and it contains database: "presentity", "presentity_contact", "presentity_extensions" and "presentity_notes", "watcherinfo", "tuple_extensions", "tuple_notes", "rls_subscription", "rls_vs", and "rls_vs_names". They all seems deprecated right? (because "pa" module is deprecated and may be others?) I'd like a confirmation that I: 1: have to install "presence" "presence_xml" modules 2: have to install database from sip router git: ./utils/kamctl/mysql/presence-create.sql 3: can safely remove the old tables: "presentity", "presentity_contact", "presentity_extensions" and "presentity_notes", "watcherinfo", "tuple_extensions", "tuple_notes", "rls_subscription", "rls_vs", and "rls_vs_names" One note: the "presentity" database currently created by ser_mysql.sh conflict with the one in "./utils/kamctl/mysql/presence-create.sql" Last general question: What about mixing kamailio & ser? I've seen for example modules with same namings: "auth" and "auth_db" in both modules_s & modules_k: does this means we can use the same core but have to choose between using modules_s or modules_k? Tks much for your help & advise, Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/

On Thu, 21 Jan 2010, Klaus Darilion wrote: [...] Then my first comment would be: why have the "pa" been removed if it's not possible to use the presence module from kamailio... In my mind, presence & presence_xml are using different independant database table and doesn't conflict with ser database? Most probably, there could be conflict with modules that depends on usrloc for example? (like pua_usrloc) Looking at developper APIs, for both usrloc kam/ser modules they are very close. I don't fully understand yet what "numeric user ids" are, but I would really like to use the ser database layout for user/location/credentials which seems really flexible compared to kamailio. So where sip-router is going? Do you target to have only the same core for both kamailio & ser, but still be different projects? Is having a common database layout an objective of the sip-router project? If I intent to implement to additionnal event package, do you advise me to stick with kamailio subscriber layout? I finally understood why my "make deb" was compiling a ser version: I just forgot to checkout the kamailio branch... That was also a source of confusion for understanding why normal step for the kamailio branch was to setup a ser database layout... Because of that error, I though first the same layout was already used... Tks, Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/

On Thursday 21 January 2010, Klaus Darilion wrote: Hi Klaus, the proposed merge scheme (which also contains plenty of informations about the differences) from Jan can be found here: http://www.iptel.org/jan/db_merge Cheers, Henning

Klaus Darilion writes: i'm using domain module from modules_s (because it has more features than k domain module) and it works fine with other modules from modules and modules_k. regarding database schema, i created a k style schema for modules_s domain module. -- juha

Hi again, Tks for your answers on this topic. To answer one of your question: my goal is to implement a new module for a non standard SIP event package. Here is a patch for current kamailio 3.0 branch to allow adding a new event package without changing the core: (without having a new define in the "event" header parser.) http://sip.antisip.com/patch-siprouter-presence-anypackage.diff If the "type" is EVENT_OTHER, the SUBSCRIBE and PUBLISH will be accepted if the package name exist in the list. If this patch doesn't fit you, please let me know how you would like it to be! I'm now working on my new module and have a question: I have a specific header in SUBSCRIBE which impact NOTIFY contents: do I have any existing way to attach this information to my dialog information within "active_watchers" database so I can have the information available when I'm building my NOTIFY contents? (equivalent to presence agregations). Just a hint would be appreciated. Tks, Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/ On Thu, 21 Jan 2010, Daniel-Constantin Mierla wrote:

On 1/22/10 4:11 PM, Aymeric Moizard wrote: I have applied the patch on git master branch. Thanks, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/