Mickael
>
>
>
> *From:*Mickael Marrache [mailto:mickaelmarra...@gmail.com]
> *Sent:* Monday, April 13, 2015 5:13 PM
> *To:* mico...@gmail.com; 'Kamailio (SER) - Users Mailing List'
> *Subject:* RE: [SR-Users] CDR fields are all strings
>
>
>
> We are using MongoDB and a
2015 3:03 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] CDR fields are all strings
Hello,
On 13/04/15 11:48, Mickael Marrache wrote:
Hi,
Why are all the CDR fields inserted as strings?
For extra fields, I can understand it is easier to implement. However, for
th
List
Subject: Re: [SR-Users] CDR fields are all strings
Hello,
On 13/04/15 11:48, Mickael Marrache wrote:
Hi,
Why are all the CDR fields inserted as strings?
For extra fields, I can understand it is easier to implement. However, for
the built in fields (e.g. duration), we need to
Hello,
On 13/04/15 11:48, Mickael Marrache wrote:
>
> Hi,
>
>
>
> Why are all the CDR fields inserted as strings?
>
>
>
> For extra fields, I can understand it is easier to implement. However,
> for the built in fields (e.g. duration), we need to perform queries
> based on duration and time a
Hi,
Why are all the CDR fields inserted as strings?
For extra fields, I can understand it is easier to implement. However, for
the built in fields (e.g. duration), we need to perform queries based on
duration and time and it is not really possible using strings.
I see that the time fiel
