Re: [SR-Users] core parsing of SIP message failed errors

[Jeff Cohn]

I turned on debug=3 and the messages change a bit (listed both below)
Look into how to check database and traffic..sorry, not super strong on that 
side.

Thanks again for thoughts.

debug=1
---
Mar  9 09:41:05 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11664]: INFO: 
 [main.c:793]: sig_usr(): signal 15 received
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11749]: ERROR: 
sipcapture [hep.c:60]: hep_msg_received(): sipcapture:hep_msg_received HEP is 
not enabled
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11753]: ERROR: 
sipcapture [hep.c:60]: hep_msg_received(): sipcapture:hep_msg_received HEP is 
not enabled
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11769]: ERROR: 
 [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad 
message (offset: 0)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11769]: ERROR: 
 [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: 
message=
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11769]: ERROR: 
 [receive.c:129]: receive_msg(): core parsing of SIP message failed 
(127.0.0.1:33264/1)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]: ERROR: 
 [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad 
message (offset: 0)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]: ERROR: 
 [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: 
message=
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]: ERROR: 
 [receive.c:129]: receive_msg(): core parsing of SIP message failed 
(127.0.0.1:33264/1)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11751]: ERROR: 
sipcapture [hep.c:60]: hep_msg_received(): sipcapture:hep_msg_received HEP is 
not enabled
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]: ERROR: 
 [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad 
message (offset: 0)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]: ERROR: 
 [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: 
message=
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]: ERROR: 
 [receive.c:129]: receive_msg(): core parsing of SIP message failed 
(127.0.0.1:33264/1)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11752]: ERROR: 
sipcapture [hep.c:60]: hep_msg_received(): sipcapture:hep_msg_received HEP is 
not enabled
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]: ERROR: 
 [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad 
message (offset: 0)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]: ERROR: 
 [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: 
message=
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11750]: ERROR: 
sipcapture [hep.c:60]: hep_msg_received(): sipcapture:hep_msg_received HEP is 
not enabled
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]: ERROR: 
 [receive.c:129]: receive_msg(): core parsing of SIP message failed 
(127.0.0.1:33264/1)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11765]: ERROR: 
 [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad 
message (offset: 0)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11765]: ERROR: 
 [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: 
message=
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11765]: ERROR: 
 [receive.c:129]: receive_msg(): core parsing of SIP message failed 
(127.0.0.1:33264/1)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]: ERROR: 
 [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad 
message (offset: 0)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]: ERROR: 
 [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: 
message=
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]: ERROR: 
 [receive.c:129]: receive_msg(): core parsing of SIP message failed 
(127.0.0.1:33264/1)


debug=3
---
Mar  9 09:40:19 coeo-homer2 rsyslogd-2177: imuxsock lost 1059 messages from pid 
11677 due to rate-limiting
Mar  9 09:40:19 coeo-homer2 rsyslogd-2177: imuxsock lost 1091 messages from pid 
11676 due to rate-limiting
Mar  9 09:40:19 coeo-homer2 rsyslogd-2177: imuxsock lost 1079 messages from pid 
11675 due to rate-limiting
Mar  9 09:40:19 coeo-homer2 rsyslogd-2177: imuxsock lost  messages from pid 
11686 due to rate-limiting
Mar  9 09:40:19 coeo-homer2 rsyslogd-2177: imuxsock lost 1084 messages from pid 
11672 due to rate-limiting
Mar  9 09:40:19 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11687]: ERROR: 

Re: [SR-Users] core parsing of SIP message failed errors

[Jeff Cohn]

Any thoughts on this?
Thanks
Jeff



From: Jeff Cohn mailto:jc...@coeosolutions.com>>
Date: Monday, March 9, 2015 at 9:45 AM
To: Daniel-Constantin Mierla mailto:mico...@gmail.com>>, 
"Kamailio (SER) - Users Mailing List" 
mailto:sr-users@lists.sip-router.org>>
Subject: Re: [SR-Users] core parsing of SIP message failed errors

I turned on debug=3 and the messages change a bit (listed both below)
Look into how to check database and traffic..sorry, not super strong on that 
side.

Thanks again for thoughts.

debug=1
---
Mar  9 09:41:05 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11664]: INFO: 
 [main.c:793]: sig_usr(): signal 15 received
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11749]: ERROR: 
sipcapture [hep.c:60]: hep_msg_received(): sipcapture:hep_msg_received HEP is 
not enabled
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11753]: ERROR: 
sipcapture [hep.c:60]: hep_msg_received(): sipcapture:hep_msg_received HEP is 
not enabled
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11769]: ERROR: 
 [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad 
message (offset: 0)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11769]: ERROR: 
 [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: 
message=
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11769]: ERROR: 
 [receive.c:129]: receive_msg(): core parsing of SIP message failed 
(127.0.0.1:33264/1)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]: ERROR: 
 [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad 
message (offset: 0)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]: ERROR: 
 [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: 
message=
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]: ERROR: 
 [receive.c:129]: receive_msg(): core parsing of SIP message failed 
(127.0.0.1:33264/1)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11751]: ERROR: 
sipcapture [hep.c:60]: hep_msg_received(): sipcapture:hep_msg_received HEP is 
not enabled
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]: ERROR: 
 [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad 
message (offset: 0)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]: ERROR: 
 [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: 
message=
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]: ERROR: 
 [receive.c:129]: receive_msg(): core parsing of SIP message failed 
(127.0.0.1:33264/1)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11752]: ERROR: 
sipcapture [hep.c:60]: hep_msg_received(): sipcapture:hep_msg_received HEP is 
not enabled
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]: ERROR: 
 [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad 
message (offset: 0)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]: ERROR: 
 [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: 
message=
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11750]: ERROR: 
sipcapture [hep.c:60]: hep_msg_received(): sipcapture:hep_msg_received HEP is 
not enabled
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]: ERROR: 
 [receive.c:129]: receive_msg(): core parsing of SIP message failed 
(127.0.0.1:33264/1)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11765]: ERROR: 
 [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad 
message (offset: 0)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11765]: ERROR: 
 [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: 
message=
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11765]: ERROR: 
 [receive.c:129]: receive_msg(): core parsing of SIP message failed 
(127.0.0.1:33264/1)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]: ERROR: 
 [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad 
message (offset: 0)
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]: ERROR: 
 [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: 
message=
Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]: ERROR: 
 [receive.c:129]: receive_msg(): core parsing of SIP message failed 
(127.0.0.1:33264/1)


debug=3
---
Mar  9 09:40:19 coeo-homer2 rsyslogd-2177: imuxsock lost 1059 messages from pid 
11677 due to rate-limiting
Mar  9 09:40:19 coeo-homer2 rsyslogd-2177: imuxsock lost 1091 messages from pid 
11676 due to rate-limiting
Mar  9 09:40:19 coeo-homer2 rsyslogd-2177: imuxsock lost 1079 messages from pid 
11675 due to rate-limiting
Mar  9 09:40:19 coeo-homer2 rsyslogd-2177: imuxsock lost  messages from pid 
11686 due to rate-limiting
Mar  9 09:40:19 coeo-homer2 rsyslogd-2177: imuxsock lost 1084 messages from pid 
11672 due to rate-limiting
Mar  9 09:40:19 coeo-homer2 /usr/local/kama

Re: [SR-Users] kamailio 4.2.3 Segmentation fault when using db_cluster module

[Daniel-Constantin Mierla]

Hello,

can you give the output from gdb for:

p cls
p *cls
p i
bt full

Cheers,
Daniel

On 09/03/15 20:21, Jan Hazenberg wrote:
> Olle,
>
> Here is the gdb debug trace
>
> (gdb) backtrace
> #0  0x7ff76e13bddc in db_cluster_delete (_h=0x7ff7716f2428,
> _k=0x0, _o=0x0, _v=0x0, _n=0) at dbcl_api.c:390
> #1  0x7ff769d0193c in load_dialog_info_from_db
> (dlg_hash_size=4096, fetch_num_rows=200) at dlg_db_handler.c:462
> #2  0x7ff769cfcb9a in init_dlg_db (db_url=0x7ff769f58a90 ,
> dlg_hash_size=4096, db_update_period=60, fetch_num_rows=200) at
> dlg_db_handler.c:167
> #3  0x7ff769d1f15c in mod_init () at dialog.c:696
> #4  0x0053a68d in init_mod (m=0x7ff7715af7b0) at sr_module.c:966
> #5  0x0053a99a in init_modules () at sr_module.c:995
> #6  0x00531151 in main (argc=1, argv=0x7fffd2fad8f8) at
> main.c:2519
> (gdb)
>
>
> Jan
>
>
> Olle E. Johansson schreef op 2015-03-09 17:41:
>> On 09 Mar 2015, at 17:16, Jan Hazenberg  wrote:
>>
>>> Hello,
>>>
>>> I have a issue on kamailio 4.2.3 when using the db_cluster module. I
>>> have the following config:
>>>
>>> #!define DBURL "cluster://cls1"
>>>
>>> # - db_cluster params -
>>> modparam("db_cluster", "connection",
>>> "con1=>mysql://kamailio:kamailiorw@10.121.0.120/kamailio")
>>> modparam("db_cluster", "connection",
>>> "con2=>mysql://kamailio:kamailiorw@10.121.0.121/kamailio")
>>> modparam("db_cluster", "connection",
>>> "con3=>mysql://kamailio:kamailiorw@10.121.0.122/kamailio")
>>> modparam("db_cluster", "cluster",
>>> "cls1=>con1=9r8r;con2=9r8r;con3=9r8r")
>>> modparam("db_cluster", "inactive_interval", 180)
>>> modparam("db_cluster", "max_query_length", 5)
>>>
>>> # - sqlops params -
>>> modparam("sqlops","sqlcon","ca=>cluster://cls1")
>>>
>>>
>>> When i start kamailio it fails with:
>>>
>>> Mar  9 17:11:49 localhost kamailio[31063]: INFO: rr
>>> [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob
>>> Mar  9 17:11:49 localhost kamailio[31063]: INFO: rr [rr_mod.c:160]:
>>> mod_init(): outbound module not available
>>> Mar  9 17:11:49 localhost kamailio[31063]: INFO: usrloc
>>> [hslot.c:53]: ul_init_locks(): locks array size 1024
>>> Mar  9 17:11:49 localhost kamailio[31063]: INFO: permissions
>>> [parse_config.c:251]: parse_config_file(): file not found:
>>> /usr/local/etc/kamailio/permissions.allow
>>> Mar  9 17:11:49 localhost kamailio[31063]: INFO: permissions
>>> [permissions.c:608]: mod_init(): default allow file
>>> (/usr/local/etc/kamailio/permissions.allow) not found => empty rule set
>>> Mar  9 17:11:49 localhost kamailio[31063]: INFO: permissions
>>> [parse_config.c:251]: parse_config_file(): file not found:
>>> /usr/local/etc/kamailio/permissions.deny
>>> Mar  9 17:11:49 localhost kamailio[31063]: INFO: permissions
>>> [permissions.c:617]: mod_init(): default deny file
>>> (/usr/local/etc/kamailio/permissions.deny) not found => empty rule set
>>> Mar  9 17:11:49 localhost kernel: kamailio[31063]: segfault at 80 ip
>>> 7f7f4f9ffddc sp 7fffde2f88a0 error 4 in
>>> db_cluster.so[7f7f4f9ec000+28000]
>>> Mar  9 17:11:50 localhost kamailio: ERROR:  [daemonize.c:315]:
>>> daemonize(): Main process exited before writing to pipe
>>>
>>>
>>> Could this be a bug or is this a configuration issue? I tested the
>>> dbnodes and they seem to respond fine to any query's i send.
>>
>> Configurations should never create segmentation faults, so it's
>> clearly a bug. Can you find the core dump file and produce a
>> backtrace?
>>
>> /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

-- 
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] Dialog order of operations

[Daniel-Constantin Mierla]

On 09/03/15 22:40, Alex Balashov wrote:
> Daniel,
>
> Thanks for that insight. This does make me wonder if there are other
> unforeseen implications in suspending/continue TM transactions, in
> terms of "baggage" associated with the transaction or message, but not
> part of the core TM structure, not making it across the
> suspend/continue gap.
>
X/AVPs and flags are taken over, being the attributes associated with
transaction/message. Anything else that is in the context of the local
process (e.g., $var(xyz)) are lost.

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

[SR-Users] WARNING when querying data using db_mongodb

[Mickael Marrache]

Hi,



I'm continuously seeing the following WARNING in my logs:



WARNING: db_mongodb [mongodb_dbase.c:454]: db_mongodb_get_columns():
unhandled data type column (instance) type id (10), use DB1_STRING as
default



It looks like the WARNING appears when data is fetched from the location
collection. The instance field is always null in my case.



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

Re: [SR-Users] kamailio 4.2.3 Segmentation fault when using db_cluster module

[Jan Hazenberg]

Daniel,


Here the gdb output:

(gdb) p cls
$1 = (dbcl_cls_t *) 0x7ff7715b7390
(gdb) p *cls
$2 = {name = {s = 0x7ff7715b72d8 "cls1=>con1=9r8r;con2=9r8r;con3=9r8r", 
len = 4}, clsid = 1863538307, ref = 1, rlist = {{clist = {0x0, 0x0, 0x0, 
0x0, 0x0}, clen = 0, prio = 0, mode = 0, crt = 0}, {clist = {0x0, 0x0, 
0x0, 0x0, 0x0}, clen = 0, prio = 0, mode = 0,
  crt = 0}, {clist = {0x0, 0x0, 0x0, 0x0, 0x0}, clen = 0, prio = 0, 
mode = 0, crt = 0}, {clist = {0x0, 0x0, 0x0, 0x0, 0x0}, clen = 0, prio = 
0, mode = 0, crt = 0}, {clist = {0x0, 0x0, 0x0, 0x0, 0x0}, clen = 0, 
prio = 0, mode = 0, crt = 0}, {clist = {0x0, 0x0, 0x0,
0x0, 0x0}, clen = 0, prio = 0, mode = 0, crt = 0}, {clist = 
{0x0, 0x0, 0x0, 0x0, 0x0}, clen = 0, prio = 0, mode = 0, crt = 0}, 
{clist = {0x0, 0x0, 0x0, 0x0, 0x0}, clen = 0, prio = 0, mode = 0, crt = 
0}, {clist = {0x0, 0x0, 0x0, 0x0, 0x0}, clen = 0, prio = 0,
  mode = 0, crt = 0}, {clist = {0x7ff7715b7030, 0x7ff7715b6cd0, 
0x7ff7715b6970, 0x0, 0x0}, clen = 3, prio = 9, mode = 114, crt = 2}}, 
wlist = {{clist = {0x0, 0x0, 0x0, 0x0, 0x0}, clen = 0, prio = 0, mode = 
0, crt = 0}, {clist = {0x0, 0x0, 0x0, 0x0, 0x0}, clen = 0,
  prio = 0, mode = 0, crt = 0}, {clist = {0x0, 0x0, 0x0, 0x0, 0x0}, 
clen = 0, prio = 0, mode = 0, crt = 0}, {clist = {0x0, 0x0, 0x0, 0x0, 
0x0}, clen = 0, prio = 0, mode = 0, crt = 0}, {clist = {0x0, 0x0, 0x0, 
0x0, 0x0}, clen = 0, prio = 0, mode = 0, crt = 0}, {
  clist = {0x0, 0x0, 0x0, 0x0, 0x0}, clen = 0, prio = 0, mode = 0, 
crt = 0}, {clist = {0x0, 0x0, 0x0, 0x0, 0x0}, clen = 0, prio = 0, mode = 
0, crt = 0}, {clist = {0x0, 0x0, 0x0, 0x0, 0x0}, clen = 0, prio = 0, 
mode = 0, crt = 0}, {clist = {0x7ff7715b7030,
0x7ff7715b6cd0, 0x7ff7715b6970, 0x0, 0x0}, clen = 3, prio = 8, 
mode = 114, crt = 0}, {clist = {0x0, 0x0, 0x0, 0x0, 0x0}, clen = 0, prio 
= 0, mode = 0, crt = 0}}, usedcon = 0x7ff7715b6cd0, next = 0x0}

(gdb) p i
$3 = 8
(gdb) bt full
#0  0x7ff76e13bddc in db_cluster_delete (_h=0x7ff7716f2428, _k=0x0, 
_o=0x0, _v=0x0, _n=0) at dbcl_api.c:390

ret = -1
i = 8
k = 0
sec = 13502139
rc = 0
rok = 0
j = 0
dbh = 0x7ff7716f4ad0
cls = 0x7ff7715b7390
__FUNCTION__ = "db_cluster_delete"
#1  0x7ff769d0193c in load_dialog_info_from_db (dlg_hash_size=4096, 
fetch_num_rows=200) at dlg_db_handler.c:462

res = 0x7ff7716f4c40
values = 0x1d2fad4b0
rows = 0x0
i = 0
nr_rows = 0
dlg = 0x7fffd2fad8f0
callid = {s = 0x7fffd2fad4b0 " \325\372\322\377\177", len = 
1875525114}

from_uri = {s = 0x0, len = 0}
to_uri = {s = 0x73cdb8 "DEBUG", len = -755312400}
from_tag = {s = 0x7ff7715b5d68 "cluster://cls1", len = 
1775544688}
to_tag = {s = 0x9c8b50  "\364\266q", len = 
1903119320}
req_uri = {s = 0x7fffd2fad460 "\260\324\372\322\001", len = 
1846750789}

cseq1 = {s = 0xe , len = 1901813096}
cseq2 = {s = 0x7fffd2fad350 "\205P\313o\367\177", len = 
1901584760}

contact1 = {s = 0x7fffd2fad340 "\220P\313o\367\177", len = 0}
contact2 = {s = 0x7ff769d4450b "dialog_vars", len = 11}
rroute1 = {s = 0x4 , len = 
1846854459}
rroute2 = {s = 0x7ff7715b68b8 
"con1=>mysql://kamailio:kamailiorw@10.121.0.120/kamailio", len = 
1903119424}

toroute_name = {s = 0x7ff76fcb5085 "table_name", len = 10}
xdata = {s = 0x7ff76fcb5090 "table_version", len = 13}
next_id = 32759
jdoc = {root = 0x7fffd2fad3c0, flags = 6405665, buf = {s = 
0x7fffd2fad340 "\220P\313o\367\177", len = 1777699264}, malloc_fn = 
0x7ff7716f2428, free_fn = 0x7ff769f59c00 }

__FUNCTION__ = "load_dialog_info_from_db"
#2  0x7ff769cfcb9a in init_dlg_db (db_url=0x7ff769f58a90 , 
dlg_hash_size=4096, db_update_period=60, fetch_num_rows=200) at 
dlg_db_handler.c:167

__FUNCTION__ = "init_dlg_db"
#3  0x7ff769d1f15c in mod_init () at dialog.c:696
n = 12
__FUNCTION__ = "mod_init"
#4  0x0053a68d in init_mod (m=0x7ff7715af7b0) at sr_module.c:966
__FUNCTION__ = "init_mod"
#5  0x0053a99a in init_modules () at sr_module.c:995
t = 0x7ff77213bdc0 
i = 200
__FUNCTION__ = "init_modules"
#6  0x00531151 in main (argc=1, argv=0x7fffd2fad8f8) at 
main.c:2519

cfg_stream = 0x1f9c010
c = -1
r = 11538501
tmp = 0x1 
tmp_len = 0
port = 0
proto = 32767
options = 0x71ea48 
":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:"

ret = -1
seed = 84040262
rfd = 4
debug_save = 0
debug_flag = 0
dont_fork_cnt = 0
n_lst = 0xf63d4e2e
p = 0x7ff772774000 ""
---Type  to continue, or q  to quit---
__FUNCTION__ = "main"
(gdb)


Jan

Daniel-Constantin Mierla schreef op 2015-03-10 09:34:

Hello,

can you give the output from gdb for:

p cls
p *cls
p i
bt full

Cheers,
Daniel

[SR-Users] We’ve got free Tickets for CeBIT 2015!

[Carsten Bock]

Hi,

Due to our presentation at CeBIT 2015 at the Open-Source Business
Alliance’s Booth, we’ve received a limited number of free tickets for
CeBIT 2015!

If you want a free ticket, please answer the following question:
- What is the key benefit of deploying VoLTE in a mobile network?

Send your answer to i...@ng-voice.com (hint: we’ve got some benefits
posted on our website: www.ng-voice.com/volte), I will send the ticket
by email to the 5 best answers!

Don’t miss my presentation on Kamailio & VoLTE at the booth of the
Open-Source Business Alliance (www.osb-alliance.de), Tuesday, March
17th, ~2 PM, Hall 6, Stand H16, (410)!

Thanks,
Carsten


-- 
Carsten Bock
CEO (Geschäftsführer)

ng-voice GmbH
Schomburgstr. 80
D-22767 Hamburg / Germany

http://www.ng-voice.com
mailto:cars...@ng-voice.com

Office +49 40 5247593-0
Fax +49 40 5247593-99

Sitz der Gesellschaft: Hamburg
Registergericht: Amtsgericht Hamburg, HRB 120189
Geschäftsführer: Carsten Bock
Ust-ID: DE279344284

Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
http://www.ng-voice.com/imprint/

___
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] WARNING when querying data using db_mongodb

[Daniel-Constantin Mierla]

Hello,

On 10/03/15 10:05, Mickael Marrache wrote:
>
> Hi, 
>
> I'm continuously seeing the following WARNING in my logs:
>
> WARNING: db_mongodb [mongodb_dbase.c:454]: db_mongodb_get_columns():
> unhandled data type column (instance) type id (10), use DB1_STRING as
> default 
>
> It looks like the WARNING appears when data is fetched from the
> location collection. The instance field is always null in my case.
>
if the field in the mongodb document is null, then its effective data
type cannot be found via json data type. The the mongodb is mapping that
to kamailio's internal data type string -- the value is null.

Perhaps this warning must be done an INFO.

A solution would be to specify the document structure via some schema
definition (e.g., a json with same fields, but instead of value to have
the data type), which to be used by db_mongodb when converting from json
data value to internal data representation for db drivers.

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] We’ve got free Tickets for CeBIT 2015!

[Daniel-Constantin Mierla]

Hello,

I am planning to visit the show for one day, but I haven't decided yet.
Tuesday, 17th of March, is a good candidate now.

If anyone else from the community is going to the show, let's see what
would be the day with most of us there -- would be good to have a
meeting and chat a bit. Reply here with the dates when you will be at
the show and let's see if we can manage something convenient.

Cheers,
Daniel

On 10/03/15 10:54, Carsten Bock wrote:
> Hi,
>
> Due to our presentation at CeBIT 2015 at the Open-Source Business
> Alliance’s Booth, we’ve received a limited number of free tickets for
> CeBIT 2015!
>
> If you want a free ticket, please answer the following question:
> - What is the key benefit of deploying VoLTE in a mobile network?
>
> Send your answer to i...@ng-voice.com (hint: we’ve got some benefits
> posted on our website: www.ng-voice.com/volte), I will send the ticket
> by email to the 5 best answers!
>
> Don’t miss my presentation on Kamailio & VoLTE at the booth of the
> Open-Source Business Alliance (www.osb-alliance.de), Tuesday, March
> 17th, ~2 PM, Hall 6, Stand H16, (410)!
>
> Thanks,
> Carsten
>
>

-- 
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] kamailio 4.2.3 Segmentation fault when using db_cluster module

[Daniel-Constantin Mierla]

Thanks, it helped to spot the issue. Can you try with the latest version
from branch 4.2?

Cheers,
Daniel

On 10/03/15 10:46, Jan Hazenberg wrote:
> Daniel,
>
>
> Here the gdb output:
>
> ...

-- 
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] 4.2.3 textops: flag "f" doesn't work in subst_hf(hf, subexp, flags)

[Daniel-Constantin Mierla]

Hello,

thanks for reporting back the results to know all works fine with the patch.

Cheers,
Daniel

On 09/03/15 13:10, Julia Boudniatsky wrote:
> Hello Daniel,
>
> Thank you so much, it's working now!
>
> BR,
> Julia
>
> On Mon, Mar 9, 2015 at 1:43 PM, Daniel-Constantin Mierla
> mailto:mico...@gmail.com>> wrote:
>
> Hello,
>
> can you try with latest version from branch 4.2, I pushed a patch
> that should fix the case for f flag.
>
> Cheers,
> Daniel
>
>
> On 08/03/15 17:49, Julia Boudniatsky wrote:
>> Hello,
>>
>> I received INVITE with 3 Diversion headers. 
>> I try to make substitutions in the body of a first Diversion
>> header field by using flag "f",
>>
>> command *subst_hf("Diversion", /sip:(.*)@/sip:$var(dU)@/", "f") ;*
>> substitutes *all headers *Diversion instead of only first header,
>>
>> command *subst_hf("Diversion", /sip:(.*)@/sip:$var(dU)@/", "*l*") ;*
>> substitutes  only *last*Diversion header.
>>
>> Thanks for help,
>> Julia.
>>
>>
>>
>>
>>
>> ___
>> 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
>
>

-- 
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] Transfer call between devices

[Daniel-Constantin Mierla]

Hello,


On 07/03/15 11:46, Phil Daws wrote:
> Hello:
>
> wish to ask how one may configure Kamailio so that if a user has a
> number of devices registered eg. deskphone, soft client on tablet, and
> soft client on cellphone when a call is originated or received how it
> can be passed between devices.  Is it as simple as configuring a blind
> transfer ?
based on SIP RFC specs and when using a sip signaling server (such as
kamailio), the call transfer is done by the phone itself. Kamailio is
just routing the signaling packages related to the transfer without any
special rules in configuration file.
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] sipcapture - core parsing of SIP message failed errors

[Daniel-Constantin Mierla]

You can look at the network traffic using tools such as ngrep, sipgrep,
tcpdump or wireshark.

An example with ngrep for sip udp on port 5060:

ngrep -d any -qt -W byline port 5060

I am not the developer of sipcapture module, but from the parser errors
it seems that it tries to parse an empty string.

The database errors are related to a duplicated value on an unique key
column.

Maybe Alexandr (author of sipcapture) can comment more on the logs.

Cheers,
Daniel

On 10/03/15 03:48, Jeff Cohn wrote:
> Any thoughts on this?
> Thanks
> Jeff
>
>
>
> From: Jeff Cohn mailto:jc...@coeosolutions.com>>
> Date: Monday, March 9, 2015 at 9:45 AM
> To: Daniel-Constantin Mierla  >, "Kamailio (SER) - Users Mailing List"
> mailto:sr-users@lists.sip-router.org>>
> Subject: Re: [SR-Users] core parsing of SIP message failed errors
>
> I turned on debug=3 and the messages change a bit (listed both below)
> Look into how to check database and traffic..sorry, not super strong
> on that side.
>
> Thanks again for thoughts.
>
> debug=1
> ---
> Mar  9 09:41:05 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11664]:
> INFO:  [main.c:793]: sig_usr(): signal 15 received
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11749]:
> ERROR: sipcapture [hep.c:60]: hep_msg_received():
> sipcapture:hep_msg_received HEP is not enabled
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11753]:
> ERROR: sipcapture [hep.c:60]: hep_msg_received():
> sipcapture:hep_msg_received HEP is not enabled
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11769]:
> ERROR:  [parser/parse_fline.c:257]: parse_first_line():
> parse_first_line: bad message (offset: 0)
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11769]:
> ERROR:  [parser/msg_parser.c:688]: parse_msg(): ERROR:
> parse_msg: message=
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11769]:
> ERROR:  [receive.c:129]: receive_msg(): core parsing of SIP
> message failed (127.0.0.1:33264/1)
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]:
> ERROR:  [parser/parse_fline.c:257]: parse_first_line():
> parse_first_line: bad message (offset: 0)
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]:
> ERROR:  [parser/msg_parser.c:688]: parse_msg(): ERROR:
> parse_msg: message=
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]:
> ERROR:  [receive.c:129]: receive_msg(): core parsing of SIP
> message failed (127.0.0.1:33264/1)
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11751]:
> ERROR: sipcapture [hep.c:60]: hep_msg_received():
> sipcapture:hep_msg_received HEP is not enabled
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]:
> ERROR:  [parser/parse_fline.c:257]: parse_first_line():
> parse_first_line: bad message (offset: 0)
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]:
> ERROR:  [parser/msg_parser.c:688]: parse_msg(): ERROR:
> parse_msg: message=
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]:
> ERROR:  [receive.c:129]: receive_msg(): core parsing of SIP
> message failed (127.0.0.1:33264/1)
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11752]:
> ERROR: sipcapture [hep.c:60]: hep_msg_received():
> sipcapture:hep_msg_received HEP is not enabled
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]:
> ERROR:  [parser/parse_fline.c:257]: parse_first_line():
> parse_first_line: bad message (offset: 0)
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]:
> ERROR:  [parser/msg_parser.c:688]: parse_msg(): ERROR:
> parse_msg: message=
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11750]:
> ERROR: sipcapture [hep.c:60]: hep_msg_received():
> sipcapture:hep_msg_received HEP is not enabled
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11767]:
> ERROR:  [receive.c:129]: receive_msg(): core parsing of SIP
> message failed (127.0.0.1:33264/1)
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11765]:
> ERROR:  [parser/parse_fline.c:257]: parse_first_line():
> parse_first_line: bad message (offset: 0)
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11765]:
> ERROR:  [parser/msg_parser.c:688]: parse_msg(): ERROR:
> parse_msg: message=
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11765]:
> ERROR:  [receive.c:129]: receive_msg(): core parsing of SIP
> message failed (127.0.0.1:33264/1)
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]:
> ERROR:  [parser/parse_fline.c:257]: parse_first_line():
> parse_first_line: bad message (offset: 0)
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]:
> ERROR:  [parser/msg_parser.c:688]: parse_msg(): ERROR:
> parse_msg: message=
> Mar  9 09:41:35 coeo-homer2 /usr/local/kamailio/sbin/kamailio[11775]:
> ERROR:  [receive.c:129]: receive_msg(): core parsing of SIP
> mes

Re: [SR-Users] Sipcapture module insert error

[Daniel-Constantin Mierla]

Hello,

maybe the values are too big for the defined column size. You can try
altering the table and increase the size for correlation_id column.

I cc-ed Alexandr, who wrote the module and can eventually comment more
on the issue.

Cheers,
Daniel

On 06/03/15 20:09, Spencer Thomason wrote:
> Hello,
> I’m not sure if this is the correct forum for this question but here goes… 
> I’m facing an issue setting up a sipcapture server.  I’m seeing several db 
> errors in the logs:
> Mar  6 10:45:13 sipcapture /usr/local/sbin/kamailio[37872]: ERROR: db_mysql 
> [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Data too 
> long for column 'correlation_id' at row 1 
>
> I did a packet capture of the sql query and it appears that the value for the 
> correlation_id is omitted.  Interestingly its not all packets but maybe 60%.  
> Do I have something misconfigured?
>
> Thanks,
> Spencer
>
>
> A sanitized version of the query is below:
> insert into sip_capture 
> (date,micro_ts,method,reply_reason,ruri,ruri_user,from_user,from_tag,to_user,to_tag,pid_user,contact_user,auth_user,callid,callid_aleg,via_1,via_1_branch,cseq,reason,content_type,auth,user_agent,source_ip,source_port,destination_ip,destination_port,contact_ip,contact_port,originator_ip,originator_port,proto,family,rtp_stat,type,node,correlation_id,msg
>  ) values ('2015-03-06 
> 10:50:22',1425667824109829,'180','Ringing','','','+1205222','gK007b315d','+1205111','3Sr0m4vyjy2UK','','+1205111','','2080378443_116641441@1.1.1.1','','SIP/2.0/UDP
>  
> 1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7','z9hG4bK00B5617ed64f1ebf7d7','1888238783
>  
> INVITE','','','','','3.3.3.3',5060,'1.1.1.1',5060,'2.2.2.2',6038,'',0,1,2,'',2,'node1:2001','SIP/2.0
>  180 Ringing\r\nVia: SIP/2.0/UDP 
> 1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7\r\nRecord-Route: 
> \r\nFrom: 
> ;tag=gK007b315d\r\nTo: 
> ;tag=3Sr0m4vyjy2UK\r\nCall-ID: 
> 2080378443_116641441@1.1.1.1\r\nCSeq: 1888238783 INVITE\r\nContact: 
> \r\nAccept: 
> application/sdp\r\nAllow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, 
> UPDATE\r\nSupported: path\r\nContent-Length: 0\r\n\r\n','SIP/2.0 180 
> Ringing\r\nVia: SIP/2.0/UDP 
> 1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7\r\nRecord-Route: 
> \r\nFrom: 
> ;tag=gK007b315d\r\nTo: 
> ;tag=3Sr0m4vyjy2UK\r\nCall-ID: 
> 2080378443_116641441@1.1.1.1\r\nCSeq: 1888238783 INVITE\r\nContact: 
> \r\nAccept: 
> application/sdp\r\nAllow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, 
> UPDATE\r\nSupported: path\r\nContent-Length: 0\r\n\r\n') 
>  
> ___
> 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] help with a new install

[Daniel-Constantin Mierla]

Hello,

check the network traffic to see if the packages are sent to the
sipcapture node.

If kamailio is involved somehow, try to run it with debug=3 in kamailio.cfg

Cheers,
Daniel

On 06/03/15 21:33, David Dunlap wrote:
> Hello,
>
> I am seeking help with a new test server.
> I have SIP messages coming from a working FreeSwitch and getting
> posted into the sip_capture table.
> Homer web service is responding allowing me to manage log on accounts
> and other database settings however I do not see any packets in the
> web gui.
> I used the install script from the web page and did not notice any
> errors as it worked.
>
> I sure would appreciate some help.
>
> The IRC channel was empty.
>
> Thanks
>
> *David Dunlap
> /
> /
> **/
> /3105 N. Main St. East Peoria, IL 61611
> Direct: 309-427-7226
> Main: 309-427-7000 
> Fax:  309-427-7326
> Email: ddun...@heart.net
> www.heart.net*
>
> *
> *
>
>
> ___
> 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] SIP 500 on WSS connection lookup failure

[Daniel-Constantin Mierla]

Hello,

On 07/03/15 00:27, Armen Babikyan wrote:
> Hi Daniel,
>
> Thanks for the tip about disabling internal replies in the transaction
> module.
>
> About the new feature in usrloc - it looks like close_expired_tcp
> feature disconnects the connection if contacts on it expire.  I'm
> hoping to achieve the reverse, where I get to clean up when a
> connection closes abruptly.  To this end, for websockets, will
> Kamailio allow me to use uac_req_send() from within
> event_route[websocket:closed]?  I'm looking for a way to generate a
> de-REGISTER packet to send on to my registrar when a client abruptly
> closes their SIP/WS connection.  If not, do you have any suggestions
> to achieve something similar?

if you want to avoid attempting to send the sip message when there is no
connection, then the option is to use set_forward_no_connect() before
relaying.

 https://www.kamailio.org/wiki/cookbooks/4.2.x/core#set_forward_no_connect

Otherwise, look inside the usrloc module for the option to remove the
record when the connection associated with it is no longer available
(this is done on a timer check). Then you can get the event route
executed for expired contact and there you can trigger something to
trigger an un-register to the other server.

uac_req_send() should work fine in event routes.

Cheers,
Daniel

>
> Thanks again!
>
> Armen
>
>
> On Fri, Mar 6, 2015 at 12:32 PM, Daniel-Constantin Mierla
> mailto:mico...@gmail.com>> wrote:
>
> Hello,
>
> On 06/03/15 03:38, Armen Babikyan wrote:
> > Hello,
> >
> > I am setting up this scenario using Kamailio 4.2.2:
> >
> > [UA] <-> [kamailio1] <-> [kamailio2] <-> [other stuff]
> >
> > UA connects to kamailio1 using SIP/WSS, kamailio1 proxies request
> > along to kamailio2.  Note that my intent here is to have kamailio2
> > provide the registrar functionality.  The kamailio2 (or something
> > behind it) can also initiate transactions to UA, like OPTIONS, for
> > example.
> >
> > I'm having an issue though: when the websocket connection between
> > kamailio1 and UA dies, transaction requests from kamailio2 show
> up to
> > kamailio1, and I get errors in kamailio1's logs because the WSS
> > connection is gone.  I get messages as follows (debug=2):
> >
> > Mar  6 00:17:33 kamailio1 /usr/local/sbin/kamailio[5653]: WARNING:
> >  [msg_translator.c:2778]: via_builder(): TCP/TLS
> connection (id:
> > 0) for WebSocket could not be found
> > Mar  6 00:17:33 kamailio1 /usr/local/sbin/kamailio[5653]: ERROR:
> >  [msg_translator.c:1996]: build_req_buf_from_sip_req(): could
> > not create Via header
> > Mar  6 00:17:33 kamailio1 /usr/local/sbin/kamailio[5653]: ERROR: tm
> > [t_fwd.c:527]: prepare_new_uac(): could not build request
> > Mar  6 00:17:33 kamailio1 /usr/local/sbin/kamailio[5653]: ERROR: tm
> > [t_fwd.c:1777]: t_forward_nonack(): ERROR: t_forward_nonack: failure
> > to add branches
> >
> > At debug=4, I get the output here: http://pastebin.com/d3RumekG
> >
> > In a running tshark, I see kamailio1 responding to kamailio2 with a
> > "SIP/2.0 500 No error (2/TM)".  It appears to me that this is
> > happening before t_relay() even returns.
> >
> > Is there a way to prevent the SIP 500 from being sent back to the
> > client?  I am calling t_on_branch_failure("kam2bf") and
> > t_on_failure("kam2f"), with each of those handlers
> > (event_route[tm:branch-failure:kam2bf] and failure_route[kam2f])
> > written to print a log message, but it appears that neither of those
> > handlers are being called.  I tried installing these handlers
> > independently to no avail.
> >
> > I also tried registering a t_on_reply() handler, thinking it was an
> > internally-generated SIP response that might make it through my
> > handler on its way out to kam2, but that is also not getting
> invoked.
> >
> > I want to return a 404 or something similar instead of having a 500
> > auto-returned for me.
> >
> > Related to this, is there a way to query kamailio's in-memory client
> > connectivity data structure for the connectivity status of a client?
> > Or is this something best done by keeping track of every client
> myself
> > using (e.g.) localcache?
> >
> > Any pointers are appreciated.  Thanks!
>
> If you want tm not to send an reply internally, see:
>
> -
> 
> http://kamailio.org/docs/modules/4.2.x/modules/tm.html#tm.f.t_set_disable_internal_reply
>
> Also, you can list the details of tcp connections via tcp -- see
> 'kamcmd
> help' for the tcp related commands. Iirc, something similar should be
> for websocket connections.
>
> The usrloc module keeps the id of the tcp connection for the
> client, the
> development version (master branch) has the option to delete the
> record
> if the connection is gone. 

Re: [SR-Users] kamailio 4.2.3 Segmentation fault when using db_cluster module

[Jan Hazenberg]

Daniel,

Yes thanks, that seems to solve the issue.

Jan

Daniel-Constantin Mierla schreef op 2015-03-10 13:57:
Thanks, it helped to spot the issue. Can you try with the latest 
version

from branch 4.2?

Cheers,
Daniel

On 10/03/15 10:46, Jan Hazenberg wrote:

Daniel,


Here the gdb output:

...


___
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 4.2.3 Segmentation fault when using db_cluster module

[Daniel-Constantin Mierla]

Thanks for testing and reporting the results to close the issue.

Cheers,
Daniel

On 10/03/15 15:01, Jan Hazenberg wrote:
> Daniel,
>
> Yes thanks, that seems to solve the issue.
>
> Jan
>
> Daniel-Constantin Mierla schreef op 2015-03-10 13:57:
>> Thanks, it helped to spot the issue. Can you try with the latest version
>> from branch 4.2?
>>
>> Cheers,
>> Daniel
>>
>> On 10/03/15 10:46, Jan Hazenberg wrote:
>>> Daniel,
>>>
>>>
>>> Here the gdb output:
>>>
>>> ...
>
> ___
> 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] SIREMIS error

[Daniel-Constantin Mierla]

Hello,

can you post exactly the errors you get? I think some should be fixed
for php 5.6.

Cheers,
Daniel

On 02/03/15 17:06, Agiftel wrote:
> Hi, i tried to install SIREMIS v 4.2 and i get error, already posted on
> internet/forum, regarding versione of PHP 5.6
>
> What i didn't find is a solution. So my question is, I still unsupported by
> SIREMIS php v 5.4 and upper?
> Is there a solution?'
>
>
> Regards
>
>
>
> --
> View this message in context: 
> http://sip-router.1086192.n5.nabble.com/SIREMIS-error-tp135884.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

-- 
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] building kamailio with MongoDB

[Daniel-Constantin Mierla]

On 02/03/15 14:48, Tom Braarup Cuykens wrote:
> I am trying to setup a Kamailio with MongoDB but the complilation fails:
>
> make include_modules="db_mongodb rtpproxy" cfg
> make all
>
> [...]
>
> In file included from mongodb_connection.c:24:0:
> mongodb_connection.h:26:20: fatal error: mongoc.h: No such file or
> directory
> compilation terminated.
> make[1]: *** [mongodb_connection.o] Error 1
> make: *** [modules] Error 1
>
> I have build the mongodb C driver from
> https://github.com/mongodb/mongo-c-driver/
>
> Not sure if the issue is related to the Kamailio MongoDB module or the
> Mongo C driver.
Can you locate where the mongoc.h file was installed (by the
mongo-c-driver)?

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

[SR-Users] kamailio asterisk NOTIFY

[Slava Bendersky]

Hello Everyone, 
Having issue with NOTIFY, is not forwarded to client properly. 

asterisk ---> private kamailio public > soft client 


http://fpaste.org/196257/99948714/ 

I see kamailio trying connect always with private IP to the client when NOTIFY 
is come is in. Is this something to do with 
rr_advertise_address ? 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) ERROR:  [tcp_main.c:4338]: 
tcpconn_main_timeout(): connect 192.168.88.246:5064 failed (timeout) 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG:  [tcp_main.c:4362]: 
tcpconn_main_timeout(): tcp_main: timeout for 0x7fbbb64e2800 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG:  [io_wait.h:610]: 
io_watch_del(): DBG: io_watch_del (0x9dbf00, 33, -1, 0x10) fd_no=24 called 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG:  [tcp_main.c:4320]: 
tcpconn_main_timeout(): tcp_main: entering timer for 0x7fbbb64eb6c0 
(ticks=839577436, timeout=839634956 (3595 s), wr_timeout=839577436 (0 s)), 
write queue: 798 bytes 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) ERROR:  [tcp_main.c:4338]: 
tcpconn_main_timeout(): connect 192.168.88.246:5066 failed (timeout) 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG:  [tcp_main.c:4362]: 
tcpconn_main_timeout(): tcp_main: timeout for 0x7fbbb64eb6c0 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG:  [io_wait.h:610]: 
io_watch_del(): DBG: io_watch_del (0x9dbf00, 34, -1, 0x10) fd_no=23 called 
Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm [t_reply.c:1294]: 
t_should_relay_response(): -> T_code=0, new_code=408 
Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm [t_reply.c:1812]: 
relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=0 icode=0 
Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG:  
[mem/shm_mem.c:111]: _shm_resize(): WARNING:vqm_resize: resize(0) called 
Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm [t_reply.c:1294]: 
t_should_relay_response(): -> T_code=0, new_code=408 
Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm [t_reply.c:1812]: 
relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=0 icode=0 

I have in configuration in WITHINDLG 

if (is_method("NOTIFY")) { 
record_route(); 
} 

and in NATDETECT 

if(is_method("INVITE|SUBSCRIBE|UPDATE|NOTIFY")) { 
set_contact_alias(); 
} 

Slava. 
___
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] Sipcapture module insert error

[Spencer Thomason]

Thanks Daniel and Alexandr,
I’m not sure if any of this is pertinent but this is a FreeBSD 10.1 system 
using clang.  I just did a rebuild from master to rule out any build skew and 
everything seems ok for a short period of time (about 5 minutes) and then the 
value for correlation_id seems to have the same value as the msg column in many 
queries.

Thanks,
Spencer


On Mar 10, 2015, at 6:08 AM, Daniel-Constantin Mierla  wrote:

> Hello,
> 
> maybe the values are too big for the defined column size. You can try
> altering the table and increase the size for correlation_id column.
> 
> I cc-ed Alexandr, who wrote the module and can eventually comment more
> on the issue.
> 
> Cheers,
> Daniel
> 
> On 06/03/15 20:09, Spencer Thomason wrote:
>> Hello,
>> I’m not sure if this is the correct forum for this question but here goes… 
>> I’m facing an issue setting up a sipcapture server.  I’m seeing several db 
>> errors in the logs:
>> Mar  6 10:45:13 sipcapture /usr/local/sbin/kamailio[37872]: ERROR: db_mysql 
>> [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Data too 
>> long for column 'correlation_id' at row 1 
>> 
>> I did a packet capture of the sql query and it appears that the value for 
>> the correlation_id is omitted.  Interestingly its not all packets but maybe 
>> 60%.  Do I have something misconfigured?
>> 
>> Thanks,
>> Spencer
>> 
>> 
>> A sanitized version of the query is below:
>> insert into sip_capture 
>> (date,micro_ts,method,reply_reason,ruri,ruri_user,from_user,from_tag,to_user,to_tag,pid_user,contact_user,auth_user,callid,callid_aleg,via_1,via_1_branch,cseq,reason,content_type,auth,user_agent,source_ip,source_port,destination_ip,destination_port,contact_ip,contact_port,originator_ip,originator_port,proto,family,rtp_stat,type,node,correlation_id,msg
>>  ) values ('2015-03-06 
>> 10:50:22',1425667824109829,'180','Ringing','','','+1205222','gK007b315d','+1205111','3Sr0m4vyjy2UK','','+1205111','','2080378443_116641441@1.1.1.1','','SIP/2.0/UDP
>>  
>> 1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7','z9hG4bK00B5617ed64f1ebf7d7','1888238783
>>  
>> INVITE','','','','','3.3.3.3',5060,'1.1.1.1',5060,'2.2.2.2',6038,'',0,1,2,'',2,'node1:2001','SIP/2.0
>>  180 Ringing\r\nVia: SIP/2.0/UDP 
>> 1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7\r\nRecord-Route: 
>> \r\nFrom: 
>> ;tag=gK007b315d\r\nTo: 
>> ;tag=3Sr0m4vyjy2UK\r\nCall-ID: 
>> 2080378443_116641441@1.1.1.1\r\nCSeq: 1888238783 INVITE\r\nContact: 
>> \r\nAccept: 
>> application/sdp\r\nAllow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, 
>> UPDATE\r\nSupported: path\r\nContent-Length: 0\r\n\r\n','SIP/2.0 180 
>> Ringing\r\nVia: SIP/2.0/UDP 
>> 1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7\r\nRecord-Route: 
>> \r\nFrom: 
>> ;tag=gK007b315d\r\nTo: 
>> ;tag=3Sr0m4vyjy2UK\r\nCall-ID: 
>> 2080378443_116641441@1.1.1.1\r\nCSeq: 1888238783 INVITE\r\nContact: 
>> \r\nAccept: 
>> application/sdp\r\nAllow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, 
>> UPDATE\r\nSupported: path\r\nContent-Length: 0\r\n\r\n') 
>> 
>> ___
>> 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


___
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 asterisk NOTIFY

[Daniel-Constantin Mierla]

Hello,

fpaste link doesn't show anything.

Can you check if the NOTIFY coming to Kamailio has two Route headers?

Cheers,
Daniel

On 10/03/15 18:44, Slava Bendersky wrote:
> Hello Everyone,
> Having issue with NOTIFY, is not forwarded to client properly.
>
> asterisk ---> private kamailio public > soft client
>
>
>   http://fpaste.org/196257/99948714/
>
> I see kamailio trying connect always with private IP to the client
> when NOTIFY is come is in. Is this something to do with
> rr_advertise_address ?
> Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) ERROR: 
> [tcp_main.c:4338]: tcpconn_main_timeout(): connect 192.168.88.246:5064
> failed (timeout)
> Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: 
> [tcp_main.c:4362]: tcpconn_main_timeout(): tcp_main: timeout for
> 0x7fbbb64e2800
> Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: 
> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9dbf00, 33, -1,
> 0x10) fd_no=24 called
> Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: 
> [tcp_main.c:4320]: tcpconn_main_timeout(): tcp_main: entering timer
> for 0x7fbbb64eb6c0 (ticks=839577436, timeout=839634956 (3595 s),
> wr_timeout=839577436 (0 s)), write queue: 798 bytes
> Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) ERROR: 
> [tcp_main.c:4338]: tcpconn_main_timeout(): connect 192.168.88.246:5066
> failed (timeout)
> Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: 
> [tcp_main.c:4362]: tcpconn_main_timeout(): tcp_main: timeout for
> 0x7fbbb64eb6c0
> Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: 
> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9dbf00, 34, -1,
> 0x10) fd_no=23 called
> Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm
> [t_reply.c:1294]: t_should_relay_response(): -> T_code=0,
> new_code=408
> Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm
> [t_reply.c:1812]: relay_reply(): DEBUG: relay_reply: branch=0, save=0,
> relay=0 icode=0
> Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: 
> [mem/shm_mem.c:111]: _shm_resize(): WARNING:vqm_resize: resize(0) called
> Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm
> [t_reply.c:1294]: t_should_relay_response(): -> T_code=0,
> new_code=408
> Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm
> [t_reply.c:1812]: relay_reply(): DEBUG: relay_reply: branch=0, save=0,
> relay=0 icode=0
>
> I have in configuration in WITHINDLG
>
> if (is_method("NOTIFY")) {
>  record_route();
> }
>
> and in NATDETECT
>
> if(is_method("INVITE|SUBSCRIBE|UPDATE|NOTIFY")) {
> set_contact_alias();
> }
>
> Slava.
>
>
> ___
> 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

[SR-Users] ims_charging module

[Shane Harrison]

Hi all ims'ers

I have modified the ims_charging module to cope with the CCA return code of 
"CREDIT CONTROL NOT APPLICABLE".  This means the call is not a chargeable call 
and the charging module now returns a unique return code for this.

Currently there are two scenarios handled:
1) CCA grants the credit required for the call --> route the INVITE and then 
automatically new CCR requests are made for further credit as the call 
progresses
2) CCA doesn't grant the credit  ---> send an error response back to INVITE 
originator - I assume this will clear all dialogs and no further credit 
requests are made. 

The question I have, is how do I cope with this unique return code so that I 
can continue to route the call but not make any more CCR requests to the credit 
control server?  As I am not sure how the ims_charging module continues to 
generate CCR requests, it is difficult for me to understand how to essentially 
clear the whole CCR session without clearing the call.

Kind regards
Shane




Shane Harrison
Senior Software Engineer

Imagination Technologies NZ Limited
Level 2
1 Market Grove
Lower Hutt, 5010
New Zealand

PO Box 30-449
Lower Hutt, 5040
New Zealand

Phone: +64 4 890-3681 ext 3361



___
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] Continent Code GeoIP module, kamailio 4.2

[Rene Montilva]

Hi list

i'm trying to configure rtp engine routing by source ip, i'd like divide it
by continent code, is there any pseudo-variables or possibilites to handle
continent code.

Team, any idea about it?
___
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] Continent Code GeoIP module, kamailio 4.2

[Sergey Okhapkin]

Hmm, I can add continent code pvar to geoip2 module in kamailio trunk. Is it 
really useful instead of country code?

On Tuesday 10 March 2015 19:03:35 Rene Montilva wrote:
> Hi list
> 
> i'm trying to configure rtp engine routing by source ip, i'd like divide it
> by continent code, is there any pseudo-variables or possibilites to handle
> continent code.
> 
> Team, any idea about it?

___
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] Continent Code GeoIP module, kamailio 4.2

[Rene Montilva]

I am trying to separate from continent to have rtp more dynamic to
simplify the assignment, the geoip i'm working on v1


On Tue, Mar 10, 2015 at 7:22 PM, Sergey Okhapkin 
wrote:

> Hmm, I can add continent code pvar to geoip2 module in kamailio trunk. Is
> it
> really useful instead of country code?
>
> On Tuesday 10 March 2015 19:03:35 Rene Montilva wrote:
> > Hi list
> >
> > i'm trying to configure rtp engine routing by source ip, i'd like divide
> it
> > by continent code, is there any pseudo-variables or possibilites to
> handle
> > continent code.
> >
> > Team, any idea about it?
>
> ___
> 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] Calling ims charging function in route_failure

[Shane Harrison]

Hi all,

What I want to do
~~
If a call to a SIP AoR fails then try the PSTN number associated with the AoR 
by routing the request to a PSTN gateway.  Calls to a PSTN gateway need to be 
charged so need to call the Ro_CCR function in ims_charging module.

How I tried to do it
~~
In the failure_route[MANAGE_FAILURE] block I call the Ro_CCR()

Result was

Kamailio fails to parse config file.
yyparse(): misused command Ro_CCR
 yyerror_at(): parse error in config file //etc/kamailio/kamailio.cfg, line 
1162, column 91: Command cannot be used in the block

So two questions:
1) What constraints are there for calling functions in the failure_route blocks 
i.e. how does parser decide what can be called and what can't
2) Any thoughts of how I can do effectively a late charging decision

Cheers and thanks in advance
Shane

Shane Harrison
Senior Software Engineer

Imagination Technologies NZ Limited
Level 2
1 Market Grove
Lower Hutt, 5010
New Zealand

PO Box 30-449
Lower Hutt, 5040
New Zealand

Phone: +64 4 890-3681 ext 3361



___
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] Calling ims charging function in route_failure

[Shane Harrison]

Hi all,

Using a technique Daniel mentioned in a previous post, I have removed the 
parser issue.  I called a separate route block from the failure_route block and 
call the Ro_CCR from there.

However my questions still remain as I don't really know how to determine if 
that Ro_CCR() is safe to call from there.  Documentation has some stern 
warnings :-)

Cheers
Shane

> -Original Message-
> From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
> Shane Harrison
> Sent: Wednesday, 11 March 2015 4:06 p.m.
> To: Kamailio (SER) - Users Mailing List
> Subject: [SR-Users] Calling ims charging function in route_failure
> 
> Hi all,
> 
> What I want to do
> ~~
> If a call to a SIP AoR fails then try the PSTN number associated with the AoR
> by routing the request to a PSTN gateway.  Calls to a PSTN gateway need to
> be charged so need to call the Ro_CCR function in ims_charging module.
> 
> How I tried to do it
> ~~
> In the failure_route[MANAGE_FAILURE] block I call the Ro_CCR()
> 
> Result was
> 
> Kamailio fails to parse config file.
> yyparse(): misused command Ro_CCR
>  yyerror_at(): parse error in config file //etc/kamailio/kamailio.cfg, line 
> 1162,
> column 91: Command cannot be used in the block
> 
> So two questions:
> 1) What constraints are there for calling functions in the failure_route 
> blocks
> i.e. how does parser decide what can be called and what can't
> 2) Any thoughts of how I can do effectively a late charging decision
> 
> Cheers and thanks in advance
> Shane
> 
> Shane Harrison
> Senior Software Engineer
> 
> Imagination Technologies NZ Limited
> Level 2
> 1 Market Grove
> Lower Hutt, 5010
> New Zealand
> 
> PO Box 30-449
> Lower Hutt, 5040
> New Zealand
> 
> Phone: +64 4 890-3681 ext 3361
> 
> 
> 
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-
> us...@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