4 Sep
2018
4 Sep
'18
11:06 a.m.
Hi Community,
Is there a documentation regarding the Call Detail Logs in any of the OSMO Elements such
as Call Information (call started, duration and end/caller and callee information,etc...)
and SMS Information (sent/received time/sender and receiver,etc...)?
And may we know what log level configuration do we need to configure for us to see those
information?
Thanks in advance.
Best Regard,
Ron Menez
ron.menez@entropysolution.com<mailto:ron.menez@entropysolution.com>
5 Sep
5 Sep
12:09 p.m.
On Tue, Sep 04, 2018 at 09:06:37AM +0000, Ron wrote:
Is there a documentation regarding the Call Detail
Logs in any of the OSMO Elements such as Call Information (call started, duration and
end/caller and callee information,etc...) and SMS Information (sent/received time/sender
and receiver,etc...)?
The component that knows most about caller identities and duration is the MSC,
but it doesn't (yet) conveniently summarize call details anywhere. More suited
would be the use of an external call router via MNCC, I guess.
~N
6 Sep
6 Sep
4:23 a.m.
Thanks for info Neels.
Best Regard,
Ron Menez
ron.menez@entropysolution.com<mailto:ron.menez@entropysolution.com>
On Sep 5, 2018, at 6:09 PM, Neels Hofmeyr
<nhofmeyr@sysmocom.de<mailto:nhofmeyr@sysmocom.de>> wrote:
On Tue, Sep 04, 2018 at 09:06:37AM +0000, Ron wrote:
Is there a documentation regarding the Call Detail Logs in any of the OSMO Elements such
as Call Information (call started, duration and end/caller and callee information,etc...)
and SMS Information (sent/received time/sender and receiver,etc...)?
The component that knows most about caller identities and duration is the MSC,
but it doesn't (yet) conveniently summarize call details anywhere. More suited
would be the use of an external call router via MNCC, I guess.
~N
5 Sep
5 Sep
7:24 p.m.
Hello Ron,
It's been a few months since I've worked with the osmocom CDR's, but from
memory I think what you're looking for is the cdr configuration option. In
osmocom, "log" refers to the logs of the actual programs (think what you
would see in syslog). I've only ever used cdr's in the SGSN to track data
usage for billing, but I believe you can get the same information on the
circuit switched side of the world too. In the SGSN, the relevant config
line is detailed in the latest SGSN manual
http://ftp.osmocom.org/docs/latest/osmosgsn-usermanual.pdf , although
suspiciously the cdr config options are not listed under the SGSN vty
reference anymore.
Regards,
-Matt J.
On Tue, Sep 4, 2018 at 2:06 AM Ron <ron.menez(a)entropysolution.com> wrote:
Hi Community,
Is there a documentation regarding the Call Detail Logs in any of the OSMO
Elements such as Call Information (call started, duration and end/caller
and callee information,etc...) and SMS Information (sent/received
time/sender and receiver,etc...)?
And may we know what log level configuration do we need to configure for
us to see those information?
Thanks in advance.
Best Regard,
Ron Menez
ron.menez(a)entropysolution.com
6 Sep
6 Sep
4:23 a.m.
Thanks for the input Matthew.
We’ll explore the CDR from other OSMO elements if it is still available.
Best Regard,
Ron Menez
ron.menez@entropysolution.com<mailto:ron.menez@entropysolution.com>
On Sep 6, 2018, at 1:24 AM, Matthew Johnson
<matt9j@cs.washington.edu<mailto:matt9j@cs.washington.edu>> wrote:
Hello Ron,
It's been a few months since I've worked with the osmocom CDR's, but from
memory I think what you're looking for is the cdr configuration option. In osmocom,
"log" refers to the logs of the actual programs (think what you would see in
syslog). I've only ever used cdr's in the SGSN to track data usage for billing,
but I believe you can get the same information on the circuit switched side of the world
too. In the SGSN, the relevant config line is detailed in the latest SGSN manual
http://ftp.osmocom.org/docs/latest/osmosgsn-usermanual.pdf , although suspiciously the cdr
config options are not listed under the SGSN vty reference anymore.
Regards,
-Matt J.
On Tue, Sep 4, 2018 at 2:06 AM Ron
<ron.menez@entropysolution.com<mailto:ron.menez@entropysolution.com>> wrote:
Hi Community,
Is there a documentation regarding the Call Detail Logs in any of the OSMO Elements such
as Call Information (call started, duration and end/caller and callee information,etc...)
and SMS Information (sent/received time/sender and receiver,etc...)?
And may we know what log level configuration do we need to configure for us to see those
information?
Thanks in advance.
Best Regard,
Ron Menez
ron.menez@entropysolution.com<mailto:ron.menez@entropysolution.com>
7:48 a.m.
Hi Matthew,
thanks for sharing your experience!
On Wed, Sep 05, 2018 at 10:24:16AM -0700, Matthew Johnson wrote:
It's been a few months since I've worked with
the osmocom CDR's, but from
memory I think what you're looking for is the cdr configuration option.
In osmocom, "log" refers to the logs of the
actual programs (think
what you would see in syslog).
this is correct.
I've only ever used cdr's in the SGSN to track
data
usage for billing, but I believe you can get the same information on the
circuit switched side of the world too.
Unfortunately we don't have any CDR generation in OsmoMSC. This reasons
are twofold:
a) this is an "enterprise" feature, i.e. nothing that you'd need for
research/lab type use, and hence nothing that anyone would likely
volunteer to do in their spare time. The SGSN CDR was developed
under funding from a specific enterprise user who had a related
requirement.
b) most networks don't end at the MSC but they actually have some kind
of other (soft)switch infrastructure behind the MSC, and hence the
voice call related logs can be obtained there. This doesn't apply
to the same degree for SMS, though.
although suspiciously the cdr config options are not
listed under the
SGSN vty reference anymore.
This is definitely not how it's supposed to be. Would you mind opening a
new issue about this in the OsmoSGSN issue tracker at
https://osmocom.org/projects/osmosgsn/issues ? Thanks!
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
11:29 p.m.
Hello Harald,
I went to go file the bug, and realized that I had made an error! I was
looking quickly through several manuals at the same time, and was searching
the GGSN VTY reference by accident.
Ron,
The details on the CDR configuration options for the SGSN are available as
expected in the SGSN's VTY reference manual
http://ftp.osmocom.org/docs/latest/osmosgsn-vty-reference.pdf
Cheers,
-Matt J.
On Wed, Sep 5, 2018 at 10:50 PM Harald Welte <laforge(a)gnumonks.org> wrote:
Hi Matthew,
thanks for sharing your experience!
On Wed, Sep 05, 2018 at 10:24:16AM -0700, Matthew Johnson wrote:
It's been a few months since I've worked
with the osmocom CDR's, but from
memory I think what you're looking for is the cdr configuration option.
In osmocom, "log" refers to the logs of
the actual programs (think
what you would see in syslog).
this is correct.
I've only ever used cdr's in the SGSN to
track data
usage for billing, but I believe you can get the same information on the
circuit switched side of the world too.
Unfortunately we don't have any CDR generation in OsmoMSC. This reasons
are twofold:
a) this is an "enterprise" feature, i.e. nothing that you'd need for
research/lab type use, and hence nothing that anyone would likely
volunteer to do in their spare time. The SGSN CDR was developed
under funding from a specific enterprise user who had a related
requirement.
b) most networks don't end at the MSC but they actually have some kind
of other (soft)switch infrastructure behind the MSC, and hence the
voice call related logs can be obtained there. This doesn't apply
to the same degree for SMS, though.
although suspiciously the cdr config options are
not listed under the
SGSN vty reference anymore.
This is definitely not how it's supposed to be. Would you mind opening a
new issue about this in the OsmoSGSN issue tracker at
https://osmocom.org/projects/osmosgsn/issues ? Thanks!
--
- Harald Welte <laforge(a)gnumonks.org>
http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch.
A6)
2068
days inactive
2070
days old
6 comments
4 participants
participants (4)
-
Harald Welte -
Matthew Johnson -
Neels Hofmeyr -
Ron