date:20150130

Re: [SR-Users] Core dump while saving user location in mongo

2015-01-30 Thread Mickael Marrache

Hi,

 

Thanks for the patch, Kamailio doesn't crash anymore.

 

However, I'm encountering another issue with usrloc + Mongo, I will write a new 
post.

 

Thanks,

Mickael

 

From: Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Sent: Friday, January 30, 2015 7:22 AM
To: Mickael Marrache
Cc: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Core dump while saving user location in mongo

 

Hello,

 

I pushed a patch that takes care of initializing the columns array of the 
result - it is in the master branch for now.

 

However, the log messages don't seem to be complete, were you sending all. The 
backtrace shows a line which is executed only if an error message is printed, 
it is not in the logs you sent.

 

One thing that I remembered was that usrloc requires parameter db_insert_null 
to be set in order to work with mongodb:

 

- 
http://kamailio.org/docs/modules/stable/modules/usrloc.html#usrloc.p.db_insert_null

 

The crash shouldn't happen and hopefully the patch I pushed catches it. Try the 
patch without db_insert_null just to see if there is still a crash or not.

 

Cheers,

Daniel

 

On Thu, Jan 29, 2015 at 11:51 AM, Mickael Marrache  
wrote:

Now, it didn't crash during the REGISTER but during the INVITE:

 

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:705]: db_mongodb_query(): 
query to collection [location]

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:726]: db_mongodb_query(): 
query filter: { "username" : "m1" }

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:745]: db_mongodb_query(): 
columns filter: { "contact" : 1, "expires" : 1, "q" : 1, "callid" : 1, "cseq" : 
1, "flags" :

1, "cflags" : 1, "user_agent" : 1, "received" : 1, "path" : 1, "socket" : 1, 
"methods" : 1, "last_modified" : 1, "ruid" : 1, "instance" : 1, "reg_id" : 1 }

kamailio[32599]: DEBUG:  [db_res.c:118]: db_new_result(): allocate 56 
bytes for result set at 0x7f83a32daa48

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:203]: 
db_mongodb_get_columns(): 16 columns returned from the query

kamailio[32599]: DEBUG:  [db_res.c:155]: db_allocate_columns(): allocate 
128 bytes for result names at 0x7f83a32daf98

kamailio[32599]: DEBUG:  [db_res.c:165]: db_allocate_columns(): allocate 
64 bytes for result types at 0x7f83a32daed8

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:231]: 
db_mongodb_get_columns(): Found a field[0] named: contact

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:250]: 
db_mongodb_get_columns(): allocate 16 bytes for RES_NAMES[0] at 0x7f83a32daab8

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:285]: 
db_mongodb_get_columns(): use DB1_STRING result type

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:314]: 
db_mongodb_get_columns(): RES_NAMES(0x7f83a32daab8)[0]=[contact] (2)

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:231]: 
db_mongodb_get_columns(): Found a field[1] named: expires

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:250]: 
db_mongodb_get_columns(): allocate 16 bytes for RES_NAMES[1] at 0x7f83a32dab98

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:275]: 
db_mongodb_get_columns(): use DB1_DATETIME result type

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:314]: 
db_mongodb_get_columns(): RES_NAMES(0x7f83a32dab98)[1]=[expires] (9)

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:231]: 
db_mongodb_get_columns(): Found a field[2] named: q

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:250]: 
db_mongodb_get_columns(): allocate 16 bytes for RES_NAMES[2] at 0x7f83a32dabe0

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:270]: 
db_mongodb_get_columns(): use DB1_DOUBLE result type

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:314]: 
db_mongodb_get_columns(): RES_NAMES(0x7f83a32dabe0)[2]=[q] (1)

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:231]: 
db_mongodb_get_columns(): Found a field[3] named: callid

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:250]: 
db_mongodb_get_columns(): allocate 16 bytes for RES_NAMES[3] at 0x7f83a32dac70

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:285]: 
db_mongodb_get_columns(): use DB1_STRING result type

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:314]: 
db_mongodb_get_columns(): RES_NAMES(0x7f83a32dac70)[3]=[callid] (2)

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:231]: 
db_mongodb_get_columns(): Found a field[4] named: cseq

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:250]: 
db_mongodb_get_columns(): allocate 16 bytes for RES_NAMES[4] at 0x7f83a32dac28

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:260]: 
db_mongodb_get_columns(): use DB1_INT result type

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:314]: 
db_mongodb_get_columns(): RES_NAMES(0x7f83a32dac28)[4]=[cseq] (16)

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:231]: 
db_mongodb_get_columns(): Found a field[5] named: flags

kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:250]: 
db_mongodb_get_columns(): allocate 16 bytes for RES_NA

Re: [SR-Users] Can kamailio generate a PRACK

2015-01-30 Thread Olle E. Johansson


On 30 Jan 2015, at 07:58, Rahul MathuR  wrote:

> Hello,
> 
> I was wondering whether Kamailio (as proxy) can generate a PRACK on its own ( 
> since one of the custom written dialer is not sending PRACK) ?
> Is there any way I can achieve this ?
Kamailio can not participate in a dialog between two UAs like that. The CSEQ 
would be out of sync
and it would disrupt further messaging in the dialog.

You need a back2back user agent like Asterisk or FreeSwitch to do that. There 
are patches
for Asterisk that implements PRACK (which I've coded).

/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

[SR-Users] Wrong location entries when using usrloc with Mongo

2015-01-30 Thread Mickael Marrache

Hi,

 

I start with no location nor in Mongo, nor in memory. My UA registers
successfully and I can see the location entry in Mongo. Then, I close my UA
which unregisters (by setting Expires header to 0). Then, I open the app
again and a new registration is made.

 

The entry after first registration. Looks okay.

 

{ "_id" : ObjectId("54cb38f684e58133783f2b42"), "username" : "A", "contact"
: "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp", "expires" :
ISODate("2015-01-30T08:55:34Z"), "q" : -1, "callid" :
"297EC55073A07BF78F0C05822A6CCDFB47E48705", "cseq" : 8809, "flags" : 0,
"cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received" :
"sip:XXX:54217;transport=tcp", "path" :
"",
"socket" : "udp:X:5060", "methods" : 4751, "last_modified" :
ISODate("2015-01-30T07:55:34Z"), "ruid" : "uloc-54cb38df-3378-2", "instance"
: null, "reg_id" : 0 }

 

The same entry after un register (Expires 0). Note that the username field
is missing. In any case, I expected the entry to be deleted.

 

{ "_id" : ObjectId("54cb38f684e58133783f2b42"), "expires" :
ISODate("2015-01-30T08:56:51Z"), "q" : -1, "cseq" : 8811, "flags" : 0,
"cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received" :
"sip: X:54217;transport=tcp", "path" : "", "socket" :
"udp: X:5060", "methods" : 4751, "last_modified" :
ISODate("2015-01-30T07:56:51Z"), "callid" :
"297EC55073A07BF78F0C05822A6CCDFB47E48705", "instance" : null, "reg_id" : 0,
"contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp" }

 

The entries after second registration. The new entry looks okay. But, the
old entry is still here.

 

{ "_id" : ObjectId("54cb38f684e58133783f2b42"), "expires" :
ISODate("2015-01-30T08:56:51Z"), "q" : -1, "cseq" : 8811, "flags" : 0,
"cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received" :
"sip: X:54217;transport=tcp", "path" : "", "socket" :
"udp: X:5060", "methods" : 4751, "last_modified" :
ISODate("2015-01-30T07:56:51Z"), "callid" :
"297EC55073A07BF78F0C05822A6CCDFB47E48705", "instance" : null, "reg_id" : 0,
"contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp" }

 

{ "_id" : ObjectId("54cb3a7884e581337a25b895"), "username" : "A", "contact"
: "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp", "expires" :
ISODate("2015-01-30T09:02:00Z"), "q" : -1, "callid" :
"297EC55073A07BF78F0C05822A6CCDFB47E48705", "cseq" : 8813, "flags" : 0,
"cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received" :
"sip: X:54217;transport=tcp", "path" : "", "socket" :
"udp: X:5060", "methods" : 4751, "last_modified" :
ISODate("2015-01-30T08:02:00Z"), "ruid" : "uloc-54cb38df-337a-1", "instance"
: null, "reg_id" : 0 }

 

The issue is the entry is not deleted after un registering.

 

I precise that registrations are dispatched over multiple registrars with
all accesses the same Mongo cluster.

 

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] Wrong location entries when using usrloc with Mongo

2015-01-30 Thread Mickael Marrache

I forgot to precise that I allow only one contact per AOR.

 

modparam("registrar", "max_contacts", 1)

save("location", "0x04")

 

From: Mickael Marrache [mailto:mickaelmarra...@gmail.com] 
Sent: Friday, January 30, 2015 10:51 AM
To: sr-users@lists.sip-router.org
Subject: Wrong location entries when using usrloc with Mongo

 

Hi,

 

I start with no location nor in Mongo, nor in memory. My UA registers
successfully and I can see the location entry in Mongo. Then, I close my UA
which unregisters (by setting Expires header to 0). Then, I open the app
again and a new registration is made.

 

The entry after first registration. Looks okay.

 

{ "_id" : ObjectId("54cb38f684e58133783f2b42"), "username" : "A", "contact"
: "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp", "expires" :
ISODate("2015-01-30T08:55:34Z"), "q" : -1, "callid" :
"297EC55073A07BF78F0C05822A6CCDFB47E48705", "cseq" : 8809, "flags" : 0,
"cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received" :
"sip:XXX:54217;transport=tcp", "path" :
"",
"socket" : "udp:X:5060", "methods" : 4751, "last_modified" :
ISODate("2015-01-30T07:55:34Z"), "ruid" : "uloc-54cb38df-3378-2", "instance"
: null, "reg_id" : 0 }

 

The same entry after un register (Expires 0). Note that the username field
is missing. In any case, I expected the entry to be deleted.

 

{ "_id" : ObjectId("54cb38f684e58133783f2b42"), "expires" :
ISODate("2015-01-30T08:56:51Z"), "q" : -1, "cseq" : 8811, "flags" : 0,
"cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received" :
"sip: X:54217;transport=tcp", "path" : "", "socket" :
"udp: X:5060", "methods" : 4751, "last_modified" :
ISODate("2015-01-30T07:56:51Z"), "callid" :
"297EC55073A07BF78F0C05822A6CCDFB47E48705", "instance" : null, "reg_id" : 0,
"contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp" }

 

The entries after second registration. The new entry looks okay. But, the
old entry is still here.

 

{ "_id" : ObjectId("54cb38f684e58133783f2b42"), "expires" :
ISODate("2015-01-30T08:56:51Z"), "q" : -1, "cseq" : 8811, "flags" : 0,
"cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received" :
"sip: X:54217;transport=tcp", "path" : "", "socket" :
"udp: X:5060", "methods" : 4751, "last_modified" :
ISODate("2015-01-30T07:56:51Z"), "callid" :
"297EC55073A07BF78F0C05822A6CCDFB47E48705", "instance" : null, "reg_id" : 0,
"contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp" }

 

{ "_id" : ObjectId("54cb3a7884e581337a25b895"), "username" : "A", "contact"
: "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp", "expires" :
ISODate("2015-01-30T09:02:00Z"), "q" : -1, "callid" :
"297EC55073A07BF78F0C05822A6CCDFB47E48705", "cseq" : 8813, "flags" : 0,
"cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received" :
"sip: X:54217;transport=tcp", "path" : "", "socket" :
"udp: X:5060", "methods" : 4751, "last_modified" :
ISODate("2015-01-30T08:02:00Z"), "ruid" : "uloc-54cb38df-337a-1", "instance"
: null, "reg_id" : 0 }

 

The issue is the entry is not deleted after un registering.

 

I precise that registrations are dispatched over multiple registrars with
all accesses the same Mongo cluster.

 

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] why do not support tcp:eth1:5062，only support eht1:5062

2015-01-30 Thread 张顺通

Jan 30 16:54:17 voip098023 kamailio: :  [cfg.y:3436]: yyerror_at():
parse error in config file
/home/shuntong.zhang/install_voip/cc_test/edge/etc/kamailio/edge.cfg, line
44, column 8-16: syntax error

Jan 30 16:54:17 voip098023 kamailio: :  [cfg.y:3436]: yyerror_at():
parse error in config file
/home/shuntong.zhang/install_voip/cc_test/edge/etc/kamailio/edge.cfg, line
44, column 8-16: ip address, interface name or hostname expected

Jan 30 16:54:17 voip098023 kamailio: :  [cfg.y:3439]: yyerror_at():
parse error in config file
/home/shuntong.zhang/install_voip/cc_test/edge/etc/kamailio/edge.cfg, line
44, column 17:


and line 44 is listen=tcp:bond0:9002

2015-01-30 13:32 GMT+08:00 Daniel-Constantin Mierla :

> Hello,
>
> can you give the log messages with debug=3 in your config file?
>
> Cheers,
> Daniel
>
> On Thu, Jan 29, 2015 at 8:54 AM, 张顺通  wrote:
>
>> especially i want to use tls:eth1:5063
>>
>> 2015-01-29 15:52 GMT+08:00 张顺通 :
>>
>>> what can i do to user tcp:eth1:5062
>>>
>>> 2014-11-12 10:53 GMT+08:00 张顺通 :
>>>
 why do not support tcp:eth1:5062，only support eht1:5062?
 I need to bind on eth1 only tcp.

>>>
>>>
>>
>> ___
>> 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://www.asipto.com
> http://twitter.com/#!/miconda - http://www.linkedin.com/in/micond
> 
>
> ___
> 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] tls_port_no maybe do not work

2015-01-30 Thread 张顺通

I set cfg like this:

tls_port_no=9004
listen=bond0:9002

but result is:

 udp: 10.232.98.23 [10.232.98.23]:9002

 tcp: 10.232.98.23 [10.232.98.23]:9002

 tls: 10.232.98.23 [10.232.98.23]:9003
___
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] Wrong location entries when using usrloc with Mongo

2015-01-30 Thread Daniel-Constantin Mierla

Hello,

it seems that the fileds inside the object are deleted, not the entire
object. The match was done on username and ruid for deletion, both of them
are missing.

I will look at the mongo api to see if something was set wrong there for
the delete command.

Cheers,
Daniel


On Fri, Jan 30, 2015 at 9:54 AM, Mickael Marrache  wrote:

> I forgot to precise that I allow only one contact per AOR.
>
>
>
> modparam("registrar", "max_contacts", 1)
>
> save("location", "0x04")
>
>
>
> *From:* Mickael Marrache [mailto:mickaelmarra...@gmail.com]
> *Sent:* Friday, January 30, 2015 10:51 AM
> *To:* sr-users@lists.sip-router.org
> *Subject:* Wrong location entries when using usrloc with Mongo
>
>
>
> Hi,
>
>
>
> I start with no location nor in Mongo, nor in memory. My UA registers
> successfully and I can see the location entry in Mongo. Then, I close my
> UA which unregisters (by setting Expires header to 0). Then, I open the app
> again and a new registration is made.
>
>
>
> The entry after first registration. Looks okay.
>
>
>
> { "_id" : ObjectId("54cb38f684e58133783f2b42"), "username" : "A",
> "contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp",
> "expires" : ISODate("2015-01-30T08:55:34Z"), "q" : -1, "callid" :
> "297EC55073A07BF78F0C05822A6CCDFB47E48705", "cseq" : 8809, "flags" : 0,
> "cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received"
> : "sip:XXX:54217;transport=tcp", "path" : "<
> sip:XX;lr;received=sip:XXX:54217%3Btransport%3Dtcp>",
> "socket" : "udp:X:5060", "methods" : 4751, "last_modified" :
> ISODate("2015-01-30T07:55:34Z"), "ruid" : "uloc-54cb38df-3378-2",
> "instance" : null, "reg_id" : 0 }
>
>
>
> The same entry after un register (Expires 0). Note that the username field
> is missing. In any case, I expected the entry to be deleted.
>
>
>
> { "_id" : ObjectId("54cb38f684e58133783f2b42"), "expires" :
> ISODate("2015-01-30T08:56:51Z"), "q" : -1, "cseq" : 8811, "flags" : 0,
> "cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received"
> : "sip: X:54217;transport=tcp", "path" : " X;lr;received=sip: X:54217%3Btransport%3Dtcp>", "socket" :
> "udp: X:5060", "methods" : 4751, "last_modified" :
> ISODate("2015-01-30T07:56:51Z"), "callid" :
> "297EC55073A07BF78F0C05822A6CCDFB47E48705", "instance" : null, "reg_id" :
> 0, "contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp"
> }
>
>
>
> The entries after second registration. The new entry looks okay. But, the
> old entry is still here.
>
>
>
> { "_id" : ObjectId("54cb38f684e58133783f2b42"), "expires" :
> ISODate("2015-01-30T08:56:51Z"), "q" : -1, "cseq" : 8811, "flags" : 0,
> "cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received"
> : "sip: X:54217;transport=tcp", "path" : " X;lr;received=sip: X:54217%3Btransport%3Dtcp>", "socket" :
> "udp: X:5060", "methods" : 4751, "last_modified" :
> ISODate("2015-01-30T07:56:51Z"), "callid" :
> "297EC55073A07BF78F0C05822A6CCDFB47E48705", "instance" : null, "reg_id" :
> 0, "contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp"
> }
>
>
>
> { "_id" : ObjectId("54cb3a7884e581337a25b895"), "username" : "A",
> "contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp",
> "expires" : ISODate("2015-01-30T09:02:00Z"), "q" : -1, "callid" :
> "297EC55073A07BF78F0C05822A6CCDFB47E48705", "cseq" : 8813, "flags" : 0,
> "cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received"
> : "sip: X:54217;transport=tcp", "path" : " X;lr;received=sip: X:54217%3Btransport%3Dtcp>", "socket" :
> "udp: X:5060", "methods" : 4751, "last_modified" :
> ISODate("2015-01-30T08:02:00Z"), "ruid" : "uloc-54cb38df-337a-1",
> "instance" : null, "reg_id" : 0 }
>
>
>
> The issue is the entry is not deleted after un registering.
>
>
>
> I precise that registrations are dispatched over multiple registrars with
> all accesses the same Mongo cluster.
>
>
>
> Thanks,
>
> Mickael
>
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>


-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/micond

___
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] why do not support tcp:eth1:5062，only support eht1:5062

2015-01-30 Thread Daniel-Constantin Mierla

I just tested on my computer with:

listen=tcp:wlan0:5060

and kamailio started ok, listening on the ip assigned to wlan0.

Can you set debug=3 in kamailio.cfg, then run and send all debug messages?

Cheers,
Daniel

On Fri, Jan 30, 2015 at 9:55 AM, 张顺通  wrote:

> Jan 30 16:54:17 voip098023 kamailio: :  [cfg.y:3436]: yyerror_at():
> parse error in config file
> /home/shuntong.zhang/install_voip/cc_test/edge/etc/kamailio/edge.cfg, line
> 44, column 8-16: syntax error
>
> Jan 30 16:54:17 voip098023 kamailio: :  [cfg.y:3436]: yyerror_at():
> parse error in config file
> /home/shuntong.zhang/install_voip/cc_test/edge/etc/kamailio/edge.cfg, line
> 44, column 8-16: ip address, interface name or hostname expected
>
> Jan 30 16:54:17 voip098023 kamailio: :  [cfg.y:3439]: yyerror_at():
> parse error in config file
> /home/shuntong.zhang/install_voip/cc_test/edge/etc/kamailio/edge.cfg, line
> 44, column 17:
>
>
> and line 44 is listen=tcp:bond0:9002
>
> 2015-01-30 13:32 GMT+08:00 Daniel-Constantin Mierla :
>
>> Hello,
>>
>> can you give the log messages with debug=3 in your config file?
>>
>> Cheers,
>> Daniel
>>
>> On Thu, Jan 29, 2015 at 8:54 AM, 张顺通  wrote:
>>
>>> especially i want to use tls:eth1:5063
>>>
>>> 2015-01-29 15:52 GMT+08:00 张顺通 :
>>>
 what can i do to user tcp:eth1:5062

 2014-11-12 10:53 GMT+08:00 张顺通 :

> why do not support tcp:eth1:5062，only support eht1:5062?
> I need to bind on eth1 only tcp.
>


>>>
>>> ___
>>> 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://www.asipto.com
>> http://twitter.com/#!/miconda - http://www.linkedin.com/in/micond
>> 
>>
>> ___
>> 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://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/micond

___
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] why do not support tcp:eth1:5062，only support eht1:5062

2015-01-30 Thread 张顺通

already set debug=3

cfg file :

debug=3

#log_stderror=no
log_facility=LOG_LOCAL0
log_name="ka_cctest_edge"

fork=yes

# FIXME
#user="admin"
children=1
tcp_children=1
disable_core_dump=no

auto_aliases=no
alias=ab.com

listen=tcp:bond0:9002


open_files_limit=1
tcp_max_connections=1
tcp_no_connect=yes
tcp_connection_lifetime=60
tcp_send_timeout=3
tcp_accept_aliases=yes
tcp_keepalive=yes
tcp_keepcnt=3
tcp_keepidle=5
tcp_keepintvl=2

tls_max_connections=2048

tcp_crlf_ping=yes

force_rport=yes

2015-01-30 18:44 GMT+08:00 Daniel-Constantin Mierla :

> I just tested on my computer with:
>
> listen=tcp:wlan0:5060
>
> and kamailio started ok, listening on the ip assigned to wlan0.
>
> Can you set debug=3 in kamailio.cfg, then run and send all debug messages?
>
> Cheers,
> Daniel
>
> On Fri, Jan 30, 2015 at 9:55 AM, 张顺通  wrote:
>
>> Jan 30 16:54:17 voip098023 kamailio: :  [cfg.y:3436]: yyerror_at():
>> parse error in config file
>> /home/shuntong.zhang/install_voip/cc_test/edge/etc/kamailio/edge.cfg, line
>> 44, column 8-16: syntax error
>>
>> Jan 30 16:54:17 voip098023 kamailio: :  [cfg.y:3436]: yyerror_at():
>> parse error in config file
>> /home/shuntong.zhang/install_voip/cc_test/edge/etc/kamailio/edge.cfg, line
>> 44, column 8-16: ip address, interface name or hostname expected
>>
>> Jan 30 16:54:17 voip098023 kamailio: :  [cfg.y:3439]: yyerror_at():
>> parse error in config file
>> /home/shuntong.zhang/install_voip/cc_test/edge/etc/kamailio/edge.cfg, line
>> 44, column 17:
>>
>>
>> and line 44 is listen=tcp:bond0:9002
>>
>> 2015-01-30 13:32 GMT+08:00 Daniel-Constantin Mierla :
>>
>>> Hello,
>>>
>>> can you give the log messages with debug=3 in your config file?
>>>
>>> Cheers,
>>> Daniel
>>>
>>> On Thu, Jan 29, 2015 at 8:54 AM, 张顺通  wrote:
>>>
 especially i want to use tls:eth1:5063

 2015-01-29 15:52 GMT+08:00 张顺通 :

> what can i do to user tcp:eth1:5062
>
> 2014-11-12 10:53 GMT+08:00 张顺通 :
>
>> why do not support tcp:eth1:5062，only support eht1:5062?
>> I need to bind on eth1 only tcp.
>>
>
>

 ___
 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://www.asipto.com
>>> http://twitter.com/#!/miconda - http://www.linkedin.com/in/micond
>>> 
>>>
>>> ___
>>> 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://www.asipto.com
> http://twitter.com/#!/miconda - http://www.linkedin.com/in/micond
> 
>
> ___
> 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] NDB_REDIS password to REDIS remote DB

2015-01-30 Thread Marc Soda

Thanks for the insight.  I ended up doing something like this:

redis_cmd("localredis", "AUTH REDIS_PASS", "r");

if ($redis(r=>type) == REDIS_REPLY_ERROR) {
xlog("L_ERROR", "Redis authentication error");
exit;
}

I think the confusion came from the fact that you do not specify the
password in the modparam() connection string, as you do with other DB
modules.  Maybe calling something like this out in the documentation would
help clear that up.

On Thu, Jan 29, 2015 at 3:48 PM, Marc Soda  wrote:

> Ah, so you should be able to do something like:
>
> redis_cmd("localredis", "AUTH $var(redis_password)");
>
> Nice.  I will try that and post my results.
>
> On Thu, Jan 29, 2015 at 1:28 PM, Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>>  Hello,
>>
>> it appears that hiredis library does the authentication after connecting
>> and can be done from config -- that's on a very quick search, not sure if
>> something has changed with the hiredis api meanwhile:
>>
>>  - https://github.com/redis/hiredis/issues/56
>>
>> Cheers,
>> Daniel
>>
>>
>> On 29/01/15 17:20, Marc Soda wrote:
>>
>> The only way it will work right now is to not use a password:
>>
>> modparam("ndb_redis", "server",
>> "name=localredis;addr=localhost;port=6379")
>>
>> I've been wanting to look at contributing support at that, but no time...
>>  On Thu, Jan 29, 2015 at 10:16 AM, Yuriy Gorlichenko > > wrote:
>>
>>> Hello. I try to use NDB_REDIS with remote REDIS DB and can not to
>>> connect because remote DB use password, but Kamailio module have no any
>>> variable or attr of modparam that implenets password for DB.
>>>
>>> How I can connect to my REDIS?
>>>
>>> ___
>>> 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 
>> listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>> --
>> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - 
>> http://www.linkedin.com/in/miconda
>>
>>
>> ___
>> 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] NDB_REDIS password to REDIS remote DB

2015-01-30 Thread Daniel-Constantin Mierla

I don't remember the reason authentication was not approached at the time
implementing the module, could be that it was not available in hiredis at
that time.

Now I just googled quickly to see how can be done. Perhaps makes sense to
add it inside the code, I guess it is not complex. For the moment I don't
have any time to put a redis testbed up so it may take some time in my
side, but someone else sends a patch meanwhile and it will be accepted.

You can send a patch to documentation too, for what you want to make it
more clear. Update the admin file in modules/ndb_redis/doc/.

Cheers,
Daniel

On Fri, Jan 30, 2015 at 2:46 PM, Marc Soda  wrote:

> Thanks for the insight.  I ended up doing something like this:
>
> redis_cmd("localredis", "AUTH REDIS_PASS", "r");
>
> if ($redis(r=>type) == REDIS_REPLY_ERROR) {
> xlog("L_ERROR", "Redis authentication error");
> exit;
> }
>
> I think the confusion came from the fact that you do not specify the
> password in the modparam() connection string, as you do with other DB
> modules.  Maybe calling something like this out in the documentation would
> help clear that up.
>
> On Thu, Jan 29, 2015 at 3:48 PM, Marc Soda  wrote:
>
>> Ah, so you should be able to do something like:
>>
>> redis_cmd("localredis", "AUTH $var(redis_password)");
>>
>> Nice.  I will try that and post my results.
>>
>> On Thu, Jan 29, 2015 at 1:28 PM, Daniel-Constantin Mierla <
>> mico...@gmail.com> wrote:
>>
>>>  Hello,
>>>
>>> it appears that hiredis library does the authentication after connecting
>>> and can be done from config -- that's on a very quick search, not sure if
>>> something has changed with the hiredis api meanwhile:
>>>
>>>  - https://github.com/redis/hiredis/issues/56
>>>
>>> Cheers,
>>> Daniel
>>>
>>>
>>> On 29/01/15 17:20, Marc Soda wrote:
>>>
>>> The only way it will work right now is to not use a password:
>>>
>>> modparam("ndb_redis", "server",
>>> "name=localredis;addr=localhost;port=6379")
>>>
>>> I've been wanting to look at contributing support at that, but no time...
>>>  On Thu, Jan 29, 2015 at 10:16 AM, Yuriy Gorlichenko <
>>> ovoshl...@gmail.com> wrote:
>>>
 Hello. I try to use NDB_REDIS with remote REDIS DB and can not to
 connect because remote DB use password, but Kamailio module have no any
 variable or attr of modparam that implenets password for DB.

 How I can connect to my REDIS?

 ___
 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 
>>> listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>> --
>>> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - 
>>> http://www.linkedin.com/in/miconda
>>>
>>>
>>> ___
>>> 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://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/micond

___
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] Wrong location entries when using usrloc with Mongo

2015-01-30 Thread Daniel-Constantin Mierla

I checked quickly the code and mongo c api, it looks ok. Can you see a
debug message with content like:

... delete filter document: ...

when running with debug=3? If yes, can you send it over to check if is
correct?

Cheers,
Daniel

On Fri, Jan 30, 2015 at 10:45 AM, Daniel-Constantin Mierla <
mico...@gmail.com> wrote:

> Hello,
>
> it seems that the fileds inside the object are deleted, not the entire
> object. The match was done on username and ruid for deletion, both of them
> are missing.
>
> I will look at the mongo api to see if something was set wrong there for
> the delete command.
>
> Cheers,
> Daniel
>
>
> On Fri, Jan 30, 2015 at 9:54 AM, Mickael Marrache <
> mickaelmarra...@gmail.com> wrote:
>
>> I forgot to precise that I allow only one contact per AOR.
>>
>>
>>
>> modparam("registrar", "max_contacts", 1)
>>
>> save("location", "0x04")
>>
>>
>>
>> *From:* Mickael Marrache [mailto:mickaelmarra...@gmail.com]
>> *Sent:* Friday, January 30, 2015 10:51 AM
>> *To:* sr-users@lists.sip-router.org
>> *Subject:* Wrong location entries when using usrloc with Mongo
>>
>>
>>
>> Hi,
>>
>>
>>
>> I start with no location nor in Mongo, nor in memory. My UA registers
>> successfully and I can see the location entry in Mongo. Then, I close my
>> UA which unregisters (by setting Expires header to 0). Then, I open the app
>> again and a new registration is made.
>>
>>
>>
>> The entry after first registration. Looks okay.
>>
>>
>>
>> { "_id" : ObjectId("54cb38f684e58133783f2b42"), "username" : "A",
>> "contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp",
>> "expires" : ISODate("2015-01-30T08:55:34Z"), "q" : -1, "callid" :
>> "297EC55073A07BF78F0C05822A6CCDFB47E48705", "cseq" : 8809, "flags" : 0,
>> "cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received"
>> : "sip:XXX:54217;transport=tcp", "path" : "<
>> sip:XX;lr;received=sip:XXX:54217%3Btransport%3Dtcp>",
>> "socket" : "udp:X:5060", "methods" : 4751, "last_modified" :
>> ISODate("2015-01-30T07:55:34Z"), "ruid" : "uloc-54cb38df-3378-2",
>> "instance" : null, "reg_id" : 0 }
>>
>>
>>
>> The same entry after un register (Expires 0). Note that the username
>> field is missing. In any case, I expected the entry to be deleted.
>>
>>
>>
>> { "_id" : ObjectId("54cb38f684e58133783f2b42"), "expires" :
>> ISODate("2015-01-30T08:56:51Z"), "q" : -1, "cseq" : 8811, "flags" : 0,
>> "cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received"
>> : "sip: X:54217;transport=tcp", "path" : "> X;lr;received=sip: X:54217%3Btransport%3Dtcp>", "socket" :
>> "udp: X:5060", "methods" : 4751, "last_modified" :
>> ISODate("2015-01-30T07:56:51Z"), "callid" :
>> "297EC55073A07BF78F0C05822A6CCDFB47E48705", "instance" : null, "reg_id" :
>> 0, "contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp"
>> }
>>
>>
>>
>> The entries after second registration. The new entry looks okay. But, the
>> old entry is still here.
>>
>>
>>
>> { "_id" : ObjectId("54cb38f684e58133783f2b42"), "expires" :
>> ISODate("2015-01-30T08:56:51Z"), "q" : -1, "cseq" : 8811, "flags" : 0,
>> "cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received"
>> : "sip: X:54217;transport=tcp", "path" : "> X;lr;received=sip: X:54217%3Btransport%3Dtcp>", "socket" :
>> "udp: X:5060", "methods" : 4751, "last_modified" :
>> ISODate("2015-01-30T07:56:51Z"), "callid" :
>> "297EC55073A07BF78F0C05822A6CCDFB47E48705", "instance" : null, "reg_id" :
>> 0, "contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp"
>> }
>>
>>
>>
>> { "_id" : ObjectId("54cb3a7884e581337a25b895"), "username" : "A",
>> "contact" : "sip:A@192.168.1.3:54217;rinstance=DFAEBBC7;transport=tcp",
>> "expires" : ISODate("2015-01-30T09:02:00Z"), "q" : -1, "callid" :
>> "297EC55073A07BF78F0C05822A6CCDFB47E48705", "cseq" : 8813, "flags" : 0,
>> "cflags" : 0, "user_agent" : "Acrobits Softphone Business/3.1", "received"
>> : "sip: X:54217;transport=tcp", "path" : "> X;lr;received=sip: X:54217%3Btransport%3Dtcp>", "socket" :
>> "udp: X:5060", "methods" : 4751, "last_modified" :
>> ISODate("2015-01-30T08:02:00Z"), "ruid" : "uloc-54cb38df-337a-1",
>> "instance" : null, "reg_id" : 0 }
>>
>>
>>
>> The issue is the entry is not deleted after un registering.
>>
>>
>>
>> I precise that registrations are dispatched over multiple registrars with
>> all accesses the same Mongo cluster.
>>
>>
>>
>> Thanks,
>>
>> Mickael
>>
>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>
>
> --
> Daniel-Constantin Mierla - http://www.asipto.com
> http://twitter.com/#!/miconda - http://www.linkedin.com/in/micond
> 
>



-- 
Daniel-Constantin Mierla - http://www.asipto.com
ht

Re: [SR-Users] Possible memory leak dealing with presence in kamailio

2015-01-30 Thread Nuno Reis

Hi Daniel.

Thanks for answering me back. I'll follow the exact procedures from here:
http://www.kamailio.org/wiki/tutorials/troubleshooting/memory and will let
you know about my exact finding soon.

Cheers,

--

*Nuno Miguel Reis* | *Unified Communication** Systems*
M. +351 913907481 | nr...@wavecom.pt
WAVECOM-Soluções Rádio, S.A.
Cacia Park | Rua do Progresso, Lote 15
3800-639 AVEIRO | Portugal
T. +351 309 700 225 | F. +351 234 919 191
*GPS

| www.wavecom.pt ** *

[image: Description: Description: WavecomSignature]


[image: Publicity] 



On Fri, Jan 30, 2015 at 5:23 AM, Daniel-Constantin Mierla  wrote:

> Hello,
>
> which memory is increasing? shared or private memory? or is system memory?
>
> Cheers,
> Daniel
>
> On Fri, Jan 30, 2015 at 4:24 AM, Nuno Reis  wrote:
>
>> Hi Juha and all.
>>
>> I understand that and that is what the RFC says. It seems pua module does
>> that right. Although something is clearly not right in my production
>> environment because kamailio memory consumption still grows pretty fast.
>> Kamailio memory usage starts in ~500MB and after ~24H kamailio is using
>> ~3GB. If I disable kamailio from listening on the localhost(127.0.0.1)
>> where pua is generating the SIP Publishes kamailio just keeps around the
>> ~500MB all the time.
>> This is a small production environment with 70 extensions with Yealink
>> phones.
>> Any ideas on how to chase down this memory leak? Should I open a git
>> issue for this one?
>>
>>
>>
>> --
>>
>> *Nuno Miguel Reis* | *Unified Communication** Systems*
>> M. +351 913907481 | nr...@wavecom.pt
>> WAVECOM-Soluções Rádio, S.A.
>> Cacia Park | Rua do Progresso, Lote 15
>> 3800-639 AVEIRO | Portugal
>> T. +351 309 700 225 | F. +351 234 919 191
>> *GPS
>> 
>> | www.wavecom.pt ** *
>>
>> [image: Description: Description: WavecomSignature]
>> 
>>
>> [image: Publicity] 
>>
>>
>>
>> On Wed, Jan 21, 2015 at 8:45 PM, Juha Heinanen  wrote:
>>
>>> Nuno Reis writes:
>>>
>>> > Here my publisher is Kamailio itself. Can someone elaborate a bit more
>>> on
>>> > this issue and maybe we can get to bottom of it?
>>>
>>> when your application issues initial publish request, it does so without
>>> SIP-If-Match header.  200 ok from presence server then contains an etag
>>> in SIP-ETag header. when your application refreshes the publish, it must
>>> place this etag in SIP-If-Match header to prevent presence server from
>>> creating a new publication.
>>>
>>> for subscribes, your application must place in re-subscribe the
>>> same event header id param as the previous one had in order for the
>>> presence server to know that subscribe was not a new subscription.
>>>
>>> -- juha
>>>
>>
>>
>
>
> --
> Daniel-Constantin Mierla - http://www.asipto.com
> http://twitter.com/#!/miconda - http://www.linkedin.com/in/micond
> 
>
___
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] What could cause an intermittent fault (28) with http_query()?

2015-01-30 Thread Tim Chubb

Hi All

I seem to be experiencing an intermittent fault with the utils http_query() 
method.  We are implementing a routing and white list component that is 
accessed via a REST api, however i have observed several occasions where this 
is logged:
Jan 30 16:04:17 vs-kam-prod02 /usr/local/sbin/kamailio[13184]: ERROR: utils 
[functions.c:149]: http_query(): failed to perform curl (28)

The indicated error number (28) seems to suggest a timeout is occurring with 
curl, however examining a capture of network traffic when this happens shows 
that a http request is not sent from the server to the destination at all, 
usually attempting a second call results in everything working correctly.

As stated its intermittent in its nature and so I cannot reliably trigger this 
issue, other than through sheer repetition, so any ideas as to what could be 
causing this issue would be gratefully received,
___
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 IMS: can not register

2015-01-30 Thread dfretes

Hi all. I'm trying to setup Kamailio for IMS server, but I've reached a 
point where I can not move. Trying to register from the Boghe client, I 
get these errors from the pcscf:


tail -f /var/log/syslog|grep './pcscf'

Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** 
cfgtrace:request_route=[DE 
FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=402 a=25 n=xlog
Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR:

Re: [SR-Users] Dispatcher weight dont work

2015-01-30 Thread Will Ferrer

Hi Yuriy

Sounds great. I am glad to hear you got a good working solution.

I hope you have a great weekend.

All the best.

Will

On Thu, Jan 29, 2015 at 2:52 AM, Yuriy Gorlichenko 
wrote:

> Will, thanks for your answer. I already implemented my own lgorithm
> without using dispatcher module. It works better for me. Now I try to
> implement it with REDIS for faster results.
>
> 2015-01-29 1:35 GMT+03:00 Will Ferrer :
>
>> Hi Yuri
>>
>> I shared your issue with my business partner who works on the configs
>> with me. I had remembered he had some similar issue he pinged me about some
>> time back.
>>
>> His response to your issue follows:
>>
>> Looks like he is missing flags 8 and the trailing ; after weight in
>> attrs.
>> CREATE TABLE `dispatcher` (
>> `id`   `setid` `destination` `flags` `priority` `attrs`  `description`
>> 1 1 sip:10.0.0.1 8 1 weight=50;
>> 2 1 sip:10.0.0.2 8 2 weight=50;
>>
>> To see if it changes is being used by Kamailio run:
>> kamcmd dispatcher.list
>>
>> BODY: weight=50  <-- this is the raw attrs
>> WEIGHT: 50 <-- this show that the attribute has been processed.
>>
>> {
>> NRSETS: 1
>> RECORDS: {
>> SET: {
>> ID: 1
>> TARGETS: {
>> DEST: {
>> URI: sip:10.0.0.1
>> FLAGS: AP
>> PRIORITY: 1
>> ATTRS: {
>> BODY: weight=50
>> DUID:
>> MAXLOAD: 0
>> WEIGHT: 50
>> }
>> }
>> DEST: {
>> URI: sip:10.0.0.2
>> FLAGS: AP
>> PRIORITY: 1
>> ATTRS: {
>> BODY: weight=50
>> DUID:
>> MAXLOAD: 0
>> WEIGHT: 50
>> }
>> }
>> }
>> }
>> }
>> }
>>
>> I hope that helps.
>>
>> All the best.
>>
>> Will
>>
>> On Tue, Jan 27, 2015 at 3:12 AM, Yuriy Gorlichenko 
>> wrote:
>>
>>> Hello I use dipatcher  algorithm 8 that works with weight. I added  2
>>> Asterisks and try to call its with my kam.We use 4.3 version.
>>>
>>> Tthis config select needed dst from database with my scenario.
>>>
>>> if(!ds_select_dst("$var(setid)", "8"))
>>>
>>> $var(setid)- is variable for setting setid that i get from database with
>>> my own scenario. IT does not matter.
>>>
>>> When running asterisk with weight 90 - all calls goes through it. When I
>>> starting asterisk with weight 10 -calls going through asterisk 90. When I
>>> shut down asterisk with weight 90 -calls goes through asterisk 10? but when
>>> i start asterisk weight 90 all calls goes through sterisk 10 until I shut
>>> down it.
>>>
>>> root@Kamailio:~# kamailio -v
>>> version: kamailio 4.3.0-dev3 (x86_64/linux) 8cdbe7
>>> flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
>>> DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
>>> F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
>>> USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
>>> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
>>> MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
>>> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
>>> id: 8cdbe7
>>> compiled on 01:17:56 Jan 21 2015 with gcc 4.8.2
>>>
>>>
>>> id setid   destination  flags priority attrs
>>> 1   2   sip:34.25.123.45:506000  0 weight=10
>>>
>>>
>>>
>>> 2   2   sip:10.0.1.6:506000  0weight=90
>>>
>>> modparam("dispatcher", "db_url",DBURL)
>>> modparam("dispatcher", "table_name", "dispatcher")
>>> modparam("dispatcher", "setid_col", "setid")
>>> modparam("dispatcher", "destination_col", "destination")
>>> modparam("dispatcher", "force_dst", 1)
>>> modparam("dispatcher", "flags", 3)
>>> modparam("dispatcher", "dst_avp", "$avp(i:271)")
>>> modparam("dispatcher", "grp_avp", "$avp(i:272)")
>>> modparam("dispatcher", "cnt_avp", "$avp(i:273)")
>>> modparam("dispatcher", "ds_ping_from", "sip:proxy@10.0.1.1")
>>> modparam("dispatcher", "ds_ping_interval",15)
>>> modparam("dispatcher", "ds_probing_mode", 1)
>>> modparam("dispatcher", "ds_ping_reply_codes",
>>> "class=2;code=403;code=404;code=484;class=3")
>>> modparam("tm", "reparse_on_dns_failover", 0)
>>>
>>>
>>> Thanks
>>>
>>> ___

Re: [SR-Users] Async module taking down our server

2015-01-30 Thread Will Ferrer

Hi Brandon

The feature fixed some issues one of our clients auto dialer were having.

I hope you have a great weekend.

All the best.

Will

On Thu, Jan 29, 2015 at 5:06 AM, Brandon Armstead  wrote:

> Why not just kill the call and have billing fix up for minimum duration
> occur during CDR creation?  Does not make sense to delay Hangup just to
> meet minimum duration.
>
> Sent from my iPhone
>
> On Jan 28, 2015, at 5:37 PM, Will Ferrer 
> wrote:
>
> Hi Daniel
>
> Yeah I am happy to be able to report the success. Thanks for everything as
> always!
>
> I hope you are well.
>
> Will
>
> On Wed, Jan 28, 2015 at 5:54 AM, Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>>  Hello,
>>
>> great that it was sorted out and it was not on Kamailio side :-)
>>
>> Also, glad to hear that async processing did increase capacity to handle
>> more concurrent calls, even it was causing troubles to other applications
>> ...
>>
>> Cheers,
>> Daniel
>>
>>
>> On 28/01/15 05:40, Will Ferrer wrote:
>>
>> Hello
>>
>>  I wanted to give an update on this.
>>
>>  My business partner that found the issue and has been monitoring the
>> problem has tracked down the issue. It turns out that the features we
>> implemented using the async module were leading to more calls going on con
>> currently (as they were intended to) and this was causing and issue with
>> voip monitor. So the issue was not with the Async module.
>>
>>  All the best.
>>
>>  Will Ferrer
>>
>>  Switchsoft
>>
>> On Mon, Jan 19, 2015 at 8:43 PM, Will Ferrer 
>> wrote:
>>
>>> Hi All
>>>
>>> We are trying to use the async module to to delay sending a bye on from
>>> one end of the call to the other.
>>>
>>> We are using async_route(routename, seconds) to delay
>>> the WITHINDLG route. The idea is that in the future we want to be able to
>>> have our billing min duration enforced (though currently we are having
>>> issues with the dialog module that we are discussing in another thread).
>>>
>>>  After running this on our deploy servers, the delays before sending on
>>> the byes get longer and longer, and then kamailio goes down. Then the
>>> receive udp buffer fills up.
>>>
>>> We tried it with both 4 and 400 async workers, and it made no difference.
>>>
>>>  I am including a screen capture of the servers stats when this happens
>>> taken from voip monitor.
>>>
>>>  Here are the relevant parts of the config:
>>>
>>>  ...
>>> loadmodule "async.so"
>>>  ...
>>> modparam("async", "workers", ASYNC_THREADS)
>>>  ...
>>> request_route {
>>> ...
>>> route(DELAYED_BYE_STATIC);
>>>  ...
>>>  route[DELAYED_BYE_STATIC] {
>>>  xlog("L_DEBUG","route DELAYED_BYE_STATIC");
>>>  #!ifdef WITH_DELAYED_BYE_STATIC
>>>  if (is_method("BYE")) {
>>>  xlog("L_DEBUG","route DELAYED_BYE_STATIC, from self \n");
>>>  #if (from_uri == myself) {
>>>  if ((allow_trusted() || allow_source_address()) && from_uri == myself)
>>> {
>>>  xlog("L_DEBUG","route DELAYED_BYE_STATIC, Bye detected, from self \n");
>>>  send_reply("200", "OK");
>>>  xlog("L_DEBUG","route DELAYED_BYE_STATIC, sent 200 about to sleep \n");
>>>  setflag(FLT_ACC); # do accounting ...
>>>  setflag(FLT_ACCFAILED); # ... even if the transaction fails
>>>  if (has_totag()) {
>>>  xlog("L_DEBUG","route DELAYED_BYE_STATIC, sleeping to
>>> WITHINDLG_DELAYED \n");
>>>  async_route("WITHINDLG_DELAYED", MIN_DURATION);
>>>  } else {
>>>  xlog("L_DEBUG","route DELAYED_BYE_STATIC, sleeping to WITHINDLG \n");
>>>  async_route("WITHINDLG", MIN_DURATION);
>>>  }
>>>  xlog("L_DEBUG","route DELAYED_BYE_STATIC, slept\n");
>>>  exit;
>>>  }
>>>  }
>>>  #!endif
>>>  return;
>>> }
>>>  ...
>>>  route[WITHINDLG_DELAYED] {
>>>  xlog("L_DEBUG", "route WITHINDLG_DELAYED: triggered \n");
>>>  $avp(was_delayed) = 1;
>>>  route(WITHINDLG);
>>> }
>>>  ...
>>>  route[WITHINDLG] {
>>>  xlog("L_DEBUG", "route WITHINDLG: will -- DLG triggered, request
>>> method: $rm \n");
>>>  #!ifdef WITH_DISPATCHER
>>>  if(is_method("BYE|CANCEL")) {
>>>  xlog("L_DEBUG","route WITHINDLG:  cancel or bye detected, request
>>> method: $rm \n");
>>>  #!ifdef WITH_DISPATCHER_LOAD_AWARE
>>>  xlog("L_DEBUG","route WITHINDLG: running ds_load_update, request
>>> method: $rm \n");
>>>  ds_load_update();
>>>  #dlg_get ("$ci","$ft","$tt");
>>>  #dlg_bye ("all");
>>> #!endif
>>>  }
>>>  #!endif
>>>
>>>  if (has_totag() || $avp(was_delayed) == 1) {
>>>  xlog("L_DEBUG", "route WITHINDLG: will -- DLG has totag or
>>> was_delayed: $avp(was_delayed)  \n");
>>>  # sequential request withing a dialog should
>>>  # take the path determined by record-routing
>>>  if (loose_route()) {
>>>  xlog("L_DEBUG", "route WITHINDLG: will -- DLG has loose route \n");
>>>  route(DLGURI);
>>>  if (is_method("BYE")) {
>>>  xlog("L_DEBUG","route WITHINDLG: BYE detected");
>>>  setflag(FLT_ACC); # do accounting ...
>>>  setflag(FLT_ACCFAILED); # ... even if the transaction fails
>>>  xlog("L_DEBUG","route WITHINDLG: ACC flag set");
>>>   }
>>>  else if ( is_method("ACK") ) {
>>>  # ACK is fo

Re: [SR-Users] Core dump while saving user location in mongo

Re: [SR-Users] Can kamailio generate a PRACK

[SR-Users] Wrong location entries when using usrloc with Mongo

Re: [SR-Users] Wrong location entries when using usrloc with Mongo

Re: [SR-Users] why do not support tcp:eth1:5062，only support eht1:5062

[SR-Users] tls_port_no maybe do not work

Re: [SR-Users] Wrong location entries when using usrloc with Mongo

Re: [SR-Users] why do not support tcp:eth1:5062，only support eht1:5062

Re: [SR-Users] why do not support tcp:eth1:5062，only support eht1:5062

Re: [SR-Users] NDB_REDIS password to REDIS remote DB

Re: [SR-Users] NDB_REDIS password to REDIS remote DB

Re: [SR-Users] Wrong location entries when using usrloc with Mongo

Re: [SR-Users] Possible memory leak dealing with presence in kamailio

[SR-Users] What could cause an intermittent fault (28) with http_query()?

[SR-Users] Kamailio IMS: can not register

Re: [SR-Users] Dispatcher weight dont work

Re: [SR-Users] Async module taking down our server

17 matches

Site Navigation

Mail list logo

Footer information