Re: [SR-Users] is kamilio support RFC5626 now ?

[Richard Brady]

Hi Daniel, Peter, Klaus.

Sorry for delay I accidentally muted this thread :(

Thanks for the advice and great to hear it is being worked on. I will keep
you updated on our testing.

Richard

On 25 September 2012 11:52, Klaus Darilion wrote:

>
>
> On 25.09.2012 10:16, Daniel-Constantin Mierla wrote:
>
>> Hello,
>>
>> On 9/10/12 3:52 PM, Richard Brady wrote:
>>
>>> The other thing to consider within the "flow switching part" is the
>>> ability to "provide a limited version of a STUN server on the same
>>> interface and UDP port" as SIP.
>>>
>> this is implemented (or at least partial) - I had no chance to look
>> better at it to know exactly how far it is, being developed during SER
>> times. See the files ser_stun.{c,h} in the core.
>>
>
> Hi Richard! If you want to test it, make sure to enable the code with
> STUN=1 while building.
>
> regards
> Klaus
>
>
> __**_
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] [Kamailio-Business] Kamailio v3.3.2 Released

[Manwe]

El Tue, 16 Oct 2012 17:00:03 +0200
Daniel-Constantin Mierla  escribió:

> Hello,
> 
> Kamailio SIP Server v3.3.2 stable release is out.
> 
> 
> For more details about version 3.3.2 (including links and hints to 
> download the tarball or from GIT repository), visit:
> 
>* http://www.kamailio.org/w/2012/10/kamailio-v3-3-2-released/
> 
> RPM, Debian/Ubuntu packages will be available soon as well.
> 

Debian and Ubuntu packages are ready. Please find the instructions
below:

http://www.kamailio.org/dokuwiki/doku.php/packages:debs


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Kamailio 3.2.4 presence

[Juha Heinanen]

Vitaliy Aleksandrov writes:

> db_mode is 0 (DB_MEMORY_ONLY) and according to comments in the 
> presence.h kamailio holds subscription in memory and periodically 
> updates to db, but retrieves from db only at startup.
> And it's true, I see that kamailio tries to update the active_watchers 
> table, but it never inserts new subscriptions there.

i suggest you upgrade to 3.3.  according to its readme, subs_db_mode=0
means that db is disabled.  perhaps it was the same with 3.2, which
according to its readme does not have db_mode param.

-- juha

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Kamailio 3.2.4 presence

[Vitaliy Aleksandrov]

Hi all,

I'm facing problems with active subscription restoration after sipproxy 
restart.


db_mode is 0 (DB_MEMORY_ONLY) and according to comments in the 
presence.h kamailio holds subscription in memory and periodically 
updates to db, but retrieves from db only at startup.
And it's true, I see that kamailio tries to update the active_watchers 
table, but it never inserts new subscriptions there.


There are no problems with access to the database since when db_mode is 
2 (DB_ONLY) kamailio inserts new records into the active_watchers 
without any problems.


Here are presence module settings:
modparam("presence", "db_url", "sqlite:var/db/presence.db")
modparam("presence", "db_mode", 0)
modparam("presence", "timeout_rm_subs", 1)
modparam("presence", "pres_htable_size", 8)
modparam("presence", "subs_htable_size", 8)
modparam("presence", "max_expires", 3600)
modparam("presence", "db_update_period", 60)
modparam("presence", "clean_period", 60)

Does anybody have success with db_mode = DB_MEMORY_ONLY and 
active_watchers db table ?


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Kamailio v3.3.2 Released

[Daniel-Constantin Mierla]

Hello,

Kamailio SIP Server v3.3.2 stable release is out.

This is a maintenance release of the latest stable branch, 3.3, that 
includes fixes since release of v3.3.1. There is no change to database 
schema or configuration language structure that you have to do on 
installations of v3.3.0 or v3.3.1. Deployments running previous v3.x.x 
versions are strongly recommended to be upgraded to v3.3.2.


For more details about version 3.3.2 (including links and hints to 
download the tarball or from GIT repository), visit:


  * http://www.kamailio.org/w/2012/10/kamailio-v3-3-2-released/

RPM, Debian/Ubuntu packages will be available soon as well.

Cheers,
Daniel


--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] IPv6 addresses in dispatcher on IPv4 only proxy

[Daniel-Constantin Mierla]

Hello,

On 10/16/12 1:37 PM, Alex Hermann wrote:

On Monday 15 October 2012, Daniel-Constantin Mierla wrote:

On 10/11/12 2:11 PM, Alex Hermann wrote:

On Thursday 11 October 2012, Daniel-Constantin Mierla wrote:
DEBUG:  [dns_cache.c:567]: dns_hash_find([IPv6 Address](30), 1),
h=707 DEBUG:  [resolve.c:727]: get_record: lookup([IPv6 Address],
1) failed DEBUG:  [dns_cache.c:895]: dns_cache_mk_bad_entry([IPv6
Address], 1, 60, 1)
DEBUG:  [dns_cache.c:828]: dns_cache_add: adding [IPv6 Address](30)
1 (flags=1) at 707
ERROR: dispatcher [dispatch.c:325]: could not resolve [IPv6 Address]
WARNING:  [mem/f_malloc.c:474]: WARNING:fm_free: free(0) called

looking at the code it seems to be ending in doing an A lookup instead
of 

Why would it even query for ? The entry is an IP(v6) address, no lookup
should be done at all.
well, maybe improper formulation, the functions in core doing A/ 
lookups detect if it is an IP address and don't do the dns query in that 
case, but convert directly the address to socket structure.


The idea was to add some debug messages to discover why its ending in 
IPv4-specific function and not in the one for IPv6.


Cheers,
Daniel

--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] IPv6 addresses in dispatcher on IPv4 only proxy

[Alex Hermann]

On Thursday 11 October 2012, Alex Hermann wrote:
> I am using the dispatcher module with a database table shared among
> multiple proxies. Some proxies do both IPv4 and IPv6, others only do IPv4.
> The problem is when i use an IPv6 address in the dispatcher table. Then
> the IPv4-only proxies fail to load the table.

For reference, this little patch solved my issue. Probably not suitable
for inclusion without a config option.

diff --git a/modules_k/dispatcher/dispatch.c b/modules_k/dispatcher/dispatch.c
index 50df1fc..e0dadda 100644
--- a/modules_k/dispatcher/dispatch.c
+++ b/modules_k/dispatcher/dispatch.c
@@ -259,7 +259,14 @@ int add_dest2list(int id, str uri, int flags, int 
priority, str *attrs,
LM_ERR("bad uri [%.*s]\n", uri.len, uri.s);
goto err;
}
-   
+
+   /* skip IPv6 references if IPv6 lookups are disabled */
+   if (default_core_cfg.dns_try_ipv6 == 0 &&
+   puri.host.s[0] == '[' && puri.host.s[puri.host.len-1] == ']') {
+   LM_DBG("skipping IPv6 record %.*s\n", puri.host.len, 
puri.host.s);
+   return 0;
+   }
+
/* get dest set */
sp = ds_lists[list_idx];
while(sp)

-- 
Greetings,

Alex Hermann


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Error while running TLS enabled Kamailio proxy

[Kamal Palei]

Resolved this error, modified tls.cfg file.
Replaced default certificate/key file names with actual ones.

Thanks
-Kamal



On Tue, Oct 16, 2012 at 6:05 PM, Kamal Palei  wrote:

> Dear All
> While executing TLS enabled Kamailio proxy (3.1.5), getting below error.
>
> * 0(15895) INFO: tls [tls_domain.c:227]: TLSs: verify_depth=9
>  0(15895) ERROR: tls [tls_domain.c:393]: TLSs: Unable to load
> certificate file './modules/tls/ser-selfsigned.pem'
>  0(15895) ERROR: tls [tls_domain.c:394]: load_cert:error:02001002:system
> library:fopen:No such file or directory
>  0(15895) ERROR: tls [tls_domain.c:394]: load_cert:error:20074002:BIO
> routines:FILE_CTRL:system lib
>  0(15895) ERROR: tls [tls_domain.c:394]: load_cert:error:140DC002:SSL
> routines:SSL_CTX_use_certificate_chain_file:system lib
>  0(15895) ERROR:  [sr_module.c:832]: init_mod_child(): Error while
> initializing module tls (/usr/local/lib/kamailio/modules/tls.so)
>  0(15895) ERROR:  [main.c:1532]: ERROR: main: error in
> init_child(PROC_INT) -- exiting
>  0(15895) :  [mem/q_malloc.c:431]: BUG: qm_free: bad pointer (nil)
> (out of memory block!) - aborting
>  0(15893) ERROR:  [daemonize.c:307]: Main process exited before
> writing to pipe
> *
>
> I performed below steps to compile and install.
>
> 1. I had a working Kamailio-3.1.5 code base without TLS
> 2. Downloaded latest openssl source code
> 3. Compiled and generated libssl.a  and libcrypto.a
> 4. Next, I recompiled kamailio proxy, compilation did not go through. I
> had to modify Makefile in modules/tls module, added path for openssl/bio.h
> and path for libssl.a
> 5. Then executed make all clean  and  make all include_modules=tls , this
> time compilation succeeded
> 6. Next I did make install
> 7. Generated certificates using openssl library that comes by default with
> ubuntu 10.04 lte
> 8. Added below entries in kamailio.cfg
>
>
> #!define WITH_TLS
>
>
> #!ifdef WITH_TLS
> loadmodule "tls.so"
> modparam("tls", "config", "/usr/local/etc/kamailio/tls.cfg")
> modparam("tls", "private_key", "/etc/certs/localb2bua.com/key.pem")
> modparam("tls", "certificate", "/etc/certs/localb2bua.com/cert.pem")
> modparam("tls", "ca_list", "/etc/certs/demoCA/cert.pem")
> enable_tls=yes
> #!endif
>
> 9. Then I tried running kamailio proxy
> It complained not getting tls.so and tls.cfg
> Copied these files from modules/tls to /usr/local/etc/kamailio/ path
>
> 10. Then I was able to run Kamailio proxy and got the errors pasted at top
> of email (* Unable to load certificate file
> './modules/tls/ser-selfsigned.pem')
> *
> Please guide me what should I do to avoid this error.
>
> Thanks a lot.
> -Kamal
>
> *
> *
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] unsubscribe

[Carlos Ruiz Díaz]

To unsubscribe, go to:
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users, search for
the button "unsubscribe or edit options".

2012/10/16 Pablo R. Digonzelli 

>
>
> --
> *Ing. Pablo Digonzelli*
> Sofware Solutions
> IP Soluciones SRL
>
> 25 de Mayo 521. Entrepiso A
> email: pdigonze...@softsargentina.com
> email: pdigonze...@gmail.com
> twitter: @pdigonzelli
> Tel: 0381 4227378
> Cel: 0381 155982714
>
> --
> *De: *"Pablo R. Digonzelli" 
> *Para: *"SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
> Users Mailing List" 
> *Enviados: *Martes, 16 de Octubre 2012 9:59:23
> *Asunto: *[SR-Users] unsubscribe
>
>
>
>
> --
> *Ing. Pablo Digonzelli*
> Sofware Solutions
> IP Soluciones SRL
>
> 25 de Mayo 521. Entrepiso A
> email: pdigonze...@softsargentina.com
> email: pdigonze...@gmail.com
> twitter: @pdigonzelli
> Tel: 0381 4227378
> Cel: 0381 155982714
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] unsubscribe

[Pablo R. Digonzelli]

Ing. Pablo Digonzelli 
Sofware Solutions 
IP Soluciones SRL 

25 de Mayo 521. Entrepiso A 
email: pdigonze...@softsargentina.com 
email: pdigonze...@gmail.com 
twitter: @pdigonzelli 
Tel: 0381 4227378 
Cel: 0381 155982714 

- Mensaje original -

De: "Pablo R. Digonzelli"  
Para: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users 
Mailing List"  
Enviados: Martes, 16 de Octubre 2012 9:59:23 
Asunto: [SR-Users] unsubscribe 




Ing. Pablo Digonzelli 
Sofware Solutions 
IP Soluciones SRL 

25 de Mayo 521. Entrepiso A 
email: pdigonze...@softsargentina.com 
email: pdigonze...@gmail.com 
twitter: @pdigonzelli 
Tel: 0381 4227378 
Cel: 0381 155982714 


___ 
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list 
sr-users@lists.sip-router.org 
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users 

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] unsubscribe

[Pablo R. Digonzelli]

Ing. Pablo Digonzelli 
Sofware Solutions 
IP Soluciones SRL 

25 de Mayo 521. Entrepiso A 
email: pdigonze...@softsargentina.com 
email: pdigonze...@gmail.com 
twitter: @pdigonzelli 
Tel: 0381 4227378 
Cel: 0381 155982714 

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] IPv6 addresses in dispatcher on IPv4 only proxy

[Alex Hermann]

On Monday 15 October 2012, Daniel-Constantin Mierla wrote:
> On 10/11/12 2:11 PM, Alex Hermann wrote:
> > On Thursday 11 October 2012, Daniel-Constantin Mierla wrote:

> > DEBUG:  [dns_cache.c:567]: dns_hash_find([IPv6 Address](30), 1),
> > h=707 DEBUG:  [resolve.c:727]: get_record: lookup([IPv6 Address],
> > 1) failed DEBUG:  [dns_cache.c:895]: dns_cache_mk_bad_entry([IPv6
> > Address], 1, 60, 1)
> > DEBUG:  [dns_cache.c:828]: dns_cache_add: adding [IPv6 Address](30)
> > 1 (flags=1) at 707
> > ERROR: dispatcher [dispatch.c:325]: could not resolve [IPv6 Address]
> > WARNING:  [mem/f_malloc.c:474]: WARNING:fm_free: free(0) called
> 
> looking at the code it seems to be ending in doing an A lookup instead
> of , a matter of dns_flags value that should be enabled for IPv6 if
> you set  dns_try_ipv6 global parameter. I couldn't spot where this would
> be disabled if no IPv6 listen socket is provided.

in main.c:
if (default_core_cfg.dns_try_ipv6 && !(socket_types & SOCKET_T_IPV6)){
/* if we are not listening on any ipv6 address => no point
 * to try to resovle ipv6 addresses */
default_core_cfg.dns_try_ipv6=0;
}


> If you try the trick of adding one udp worker to listen on ::1, like:
> 
> socket_workers=1
> listen=[::1]
> 
> Does it work?
Yes, that works, but I'd like to prevent the process from listening on IPv6 at 
all.

I think i'll go with the database view solution or patch dispatcher locally to 
skip IPv6 records.

Thanks,

-- 
Met vriendelijke groet,


Alex Hermann
SpeakUp BV
T: 088-SPEAKUP (088-7732587)
F: 088-7732588

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Error while running TLS enabled Kamailio proxy

[Kamal Palei]

Dear All
While executing TLS enabled Kamailio proxy (3.1.5), getting below error.

* 0(15895) INFO: tls [tls_domain.c:227]: TLSs: verify_depth=9
 0(15895) ERROR: tls [tls_domain.c:393]: TLSs: Unable to load
certificate file './modules/tls/ser-selfsigned.pem'
 0(15895) ERROR: tls [tls_domain.c:394]: load_cert:error:02001002:system
library:fopen:No such file or directory
 0(15895) ERROR: tls [tls_domain.c:394]: load_cert:error:20074002:BIO
routines:FILE_CTRL:system lib
 0(15895) ERROR: tls [tls_domain.c:394]: load_cert:error:140DC002:SSL
routines:SSL_CTX_use_certificate_chain_file:system lib
 0(15895) ERROR:  [sr_module.c:832]: init_mod_child(): Error while
initializing module tls (/usr/local/lib/kamailio/modules/tls.so)
 0(15895) ERROR:  [main.c:1532]: ERROR: main: error in
init_child(PROC_INT) -- exiting
 0(15895) :  [mem/q_malloc.c:431]: BUG: qm_free: bad pointer (nil)
(out of memory block!) - aborting
 0(15893) ERROR:  [daemonize.c:307]: Main process exited before
writing to pipe
*

I performed below steps to compile and install.

1. I had a working Kamailio-3.1.5 code base without TLS
2. Downloaded latest openssl source code
3. Compiled and generated libssl.a  and libcrypto.a
4. Next, I recompiled kamailio proxy, compilation did not go through. I had
to modify Makefile in modules/tls module, added path for openssl/bio.h and
path for libssl.a
5. Then executed make all clean  and  make all include_modules=tls , this
time compilation succeeded
6. Next I did make install
7. Generated certificates using openssl library that comes by default with
ubuntu 10.04 lte
8. Added below entries in kamailio.cfg


#!define WITH_TLS


#!ifdef WITH_TLS
loadmodule "tls.so"
modparam("tls", "config", "/usr/local/etc/kamailio/tls.cfg")
modparam("tls", "private_key", "/etc/certs/localb2bua.com/key.pem")
modparam("tls", "certificate", "/etc/certs/localb2bua.com/cert.pem")
modparam("tls", "ca_list", "/etc/certs/demoCA/cert.pem")
enable_tls=yes
#!endif

9. Then I tried running kamailio proxy
It complained not getting tls.so and tls.cfg
Copied these files from modules/tls to /usr/local/etc/kamailio/ path

10. Then I was able to run Kamailio proxy and got the errors pasted at top
of email (* Unable to load certificate file
'./modules/tls/ser-selfsigned.pem')
*
Please guide me what should I do to avoid this error.

Thanks a lot.
-Kamal

*
*
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio 3.3.0 CDR logging call "duration"

[Nord7]

Hello,

In ACC module i'm set extra field "duration=$avp(i:256)" and added after
"lose_route", in method "BYE"
$avp_printf("$avp(i:256)", "$DLG_lifetime") function.
Now after call, in databasse field "duration" i have text "". If i
set function like this:  $avp_printf("$avp(i:256)", "TEST") all is okay,
database field "duration" receive "TEST".
Something wrong in dialog module configuration?
Any suggestions.

MY CHANGES::
--- acc params --
modparam("acc", "log_extra",
"src_user=$fU;src_domain=$fd;src_ip=$si;"
"dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;"
"duration=$DLG_lifetime")
modparam("acc", "db_extra",
"src_user=$fU;src_domain=$fd;src_ip=$si;"  /* extra fields created in
DataBase */
"dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;"
"duration=$avp(i:256)")

-route-

route[WITHINDLG] {
<-->if (has_totag()) {
<--><--># sequential request withing a dialog should
<--><--># take the path determined by record-routing
<--><-->if (loose_route()) {
<--><--><-->if (is_method("BYE")) {
<--><--><--><-->setflag(DLG_FLAG);
<--><--><--><-->avp_printf("$avp(i:256)", "$DLG_lifetime");
<--><--><--><-->setflag(FLT_ACC); # do accounting ...
<--><--><--><-->setflag(FLT_ACCFAILED); # ... even if the
transaction fails
<--><--><-->}
<--><--><-->if ( is_method("ACK") ) {
<--><--><--><--># ACK is forwarded statelessy
<--><--><--><-->route(NATMANAGE);
<--><--><-->}
<--><--><-->route(RELAY);
<--><-->} else {
...
Best regards, Kirill Ushakov


2012/10/15 Daniel-Constantin Mierla 

>  Hello,
>
> do not reply to private email only when it is about a discussion on the
> mailing list - such messages will be ignored.
>
> Try to store the value in an avp when processing the BYE, after
> loose_route(), and store that avp in acc.
>
> Daniel
>
>
> On 10/15/12 1:13 PM, Nord7 wrote:
>
> Hello,
> no I'm not getting error messages.
> Problem:
> I can not get kamailio record duration dialogue created field "duration".
> I make a test call, answer it, wait 5-6 seconds and hang up.
> Now I have to get 5-6 seconds duration in the "duration", but the field is
> blank. The rest of the field information about the call is entered
> correctly.
> So the variable $ DLG_lifetime information about the duration of the call
> does not get.
> But most of all I am wrong somewhere.
>
>
> 2012/10/15 Daniel-Constantin Mierla 
>
>>  Hello,
>>
>> do you get any error message or what is the problem you encounter?
>>
>> Cheers,
>> Daniel
>>
>>
>> On 10/15/12 10:14 AM, Nord7 wrote:
>>
>>  Hello
>>
>>  Kamailio 3.3.0
>> All default "extra fields" created in database. I create in Database new
>> field "duration" and trying write in this field variable $DLG_lifetime
>> (from dialog module) , but can't do this. What i'm doing wrong?
>>
>>  installed modules: ACC, DIALOG
>>  # - acc params -
>> /* what special events should be accounted ? */
>> modparam("acc", "early_media", 0)
>>  modparam("acc", "report_ack", 0)
>> modparam("acc", "report_cancels", 0)
>> modparam("acc", "detect_direction", 0)
>> /* account triggers (flags) */
>> modparam("acc", "log_level", 1)
>> modparam("acc", "log_flag", FLT_ACC)
>> modparam("acc", "log_missed_flag", FLT_ACCMISSED)
>> modparam("acc", "log_extra",
>> "src_user=$fU;src_domain=$fd;src_ip=$si;"
>> "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;"
>> "duration=$DLG_lifetime")
>> modparam("acc", "failed_transaction_flag", FLT_ACCFAILED)
>> /* enhanced DB accounting */
>> modparam("acc", "db_flag", FLT_ACC)
>> modparam("acc", "db_missed_flag", FLT_ACCMISSED)
>> modparam("acc", "db_url", DBURL)
>> modparam("acc", "db_extra",
>> "src_user=$fU;src_domain=$fd;src_ip=$si;"  /* extra fields
>> created in DataBase */
>> "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;"
>> "duration=$DLG_lifetime")
>> modparam("acc", "cdr_enable", 1)
>> modparam("acc", "cdr_start_on_confirmed", 0)
>> modparam("acc", "cdr_facility", "LOG_DAEMON")
>>
>>   # - dialog params -
>> modparam("dialog", "enable_stats", 1)
>> modparam("dialog", "hash_size", 4096)
>> modparam("dialog", "rr_param", "did")
>> modparam("dialog", "dlg_flag", DLG_FLAG)  /* DLG_FLAG=4 */
>> modparam("dialog", "default_timeout", 21600)
>> modparam("dialog", "timeout_avp", "$avp(i:10)")
>> modparam("dialog", "dlg_match_mode", 0)
>> modparam("dialog", "detect_spirals", 1)
>> modparam("dialog", "db_url", DBURL)
>> modparam("dialog", "db_mode", 1)
>> modparam("dialog", "db_fetch_rows", 500)
>>
>>
>>  Routing Logic
>>
>>  route[RELAY] {
>>
>>  # enable additional event routes for forwarded requests
>> # - serial forking, RTP relaying handling, a.s.o.
>> if (is_method("INVITE|SUBSCRIBE")) {
>> t_on_branch("MANAGE_BRANCH");
>> t_on_reply("MANAGE_REPLY");
>> }
>>

Re: [SR-Users] segfault in siptrace module using setflag?

[samuel]

Hi all,

I had some problems with git (was it git fetch to update the local copy
from the "main" reposiory?) and I manually changed siptrace.c with the
addition of the len pointer in case it was using version 2 of HEP.
So far the server has not crashed. Before with just a few calls (less than
10) the pointer got lost but now, with almost a hundred calls, kamailio is
solid as a rock.

Thanks a lot, specially to Daniel and Dragos, for the attention received!

Samuel.

On 16 October 2012 13:02, samuel  wrote:

> I'll try the last branch to see whether it solves the issue.
>
> thanks a lot indeed for the fast attention and reaction!
>
> Samuel.
>
>
> On 16 October 2012 12:12, Dragos Dinu  wrote:
>
>> Hi Samuel,
>>
>> Could you try to test again with the updated siptrace sources from 3.3
>> branch? I had a patch recently commited for a crash in siptrace, so I'm
>> pretty sure you have the same issue.
>> Please tell us if your problem was fixed.:)
>>
>> Dragos
>>
>>
>> On 10/09/2012 12:00 PM, samuel wrote:
>>
>>> Hi folks,
>>>
>>> I was making some tests with kamailio (both 3.3.0 and 3.3.1 tgz) with
>>> siptrace module sending "homer" packets to a remote central agent where the
>>> data is stored and presented to the user.
>>>
>>> The related config is:
>>> # - siptrace params from HOMER -
>>> modparam("siptrace", "duplicate_uri", "sip:A.B.C.D:9060")
>>> modparam("siptrace", "trace_to_database", 0)
>>> modparam("siptrace", "trace_flag", 22)
>>> modparam("siptrace", "trace_on", 1)
>>> #HEPv2 == timestamp will be included to HEP header
>>> modparam("siptrace", "hep_version", 2)
>>> modparam("siptrace", "hep_mode_on", 1)
>>> modparam("siptrace", "hep_capture_id", 1)
>>>
>>> basically for all incoming messages, a route is called with the
>>> following actions:
>>>
>>> route[HOMER] {
>>> setflag(22);
>>> sip_trace();
>>> }
>>>
>>> I've been making some tests and if I disable the setflag action, there
>>> is no problem (well, no transaction messages are sent to the central
>>> agent), but as soon as I activated setflag, kamailio crashes with the
>>> following error:
>>>
>>>  [pass_fd.c:293]: ERROR: receive_fd: EOF on 28
>>>
>>> There's no concrete point in the config file where it fails so I think
>>> the problem is more tm-internals related. I can provide further information
>>> in case you need it.
>>>
>>> Just for adding information, and without any intention to start a
>>> flame-war, with opensips 1.8.0-tls the server does not crash...
>>>
>>> Thanks in advance!
>>> Samuel.
>>>
>>
>>
>> __**_
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users
>>
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Errors issued by Kamailio

[Sangeeta Shah]

Any input on the question below.

After further looking into it, the XML is from the following RCS spec:
http://www.gsma.com/rcs/wp-content/uploads/2012/03/1technicalrealv1.pdf

Is the Kamailio Presence module capable of handling the presence rule
xml below?

Thanks,
Sangeeta

On Mon, Oct 15, 2012 at 5:19 PM, Sangeeta Shah  wrote:
> So based on the pres rules inserted by the clients, see example below
> it's unclear how Kamailio is handling all the rules. Is Kamailio OMA
> compliant. It definitely doesn't seem to like a condition without an
> identity. IT should be matching the following rule below:
>  
> 
> 
> 
> 
> confirm
> 
> 
>
> But since it doesn't find the identity tag it probably isn't matching
> any rule. What is the behavior in that case?
>
>
>
>  xmlns="urn:ietf:params:xml:ns:pres-rules"
> xmlns:op="urn:oma:xml:prs:pres-rules"
> xmlns:cr="urn:ietf:params:xml:ns:common-policy">
>
> 
> 
> 
> 
> 
> 
> 
> allow
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
> 
> 
> 
> 
> allow
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
> 
> 
> 
> 
> confirm
> 
> 
>
> 
> 
> 
>  anc="http://ip:5060/xcap-root/resource-lists/users/sip:8475551001@ip/index/~~/resource-lists/list%5B@name=%22oma_grantedcontacts%22%5D";
> />
> 
> 
> 
> allow
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
> 
> 
>  anc="http://ip:5060/xcap-root/resource-lists/users/sip:8475551001@ip/index/~~/resource-lists/list%5B@name=%22oma_blockedcontacts%22%5D";
> />
> 
> 
> 
> block
> 
> 
>
> 
>
>
> On Mon, Oct 15, 2012 at 2:08 PM, Sangeeta Shah  
> wrote:
>> I meant Kamailio does a case-sensitive search.
>>
>> Anyways, I am still trying to get the client working with Kamailio.
>> This client is proven to work with other presence server, so just
>> trying to piece things together so it works with the Kamailio PS.
>>
>> I do not have RLS. The client does put the resource list, presence
>> rules and rls services documents and I can see those in the XCAP
>> database. I still do not understand why
>> 1. Kamailio is not sending the authorization request to sub B when A
>> adds B to the contact list
>> 2. Does Kamailio just look at the pres rules document in this case and
>> authorize B if A has their pres-rules document published on the server
>> and the sub_handling is allow?
>>
>> How is this supposed to work? I don't see anything substantial going
>> to the client in the winfo notifies. They should have the watcher info
>> but they don't :(
>>
>> There are no errors that I notice right now.
>>
>> Sangeeta
>>
>> On Mon, Oct 15, 2012 at 9:42 AM, Sangeeta Shah  
>> wrote:
>>> The path is from the resource list xml inserted by the client. The
>>> issue over here was that the Kamalio code does a case insensitive
>>> search for %5b and %5d and doesn't replace the path below with the "["
>>> brackets.
>>>
>>> This was the fix I had referred to in another thread
>>> (update_subs_rlsdb: NO MATCH) that I had to make to get past this
>>> issue. Now we are still getting xml errors but the current reason is
>>> because Kamailio doesn't seem to like the pres-rules xml inserted by
>>> the client that we are using because it doesn't have an indentity tag
>>> for each condition. Excerpt from the other thread:
>>>
>>> This is what I noticed in the error log:
>>>
>>> Oct 12 14:21:46 RCS-Presence /usr/local/sbin/kamailio[11001]: DEBUG:
>>> presence_xml [xcap_auth.c:201]: node1->name= rule
>>> Oct 12 14:21:46 RCS-Presence /usr/local/sbin/kamailio[11001]: DEBUG:
>>> presence_xml [xcap_auth.c:209]: cond_node->name= conditions
>>> Oct 12 14:21:46 RCS-Presence /usr/local/sbin/kamailio[11001]: DEBUG:
>>> presence_xml [xcap_auth.c:201]: node1->name= rule
>>> Oct 12 14:21:46 RCS-Presence /usr/local/sbin/kamailio[11001]: DEBUG:
>>> presence_xml [xcap_auth.c:209]: cond_node->name= conditions
>>> Oct 12 14:21:46 RCS-Presence /usr/local/sbin/kamailio[11001]: ERROR:
>>> presence_xml [xcap_auth.c:311]: didn't find identity tag
>>>
>>> Now when I closely look at the presence rules xml document inserted by
>>> Boghe I noticed that some of the condition tags under the rule tags do
>>> not have identity tags. Is kamailio not able to handle what's being
>>> put by this client? Based on other examples I've seen I don't think
>>> every condition needs to have an identity tag. Is my understanding
>>> correct. This is the XML that's being inserted:
>>>
>>> >> xmlns="urn:ietf:params:xml:ns:pres-rules"
>>> xmlns:op="urn:oma:xml:prs:pres-rules"
>>> xmlns:cr="urn:ietf:params:xml:ns:common-policy">
>>>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> allow
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> allow
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> confirm
>>> 
>>> 
>>>
>>> 
>>> 
>>> 
>>> >> anc="http://ip:5060/xcap-root/resource-lists/users/sip:8475551001@ip/index/~~/resource-lists/list%5B@name=%22oma_grantedcontacts%22%5D";
>>> />
>>> 
>>> 
>>> 
>>> allow
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>

Re: [SR-Users] IPv6 addresses in dispatcher on IPv4 only proxy

[Alex Hermann]

On Monday 15 October 2012, Daniel-Constantin Mierla wrote:
> On 10/11/12 2:11 PM, Alex Hermann wrote:
> > On Thursday 11 October 2012, Daniel-Constantin Mierla wrote:
> > DEBUG:  [dns_cache.c:567]: dns_hash_find([IPv6 Address](30), 1),
> > h=707 DEBUG:  [resolve.c:727]: get_record: lookup([IPv6 Address],
> > 1) failed DEBUG:  [dns_cache.c:895]: dns_cache_mk_bad_entry([IPv6
> > Address], 1, 60, 1)
> > DEBUG:  [dns_cache.c:828]: dns_cache_add: adding [IPv6 Address](30)
> > 1 (flags=1) at 707
> > ERROR: dispatcher [dispatch.c:325]: could not resolve [IPv6 Address]
> > WARNING:  [mem/f_malloc.c:474]: WARNING:fm_free: free(0) called
> 
> looking at the code it seems to be ending in doing an A lookup instead
> of 

Why would it even query for ? The entry is an IP(v6) address, no lookup 
should be done at all.

-- 
Met vriendelijke groet,


Alex Hermann
SpeakUp BV
T: 088-SPEAKUP (088-7732587)
F: 088-7732588

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Supporting TLS and DTLS in RTP Proxy

[Klaus Darilion]

Not sure if this RFC is the thing Kamal is looking for. AFAIS this RFC 
is about setting up an SRTP sessions, and the key exchange for the SRTP 
session does not happen via SIP (like SDES), but via a DTLS session 
which is performed before sending SRTP packets multiplexed on the media 
ports.


regards
Klaus

On 16.10.2012 11:24, Andrew Pogrebennyk wrote:

Kamal,
perhaps RFC 5763 provides you some of the answers?

On 10/16/2012 11:06 AM, Kamal Palei wrote:

Hi Johansson, All
Sincier regards and thanks for input.

As I understand,  all media packets pass through RTP Proxy.  The RTP
Proxy will receive simple UDP media packets from endpoints. Next RTP
proxy today pass those RTP packets to destination party.

My job is precisely to support TLS and DTLS path between RTP Proxy and
destination party. In my setup the destination party is a media server.

Do you really see a risk to have this setup. If so, please elaborate.

I underdstand here the challenge setup TLS/DTLS connection with media
server and send/recv media packets with server usuing either TLS or DTLS.

Also you mentioned "There's also solutions for RTP over DTLS" , can you
please share from where I can get the reference solution, it help me to
great extent.

Best Regards
Kamal

On Tue, Oct 16, 2012 at 12:08 AM, Olle E. Johansson mailto:o...@edvina.net>> wrote:


 15 okt 2012 kl. 13:24 skrev Peter Lemenkov mailto:lemen...@gmail.com>>:

 > Hello.
 >
 > 2012/10/15 Kamal Palei mailto:palei.ka...@gmail.com>>:
 >> Hi All
 >> I am planning to enhance RTP proxy to support TLS and DTLS.
 >> We have some requirements where we need to send RTP packets
 either over TLS
 >> or over DTLS.
 >
 > Shouldn't it be better to rely on SRTP/ZRTP instead rather than making
 > your own incompatible realisation?

 SRTP use DTLS for key exchange. There's also solutions for RTP over
 DTLS,
 but the recommended way is DTLS+SRTP. This is what's standardized
 for WebRTC,
 and the way forward for SIP media as well.

 However, I don't see how RTPproxy can be the endpoint for DTLS key
 exchange, since
 it breaks the end2end path. Clients should use TURN relays...

 Curious on how you see this working!
 /O
 ___
 SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
 sr-users@lists.sip-router.org 
 http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users




___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users




___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users



___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Guidance on using Kamailio as Presence Server and Scalability issues for millions of subsribers

[Klaus Darilion]

On 15.10.2012 23:36, Thomas Hoffman wrote:

We’re trying to determine how best to design/architect a solution where
we use Kamailio as a Presence/XCAP server and be scalable to support
millions of subscribers.

I see the Dispatcher module, but it appears that requires having
dedicated instances of the server running just in Dispatcher mode – then
you can load balance across the actual instances of the presence
servers.


Yes, it is typical to use a dispatcher to dispatch the load over several 
servers which do the real stuff (presence, gateways ...), eg:


clients <--Internet-> dispatcher <--- server 1
 \--- server 2
  \-- server X

Dispatching (eg. Kamailio with dispatcher module) is much less resource 
intensive (e.g. no DB lookups, just stateless forwarding), thus a single 
dispatcher can handle the load for several backend servers.


If the load is too big for a single dispatcher node, then you need more 
dispatcher nodes. You can use for example multiple SRV records for the 
SIP domain, or provision the clients with different IP addresses (of the 
respective dispatcher nodes). Then, every dispatcher sends the traffic 
to a certain partition of the backend servers, or you distribute the 
traffic over all backend servers.


> It’s not clear if a server can be configured to work as a

dispatcher and a presence server at the same time.


Yes you can but it does not make sense - if a node itself is a presence 
server it does not make sense to dispatch the request to other presence 
servers. One if the main advantages of having a dispatcher in front of 
the cluster is to have a single border element (single IP address) which 
eases problems like NAT traversal.



Does anyone have any high-level guidance how to approach this problem?


Presence requires, that a presence server which receives a subscription 
for a presentity, also knows the status of this presentity. There are 2 
approaches to handle this problem:


a) make sure to send PUBLISH requests from a certain presentity, and the 
SUBSCRIBE requests to this presentity, to the same presence backend. In 
this setup, every presence server uses its own database (or just memory 
without a DB). In case a presence server is removed (crash, maintenace), 
all traffic needs to be moved to other nodes and the current state is 
usually lost. Further you have to be sure to have the XCAP data 
available to all nodes.


b) all presence servers use the same database. In this case, the 
presence servers can not do any caching and have to query the DB for 
every operation. This setup simplifies the SIP setup, but increases the 
load on the DB and you may need a fast DB cluster. There were recently 
much changes to the presence modules for such a DB-only mode.



regards
Klaus

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] segfault in siptrace module using setflag?

[samuel]

I'll try the last branch to see whether it solves the issue.

thanks a lot indeed for the fast attention and reaction!

Samuel.

On 16 October 2012 12:12, Dragos Dinu  wrote:

> Hi Samuel,
>
> Could you try to test again with the updated siptrace sources from 3.3
> branch? I had a patch recently commited for a crash in siptrace, so I'm
> pretty sure you have the same issue.
> Please tell us if your problem was fixed.:)
>
> Dragos
>
>
> On 10/09/2012 12:00 PM, samuel wrote:
>
>> Hi folks,
>>
>> I was making some tests with kamailio (both 3.3.0 and 3.3.1 tgz) with
>> siptrace module sending "homer" packets to a remote central agent where the
>> data is stored and presented to the user.
>>
>> The related config is:
>> # - siptrace params from HOMER -
>> modparam("siptrace", "duplicate_uri", "sip:A.B.C.D:9060")
>> modparam("siptrace", "trace_to_database", 0)
>> modparam("siptrace", "trace_flag", 22)
>> modparam("siptrace", "trace_on", 1)
>> #HEPv2 == timestamp will be included to HEP header
>> modparam("siptrace", "hep_version", 2)
>> modparam("siptrace", "hep_mode_on", 1)
>> modparam("siptrace", "hep_capture_id", 1)
>>
>> basically for all incoming messages, a route is called with the following
>> actions:
>>
>> route[HOMER] {
>> setflag(22);
>> sip_trace();
>> }
>>
>> I've been making some tests and if I disable the setflag action, there is
>> no problem (well, no transaction messages are sent to the central agent),
>> but as soon as I activated setflag, kamailio crashes with the following
>> error:
>>
>>  [pass_fd.c:293]: ERROR: receive_fd: EOF on 28
>>
>> There's no concrete point in the config file where it fails so I think
>> the problem is more tm-internals related. I can provide further information
>> in case you need it.
>>
>> Just for adding information, and without any intention to start a
>> flame-war, with opensips 1.8.0-tls the server does not crash...
>>
>> Thanks in advance!
>> Samuel.
>>
>
>
> __**_
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] segfault in siptrace module using setflag?

[Dragos Dinu]

Hi Samuel,

Could you try to test again with the updated siptrace sources from 3.3 
branch? I had a patch recently commited for a crash in siptrace, so I'm 
pretty sure you have the same issue.

Please tell us if your problem was fixed.:)

Dragos

On 10/09/2012 12:00 PM, samuel wrote:

Hi folks,

I was making some tests with kamailio (both 3.3.0 and 3.3.1 tgz) with 
siptrace module sending "homer" packets to a remote central agent 
where the data is stored and presented to the user.


The related config is:
# - siptrace params from HOMER -
modparam("siptrace", "duplicate_uri", "sip:A.B.C.D:9060")
modparam("siptrace", "trace_to_database", 0)
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "trace_on", 1)
#HEPv2 == timestamp will be included to HEP header
modparam("siptrace", "hep_version", 2)
modparam("siptrace", "hep_mode_on", 1)
modparam("siptrace", "hep_capture_id", 1)

basically for all incoming messages, a route is called with the 
following actions:


route[HOMER] {
setflag(22);
sip_trace();
}

I've been making some tests and if I disable the setflag action, there 
is no problem (well, no transaction messages are sent to the central 
agent), but as soon as I activated setflag, kamailio crashes with the 
following error:


 [pass_fd.c:293]: ERROR: receive_fd: EOF on 28

There's no concrete point in the config file where it fails so I think 
the problem is more tm-internals related. I can provide further 
information in case you need it.


Just for adding information, and without any intention to start a 
flame-war, with opensips 1.8.0-tls the server does not crash...


Thanks in advance!
Samuel.



___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1)

[Daniel-Constantin Mierla]

Hello,


On 10/16/12 10:09 AM, MARINA SERRANO MONTES wrote:

Hi,

My kamailio installation usually works right, but sometimes, it 
crashes and it shows the following error:


"ERROR: ctl [ctl.c:379]: ERROR: ctl: could not delete unix socket 
/tmp/kamailio_ctl: Operation not permitted (1) "


Do you know why it happens randomly or what's the cause ?


probably you start kamailio with a user/group that has no rights to 
delete the ctl file. You can set the ownership of that file via ctl 
module parameters.


About the crash, do you get any error message in the logs related to the 
crash (not to the ctl file)? The log message about ctl can be printed 
due to normal stop/restart. If there is a crash, maybe you get a 
coredump file and you can send the backtrace.


Cheers,
Daniel

--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Supporting TLS and DTLS in RTP Proxy

[Andrew Pogrebennyk]

Kamal,
perhaps RFC 5763 provides you some of the answers?

On 10/16/2012 11:06 AM, Kamal Palei wrote:
> Hi Johansson, All
> Sincier regards and thanks for input.
>  
> As I understand,  all media packets pass through RTP Proxy.  The RTP
> Proxy will receive simple UDP media packets from endpoints. Next RTP
> proxy today pass those RTP packets to destination party.
>  
> My job is precisely to support TLS and DTLS path between RTP Proxy and
> destination party. In my setup the destination party is a media server.
>  
> Do you really see a risk to have this setup. If so, please elaborate.
>  
> I underdstand here the challenge setup TLS/DTLS connection with media
> server and send/recv media packets with server usuing either TLS or DTLS.
>  
> Also you mentioned "There's also solutions for RTP over DTLS" , can you
> please share from where I can get the reference solution, it help me to
> great extent.
>  
> Best Regards
> Kamal
> 
> On Tue, Oct 16, 2012 at 12:08 AM, Olle E. Johansson  > wrote:
> 
> 
> 15 okt 2012 kl. 13:24 skrev Peter Lemenkov  >:
> 
> > Hello.
> >
> > 2012/10/15 Kamal Palei  >:
> >> Hi All
> >> I am planning to enhance RTP proxy to support TLS and DTLS.
> >> We have some requirements where we need to send RTP packets
> either over TLS
> >> or over DTLS.
> >
> > Shouldn't it be better to rely on SRTP/ZRTP instead rather than making
> > your own incompatible realisation?
> 
> SRTP use DTLS for key exchange. There's also solutions for RTP over
> DTLS,
> but the recommended way is DTLS+SRTP. This is what's standardized
> for WebRTC,
> and the way forward for SIP media as well.
> 
> However, I don't see how RTPproxy can be the endpoint for DTLS key
> exchange, since
> it breaks the end2end path. Clients should use TURN relays...
> 
> Curious on how you see this working!
> /O
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org 
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> 
> 
> 
> 
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> 


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Supporting TLS and DTLS in RTP Proxy

[Kamal Palei]

Hi Johansson, All
Sincier regards and thanks for input.

As I understand,  all media packets pass through RTP Proxy.  The RTP Proxy
will receive simple UDP media packets from endpoints. Next RTP proxy today
pass those RTP packets to destination party.

My job is precisely to support TLS and DTLS path between RTP Proxy and
destination party. In my setup the destination party is a media server.

Do you really see a risk to have this setup. If so, please elaborate.

I underdstand here the challenge setup TLS/DTLS connection with media
server and send/recv media packets with server usuing either TLS or DTLS.

Also you mentioned "There's also solutions for RTP over DTLS" , can you
please share from where I can get the reference solution, it help me to
great extent.

Best Regards
Kamal

On Tue, Oct 16, 2012 at 12:08 AM, Olle E. Johansson  wrote:

>
> 15 okt 2012 kl. 13:24 skrev Peter Lemenkov :
>
> > Hello.
> >
> > 2012/10/15 Kamal Palei :
> >> Hi All
> >> I am planning to enhance RTP proxy to support TLS and DTLS.
> >> We have some requirements where we need to send RTP packets either over
> TLS
> >> or over DTLS.
> >
> > Shouldn't it be better to rely on SRTP/ZRTP instead rather than making
> > your own incompatible realisation?
>
> SRTP use DTLS for key exchange. There's also solutions for RTP over DTLS,
> but the recommended way is DTLS+SRTP. This is what's standardized for
> WebRTC,
> and the way forward for SIP media as well.
>
> However, I don't see how RTPproxy can be the endpoint for DTLS key
> exchange, since
> it breaks the end2end path. Clients should use TURN relays...
>
> Curious on how you see this working!
> /O
>  ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1)

[MARINA SERRANO MONTES]

Hi,

My kamailio installation usually works right, but sometimes, it crashes and it 
shows the following error:

"ERROR: ctl [ctl.c:379]: ERROR: ctl: could not delete unix socket 
/tmp/kamailio_ctl: Operation not permitted (1) "

Do you know why it happens randomly or what's the cause ?

Many thanks.

Br,
Marina



Este mensaje se dirige exclusivamente a su destinatario. Puede consultar 
nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace 
situado m?s abajo.
This message is intended exclusively for its addressee. We only send and 
receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] preparing kamailio 3.3.2

[Daniel-Constantin Mierla]

Hello,

quick note to let everyone know that after 12:00GMT I am starting to 
package v3.3.2 -- after that time do not commit in the branch 3.3 until 
the release is announced. For urgent matters write to sr-dev first.


Cheers,
Daniel

On 10/15/12 9:03 AM, Daniel-Constantin Mierla wrote:

Hello,

I will package Kamailio v3.3.2 tomorrow. Let us know if some fixes 
from master were not backported yet.


Cheers,
Daniel

On 10/9/12 10:33 AM, Daniel-Constantin Mierla wrote:

Hello,

I am considering packaging Kamailio v3.3.2 at the beginning of next 
week (Monday or Tuesday). If any of the devs have backports to be 
done, do them before the end of this week.


Also, if someone spotted some fixes in the master that were not 
backported, write to the lists so we can care of them.


Thanks,
Daniel





--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] db_sqlite bugs

[Pedro Antonio Vico Solano]

Hello Timo,

We've done a basic test and it seems
to solve the memory leak problem. We'll do exhaustive tests in a few days.

We'll keep you informed.

Thanks a lot,
Pedro




De:      
 Timo Teras 
Para:      
 "SIP Router -
Kamailio \(OpenSER\) and SIP Express Router \(SER\) - Users Mailing List"

cc:      
 pvsol...@amper.es
Fecha:      
 15/10/2012 16:13
Asunto:    
   Re: [SR-Users]
db_sqlite bugs
Enviado por:    
   Timo Teräs 




On Thu, 11 Oct 2012 12:37:23 +0200 Pedro Antonio Vico
Solano
 wrote:

> Hello everyone,
> 
> We are developing a solution based on the SQLite module for Kamailio
> and we've found some bugs/errors regarding it. We use kamailio 3.2.4
> and SQLite 3.7.14.1. The errors are about this:
> 
> - Memory leaks on querys via sqlops. Kamailio main process leaks 4kB
> each 3 queries (aprox.) and that memory is never freed. [Attached
> basic example]
> - Segmentation fault when doing a SELECT COUNT(*) via sqlops.
> [Attached basic example 2]
> 
> Can you help us?

Does this help for the memory leak?

diff --git a/modules_k/db_sqlite/dbase.c b/modules_k/db_sqlite/dbase.c
index 0b32e07..c1d3b71 100644
--- a/modules_k/db_sqlite/dbase.c
+++ b/modules_k/db_sqlite/dbase.c
@@ -543,7 +543,12 @@ int db_sqlite_update(const db1_con_t* _h, const db_key_t*
_k, const db_op_t* _o,
 
 int db_sqlite_raw_query(const db1_con_t* _h, const str* _s, db1_res_t**
_r)
 {
-       return db_do_raw_query(_h, _s, _r,
+       int rc;
+
+       rc = db_do_raw_query(_h, _s, _r,
                    
          db_sqlite_submit_query,
                    
          db_sqlite_store_result);
+       db_sqlite_cleanup_query(_h);
+
+       return rc;
 }

Seems that all other database driver postpone the resource release to
free_results - but there's no reason why we couldn't do this right away
in sqlite. Since in sqlite free_results we just free cached result set.

Will take a look at the other bug later when I get the time to
reproduce it.

-Timo


ADVERTENCIA 

Este mensaje y/o sus anexos, pueden contener información personal y confidencial
cuyo uso, reproducción o distribución no autorizados están legalmente prohibidos.
Por lo tanto, si Vd. no fuera su destinatario y, erróneamente, lo hubiera
recibido, le rogamos que informe al remitente y lo borre de inmediato.

En cumplimiento de la Ley Orgánica 15/1999, de Protección de Datos de Carácter
Personal le informamos de que su dirección de correo electrónico, así como
sus datos personales y de empresa pasarán a formar parte de nuestro fichero
de Gestión, y serán tratados con la única finalidad de mantenimiento de
la relación adquirida con usted. Los datos personales que existen en nuestro
poder están protegidos por nuestra Política de Seguridad, y no serán compartidos
con ninguna otra empresa. Usted puede ejercitar los derechos de acceso,
rectificación, cancelación y oposición dirigiéndose por escrito a la dirección
arriba indicada.

This e-mail and its attachments may include confidential personal information
which may be protected by any legal rules and cannot be used, copied, distributed
or disclosed to any person without authorisation. If you are not the intended
recipient and have received this e-mail by mistake, please advise the sender
and erase it.

In compliance with the Spanish Organic Act 15/1999 on Personal Data Protection,
we hereby inform you that your email address, as well as your personal
and business information, will be included in our Management files and
used solely for purposes corresponding to our commercial relationship.
All personal data in our possession is protected by our Data Safety Policy
and thus shall not be released to any other third party whatsoever. You
may exercise your right to access, rectify, cancel and contest by writing
to the address provided above. 

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users