Re: [SR-Users] WebRTC video calls
Hello, kamailio + rtpengine can be used for webrtc calls between browsers as well as browser to classic sip phones. You can fine on github some config examples, published by Carlos Ruiz Diaz. Using this combination you can place an instance in front of asterisk and let asterisk behave as a classic sip/rtp media server. Cheers, Daniel On 02/05/15 00:44, Ivan Vujisic wrote: I made successful audio calls from browser to browser using Asterisk 13.1 and SIPML5 browser phone. Asterisk can't manage WebRTC video calls due to lack of codec negotiation module, but I also faced RTP ports NAT traversal issue. To my understanding Kamailio is capable to resolve this. Can anybody confirm that he made successful browser to browser video calls with Kamailio sip proxy / registrar in front of Asterisk PBX. Also, any link to good tutorial or doc pages will be appreciated. Best Regards, Ivan Vujisic ___ 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 -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ 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] Regd: Message Routing
Hello, routing MESSAGE requests is like for any other initial requests and it is done implicitly by default kamailio configuration file. You don't need anything special there. In case you need more specific features (e.g., store in case of target user is offline, see msilo module), give more details about what you want to achieve and we can provide guidelines on how to achieve it. Cheers, Daniel On 30/04/15 18:49, suryakiiran vanam wrote: Hi Team, I am using Jitsi client with Kamailio. I was able to IM between the clients. How can I control the Message routing in Kamailio script. Please help me with any link. Regards, Surya. ___ 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 -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ 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] WebSocket data in TCP connection
On Sun, May 3, 2015 at 7:21 PM, mayamatakeshi mayamatake...@gmail.com
wrote:
Hello,
about module websocket, is it possible to associate a value with the TCP
connection and have this value readable when handling SIP requests on that
connection?
Hello, I have found a way to do it using htable.
Here is the gist of it in case someone else needs this:
loadmodule xhttp.so
loadmodule websocket.so
modparam(htable, htable, websocket=size=10)
route {
if(proto == WS) {
xlog(L_DEBUG, WebSocket check: conid=$conid
val=$sht(websocket=$conid)\n);
}
}
event_route[xhttp:request] {
if (ws_handle_handshake()) {
# successful connection
#adding $conid to hash table
$sht(websocket=$conid) = $hu;
exit;
}
}
event_route[websocket:closed] {
xlog(L_DEBUG, WebSocket connection from $si:$sp has closed\n);
# deleting $conid from hash table
$sht(websocket=$conid) = $null;
}
Regards,
Takeshi
___
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] WebSocket data in TCP connection
On Mon, May 4, 2015 at 5:05 PM, mayamatakeshi mayamatake...@gmail.com
wrote:
On Sun, May 3, 2015 at 7:21 PM, mayamatakeshi mayamatake...@gmail.com
wrote:
Hello,
about module websocket, is it possible to associate a value with the TCP
connection and have this value readable when handling SIP requests on that
connection?
Hello, I have found a way to do it using htable.
Here is the gist of it in case someone else needs this:
loadmodule xhttp.so
loadmodule websocket.so
modparam(htable, htable, websocket=size=10)
route {
if(proto == WS) {
xlog(L_DEBUG, WebSocket check: conid=$conid
val=$sht(websocket=$conid)\n);
}
}
event_route[xhttp:request] {
if (ws_handle_handshake()) {
# successful connection
#adding $conid to hash table
$sht(websocket=$conid) = $hu;
exit;
}
}
event_route[websocket:closed] {
xlog(L_DEBUG, WebSocket connection from $si:$sp has closed\n);
# deleting $conid from hash table
$sht(websocket=$conid) = $null;
}
Checking again, deletion of the entry in the hash table is failing.
In older versions of kamailio, if I am not mistaken, i used:
$sht(websocket=$conid) = null;
but it seems in recent version null was replaced with $null (as if i use
null, kamailio will not start)
so I am using
$sht(websocket=$conid) = $null;
but it seems this doesn't work.
So, how do we currently delete an htable entry at config file?
Regards,
Takeshi
___
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] WebSocket data in TCP connection
On Mon, May 4, 2015 at 5:22 PM, mayamatakeshi mayamatake...@gmail.com
wrote:
On Mon, May 4, 2015 at 5:05 PM, mayamatakeshi mayamatake...@gmail.com
wrote:
On Sun, May 3, 2015 at 7:21 PM, mayamatakeshi mayamatake...@gmail.com
wrote:
Hello,
about module websocket, is it possible to associate a value with the TCP
connection and have this value readable when handling SIP requests on that
connection?
Hello, I have found a way to do it using htable.
Here is the gist of it in case someone else needs this:
loadmodule xhttp.so
loadmodule websocket.so
modparam(htable, htable, websocket=size=10)
route {
if(proto == WS) {
xlog(L_DEBUG, WebSocket check: conid=$conid
val=$sht(websocket=$conid)\n);
}
}
event_route[xhttp:request] {
if (ws_handle_handshake()) {
# successful connection
#adding $conid to hash table
$sht(websocket=$conid) = $hu;
exit;
}
}
event_route[websocket:closed] {
xlog(L_DEBUG, WebSocket connection from $si:$sp has closed\n);
# deleting $conid from hash table
$sht(websocket=$conid) = $null;
}
Checking again, deletion of the entry in the hash table is failing.
In older versions of kamailio, if I am not mistaken, i used:
$sht(websocket=$conid) = null;
but it seems in recent version null was replaced with $null (as if i use
null, kamailio will not start)
so I am using
$sht(websocket=$conid) = $null;
but it seems this doesn't work.
So, how do we currently delete an htable entry at config file?
My mistake. htable entry deletion by assignment to $null does work, the
problem is that when we get websocked:closed, $conid is not valid anymore.
I confirmed this by using this:
xlog(L_ERR, WebSocket connection from $si:$sp has closed.
conid=$conid\n);
/usr/local/src/git/sip-router-4.2/kamailio[6443]: ERROR: WebSocket
connection from 192.168.2.33:63179 has closed. conid=null
Wouldn't this be a bug? Shouldn't the $conid be available when that event
happens?
Regards,
Takeshi
___
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] WebSocket data in TCP connection
On Mon, May 4, 2015 at 5:36 PM, mayamatakeshi mayamatake...@gmail.com
wrote:
On Mon, May 4, 2015 at 5:22 PM, mayamatakeshi mayamatake...@gmail.com
wrote:
On Mon, May 4, 2015 at 5:05 PM, mayamatakeshi mayamatake...@gmail.com
wrote:
On Sun, May 3, 2015 at 7:21 PM, mayamatakeshi mayamatake...@gmail.com
wrote:
Hello,
about module websocket, is it possible to associate a value with the
TCP connection and have this value readable when handling SIP requests on
that connection?
Hello, I have found a way to do it using htable.
Here is the gist of it in case someone else needs this:
loadmodule xhttp.so
loadmodule websocket.so
modparam(htable, htable, websocket=size=10)
route {
if(proto == WS) {
xlog(L_DEBUG, WebSocket check: conid=$conid
val=$sht(websocket=$conid)\n);
}
}
event_route[xhttp:request] {
if (ws_handle_handshake()) {
# successful connection
#adding $conid to hash table
$sht(websocket=$conid) = $hu;
exit;
}
}
event_route[websocket:closed] {
xlog(L_DEBUG, WebSocket connection from $si:$sp has closed\n);
# deleting $conid from hash table
$sht(websocket=$conid) = $null;
}
Checking again, deletion of the entry in the hash table is failing.
In older versions of kamailio, if I am not mistaken, i used:
$sht(websocket=$conid) = null;
but it seems in recent version null was replaced with $null (as if i use
null, kamailio will not start)
so I am using
$sht(websocket=$conid) = $null;
but it seems this doesn't work.
So, how do we currently delete an htable entry at config file?
My mistake. htable entry deletion by assignment to $null does work, the
problem is that when we get websocked:closed, $conid is not valid anymore.
I confirmed this by using this:
xlog(L_ERR, WebSocket connection from $si:$sp has closed.
conid=$conid\n);
/usr/local/src/git/sip-router-4.2/kamailio[6443]: ERROR: WebSocket
connection from 192.168.2.33:63179 has closed. conid=null
Wouldn't this be a bug? Shouldn't the $conid be available when that event
happens?
Ah, nevermind,
I just need to use $si:$sp as htable key instead of $conid.
Regards,
Takeshi
___
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] Auth User is_subscriber
Hey, from the examples it looks like the typical usage of is_subscriber is with $fu ( From User ), however im not 100% sure I want this. in-fact, I want it to be the Auth User that is used. After all if a call was Authed, then we authoritatively know what user it is, and I think this should be used over and above the from user ( which could even be set to caller Id in some cases ). Im having some trouble getting is_subscriber to work with the Auth user, does anyone have an example of this working somewhere ? -- Sincerely Jay ___ 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] Auth User is_subscriber
On Monday 04 May 2015 19:08:56 jay binks wrote: in-fact, I want it to be the Auth User that is used. After all if a call was Authed, then we authoritatively know what user it is, and I think this should be used over and above the from user ( which could even be set to caller Id in some cases ). Im having some trouble getting is_subscriber to work with the Auth user, does anyone have an example of this working somewhere ? I don't understand what you are trying to do. If a user is authenticated, $au is set ($au!=$null) for that transaction. Authentication has nothing to do with the From headers in a message. Are you trying to prevent having to authorize subsequent transactions? ___ 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] Recommended configuration for TCP support
Hi, We sometimes get issues caused by truncated SDP bodies. Therefore, we are looking at using TCP instead of UDP. What is the recommended configuration when TCP is used? Currently, I only have the following: children=16 listen=udp:ip:5060 listen=tcp:ip:5060 disable_tcp=no tcp_connection_lifetime=605 (registration expiry is 600) Also, is there a difference with UDP regarding NAT handling? Thanks, Mickael ___ 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] TLSv1.2 and weak ciphers
Hi Daniel, Kamailio folks, We are trying to make our server more secure, but we have some issues. Right now, we have set the TLS method to method = TLSv1+ and cipher_list = HIGH The problem is, that there are still cipher suites offered which are not secure. E.g. If I check with the SSLLabs analizer, I see: This server supports anonymous (insecure) suites (see below for details). Grade set to F. Cipher Suites (SSL 3+ suites in server-preferred order; deprecated and SSL 2 suites always at the end) TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030) ECDH 256 bits (eq. 3072 bits RSA) FS 256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) ECDH 256 bits (eq. 3072 bits RSA) FS 256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH 256 bits (eq. 3072 bits RSA) FS 256 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x6b) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 256 TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x88) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 256 TLS_ECDH_anon_WITH_AES_256_CBC_SHA (0xc019) INSECURE 256 TLS_DH_anon_WITH_AES_256_GCM_SHA384 (0xa7) INSECURE 256 TLS_DH_anon_WITH_AES_256_CBC_SHA256 (0x6d) INSECURE 256 TLS_DH_anon_WITH_AES_256_CBC_SHA (0x3a) INSECURE 256 TLS_DH_anon_WITH_CAMELLIA_256_CBC_SHA (0x89) INSECURE 256 TLS_RSA_WITH_AES_256_GCM_SHA384 (0x9d) 256 TLS_RSA_WITH_AES_256_CBC_SHA256 (0x3d) 256 TLS_RSA_WITH_AES_256_CBC_SHA (0x35) 256 TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x84) 256 TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA (0xc012) ECDH 256 bits (eq. 3072 bits RSA) FS 112 TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x16) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 112 TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA (0xc017) INSECURE 112 TLS_DH_anon_WITH_3DES_EDE_CBC_SHA (0x1b) INSECURE 112 TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) 112 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) ECDH 256 bits (eq. 3072 bits RSA) FS 128 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) ECDH 256 bits (eq. 3072 bits RSA) FS 128 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH 256 bits (eq. 3072 bits RSA) FS 128 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 128 TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x67) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 128 TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 128 TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x45) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 128 TLS_ECDH_anon_WITH_AES_128_CBC_SHA (0xc018) INSECURE 128 TLS_DH_anon_WITH_AES_128_GCM_SHA256 (0xa6) INSECURE 128 TLS_DH_anon_WITH_AES_128_CBC_SHA256 (0x6c) INSECURE 128 TLS_DH_anon_WITH_AES_128_CBC_SHA (0x34) INSECURE 128 TLS_DH_anon_WITH_CAMELLIA_128_CBC_SHA (0x46) INSECURE 128 TLS_RSA_WITH_AES_128_GCM_SHA256 (0x9c) 128 TLS_RSA_WITH_AES_128_CBC_SHA256 (0x3c) 128 TLS_RSA_WITH_AES_128_CBC_SHA (0x2f) 128 TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x41) 128 How can we get rid of these _anon_ cipher suites? Thanks Attila ___ 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] TLSv1.2 and weak ciphers
Well, properly formulating the question is half-way to the solution :) I had to add cipher_list = HIGH:!ADH:!AECDH And all anon ciphers are gone. I hope this helps someone :) From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Attila Megyeri Sent: Monday, May 4, 2015 2:18 PM To: Kamailio (SER) - Users Mailing List Subject: [SR-Users] TLSv1.2 and weak ciphers Hi Daniel, Kamailio folks, We are trying to make our server more secure, but we have some issues. Right now, we have set the TLS method to method = TLSv1+ and cipher_list = HIGH The problem is, that there are still cipher suites offered which are not secure. E.g. If I check with the SSLLabs analizer, I see: This server supports anonymous (insecure) suites (see below for details). Grade set to F. Cipher Suites (SSL 3+ suites in server-preferred order; deprecated and SSL 2 suites always at the end) TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030) ECDH 256 bits (eq. 3072 bits RSA) FS 256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) ECDH 256 bits (eq. 3072 bits RSA) FS 256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH 256 bits (eq. 3072 bits RSA) FS 256 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x6b) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 256 TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x88) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 256 TLS_ECDH_anon_WITH_AES_256_CBC_SHA (0xc019) INSECURE 256 TLS_DH_anon_WITH_AES_256_GCM_SHA384 (0xa7) INSECURE 256 TLS_DH_anon_WITH_AES_256_CBC_SHA256 (0x6d) INSECURE 256 TLS_DH_anon_WITH_AES_256_CBC_SHA (0x3a) INSECURE 256 TLS_DH_anon_WITH_CAMELLIA_256_CBC_SHA (0x89) INSECURE 256 TLS_RSA_WITH_AES_256_GCM_SHA384 (0x9d) 256 TLS_RSA_WITH_AES_256_CBC_SHA256 (0x3d) 256 TLS_RSA_WITH_AES_256_CBC_SHA (0x35) 256 TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x84) 256 TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA (0xc012) ECDH 256 bits (eq. 3072 bits RSA) FS 112 TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x16) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 112 TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA (0xc017) INSECURE 112 TLS_DH_anon_WITH_3DES_EDE_CBC_SHA (0x1b) INSECURE 112 TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) 112 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) ECDH 256 bits (eq. 3072 bits RSA) FS 128 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) ECDH 256 bits (eq. 3072 bits RSA) FS 128 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH 256 bits (eq. 3072 bits RSA) FS 128 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 128 TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x67) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 128 TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 128 TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x45) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 128 TLS_ECDH_anon_WITH_AES_128_CBC_SHA (0xc018) INSECURE 128 TLS_DH_anon_WITH_AES_128_GCM_SHA256 (0xa6) INSECURE 128 TLS_DH_anon_WITH_AES_128_CBC_SHA256 (0x6c) INSECURE 128 TLS_DH_anon_WITH_AES_128_CBC_SHA (0x34) INSECURE 128 TLS_DH_anon_WITH_CAMELLIA_128_CBC_SHA (0x46) INSECURE 128 TLS_RSA_WITH_AES_128_GCM_SHA256 (0x9c) 128 TLS_RSA_WITH_AES_128_CBC_SHA256 (0x3c) 128 TLS_RSA_WITH_AES_128_CBC_SHA (0x2f) 128 TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x41) 128 How can we get rid of these _anon_ cipher suites? Thanks Attila ___ 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] kamcli - kamailio command line control tool
Hello, we just published a new command line tool for Kamailio management, named now kamcli, available at: * https://github.com/asipto/kamcli It is written in Python and adapted from a tool provided originally by a subcontractor for a specific deployment. While not being Python developers here, the benefits and flexibility proved extremely good. At this stage it is more an attempt to see if the community finds it useful and worth to get it developed further as part of Kamailio project. Short about the benefits/flexibility: - python is by default installed on OSes (including Mac OS X) (as opposite to Lua, for example) - became rather fast since Google invested in it - lot more knowledge base and developers out there (as opposite to Lua or Perl), along with tons of extensions - implementation is based on a CLI framework (Click) that makes it extremely easy to add new commands in a plugin-like fashion, therefore is easy to have custom commands when having specific needs (e.g., managing a custom database table used in kamailio.cfg via sqlops = add a new cmd_xyz.py in commands subfolder, without touching other files, not even the config) - help message is embedded in the command code file, making it easier to document commands - easy to validate parameters as well as format the output - handling kamcli configuration file options is also easy (ini format) One of my reasons of pushing this out was in the perspective of deprecating MI and working with JSONRPC fifo from command line -- I couldn't find easy ways to manage json docs with shell and common tools (e.g., cat, echo, grep, awk) only. Kamcli has implemented the JSONRPC over fifo command (see also jsonrpc-s kamailio module). Still, given the old initial implementation, at this moment, kamcli is relying on MI via fifo (mi_fifo) for some of the commands (e.g., dumping usrloc records from memory) -- (Just as side note: perhaps here we need to do a mapping, because name of commands are different, if we want to make a 'ctl transport agnostic' tool.) Here are few things to decide: - does it sound useful and are people finding it worth to develop it further? - what about the name, is it ok? Another one? If worth developing and deciding on the name, then the plan is to host the project on kamailio organization on github so each kamailio developer can code on it (it won't be inside kamailio source code tree, but a separate project inside same organization). So far, couple of commands were implemented when comparing with kamctl: - subscriber management (kamctl add/rm/passwd...) - user location management (kamctl ul ...) - database querying (kamctl db ...) - statistics (kamctl stats ...) - mi commands (kamctl mi ...) - jsonrpc commands (not in kamctl) While cross posted for the sake of getting the info to everyone in the community, let's have further discussions on sr-dev. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ 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] [sr-dev] kamcli - kamailio command line control tool
El Mon, 04 May 2015 16:16:01 +0200 Daniel-Constantin Mierla mico...@gmail.com escribió: Hello, we just published a new command line tool for Kamailio management, named now kamcli, available at: * https://github.com/asipto/kamcli Sounds like a nice tool to have. Useful to be able to deal with RPC commands from shell and deprecate Mi commands. Will test this week! thanks, Jon ___ 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] issue with TLS and 2 NIC interfaces
Are you having the same problem as myself? Thanks, V On Fri, May 1, 2015 at 8:20 PM, Slava Bendersky volga...@networklab.ca wrote: Hello Vik, I have similar setup, try define you server configuration in tls.cfg [server:ip address of alias interface:port of alias interface] method = TLSv1 verify_certificate = no require_certificate = no private_key = certificate = ca_list = crl = Slava -- *From: *Vik Killa vipki...@gmail.com *To: *sr-users sr-users@lists.sip-router.org *Sent: *Wednesday, April 29, 2015 4:32:21 PM *Subject: *[SR-Users] issue with TLS and 2 NIC interfaces Hello, if i have two interfaces (eth0 and eth0:0) I set kamailio to listen to the IP on eth0:0 This works great except when I try using TLS, kamailio routes traffic from eth0:0 to eth0 then to correct destination It should be just doing eth0:0 - correct destination If I use UDP/TCP I am not seeing this behavior. If I set kamailio to listen to eth0 and remove eth0;0, TLS works fine. I'm running kamailio compiled from source git master a few days ago. Is anyone else having this problem? I'm wondering if it's a bug. Thanks, V ___ 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] Recommended configuration for TCP support
Hello, where are typically those issues with truncated SDP? On the phones? If you use tcp and have phones behind the nat, it is recommended to not connect if there is no active connection after location lookup -- see core functions for tcp. Cheers, Daniel On 04/05/15 13:54, Mickael Marrache wrote: Hi, We sometimes get issues caused by truncated SDP bodies. Therefore, we are looking at using TCP instead of UDP. What is the recommended configuration when TCP is used? Currently, I only have the following: children=16 listen=udp:ip:5060 listen=tcp:ip:5060 disable_tcp=no tcp_connection_lifetime=605 (registration expiry is 600) Also, is there a difference with UDP regarding NAT handling? Thanks, Mickael ___ 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 -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ 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] issue with TLS and 2 NIC interfaces
Hello Vik, I don't have same problem it works fine for me, but I have same setup on public side where multiply aliases on interface is involved. Slava. From: Vik Killa vipki...@gmail.com To: sr-users sr-users@lists.sip-router.org Sent: Monday, May 4, 2015 12:54:21 PM Subject: Re: [SR-Users] issue with TLS and 2 NIC interfaces Are you having the same problem as myself? Thanks, V On Fri, May 1, 2015 at 8:20 PM, Slava Bendersky volga...@networklab.ca wrote: Hello Vik, I have similar setup, try define you server configuration in tls.cfg [server:ip address of alias interface:port of alias interface] method = TLSv1 verify_certificate = no require_certificate = no private_key = certificate = ca_list = crl = Slava From: Vik Killa vipki...@gmail.com To: sr-users sr-users@lists.sip-router.org Sent: Wednesday, April 29, 2015 4:32:21 PM Subject: [SR-Users] issue with TLS and 2 NIC interfaces Hello, if i have two interfaces (eth0 and eth0:0) I set kamailio to listen to the IP on eth0:0 This works great except when I try using TLS, kamailio routes traffic from eth0:0 to eth0 then to correct destination It should be just doing eth0:0 - correct destination If I use UDP/TCP I am not seeing this behavior. If I set kamailio to listen to eth0 and remove eth0;0, TLS works fine. I'm running kamailio compiled from source git master a few days ago. Is anyone else having this problem? I'm wondering if it's a bug. Thanks, V ___ 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
