Hello,
in about two and a half week the annual open source developer conference FOSDEM (http://fosdem.org/2010/) takes place in Brussels. As in the last year we would like to meet here for a social event, probably a dinner on Saturday evening, 6th February.
This developers already confirmed their participance:
- Daniel-Constantin Mierla - he is also giving a talk about Kamailio 3.0.0 on Saturday: http://fosdem.org/2010/schedule/events/kamailio_sip_server - Elena-Ramona Modroiu - Marius Zbihlei - 1&1 kamailio and sip-router development Bucharest - Timo Reimann - 1&1 kamailio and sip-router development Karlsruhe - Henning Westerholt
Participation at the event is free of charge, everybody pays for its own expenses. In order to organize a restaurant and do a reservation please send me a short mail if you would like to attend. Suggestions for a nice place with good food and beer are also welcome.
Looking forward to see you in Brussels.
Best regards,
Henning
P.S.: Photos of the last year event can be found on our web site: http://www.kamailio.org/events/2009-FOSDEM/FOSDEM2009-Album/
I am OK to organise and reserve a restaurant for the event.
Kind regards,
Olivier
Henning Westerholt a écrit :
Hello,
in about two and a half week the annual open source developer conference FOSDEM (http://fosdem.org/2010/) takes place in Brussels. As in the last year we would like to meet here for a social event, probably a dinner on Saturday evening, 6th February.
This developers already confirmed their participance:
- Daniel-Constantin Mierla - he is also giving a talk about Kamailio 3.0.0 on Saturday: http://fosdem.org/2010/schedule/events/kamailio_sip_server
- Elena-Ramona Modroiu
- Marius Zbihlei - 1&1 kamailio and sip-router development Bucharest
- Timo Reimann - 1&1 kamailio and sip-router development Karlsruhe
- Henning Westerholt
Participation at the event is free of charge, everybody pays for its own expenses. In order to organize a restaurant and do a reservation please send me a short mail if you would like to attend. Suggestions for a nice place with good food and beer are also welcome.
Looking forward to see you in Brussels.
Best regards,
Henning
P.S.: Photos of the last year event can be found on our web site: http://www.kamailio.org/events/2009-FOSDEM/FOSDEM2009-Album/
On Wednesday 20 January 2010, Olivier Taylor wrote:
[..]
I am OK to organise and reserve a restaurant for the event.
Hi Olivier,
thank you, it would be great if you could take care of this. Lets discuss after i got more feedback. I'll come back to you when we know the how many more people like to participate.
Cheers,
Henning
On 1/20/10 6:36 PM, Olivier Taylor wrote:
no problem, it's a pleasure to meet all of you in Brussels. I did that last year and ready to do it again.
Thanks, Olivier!
I arrive in Brussels on Friday, attempting to attend the beer event. If someone arrives on same day, maybe we will meet there, otherwise we should set a meeting place and time on Saturday, for those willing to meet at Fosdem before the dinner.
Cheers, Daniel
Henning Westerholt a écrit :
On Wednesday 20 January 2010, Olivier Taylor wrote:
[..]
I am OK to organise and reserve a restaurant for the event.
Hi Olivier,
thank you, it would be great if you could take care of this. Lets discuss after i got more feedback. I'll come back to you when we know the how many more people like to participate.
Cheers,
Henning
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
21 jan 2010 kl. 10.03 skrev Daniel-Constantin Mierla:
On 1/20/10 6:36 PM, Olivier Taylor wrote:
no problem, it's a pleasure to meet all of you in Brussels. I did that last year and ready to do it again.
Thanks, Olivier!
I arrive in Brussels on Friday, attempting to attend the beer event. If someone arrives on same day, maybe we will meet there, otherwise we should set a meeting place and time on Saturday, for those willing to meet at Fosdem before the dinner.
I'm sorry, can't attend this year. Daniel will just have to drink my beer too.
/O ;-)
On 1/21/10 10:11 AM, Olle E. Johansson wrote:
21 jan 2010 kl. 10.03 skrev Daniel-Constantin Mierla:
On 1/20/10 6:36 PM, Olivier Taylor wrote:
no problem, it's a pleasure to meet all of you in Brussels. I did that last year and ready to do it again.
Thanks, Olivier!
I arrive in Brussels on Friday, attempting to attend the beer event. If someone arrives on same day, maybe we will meet there, otherwise we should set a meeting place and time on Saturday, for those willing to meet at Fosdem before the dinner.
I'm sorry, can't attend this year. Daniel will just have to drink my beer too.
:-), then: # ls pub # more beer
Going to miss you at the table paper brainstorming and drawing (with no coke this time)...
Cheers, Daniel
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/
Aymeric Moizard schrieb:
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?
yes.
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"?
yes
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 guess yes.
I'd like a confirmation that I: 1: have to install "presence" "presence_xml" modules
yes
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"
I guess yes.
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?
You can mix, but not arbitrarily. The biggest difference between ser and kamailio is the database structure. ser uses a new database schema with numeric user-ids which map to SIP AoR. kamailio still uses the old (ser 0.9.x) database schema where every user has a fixed AoR.
Therefore you can not mix modules which require different database layouts.
Thus, in your scenario you have to mix database layouts: provisioning/location from ser and presence from kamailio. That might work. But probably much easier would be to use kamailio modules only (unless you need numeric user ids).
regards klaus
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/
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
On Thu, 21 Jan 2010, Klaus Darilion wrote:
Aymeric Moizard schrieb:
[...]
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?
You can mix, but not arbitrarily. The biggest difference between ser and kamailio is the database structure. ser uses a new database schema with numeric user-ids which map to SIP AoR. kamailio still uses the old (ser 0.9.x) database schema where every user has a fixed AoR.
Therefore you can not mix modules which require different database layouts.
Thus, in your scenario you have to mix database layouts: provisioning/location from ser and presence from kamailio. That might work. But probably much easier would be to use kamailio modules only (unless you need numeric user ids).
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/
regards klaus
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/
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Aymeric Moizard schrieb:
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.
In the archive there must be some details about ser's schema, described by Jan and Andrei. Unfortunately I could not find them now.
I only found http://lists.sip-router.org/pipermail/sr-dev/2009-July/002793.html which describes did (domain id). Googling for uuid may help.
Maybe iptel guys can find the link to the mailing list discussions.
regards klaus
On Thursday 21 January 2010, Klaus Darilion wrote:
In the archive there must be some details about ser's schema, described by Jan and Andrei. Unfortunately I could not find them now.
I only found http://lists.sip-router.org/pipermail/sr-dev/2009-July/002793.html which describes did (domain id). Googling for uuid may help.
Maybe iptel guys can find the link to the mailing list discussions.
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
On 21-01 18:21, Henning Westerholt wrote:
On Thursday 21 January 2010, Klaus Darilion wrote:
In the archive there must be some details about ser's schema, described by Jan and Andrei. Unfortunately I could not find them now.
I only found http://lists.sip-router.org/pipermail/sr-dev/2009-July/002793.html which describes did (domain id). Googling for uuid may help.
Maybe iptel guys can find the link to the mailing list discussions.
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
Yeah, that's probably the most up-to-date piece of documentation on SER's database schema.
-Jan
Klaus Darilion writes:
In the archive there must be some details about ser's schema, described by Jan and Andrei. Unfortunately I could not find them now.
I only found http://lists.sip-router.org/pipermail/sr-dev/2009-July/002793.html which describes did (domain id). Googling for uuid may help.
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
On 1/21/10 4:17 PM, Aymeric Moizard wrote:
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?
You can mix, but not arbitrarily. The biggest difference between ser and kamailio is the database structure. ser uses a new database schema with numeric user-ids which map to SIP AoR. kamailio still uses the old (ser 0.9.x) database schema where every user has a fixed AoR.
Therefore you can not mix modules which require different database layouts.
Thus, in your scenario you have to mix database layouts: provisioning/location from ser and presence from kamailio. That might work. But probably much easier would be to use kamailio modules only (unless you need numeric user ids).
Then my first comment would be: why have the "pa" been removed
I guess it was no longer update to work with latest core and db apis.
if it's not possible to use the presence module from kamailio...
you can use them, they are pretty much independent of the subscriber table and profile, you just create the afferent tables from kamailio.
In my mind, presence & presence_xml are using different independant database table and doesn't conflict with ser database?
Right.
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 haven't checked ser usrloc, we did some changes in K, some of them for presence purpose and for using the pua_usrloc you have to use K usrloc and registrar modules and from here nathelper module.
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.
Doing auth with ser modules and using presence/usrloc from K should be just fine.
So where sip-router is going? Do you target to have only the same core for both kamailio & ser, but still be different projects?
Goal is to remove duplication as much as possible. However, the db related things are the most sensitive, since people have management application relying on certain structure.
Is having a common database layout an objective of the sip-router project?
Yes, but I would say it will be the last to happen -- there will be quite some debates around.
If I intent to implement to additionnal event package, do you advise me to stick with kamailio subscriber layout?
presence and subscriber profiles are quite independent.
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...
A bit inconvenient with git, indeed, but I could not find how to fetch easily only the branch to give such guidelines.
Cheers, Daniel
Tks, Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/
regards klaus
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/
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
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/21/10 4:17 PM, Aymeric Moizard wrote:
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?
You can mix, but not arbitrarily. The biggest difference between ser and kamailio is the database structure. ser uses a new database schema with numeric user-ids which map to SIP AoR. kamailio still uses the old (ser 0.9.x) database schema where every user has a fixed AoR.
Therefore you can not mix modules which require different database layouts.
Thus, in your scenario you have to mix database layouts: provisioning/location from ser and presence from kamailio. That might work. But probably much easier would be to use kamailio modules only (unless you need numeric user ids).
Then my first comment would be: why have the "pa" been removed
I guess it was no longer update to work with latest core and db apis.
if it's not possible to use the presence module from kamailio...
you can use them, they are pretty much independent of the subscriber table and profile, you just create the afferent tables from kamailio.
In my mind, presence & presence_xml are using different independant database table and doesn't conflict with ser database?
Right.
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 haven't checked ser usrloc, we did some changes in K, some of them for presence purpose and for using the pua_usrloc you have to use K usrloc and registrar modules and from here nathelper module.
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.
Doing auth with ser modules and using presence/usrloc from K should be just fine.
So where sip-router is going? Do you target to have only the same core for both kamailio & ser, but still be different projects?
Goal is to remove duplication as much as possible. However, the db related things are the most sensitive, since people have management application relying on certain structure.
Is having a common database layout an objective of the sip-router project?
Yes, but I would say it will be the last to happen -- there will be quite some debates around.
If I intent to implement to additionnal event package, do you advise me to stick with kamailio subscriber layout?
presence and subscriber profiles are quite independent.
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...
A bit inconvenient with git, indeed, but I could not find how to fetch easily only the branch to give such guidelines.
Cheers, Daniel
Tks, Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/
regards klaus
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/
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Daniel-Constantin Mierla
Hello Aymeric,
On 1/22/10 4:11 PM, Aymeric Moizard wrote:
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
patch looks good, I am going to apply it. Haven't checked yet, but I guess the db is storing the string value for event, right?
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.
your second patch :-) for straightforward support.
When SUBSCRIBE is received and NOTIFY body built, functions from your module will be executed. Save the data you need at subs time and use it at notify. You don't have a caching mechanism for it right now, so either you db hits or use a htable. Extending db table with one more column does not affect other modules. If you have lot of data, you can use different table (you can use id column or to-tag for reference). So, depending of what you need and how you want to do it, you may not need to touch other code, just build in your mode.
In case you need to serialize/deserialize data, look at lib/cds/ seems a good way to go.
Cheers, Daniel
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/21/10 4:17 PM, Aymeric Moizard wrote:
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?
You can mix, but not arbitrarily. The biggest difference between ser and kamailio is the database structure. ser uses a new database schema with numeric user-ids which map to SIP AoR. kamailio still uses the old (ser 0.9.x) database schema where every user has a fixed AoR.
Therefore you can not mix modules which require different database layouts.
Thus, in your scenario you have to mix database layouts: provisioning/location from ser and presence from kamailio. That might work. But probably much easier would be to use kamailio modules only (unless you need numeric user ids).
Then my first comment would be: why have the "pa" been removed
I guess it was no longer update to work with latest core and db apis.
if it's not possible to use the presence module from kamailio...
you can use them, they are pretty much independent of the subscriber table and profile, you just create the afferent tables from kamailio.
In my mind, presence & presence_xml are using different independant database table and doesn't conflict with ser database?
Right.
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 haven't checked ser usrloc, we did some changes in K, some of them for presence purpose and for using the pua_usrloc you have to use K usrloc and registrar modules and from here nathelper module.
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.
Doing auth with ser modules and using presence/usrloc from K should be just fine.
So where sip-router is going? Do you target to have only the same core for both kamailio & ser, but still be different projects?
Goal is to remove duplication as much as possible. However, the db related things are the most sensitive, since people have management application relying on certain structure.
Is having a common database layout an objective of the sip-router project?
Yes, but I would say it will be the last to happen -- there will be quite some debates around.
If I intent to implement to additionnal event package, do you advise me to stick with kamailio subscriber layout?
presence and subscriber profiles are quite independent.
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...
A bit inconvenient with git, indeed, but I could not find how to fetch easily only the branch to give such guidelines.
Cheers, Daniel
Tks, Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/
regards klaus
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/
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Daniel-Constantin Mierla
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
On 1/22/10 4:11 PM, Aymeric Moizard wrote:
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
I have applied the patch on git master branch.
Thanks, Daniel
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/21/10 4:17 PM, Aymeric Moizard wrote:
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?
You can mix, but not arbitrarily. The biggest difference between ser and kamailio is the database structure. ser uses a new database schema with numeric user-ids which map to SIP AoR. kamailio still uses the old (ser 0.9.x) database schema where every user has a fixed AoR.
Therefore you can not mix modules which require different database layouts.
Thus, in your scenario you have to mix database layouts: provisioning/location from ser and presence from kamailio. That might work. But probably much easier would be to use kamailio modules only (unless you need numeric user ids).
Then my first comment would be: why have the "pa" been removed
I guess it was no longer update to work with latest core and db apis.
if it's not possible to use the presence module from kamailio...
you can use them, they are pretty much independent of the subscriber table and profile, you just create the afferent tables from kamailio.
In my mind, presence & presence_xml are using different independant database table and doesn't conflict with ser database?
Right.
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 haven't checked ser usrloc, we did some changes in K, some of them for presence purpose and for using the pua_usrloc you have to use K usrloc and registrar modules and from here nathelper module.
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.
Doing auth with ser modules and using presence/usrloc from K should be just fine.
So where sip-router is going? Do you target to have only the same core for both kamailio & ser, but still be different projects?
Goal is to remove duplication as much as possible. However, the db related things are the most sensitive, since people have management application relying on certain structure.
Is having a common database layout an objective of the sip-router project?
Yes, but I would say it will be the last to happen -- there will be quite some debates around.
If I intent to implement to additionnal event package, do you advise me to stick with kamailio subscriber layout?
presence and subscriber profiles are quite independent.
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...
A bit inconvenient with git, indeed, but I could not find how to fetch easily only the branch to give such guidelines.
Cheers, Daniel
Tks, Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/
regards klaus
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/
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Daniel-Constantin Mierla
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
On 1/22/10 4:11 PM, Aymeric Moizard wrote:
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
I have applied the patch on git master branch.
Thanks, Daniel
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/21/10 4:17 PM, Aymeric Moizard wrote:
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?
You can mix, but not arbitrarily. The biggest difference between ser and kamailio is the database structure. ser uses a new database schema with numeric user-ids which map to SIP AoR. kamailio still uses the old (ser 0.9.x) database schema where every user has a fixed AoR.
Therefore you can not mix modules which require different database layouts.
Thus, in your scenario you have to mix database layouts: provisioning/location from ser and presence from kamailio. That might work. But probably much easier would be to use kamailio modules only (unless you need numeric user ids).
Then my first comment would be: why have the "pa" been removed
I guess it was no longer update to work with latest core and db apis.
if it's not possible to use the presence module from kamailio...
you can use them, they are pretty much independent of the subscriber table and profile, you just create the afferent tables from kamailio.
In my mind, presence & presence_xml are using different independant database table and doesn't conflict with ser database?
Right.
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 haven't checked ser usrloc, we did some changes in K, some of them for presence purpose and for using the pua_usrloc you have to use K usrloc and registrar modules and from here nathelper module.
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.
Doing auth with ser modules and using presence/usrloc from K should be just fine.
So where sip-router is going? Do you target to have only the same core for both kamailio & ser, but still be different projects?
Goal is to remove duplication as much as possible. However, the db related things are the most sensitive, since people have management application relying on certain structure.
Is having a common database layout an objective of the sip-router project?
Yes, but I would say it will be the last to happen -- there will be quite some debates around.
If I intent to implement to additionnal event package, do you advise me to stick with kamailio subscriber layout?
presence and subscriber profiles are quite independent.
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...
A bit inconvenient with git, indeed, but I could not find how to fetch easily only the branch to give such guidelines.
Cheers, Daniel
Tks, Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/
regards klaus
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/
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Daniel-Constantin Mierla
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-
Aymeric Moizard -
Daniel-Constantin Mierla -
Henning Westerholt -
Jan Janak -
jh＠tutpro.com -
Klaus Darilion -
Olivier Taylor -
Olle E. Johansson