[SR-Users] Kamailio usrloc mode 3 using mongodb
Daniel-Constantin Mierla
miconda at gmail.com
Fri May 17 09:37:50 CEST 2019
Hello,
pushed the patch to master and 5.2 branches. Can you test and see if all ok?
Cheers,
Daniel
On 16.05.19 17:03, José Seabra wrote:
> Hello Daniel,
> Thank you for the feedback.
>
> Would be possible include this patch in the new kamailio release 5.2.3?
>
> Best Regards
> José Seabra
>
> Daniel-Constantin Mierla <miconda at gmail.com
> <mailto:miconda at gmail.com>> escreveu no dia quinta, 16/05/2019 à(s) 11:44:
>
> Hello,
>
> you can ignore them for the moment, at least in this case it is
> about a null value and the type doesn't matter much.
>
> I have in plan to add a schema check for db_mongodb, but I haven't
> gotten the time yet.
>
> As a solution for now, I will push soon a small patch to catch the
> null value and print dbg instead of info.
>
> Cheers,
> Daniel
>
> On 16.05.19 12:15, José Seabra wrote:
>> Hello there,
>> I'm testing usrloc module with mongodb and i have a couple of
>> questions to do.
>>
>> What i would like to know/have confirmation is if the fields that
>> are specified in the following link
>> https://kamailio.org/docs/db-tables/kamailio-db-5.2.x.html#gen-db-location-index
>> can be used to create indexes in mongodb?
>>
>> I'm noticing that when a register is updated/deleted or expires
>> kamailio prints the following INFO logs:
>>
>> /db_mongodb [mongodb_dbase.c:526]: db_mongodb_get_columns():
>> unhandled data type column (methods) type id (10), use
>> DB1_STRING as default/
>> /db_mongodb [mongodb_dbase.c:526]: db_mongodb_get_columns():
>> unhandled data type column (instance) type id (10), use
>> DB1_STRING as default/
>>
>>
>> These fields (/methods and //instance/) are stored in mongodb
>> document with a null string, e.g:
>>
>> /{/
>> /"_id" : ObjectId("5cdc775a6472740055289a11"),/
>> /"username" : "x1000",/
>> /"contact" : "sip:x1000 at 192.168.1.1:5674;transport=UDP",/
>> /"expires" : ISODate("2019-05-15T20:33:26Z"),/
>> /"q" : -1,/
>> /"callid" :
>> "sipp-ci2-edge-sip-proxy1-20190515203220-1-21 at 172.31.2.61
>> <mailto:sipp-ci2-edge-sip-proxy1-20190515203220-1-21 at 172.31.2.61>",/
>> /"cseq" : 2,/
>> /"flags" : 0,/
>> /"cflags" : 0,/
>> /"user_agent" : "sipp",/
>> /"received" : "sip:191.30.10.23:8888
>> <http://191.30.10.23:8888>",/
>> /"path" :
>> "<sip:172.31.2.61:5060;received=sip:191.30.10.23:8888;lr>",/
>> /"socket" : "udp:172.31.2.11:5060 <http://172.31.2.11:5060>",/
>> /*"methods" : null,*/
>> /"last_modified" : ISODate("2019-05-15T20:32:26Z"),/
>> /"ruid" : "uloc-15-5cdc7756-55-1",/
>> /*"instance" : null,*/
>> /"reg_id" : 0,/
>> /"server_id" : 21,/
>> /"connection_id" : -1,/
>> /"keepalive" : 0,/
>> /"partition" : 0/
>> /}/
>>
>> Should i be concerned about that log msg? how can i avoid it?
>>
>>
>> Thanks
>> Regards
>>
>> --
>> Cumprimentos
>> José Seabra
>>
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at lists.kamailio.org <mailto:sr-users at lists.kamailio.org>
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com>
> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
>
>
>
> --
> Cumprimentos
> José Seabra
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20190517/c4c0bcba/attachment.html>
More information about the sr-users
mailing list