Re: [SR-Users] presentity tabla, faster update when drop TCP/TLS connection

[Daniel-Constantin Mierla]

Hello,

I got distracted by other tasks and then the winter holidays. Can you
open an item on:

  - https://github.com/kamailio/kamailio/issues

not to forget again about this enhancemet request.

Cheers,
Daniel


On 21/11/2016 13:09, João Resende wrote:
> I can try to test, I think that this would be an important feature to
> kamailio.
>
> I know that I could do that in the client but it is better be arranged
> on the server side i guess.
>
> best
> João
>
> 2016-11-21 12:04 GMT+00:00 Daniel-Constantin Mierla  >:
>
> For the topic here I need to look a bit at the code in order to
> see what can be done now in an easier way. If I find it easier to
> just add some C code to simplify a bit kamailio.cfg, will you be
> interested in testing with kamailio master branch (devel version)?
> Because it would be rather impossible for me these days to setup
> quickly a testbed for such case..
>
> If you control the client, one thing is to rely on push
> notifications to optimize some communication with the server. I
> will also write more once I know how they can be related with the
> internal structures we have.
>
> Also, for battery life of the watcher as well as getting most up
> to date information, by subscribing only when the person it's
> looking at the contact in the body list and subscribe with
> expires=0 in order to get only one notification...
>
> Cheers,
> Daniel
>
>
> On 21/11/16 12:43, João Resende wrote:
>> Sorry for the double email, 
>>
>> I do not use UDP.
>>
>> I can control also the client side, what do you think that is the
>> simplest way to archive this goal?
>>
>> best
>> João
>>
>>
>>
>>
>> 2016-11-21 11:37 GMT+00:00 João Resende > >:
>>
>> Hello,
>>
>> Can be both option TCP or TLS. I don't test with udp.
>>
>> best,
>> João
>>
>>
>>
>
> -- 
> Daniel-Constantin Mierla
> http://twitter.com/#!/miconda  - 
> http://www.linkedin.com/in/miconda
> 
> Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - 
> http://www.asipto.com
>
-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 8-10, 2017 - 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

[SR-Users] Kamailio v5.0 - development frozen

[Daniel-Constantin Mierla]

Hello,

development (master) branch of Kamailio enters now in pre-release phase
for version 5.0.0. Therefore, no new feature should be pushed to master
until we create a dedicated branch for 5.0 (expected to be in about 4
weeks or so).

If in doubt to push or not a commit to master, push it first on a
personal branch (or attach to an email) and discuss it on sr-dev. The
new modules can be a bit more dynamic if there is need to get them to
the right shape (e.g., like decision to rename functions, parameters or
adjust database structure).

We hope to get many people involved in testing, to reach a stable state
before releasing 5.0.0. If you want to get involved and need assistance,
don't hesitate to write to mailing lists.

Besides the new features, there were two major changes for 5.0:

1) source code tree restructuring - this should not affect the stability
of the code, only installation scripts or packaging may still need tuning

2) mi (management/control interface) code has been removed. SIP routing
code should not be affected by this change that much, but testing of RPC
commands needs a special care. There are few RPC commands not ported yet
from the MI code, they can be done during the testing period

Moreover, help with updating the wiki page for migration from 4.4 to 5.0
as well as what is new in 5.0 is very appreciated. I will try post
updates about them very soon.

Many thanks to everyone involved in development of 5.0 and the early
testers that played with master branch so far.

Cheers,
Daniel


-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 8-10, 2017 - 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

[SR-Users] how to immediately close a tls connection

[Andy]

Hi,

trying to close a tls connection immediately,

have ref to the connection (tcpconn) pointer

please suggest,
thanks!



--
View this message in context: 
http://sip-router.1086192.n5.nabble.com/how-to-immediately-close-a-tls-connection-tp154630.html
Sent from the Users mailing list archive at Nabble.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

[SR-Users] RTPProxy with VPN

[Rodrigo Moreira]

Hello,

I am having problems with RTPPROXY. I need it to work as a bridge. On one
side will have a VPN tunnel called a tun0, on the other an eth0 interface.
Is it possible for RTPPROXY to run correctly in this scenario?

How can I test if RTPPROXY is running correctly? Is there any command? What
would the configuration look like inside /etc/default/rtpproxy

Please help me.

Best regards
-- 
Rodrigo M.
(37) 9132-4539
(34) 9889-3069
rodrigo.moreira2007
___
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] location

[Slava Bendersky]

Hello Daniel, 
Based on wiki page 
http://www.kamailio.org/docs/modules/4.4.x/modules/registrar.html#registrar.f.save
 

I should be able do location save with pv var and supply uri. 

save("location", "0x00", "sip:t...@kamailio.org"); 


* 

uri (optional - flags param has to be set and can be 0 for default behavior) - 
SIP URI to do be used instead of To header URI. It can be a dynamic string with 
pseudo-variables. 
I tested multiply variation all of them ignore pv var. 


Slava. 



From: "volga629"  
To: "miconda"  
Cc: "sr-users"  
Sent: Monday, January 2, 2017 11:40:33 AM 
Subject: Re: [SR-Users] location 

Hello Daniel, 
I am trying save user contact on reply 200 OK from freeswitch. Contact is set 
in $avp(aor) which contain updated user location. 

Slava. 


From: "miconda"  
To: "volga629" , "sr-users" 
 
Sent: Monday, January 2, 2017 10:45:34 AM 
Subject: Re: [SR-Users] location 



Hello, 

the third parameter is not for contact, it is the address of record -- the user 
address, eg., [ mailto:al...@sipdomain.com | al...@sipdomain.com ] , not [ 
mailto:al...@phone.ip | al...@phone.ip ] 
What exactly do you need to achieve? Maybe there are other options that you can 
use. 

Cheers, 
Daniel 

On 02/01/2017 15:12, Slava Bendersky wrote: 



Hello Daniel, 
Meaning if(!save("location", "0x04", "$var(aor)")) ---> $var(aor) ignored. It 
use default Contact. Here are the log 

$var(aor) = "sip:" + $tU + "@" + $(avp(rcvcontact){uri.host}) + ":" + 
$(avp(rcvcontact){uri.port}); 

INFO: 

Re: [SR-Users] VERY IMPORTANT: deciding when to remove the MI code

[Daniel-Constantin Mierla]

Hello,

thanks for testing...

Can you use latest master version, load jsonrpcs.so module and then
issue the command:

kamctl rpc cr.dump_routes

Note that you may need to edit kamctlrc and set ctl engine to RPCFIFO if
you have an older version of kamctlrc file installed.

Cheers,
Daniel


On 04/01/2017 11:58, Yasin CANER wrote:
>
> Hello;
>
> lastest master branched is pulled and worked with kamailio -ddd -E
> . cr.reload method works fine but cr.dump_routes gives error message
> like "error: 500 - Internal error - carrier structure"
>
> debug messages are here
>
> "[  master]# 13(1479) DEBUG: ctl [../../core/io_wait.h:380]:
> io_watch_add(): DBG: io_watch_add(0x7f05c23756c0, 8, 3, 0x1722410),
> fd_no=1
> 13(1479) DEBUG: ctl [io_listener.c:442]: handle_new_connect():
> handle_stream read: new connection (1) on /var/run/kamailio//kamailio_ctl
> 13(1479) DEBUG: carrierroute [cr_fifo.c:1177]: cr_rpc_dump_routes():
> start processing of data
> 13(1479) DEBUG: ctl [io_listener.c:495]: handle_stream_read():
> handle_stream read: eof on /var/run/kamailio//kamailio_ctl
> 13(1479) DEBUG: ctl [../../core/io_wait.h:602]: io_watch_del(): DBG:
> io_watch_del (0x7f05c23756c0, 8, -1, 0x10) fd_no=2 called
> "
>

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 8-10, 2017 - 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

[SR-Users] Diameter AVP handling from kamaiio.cfg

[Zoltán Miricz]

Dear All,

I'm wondering is it possible to catch Diameter Messages and their AVP
values from kamailio.cfg just like for SIP messages? (Using pseudo
variables)

I looked into this function from the attached S-CSCF example.

route[REG_MAR_REPLY]
{

#this is async so to know status we have to check the reply avp

xlog("L_DBG","maa_return code is *$avp(s:maa_return_code)*\n");

Sadly it gives back only 1, -1, -2. (which is based on cxdx_mar.c the rc)
What I mainly looking for is the EXPERIMENTAL_RESULT (experimental_rc) and
some different AVP values besides.


Thank you very much in advance!

*Cheers,*
*Zoltan*
#!KAMAILIO
#
# This config file implements the basic P-CSCF functionality
# - web: http://www.kamailio.org
# - git: http://sip-router.org
#
# Refer to the Core CookBook at http://www.kamailio.org/dokuwiki/doku.php
# for an explanation of possible statements, functions and parameters.
#
# Direct your questions about this file to: .
#
# For more information about the various parameters, functions and statements
# try http://sip-router.org/wiki/ .
#

### Defined Values #
# *** Value defines - IDs used later in config

# - flags
#   FLT_ - per transaction (message) flags
#   FLB_ - per branch flags

#!define FLT_CAPTURE 1
#!define FLT_DIALOG 2

#!define DLG_TIMEOUT_AVP "i:1"
#!define RR_CUSTOM_USER_AVP "i:2"
#!define DISPATCHER_DST_AVP "i:3"
#!define DISPATCHER_GRP_AVP "i:4"
#!define DISPATCHER_CNT_AVP "i:5"
#!define PDB_CARRIER "i:6"


### Global Parameters #

include_file "scscf.cfg"

#!ifdef WITH_DEBUG
debug=5
log_stderror=no
sip_warning=yes
#!else
debug=2
log_stderror=no
sip_warning=no
#!endif

### for foreground operation by FE
fork=no
log_stderror=yes
children=4

alias=HOSTNAME

user_agent_header="User-Agent: Kamailio S-CSCF"
server_header="Server: Kamailio S-CSCF"

/* comment the next line to enable the auto discovery of local aliases
   based on reverse DNS on IPs (default on) */
auto_aliases=no

check_via=no# (cmd. line: -v)
dns=no  # (cmd. line: -r)
rev_dns=no  # (cmd. line: -R)

# Do SRV-Loadbalancing:
dns_srv_lb=yes
# Always: Also try IPv6:
dns_try_ipv6=yes
# Always prefer IPv6:
dns_cache_flags=6
# DNS-Based failover
use_dns_failover = on
# Query NAPTR-Records as well:
dns_try_naptr=no

#!ifdef WITH_XMLRPC
#!ifndef WITH_TCP
#!define WITH_TCP
#!endif
#!ifndef TCP_PROCESSES
# Number of TCP Processes
#!define TCP_PROCESSES 3
#!endif
#!endif

#!ifdef WITH_TCP
# life time of TCP connection when there is no traffic
# - a bit higher than registration expires to cope with UA behind NAT
tcp_connection_lifetime=3615
#!ifdef TCP_PROCESSES
tcp_children=TCP_PROCESSES
#!endif
#!else
disable_tcp=yes
#!endif

#children=64

system.shutdownmode = 0 desc "System shutdown mode"

# -- module loading --
#mpath="/usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/:/usr/lib/kamailio/modules_k/:/usr/lib/kamailio/modules/"
# (we try both the lib64 and the lib directory)

loadmodule "tm.so"
loadmodule "pv.so"
loadmodule "sl.so"
loadmodule "rr.so"
loadmodule "ims_dialog.so"
loadmodule "textops.so"
loadmodule "maxfwd.so"
loadmodule "xlog.so"
loadmodule "sanity.so"
loadmodule "siputils.so"
loadmodule "kex.so"
#!ifdef DB_URL
loadmodule "presence"
#!endif

#!ifdef DB_URL
loadmodule "db_mysql"
#!ifdef DB_URL2
loadmodule "db_cluster"
#!endif
#!endif

#loadmodule "dispatcher"

loadmodule "enum"
loadmodule "uac"

# Control interfaces:
#loadmodule "ctl"
#loadmodule "cfg_rpc"
#loadmodule "mi_rpc"
#loadmodule "mi_fifo"
#!ifdef WITH_XMLRPC
loadmodule "xmlrpc"
#!endif

loadmodule "cdp.so"
loadmodule "cdp_avp.so"

loadmodule "ims_usrloc_scscf.so"
loadmodule "ims_registrar_scscf.so"
loadmodule "ims_auth.so"
loadmodule "ims_isc.so"

#!ifdef WITH_RO
loadmodule "ims_charging.so"
#!endif

#!ifdef CAPTURE_NODE
loadmodule "siptrace.so"
#!endif

#!ifdef WITH_DEBUG
loadmodule "debugger.so"
#!endif

# - setting module-specific parameters ---
#!ifdef DB_URL2
# - db_cluster params -
modparam("db_cluster", "connection", DB_URL)
modparam("db_cluster", "connection", DB_URL2)
modparam("db_cluster", "cluster", "cluster1=>con1=2s2s;con2=1s1s")
#!endif

# - presence params -
#!ifdef DB_URL
#!ifdef DB_URL2
modparam("presence", "db_url", "cluster://cluster1")
#!else
modparam("presence", "db_url", DB_URL)
#!endif
#modparam("presence", "fallback2db", 1)
modparam("presence", "db_update_period", 20)
#!endif

# - mi_fifo params -
#modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo")
#modparam("mi_fifo", "fifo_mode", 0666)
#modparam("mi_fifo", "fifo_user", "kamailio")
#modparam("mi_fifo", "fifo_group", "kamailio")

# - mi_fifo params -
#modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo")
#modparam("mi_fifo", "fifo_mode", 0666)
#modparam("mi_fifo", "fifo_user", "kamailio")
#modparam("mi_fifo", "fifo_group", "kamailio")

# - tm params -
# auto-discard 

Re: [SR-Users] VERY IMPORTANT: deciding when to remove the MI code

[Yasin CANER]

  
  
Hello;
      I think problem is my config. 4.4.4 version is cloned and try
  to run. it runs kamailio but kamctl cr reload command gives error
  "ERROR: This command requires a database engine - none was loaded"
  I am digging configuration. In additon , how can understand
  carrier module is loaded?
  
  Cheers.
  
  

4.01.2017 13:58 tarihinde Yasin CANER
  yazdı:


  
  Hello;
      lastest master
  branched is pulled and worked with kamailio -ddd -E .
  cr.reload method works fine but cr.dump_routes gives error
  message like "error: 500 - Internal error - carrier structure"
  

      debug messages
  are here
  "[  master]#
  13(1479) DEBUG: ctl [../../core/io_wait.h:380]:
  io_watch_add(): DBG: io_watch_add(0x7f05c23756c0, 8, 3,
  0x1722410), fd_no=1
  13(1479) DEBUG: ctl [io_listener.c:442]: handle_new_connect():
  handle_stream read: new connection (1) on
  /var/run/kamailio//kamailio_ctl
  13(1479) DEBUG: carrierroute [cr_fifo.c:1177]:
  cr_rpc_dump_routes(): start processing of data
  13(1479) DEBUG: ctl [io_listener.c:495]: handle_stream_read():
  handle_stream read: eof on /var/run/kamailio//kamailio_ctl
  13(1479) DEBUG: ctl [../../core/io_wait.h:602]:
  io_watch_del(): DBG: io_watch_del (0x7f05c23756c0, 8, -1,
  0x10) fd_no=2 called
  "
  
  My table structer  is that;
  
  
  
 
  
domain_name




















  
  
#
  id
 domain




















  
  
1'
 'myip'




















  
  
























  
  
carrierroute
  
  
#
  id
 carrier
 domain
 scan_prefix
 flags
 mask
 prob
 strip

  rewrite_host

  rewrite_prefix

  rewrite_suffix
 description
  
  
1'
 '1'
 '1'
 ''
 '0'
 '0'
 '1'
 '0'
 'ip:5060'
 ''
 ''
 '338'
  
  
























  
  
carrier_name




















  
  
#
  id
 carrier




















  
  
1'
 'default'




















  
  

Re: [SR-Users] VERY IMPORTANT: deciding when to remove the MI code

[Yasin CANER]

  
  
Hello;
    lastest master
branched is pulled and worked with kamailio -ddd -E . cr.reload
method works fine but cr.dump_routes gives error message like
"error: 500 - Internal error - carrier structure" 
  
    debug messages
are here
"[  master]#
13(1479) DEBUG: ctl [../../core/io_wait.h:380]: io_watch_add():
DBG: io_watch_add(0x7f05c23756c0, 8, 3, 0x1722410), fd_no=1
13(1479) DEBUG: ctl [io_listener.c:442]: handle_new_connect():
handle_stream read: new connection (1) on
/var/run/kamailio//kamailio_ctl
13(1479) DEBUG: carrierroute [cr_fifo.c:1177]:
cr_rpc_dump_routes(): start processing of data
13(1479) DEBUG: ctl [io_listener.c:495]: handle_stream_read():
handle_stream read: eof on /var/run/kamailio//kamailio_ctl
13(1479) DEBUG: ctl [../../core/io_wait.h:602]: io_watch_del():
DBG: io_watch_del (0x7f05c23756c0, 8, -1, 0x10) fd_no=2 called
"

My table structer  is that;



   

  domain_name
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  # id
   domain
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  1'
   'myip'
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  carrierroute


  # id
   carrier
   domain
   scan_prefix
   flags
   mask
   prob
   strip
   rewrite_host
   rewrite_prefix
   rewrite_suffix
   description


  1'
   '1'
   '1'
   ''
   '0'
   '0'
   '1'
   '0'
   'ip:5060'
   ''
   ''
   '338'


  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  carrier_name
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  # id
   carrier
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  1'
   'default'
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  domain
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  # id
   domain
   did
   last_modified
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  1'
   'myip'
   '1'
   '2016-02-11 12:18:00'
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

  





3.01.2017 12:55 tarihinde
  Daniel-Constantin Mierla yazdı:


  
  Hello,
  quick follow up to see if you got any chance to test with
latest master.
  

Re: [SR-Users] unexpected char [#015]

[AL S]

Hi,


Here is another failed test call with closing angle bracket:


Kamailio log

Jan  3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: ERROR:  
[parser/parse_to.c:626]: ERROR: parse_to : unexpected char [#015] in status 6: 
<<> .



FROM and TO in INVITE received by Kamailio


From: ;tag=gK0c9dcf07

To: ;tag=gK0c002371



FROM and TO in INVITE forward by Kamailio for the same call


From: ;tag=gK0c9dcf07

To: ;tag=gK0c002371


Thanks,

AS


From: sr-users  on behalf of AL S 

Sent: Wednesday, January 4, 2017 10:00:52 AM
To: sr-users@lists.sip-router.org
Subject: [SR-Users] unexpected char [#015]


Hi,


Kamailio is complaining about unexpected char [#015] in TO header of INVITE:


Jan  3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: ERROR:  
[parser/parse_to.c:626]: ERROR: parse_to : unexpected char [#015] in status 6: 
<<> .
Jan  3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: ERROR:  
[parser/msg_parser.c:180]: ERROR: get_hdr_field: bad to header
Jan  3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: INFO:  
[parser/msg_parser.c:353]: ERROR: bad header field [To: 

Re: [SR-Users] unexpected char [#015]

[Daniel-Constantin Mierla]

Hello,


the To URI starts with < -- see:


To:  -- it should be before ;tag= if you don't want tag
to be uri parameter instead of to header parameter (as in rfc).

Cheers,
Daniel
On 04/01/2017 16:00, AL S wrote:
>
> Hi,
>
>
> Kamailio is complaining about unexpected char [#015] in TO header of
> INVITE:
>
>
> Jan  3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: ERROR:
>  [parser/parse_to.c:626]: ERROR: parse_to : unexpected char
> [#015] in status 6: <<> .
> Jan  3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: ERROR:
>  [parser/msg_parser.c:180]: ERROR: get_hdr_field: bad to header
> Jan  3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: INFO:
>  [parser/msg_parser.c:353]: ERROR: bad header field [To:
>  Jan  3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: ERROR: tm
> [t_lookup.c:1118]: ERROR: reply cannot be parsed
>
> Here is the TO header for the same call in both text and hex format. I
> am unable to see any ^M char in this TO header. 
>
> To: 
> 546f3a203c7369703a323035373033303939374037322e33312e31322e3136313e3b7461673d674b30303663623038620d0a
>
> Any help would be appreciated. 
>
> AS,
>
>
>
> ___
> 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
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 8-10, 2017 - 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

[SR-Users] unexpected char [#015]

[AL S]

Hi,


Kamailio is complaining about unexpected char [#015] in TO header of INVITE:


Jan  3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: ERROR:  
[parser/parse_to.c:626]: ERROR: parse_to : unexpected char [#015] in status 6: 
<<> .
Jan  3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: ERROR:  
[parser/msg_parser.c:180]: ERROR: get_hdr_field: bad to header
Jan  3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: INFO:  
[parser/msg_parser.c:353]: ERROR: bad header field [To: 

[SR-Users] IMPORTANT: MI code removed (or disabled)

[Daniel-Constantin Mierla]

Hello,

as of now, no active MI reladed code should be in master branch -- the
internal library kmi and the mi_datagram, mi_fifo, mi_xmlrpc, mi_rpc and
pua_mi modules were removed.

Couple of modules still have some mi code disabled with ifdefs, they are
pending the port to RPC commands. These are:

  - carrierroute
  - ims_dialog
  - mohqueue
  - p_usrloc
  - pdb
  - rtpengine
  - userblacklist
  - utils

They should be updated in the next few days.

With MI code removed, the code is slimmer and the development effort is
reduced -- in the recent past there were various issue rising due to
usage of the old line-based MI commands.

From now on, the RPC interface has to be used for interacting with
kamailio at runtime.

The tools:
   - kamctl - was already migrated to use RPC via jsonrpcs module.
   - kamcmd - was developed to use only RPC interface via ctl module.
   - kamcli - is also working with RPC via jsonrpcs module

Helping with testing the RPC commands is very appreciated -- open an
issue on bug tracker whenever you discover a problem.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 8-10, 2017 - 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] VERY IMPORTANT: deciding when to remove the MI code

[Yasin CANER]

  
  
Hello;
    kamailio Version 4.1 installed and tried same configuration
  with carrierroute. it is working kamctl function but i had to
  remove  a "require_dbengine"
  function in kamctl. it checks that is it suport db_mysql. Anyway ,
  configuration is working with kamctl cr , it can dumping and
  reload.
link
https://github.com/kamailio/kamailio/blob/dc5a9e96a20c1099601ef5c6516458532da3124a/utils/kamctl/kamctl
line (1432)

Cheers.




[root@Test  kamailio41]# kamctl cr dump
  Printing routing information:
  Printing tree for carrier 'default' (1)
  Printing tree for domain 'myip' (1)
    NULL: 100.000 %, ' ip:5060': ON, '0', '', '', '338'
  


4.01.2017 14:24 tarihinde Yasin CANER
  yazdı:


  
  Hello;
    I think problem is my config. 4.4.4 version is cloned and
try to run. it runs kamailio but kamctl cr reload command gives
error "ERROR: This command requires a database engine - none was
loaded" I am digging configuration. In additon , how can
understand carrier module is loaded?

Cheers.


  
  4.01.2017 13:58 tarihinde Yasin CANER
yazdı:
  
  

Hello;
    lastest
master branched is pulled and worked with kamailio -ddd -E .
cr.reload method works fine but cr.dump_routes gives error
message like "error: 500 - Internal error - carrier
structure" 
  
    debug
messages are here
"[  master]#
13(1479) DEBUG: ctl [../../core/io_wait.h:380]:
io_watch_add(): DBG: io_watch_add(0x7f05c23756c0, 8, 3,
0x1722410), fd_no=1
13(1479) DEBUG: ctl [io_listener.c:442]:
handle_new_connect(): handle_stream read: new connection (1)
on /var/run/kamailio//kamailio_ctl
13(1479) DEBUG: carrierroute [cr_fifo.c:1177]:
cr_rpc_dump_routes(): start processing of data
13(1479) DEBUG: ctl [io_listener.c:495]:
handle_stream_read(): handle_stream read: eof on
/var/run/kamailio//kamailio_ctl
13(1479) DEBUG: ctl [../../core/io_wait.h:602]:
io_watch_del(): DBG: io_watch_del (0x7f05c23756c0, 8, -1,
0x10) fd_no=2 called
"

My table structer  is that;



   

  domain_name
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  # id
   domain
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  1'
   'myip'
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  carrierroute


  # id
   carrier
   domain
  
scan_prefix
   flags
   mask
   prob
   strip
  
rewrite_host
  
rewrite_prefix
  
rewrite_suffix
  
description


  1'
   '1'
   '1'
   ''
   '0'
   '0'
   '1'
   '0'
   'ip:5060'
   ''
   ''
   '338'


  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
   

Re: [SR-Users] sr-users Digest, Vol 140, Issue 3

[hema...@advaitamtech.com]

Hello Vicente,

Thanks for your response,

In response to your query,

Yes i have Built ndb_redis module and i can see ndb_redis.so in 
/usr/local/lib64/kamailio/modules folder, I have installed hiredis depenency 
also,

I have also modified the kamailio.cfg file loadmodule and modparam list,

I feel like the way i am using the redis_cmd is wrong, I think i need to add it 
in route section of kamailio.cfg file, Can you please guide me regarding how to 
use redis db in order to update user information to DB on registration of each 
user.

Thanks & Regards
Hemanth


Message: 8
Date: Wed, 4 Jan 2017 14:41:42 +0530 (IST)
From: "hema...@advaitamtech.com" 
To: sr-users@lists.sip-router.org
Subject: [SR-Users] Regarding usage of Redis Module in Kamailio core
Message-ID: <1483521102.18025...@apps.rackspace.com>
Content-Type: text/plain;charset=UTF-8

Hello,

I am using Kamailio as a SIP proxy,

I want to store Registered user information in Redis DB,

I am able to configure REDIS DB, But i am not able to run the redis command from

Kamailio core using the function 

"redis_cmd("srvN","SET key 1", "r")"

I am getting undefined reference error as below

"/usr/local/src/kamailio-4.4/kamailio/receive.c:208: undefined reference to 
`redis_cmd'"

can anyone please help me to fix this issue

Thanks & Regards
Hemanth




--

Message: 9
Date: Wed, 4 Jan 2017 10:50:05 +0100
From: Vicente Hernando 
To: sr-users@lists.sip-router.org
Subject: Re: [SR-Users] Regarding usage of Redis Module in Kamailio
core
Message-ID: 
Content-Type: text/plain; charset=utf-8; format=flowed

Hello Hemanth,

just a quick response, I would check if you compiled ndb_redis module 
correctly (also if you have hiredis library dependency).

Also I would check if you loaded ndb_redis module in your configuration 
file.


Regards,
Vicente.

On 01/04/2017 10:11 AM, hema...@advaitamtech.com wrote:
> Hello,
>
> I am using Kamailio as a SIP proxy,
>
> I want to store Registered user information in Redis DB,
>
> I am able to configure REDIS DB, But i am not able to run the redis command 
> from
>
> Kamailio core using the function
>
>  "redis_cmd("srvN","SET key 1", "r")"
>
> I am getting undefined reference error as below
>
> "/usr/local/src/kamailio-4.4/kamailio/receive.c:208: undefined reference to 
> `redis_cmd'"
>
> can anyone please help me to fix this issue
>
> Thanks & Regards
> Hemanth
>
>
> ___
> 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





--

Subject: Digest Footer

___
sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


--

End of sr-users Digest, Vol 140, Issue 3




___
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] Regarding usage of Redis Module in Kamailio core

[Vicente Hernando]

Hello Hemanth,

just a quick response, I would check if you compiled ndb_redis module 
correctly (also if you have hiredis library dependency).


Also I would check if you loaded ndb_redis module in your configuration 
file.



Regards,
Vicente.

On 01/04/2017 10:11 AM, hema...@advaitamtech.com wrote:

Hello,

I am using Kamailio as a SIP proxy,

I want to store Registered user information in Redis DB,

I am able to configure REDIS DB, But i am not able to run the redis command from

Kamailio core using the function

 "redis_cmd("srvN","SET key 1", "r")"

I am getting undefined reference error as below

"/usr/local/src/kamailio-4.4/kamailio/receive.c:208: undefined reference to 
`redis_cmd'"

can anyone please help me to fix this issue

Thanks & Regards
Hemanth


___
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] Regarding usage of Redis Module in Kamailio core

[hema...@advaitamtech.com]

Hello,

I am using Kamailio as a SIP proxy,

I want to store Registered user information in Redis DB,

I am able to configure REDIS DB, But i am not able to run the redis command from

Kamailio core using the function 

"redis_cmd("srvN","SET key 1", "r")"

I am getting undefined reference error as below

"/usr/local/src/kamailio-4.4/kamailio/receive.c:208: undefined reference to 
`redis_cmd'"

can anyone please help me to fix this issue

Thanks & Regards
Hemanth


___
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