forgotten to cc the list :-)
Klaus Darilion schrieb:
>
>
> Aymeric Moizard schrieb:
>>
>>
>> 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...
>
> I think you can (I have not tried, but it should work, maybe needs some
> tuning) - as presence tables are not related to provisioning/location
> tables. But it is more work.
>
>> 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.
>
> Agreed.
>
>> 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?
>
> There is already the same "core". But different database schema (used by
> modules)
>
>> Is having a common database layout an objective of the sip-router
>> project?
>
> I think this is not agreed yet. But as it is planned to merge common
> modules, this probably includes merging the schema too.
>
> The problem is existing schemas. Although ser's schema is more flexible,
> users avoid changing their existing schema (as this impacts the whole
> provisioning/billing subsystems).
>
>> If I intent to implement to additionnal event package, do you advise
>> me to stick with kamailio subscriber layout?
>
> Do you need subscriber layout for the presence module? Maybe you can
> describe your module a bit more.
>
>> 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...
>
> This is what I do to build kamailio:
> git clone ..uri...
> cd sip-router
> git branch --track kamailio_3.0 origin/kamailio_3.0
> git checkout kamailio_3.0
> make deb
>
> regards
> klaus
>
>
>>
>> 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(a)lists.sip-router.org
>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>>>
>
Hi list,
I'm currently willing to install/upgrade to sip-router
(currently using kamailio 1.5)
I'm doing initial testing with git with kamailio branch
(3.0.0) and need some help.
I'm using a debian lenny and willing to have debian package
using "make deb".
First question: is it possible to include/exclude modules or
modules groups when using "made deb" or does it just compile 100% of modules?
What if I want to add my own module? which file should I update?
(only main Makefile?)
First pkg/kamailio/debian-lenny is broken: it failed when applying
patch. (it seems the patch are the ones that was applied to old
core version of kamailio)
I was able to do a "make deb" using pkg/debian but as I'm using
the kamailio branch, I want somebody to confirm this is the correct
way to go!
About TLS: it seems there are several way to have TLS: what is
the one used in "make deb"? The module solution?
I'm not able to use srcmd to add user or domain:
sercmd -s unixs:/tmp/sip-router_ctl user add aymeric_test secret amoizard(a)xxx.com
error: 500 - command add not found
when I use "ls" command, I don't see the user and domain command: do
I have to load any module for this?
I tried filling a "credential" and "domain" entry by hand in my database
but it seems to not work. specifically, I don't know what to put in the
did of "domain" and "credential" tables?
That's my initial questions...
Regards,
Aymeric MOIZARD / ANTISIP
amsip - http://www.antisip.com
osip2 - http://www.osip.org
eXosip2 - http://savannah.nongnu.org/projects/exosip/
Hi list,
I'm currently willing to install/upgrade to sip-router
(currently using kamailio 1.5)
I'm doing initial testing with git with kamailio branch
(3.0.0) and need some help.
I'm using a debian lenny and willing to have debian package
using "make deb".
First question: is it possible to include/exclude modules or
modules groups when using "made deb" or does it just compile 100% of
modules?
What if I want to add my own module? which file should I update?
(only main Makefile?)
First pkg/kamailio/debian-lenny is broken: it failed when applying
patch. (it seems the patch are the ones that was applied to old
core version of kamailio)
I was able to do a "make deb" using pkg/debian but as I'm using
the kamailio branch, I want somebody to confirm this is the correct
way to go!
About TLS: it seems there are several way to have TLS: what is
the one used in "make deb"? The module solution?
That's my initial questions...
Regards,
Aymeric MOIZARD / ANTISIP
amsip - http://www.antisip.com
osip2 - http://www.osip.org
eXosip2 - http://savannah.nongnu.org/projects/exosip/
http://phentermine.viviti.com/files/documents/buy-phentermine.htmlbuy phentermine online without prescription Phentermine Information from Taking phentermine together
http://phentermine.viviti.com/files/documents/buy-phentermine-online.htmlbuy phentermi
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: SER-447
URL: http://tracker.iptel.org/browse/SER-447
Project: SER
Issue Type: Bug
Affects Versions: 2.0
Environment: 64 bit CPU, Debian lenny OS
Assigned To: Vaclav Kubart
Fix For: 2.0, Ipteldorf
When I try to store message in the database I get the following errors in
the syslog (There are no messages stored in the database):
May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0)
May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri:
May 14 15:26:40 sen ser[5853]: t_uac: no socket found
And here is ser.cfg:
xlog("L_INFO", " route[INBOUND]: (m_store (0, )) \n");
if (m_store ("0", ""))
{
xlog("L_INFO", " route[INBOUND]: offline message stored \n");
xlog("L_INFO", " route[INBOUND]: (!t_reply(202,Accepted) \n");
if (!t_reply("202", "Accepted"))
{
xlog("L_INFO", " route[INBOUND]: sl_reply_error() \n");
sl_reply_error();
}
}
the error appears in the following place accordin to my logging:
May 14 15:26:40 sen ser[5853]: route[INBOUND]: (m_store (0, ))
May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0)
May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri:
May 14 15:26:40 sen ser[5853]: t_uac: no socket found
May 14 15:26:40 sen ser[5853]: route[INBOUND]: offline message stored
May 14 15:26:40 sen ser[5853]: route[INBOUND]: (!t_reply(202,Accepted)
May 14 15:26:40 sen ser[5853]: route[INBOUND]: drop <MESSAGE>
<sip:hulk@voip.rd.touk.pl>
Below is the Message transaction sent through SER:
U 2007/05/14 15:26:40.746835 192.168.0.165:7089 -> 192.168.0.165:5060
MESSAGE sip:hulk@voip.rd.touk.pl SIP/2.0.
CSeq: 64 MESSAGE.
Via: SIP/2.0/UDP
192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport.
From: "Sen"
<sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e.
Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen.
To: "hulk@" <sip:hulk@voip.rd.touk.pl>.
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE.
Content-Type: text/plain;charset=UTF-8.
Content-Length: 12.
Max-Forwards: 70.
.
test message
#
U 2007/05/14 15:26:40.790793 192.168.0.165:5060 -> 192.168.0.165:7089
SIP/2.0 202 Accepted.
CSeq: 64 MESSAGE.
Via: SIP/2.0/UDP
192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport=7089.
From: "Sen"
<sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e.
Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen.
To: "hulk@"
<sip:hulk@voip.rd.touk.pl>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-fd05.
Server: Sip EXpress router (2.0.0-rc1 (x86_64/linux)).
Content-Length: 0.
Warning: 392 192.168.0.165:5060 "Noisy feedback tells: pid=5853
req_src_ip=192.168.0.165 req_src_port=7089 in_uri=sip:hulk@voip.rd.touk.pl
out_uri=sip:hulk@voip.rd.touk.pl via_cnt==1".
.
In the attachment is a patch for the msilo.c source file where there was a need for two small corrections.
Cheers
Tomasz Zieleniewski
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.iptel.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Hello,
due to the spam generated via anonymous tracker posting, now you have to
register before opening a issue. We look to see if we can add easily
captcha or other ways to protect against spam but let the issue creation
open without registration.
Cheers,
Daniel
--
Daniel-Constantin Mierla
* http://www.asipto.com/
in kamailio_3.0/Makefile if remove utils/kamctl from line
C_INSTALL_UTILS= utils/kamctl
still files kamctl/kamdbctl.mysql and kamctl/kamctl.mysqld get
installed. this looks to me like a bug in Makefile.
-- juha
http://phentermine.viviti.com/files/documents/buy-phentermine.htmlbuy phentermine without prescription Phentermine Information from Taking phentermine together
http://phentermine.viviti.com/files/documents/buy-phentermine-online.htmlbuy phentermine onli
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: SER-446
URL: http://tracker.iptel.org/browse/SER-446
Project: SER
Issue Type: Bug
Affects Versions: 2.0
Environment: 64 bit CPU, Debian lenny OS
Assigned To: Vaclav Kubart
Fix For: 2.0, Ipteldorf
When I try to store message in the database I get the following errors in
the syslog (There are no messages stored in the database):
May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0)
May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri:
May 14 15:26:40 sen ser[5853]: t_uac: no socket found
And here is ser.cfg:
xlog("L_INFO", " route[INBOUND]: (m_store (0, )) \n");
if (m_store ("0", ""))
{
xlog("L_INFO", " route[INBOUND]: offline message stored \n");
xlog("L_INFO", " route[INBOUND]: (!t_reply(202,Accepted) \n");
if (!t_reply("202", "Accepted"))
{
xlog("L_INFO", " route[INBOUND]: sl_reply_error() \n");
sl_reply_error();
}
}
the error appears in the following place accordin to my logging:
May 14 15:26:40 sen ser[5853]: route[INBOUND]: (m_store (0, ))
May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0)
May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri:
May 14 15:26:40 sen ser[5853]: t_uac: no socket found
May 14 15:26:40 sen ser[5853]: route[INBOUND]: offline message stored
May 14 15:26:40 sen ser[5853]: route[INBOUND]: (!t_reply(202,Accepted)
May 14 15:26:40 sen ser[5853]: route[INBOUND]: drop <MESSAGE>
<sip:hulk@voip.rd.touk.pl>
Below is the Message transaction sent through SER:
U 2007/05/14 15:26:40.746835 192.168.0.165:7089 -> 192.168.0.165:5060
MESSAGE sip:hulk@voip.rd.touk.pl SIP/2.0.
CSeq: 64 MESSAGE.
Via: SIP/2.0/UDP
192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport.
From: "Sen"
<sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e.
Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen.
To: "hulk@" <sip:hulk@voip.rd.touk.pl>.
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE.
Content-Type: text/plain;charset=UTF-8.
Content-Length: 12.
Max-Forwards: 70.
.
test message
#
U 2007/05/14 15:26:40.790793 192.168.0.165:5060 -> 192.168.0.165:7089
SIP/2.0 202 Accepted.
CSeq: 64 MESSAGE.
Via: SIP/2.0/UDP
192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport=7089.
From: "Sen"
<sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e.
Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen.
To: "hulk@"
<sip:hulk@voip.rd.touk.pl>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-fd05.
Server: Sip EXpress router (2.0.0-rc1 (x86_64/linux)).
Content-Length: 0.
Warning: 392 192.168.0.165:5060 "Noisy feedback tells: pid=5853
req_src_ip=192.168.0.165 req_src_port=7089 in_uri=sip:hulk@voip.rd.touk.pl
out_uri=sip:hulk@voip.rd.touk.pl via_cnt==1".
.
In the attachment is a patch for the msilo.c source file where there was a need for two small corrections.
Cheers
Tomasz Zieleniewski
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.iptel.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
