I would like to get more information on accounting with SER.
Ok, I followed the documentation about accounting but it doesn't give enough information about how to retrieve the accounting information. It just says that Reports are by DEFAULT sent to the syslog facility. Where is that syslog? How do I retreive that information? Is it possible to put that information in the MySQL database? How? That is by DEFAULT; so, is it possible to change that default location?
Some gurus will realize how NEWBIE I am in the Linux World. Please help me.
Thanks, __________________________________ NZEYIMANA Emery Fabrice NEFA Computing Services, Inc. P.O. Box 5078 Kigali Office Phone: +250-51 11 06 Office Fax: +250-50 15 19 Mobile: +250-08517768 Email: dg@nefacomp.net http://www.nefacomp.net/
At 10:17 PM 7/7/2003, Director General: NEFACOMP wrote:
I would like to get more information on accounting with SER.
Ok, I followed the documentation about accounting but it doesn't give enough information about how to retrieve the accounting information. It just says that Reports are by DEFAULT sent to the syslog facility. Where is that syslog?
see "man syslogd"
How do I retreive that information? Is it possible to put that information in the MySQL database?
yes
How?
see modules/acc/README
That is by DEFAULT; so, is it possible to change that default location?
Some gurus will realize how NEWBIE I am in the Linux World. Please help me.
Thanks, __________________________________ NZEYIMANA Emery Fabrice NEFA Computing Services, Inc. P.O. Box 5078 Kigali Office Phone: +250-51 11 06 Office Fax: +250-50 15 19 Mobile: +250-08517768 Email: mailto:dg@nefacomp.netdg@nefacomp.net http://www.nefacomp.net/ _______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
Syslog is a standard unix facility. Normally, in a standard linux install, you will see a file named /var/log/messages. That is where the accounting information will be written.
You can groom this, for instance, if you want to direct the messages from SER to a special file, using the syslog facility. You will need to look at the manual page, ie:
man syslog.conf
to get some ideas about this.
The syslog entries are enabled with the lines:
... loadmodule "/usr/ser/lib/ser/modules/acc.so" ... modparam("acc", "log_level", 1) modparam("acc", "log_flag", 1 ) modparam("acc", "log_fmt", "miocfsu" ) ...
route { ... setflag(1); setflag(2); ...
}
I can't comment on the accounting module for mysql, but I imagine that is described by the accounting README.txt file in the appropriate module directory.
Our implementation scans the syslog files and writes into a postgres database the call accounting stuff.
There is a bit of a learning curve involved with this. However, the programming documentation is very good and this list is great for when you get stumped, but only then :-)
---greg Greg Fausak Addaline.com, Inc.
-----Original Message----- From: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Director General: NEFACOMP Sent: Monday, July 07, 2003 3:17 PM To: serusers Subject: [Serusers] Accounting with SER
I would like to get more information on accounting with SER.
Ok, I followed the documentation about accounting but it doesn't give enough information about how to retrieve the accounting information. It just says that Reports are by DEFAULT sent to the syslog facility. Where is that syslog? How do I retreive that information? Is it possible to put that information in the MySQL database? How? That is by DEFAULT; so, is it possible to change that default location?
Some gurus will realize how NEWBIE I am in the Linux World. Please help me.
Thanks, __________________________________ NZEYIMANA Emery Fabrice NEFA Computing Services, Inc. P.O. Box 5078 Kigali Office Phone: +250-51 11 06 Office Fax: +250-50 15 19 Mobile: +250-08517768 Email: dg@nefacomp.net http://www.nefacomp.net/
MessageAccount is not compiled with MySQL support by default. Simply uncomment the line # DEFS+=-DSQL_ACC and recompile again.
But actually, if you want to leverage Acc module for CDR, you'll get disappointed probably. In normal situation, you have no problem. The trouble is, your account information is based on the SIP message exchange through the ser proxy. If a called failed after establishment and no further message is sent by UAC and UAS. If ser proxy queries both side of a call at certain intervals, that will be ok. However, I am not sure if SIP supports such status query.
Younger Wang ----- Original Message ----- From: Greg Fausak To: 'Director General: NEFACOMP' ; 'serusers' Sent: Monday, July 07, 2003 2:38 PM Subject: RE: [Serusers] Accounting with SER
Syslog is a standard unix facility. Normally, in a standard linux install, you will see a file named /var/log/messages. That is where the accounting information will be written.
You can groom this, for instance, if you want to direct the messages from SER to a special file, using the syslog facility. You will need to look at the manual page, ie:
man syslog.conf
to get some ideas about this.
The syslog entries are enabled with the lines:
... loadmodule "/usr/ser/lib/ser/modules/acc.so" ... modparam("acc", "log_level", 1) modparam("acc", "log_flag", 1 ) modparam("acc", "log_fmt", "miocfsu" ) ...
route { ... setflag(1); setflag(2); ...
}
I can't comment on the accounting module for mysql, but I imagine that is described by the accounting README.txt file in the appropriate module directory.
Our implementation scans the syslog files and writes into a postgres database the call accounting stuff.
There is a bit of a learning curve involved with this. However, the programming documentation is very good and this list is great for when you get stumped, but only then :-)
---greg Greg Fausak Addaline.com, Inc.
-----Original Message----- From: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Director General: NEFACOMP Sent: Monday, July 07, 2003 3:17 PM To: serusers Subject: [Serusers] Accounting with SER
I would like to get more information on accounting with SER.
Ok, I followed the documentation about accounting but it doesn't give enough information about how to retrieve the accounting information. It just says that Reports are by DEFAULT sent to the syslog facility. Where is that syslog? How do I retreive that information? Is it possible to put that information in the MySQL database? How? That is by DEFAULT; so, is it possible to change that default location?
Some gurus will realize how NEWBIE I am in the Linux World. Please help me.
Thanks, __________________________________ NZEYIMANA Emery Fabrice NEFA Computing Services, Inc. P.O. Box 5078 Kigali Office Phone: +250-51 11 06 Office Fax: +250-50 15 19 Mobile: +250-08517768 Email: dg@nefacomp.net http://www.nefacomp.net/
------------------------------------------------------------------------------
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
At 06:57 PM 7/8/2003, Younger Wang wrote:
Account is not compiled with MySQL support by default. Simply uncomment the line # DEFS+=-DSQL_ACC and recompile again.
But actually, if you want to leverage Acc module for CDR, you'll get disappointed probably. In normal situation, you have no problem. The trouble is, your account information is based on the SIP message exchange through the ser proxy. If a called failed after establishment and no further message is sent by UAC and UAS.
That's actually not an issue specific to SIP -- it is specific to IP networks. There is just packets and no line which may go disconnected in a way you could sense. Not too bad as long as both UAs are native-IP. If you provide PSTN access, you should buy a PSTN gateway that is able to detect a dead call and initiate a BYE. Not very different from PSTN -- if you disconnect your handset, the other call party will hang up sooner or later.
If ser proxy queries both side of a call at certain intervals, that will be ok. However, I am not sure if SIP supports such status query.
There is a mechanism called session timer. The idea is simple: make UA send keep-alive messages. If none arrives, call-stateful elements in the signaling path can remove call state.
-Jiri
At 06:57 PM 7/8/2003, Younger Wang wrote:
Account is not compiled with MySQL support by default.
Simply uncomment the line
# DEFS+=-DSQL_ACC and recompile again.
But actually, if you want to leverage Acc module for CDR,
you'll get disappointed probably. In normal situation, you have no problem. The trouble is, your account information is based on the SIP message exchange through the ser proxy. If a called failed after establishment and no further message is sent by UAC and UAS.
That's actually not an issue specific to SIP -- it is specific to IP networks. There is just packets and no line which may go disconnected in a way you could sense. Not too bad as long as both UAs are native-IP. If you provide PSTN access, you should buy a PSTN gateway that is able to detect a dead call and initiate a BYE. Not very different from PSTN -- if you disconnect your handset, the other call party will hang up sooner or later.
We are using the cisco 7206vxr gear. They report connect/disconnect messages to syslog as well. As you note we use the TDM disconnect to re-enforce our SIP BYE messages. Often the SIP BYE is missed.
If ser proxy queries both side of a call at certain
intervals, that will be ok. However, I am not sure if SIP supports such status query.
There is a mechanism called session timer. The idea is simple: make UA send keep-alive messages. If none arrives, call-stateful elements in the signaling path can remove call state.
Is there an example of the session timer with SER somewhere?
---greg
-Jiri
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
At 04:41 AM 7/8/2003, Greg Fausak wrote:
We are using the cisco 7206vxr gear. They report connect/disconnect messages to syslog as well. As you note we use the TDM disconnect to re-enforce our SIP BYE messages. Often the SIP BYE is missed.
I just want to verify I understood -- you are saying that with 7206, a TDM disconnect is sometimes not translated in a SIP BYE but is at least reported via syslog?
If ser proxy queries both side of a call at certain
intervals, that will be ok. However, I am not sure if SIP supports such status query.
There is a mechanism called session timer. The idea is simple: make UA send keep-alive messages. If none arrives, call-stateful elements in the signaling path can remove call state.
Is there an example of the session timer with SER somewhere?
That's a theoretical SIP option today, SER is not supporting session-timer. We gave it a try more than one year ago and gave up due to interop problems. The specification was developing at that time so quickly that there was not any UA which would work with another one correctly.
Once the interoperability gets better, it could be worth implementing. It is in general a nice mechanism for avoiding session state silo in network, which is good for scalability.
-Jiri
At 04:41 AM 7/8/2003, Greg Fausak wrote:
We are using the cisco 7206vxr gear. They report connect/disconnect messages to syslog as well. As you note we use the TDM disconnect to re-enforce our SIP BYE messages. Often the SIP BYE is missed.
I just want to verify I understood -- you are saying that with 7206, a TDM disconnect is sometimes not translated in a SIP BYE but is at least reported via syslog?
What we do is keep scan all ACC: messages and match the INVITEs with the BYEs/CANCELs. Also, we shoot the cisco log Messages to syslog. We match the TDM hangups to the call it was Associated with. Sometimes we don't get a BYE, but we always get The TDM disconnect from the Cisco. I don't know if the Cisco BYE is lost, or, perhaps the UA connected to the Cisco? I'll see if I Can find out.
If ser proxy queries both side of a call at certain
intervals, that will be ok. However, I am not sure if SIP supports such status query.
There is a mechanism called session timer. The idea is simple: make UA send keep-alive messages. If none arrives,
call-stateful elements
in the signaling path can remove call state.
Is there an example of the session timer with SER somewhere?
That's a theoretical SIP option today, SER is not supporting session-timer. We gave it a try more than one year ago and gave up due to interop problems. The specification was developing at that time so quickly that there was not any UA which would work with another one correctly.
Once the interoperability gets better, it could be worth implementing. It is in general a nice mechanism for avoiding session state silo in network, which is good for scalability.
I think the Jasomi does a trick with an OPTIONS message.
---greg
-Jiri
I wrote a crude little perl script that reads the SYSLOG and then generates Call Detail Records which are output to MySQL "cdrs" table and a flat file as well. Its job is to match INVITES to BYES and then compute the call duration. Works great on RedHat Linux 7.3. Can easly be modified to work on other platforms.
The syslog in the default install of RH7.3 is in /var/log/messages
Attached is the script.
Regards, Ricardo ----- Original Message ----- From: Director General: NEFACOMP To: serusers Sent: Monday, July 07, 2003 3:17 PM Subject: [Serusers] Accounting with SER
I would like to get more information on accounting with SER.
Ok, I followed the documentation about accounting but it doesn't give enough information about how to retrieve the accounting information. It just says that Reports are by DEFAULT sent to the syslog facility. Where is that syslog? How do I retreive that information? Is it possible to put that information in the MySQL database? How? That is by DEFAULT; so, is it possible to change that default location?
Some gurus will realize how NEWBIE I am in the Linux World. Please help me.
Thanks, __________________________________ NZEYIMANA Emery Fabrice NEFA Computing Services, Inc. P.O. Box 5078 Kigali Office Phone: +250-51 11 06 Office Fax: +250-50 15 19 Mobile: +250-08517768 Email: dg@nefacomp.net http://www.nefacomp.net/
------------------------------------------------------------------------------
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Director General: NEFACOMP -
Greg Fausak -
Jiri Kuthan -
Ricardo Villa -
Younger Wang