gmane.comp.voip.openser.user

Re: [SR-Users] Local subscriber lookup / usrloc

Daniel-Constantin Mierla — 2013-06-19T22:29:11

Hello,

On 6/19/13 9:29 PM, Daniel W. Graham wrote:

sqlops is recommended for sql queries if you are not tied to some avp 
operations.

If you just want to check if the subscriber exists, there is a function 
in auth_db module:
- http://kamailio.org/docs/modules/stable/modules/auth_db.html#idp42920

Another one should be in uri_db, available in older versions but not 
that much flexible as the above one.

Cheers,
Daniel

Re: [SR-Users] Script - /kamailio.log -> MongoDB ?

Daniel-Constantin Mierla — 2013-06-19T22:25:25

Hello,

Kamailio sends the logs to syslog, perhaps you can find something on the 
net that allows syslog application to write to mongodb. I know some 
versions have option to write to a database or send via network to 
another host.

Cheers,
Daniel

On 6/19/13 9:27 PM, Mick Stevens wrote:

Re: [SR-Users] Help with install using GIT

John Doe — 2013-06-19T21:13:56

Thank you Daniel, it worked.
----------------------------------------

[SR-Users] Local subscriber lookup / usrloc

Daniel W. Graham — 2013-06-19T19:29:21

My kamailio implementation sits in front of a group of asterisk servers, when a call comes into kamailio it does a series of checks on the location of the src and dst to determine if the call is allowed. If the src is PSTN  and called user is found in the location table the call is passed to an asterisk server for further processing of call forwarding options / voicemail / ring time setting etc. However if the called account is not found (not currently registered) the call is then discarded and voicemail etc can never be accessed.

I can add a avp_db_query to fetch user from the subscriber table vs location table lookup. Just wondering if there are any built in functions or other efficient ways to handle this that others are doing.

Thanks for any input

-Dan

[SR-Users] Script - /kamailio.log -> MongoDB ?

Mick Stevens — 2013-06-19T19:27:46

Hi All, 

I'm not a programmer & am new to Kamailio (but have managed to master 'ish FreeSWITCH) & am looking for a script I can use/adapt/learn from to import kamailio.log into MongoDB. 

Any offers?


Mick
 
Rgds, Mick
Tel/SMS. +44(0)7967 594432

Email/IM/MSN/Skype. mickstevens-/E1597aS9LQAvxtiuMwx3w< at >public.gmane.org
www.facebook.com/mickstevens
< at >mickstevens

[SR-Users] Variables in event_route[sl:local-response]

Sergey Okhapkin — 2013-06-19T18:58:42

Which variables I can use in 
event_route[sl:local-response] route to xlog 
proto:ip:port to which the response will be 
sent?

event_route[sl:local-response] {                                                                                            
        xlog("L_INFO","Local response to 
*$??*\n$mb\n");                                                                      
}

Re: [SR-Users] SIP Trunks Location

Stoyan Mihaylov — 2013-06-19T17:19:49

It depends.
I can imagine next scenarios:
1. Under SIP trunks you mean calls from your provider to you
A) In case your provider can send calls to you - then you can use Kamailio,
accepting all calls from your provider - based on IP.
B) In case your provider expects registration from your system - then, at
least I - dont know how to do only with Kamailio - Asterisk can register
easily to every provider.
2. Under SIP trunks you mean calls from you to World through your provider.
A) Your provider can accept all calls from you based on IP - Kamailio can
directly forward calls to your provider.
B) Your provider expects authentication - then again I dont know how this
can be done through Kamailio, but Asterisk can do it easily.

My suggestion is - you can use Kamailio for registration of users and load
balancing, and asterisk servers for everything else.


On Wed, Jun 19, 2013 at 7:30 PM, Jose Suero <ms-xaOjcqbfoNA< at >public.gmane.org> wrote:

[SR-Users] SIP Trunks Location

Jose Suero — 2013-06-19T16:30:17

Hi

I'm planning to set kamailio in front of an farm of pbx servers 
(haven't decided on freeswitch or asterisk) there's a million tutorials 
on how to do this, what I haven't found is what part of my setup 
actually handles the sip trunks my phone company provides me with.

What's the best practice when It comes to this?

Is kamailio going to be receiving the calls from the trunk and passing 
them to the PBX or is it the other way around?


please advice

Thanks in advance

Jose Suero

Re: [SR-Users] Dispatcher behaviour

Mino Haluz — 2013-06-19T14:21:05

Thank you for explanation Daniel.

Re: [SR-Users] short name in syslog

Victor V. Kustov — 2013-06-19T14:08:08

Hello, Daniel-Constantin Mierla!


ok. really it's simplest way.

--
 WBR, Victor
  JID: coyote-B6aY196UtR8< at >public.gmane.org
  JID: coyote-N7mKgWFaI+z9Ct1PEtb4cw< at >public.gmane.org
  I use FREE operation system: 3.9.4-calculate GNU/Linux

[SR-Users] Help with install using GIT

John Doe — 2013-06-19T14:06:36

Re: [SR-Users] short name in syslog

Daniel-Constantin Mierla — 2013-06-19T13:41:09

Hello,

On 6/19/13 3:30 PM, Victor V. Kustov wrote:
actually it is useful when having more installations on custom paths, 
all running. like:

/usr/local/kamailio-lb/sbin/kamailio
/usr/local/kamailio-proxy/sbin/kamailio

If you want just the short name, you can set log_name="kamailio".
In your first email you pasted two different WARNING messages, saying it 
is fixing something to them. At first sight I thought is some missing or 
extra eol.

OK, but again, I don't think the patch is needed, log_name parameter was 
added to have custom log names, so you can set it to basename.

Cheers,
Daniel

Re: [SR-Users] short name in syslog

Victor V. Kustov — 2013-06-19T13:30:23

Hello, Daniel-Constantin!



it fix long name of daemon in syslog.

/usr/local/sbin/kamailio => kamailio

full path doesnot needed in logs. 



sorry?


yes, i check it


#grep libgen *.c
cfg_parser.c:#include <libgen.h>  --already use
main.c:#include <libgen.h>        --my fix
ut.c:#include <libgen.h>  --already use



--
 WBR, Victor
  JID: coyote-B6aY196UtR8< at >public.gmane.org
  JID: coyote-N7mKgWFaI+z9Ct1PEtb4cw< at >public.gmane.org
  I use FREE operation system: 3.9.4-calculate GNU/Linux

Re: [SR-Users] short name in syslog

Daniel-Constantin Mierla — 2013-06-19T12:49:18

Hello,

what is it fixing actually? Was there an end of line?

Is basename portable? Because I see requires a new header to be 
included, if not maybe we can implement the function by ourselves to fix 
what should be fixed.

Cheers,
Daniel

On 6/19/13 12:51 PM, Victor V. Kustov wrote:

Re: [SR-Users] Dispatcher behaviour

Daniel-Constantin Mierla — 2013-06-19T12:44:30

Hello,

On 6/19/13 1:57 PM, Mino Haluz wrote:

probing is intermediary state, toward active or inactive. So with first 
threshold result, it switches to the appropriate state.

Probably it is needed a new flag to say NOPROBE when ds_probing_mode = 1 
. I will try to look over it when I have some time.

Cheers,
Danie

Re: [SR-Users] Help with install using GIT

Daniel-Constantin Mierla — 2013-06-19T12:35:27

Hello,

recent versions of git changed behaviour for --depth 1, fetching only 
one branch. You have to give --no-single-branch as parameter, see:

http://www.kamailio.org/wiki/install/4.0.x/git#getting_sources_from_git

Cheers,
Daniel

On 6/18/13 9:29 PM, John Doe wrote:

Re: [SR-Users] Compile with mysql error

Daniel-Constantin Mierla — 2013-06-19T12:33:10

Hello,

make a symbolic link to the version you want to use, like:

ln -s /usr/lib64/libmysqlclient.so.16.0.0 /usr/lib64/libmysqlclient.so

Cheers,
Daniel

On 6/17/13 12:45 AM, David Cunningham wrote:

[SR-Users] Help with install using GIT

John Doe — 2013-06-18T19:29:01

Hi all, I am trying to install the latest version using git (new to git) and after running "git checkout -b 4.0 origin/4.0" I got these messages:


[root< at >test kamailio-4.0.2]# git checkout -b 4.0 origin/4.0

fatal: Cannot update paths and switch to branch '4.0' at the same time.
Did you intend to checkout 'origin/4.0' which can not be resolved as commit?
[root< at >test kamailio-4.0.2]#

These were the commands I entered in order:

[root< at >test kamailio-4.0.2]# mkdir -p /usr/local/src/kamailio-4.0.2
[root< at >test kamailio-4.0.2]# cd /usr/local/src/kamailio-4.0.2/
[root< at >test kamailio-4.0.2]# git clone --depth 1 git://git.sip-router.org/sip-router kamailio
[root< at >test kamailio-4.0.2]# cd kamailio
[root< at >test kamailio-4.0.2]# git checkout -b 4.0 origin/4.0  --> this is were it fails


What does it mean, how should I proceed?
I appreciate any advise, thank you

[SR-Users] Dispatcher behaviour

Mino Haluz — 2013-06-19T11:57:24

Hi,

I've been playing with dispatcher settings, and I cannot get it working as
expected. I would like to have my destination IP1 being always probed and
some destinations should be marked as active non-probing.

So, in my config I have

ds_probing_mode = 0  (documentation:  If set to 0, only the gateways with
state PROBING are tested;)

Ok, so I set flag = 8 in dispatcher list for IP1 (documentation:  3 (value
8) - probing destination (sending keep alives);)

Restart of kamailio, host IP1 is AP, after first interval (10sec), 200OK
from gateway is received, and host becomes AX (active non-probing). Why ??
What I expect is that host stays AP.  Why the probing mode is turned off
when first check is OK?

I can somehow do it with ds_probing_mode = 1 but this is not I want - I
need that some gateways are not probed at all (documentation:  if set to 1,
all gateways are tested - useless for me)

I tried every flag range 0-10. I think it does not work as documentation
states or I simply do not understand its meaning

[SR-Users] short name in syslog

Victor V. Kustov — 2013-06-19T10:51:17

Hi Daniel-Constantin!

little fix for short name in syslog's log:

-before
Jun 19 14:40:37 phoenix-c2 /usr/local/sbin/kamailio[63542]: WARNING: qm_status: (0x801000000):
-after
Jun 19 14:41:44 phoenix-c2 kamailio[91432]: WARNING: qm_status: heap size= 33554432

patch attached


--
 WBR, Victor
  JID: coyote-B6aY196UtR8< at >public.gmane.org
  JID: coyote-N7mKgWFaI+z9Ct1PEtb4cw< at >public.gmane.org
  I use FREE operation system: 3.9.4-calculate GNU/Linux

[SR-Users] bug in 4.0.2 dialog module, no keep alives when src==dst

Daniel Tryba — 2013-06-19T09:11:45

Trying to implement calllimits with the dialog module I can reproduce a 
hanging dialog using a Linksys 962 by calling itself. When trying to answer 
the call the INVITES end in a 200 OK but the call is terminated [linksys.txt].

That might be a bug in the 962, but the bad part is the dialog will be kept in 
kamailio even though keep alives are enabled. OPTIONS are not being sent to 
detect this dead dialog. If this devices calls an other device (either 
registered to this kamailio or to the PSTN) KA work like configured (they are 
being send to this device). Severing the connection will be detected and the 
dialog will be removed. But when source and destination is the same device, no 
OPTIONS are sent.

About 1 hour later the dialog is still there:

# kamctl mi dlg_list
dialog::  hash=3456:6742
        state:: 3
        ref_count:: 2
        timestart:: 1371572203
        timeout:: 68536211
        callid:: 86a23723-4b71d5ad< at >localhost
        from_uri:: sip:anonymous< at >localhost
        from_tag:: 1736b8ab3e