hi everybody, I've just put my openser 0.9.5 in the production environment and it works well. For now, I jus use a query to extract the CDR as "call_date", "orig_number", "termination_number", "duration" and "src_ip". but when the volume is very large I get the following problem. The scenario is as follows.
call_date | orig_number | term_number | duration | src_ip 2005-09-25 20:45:30 | 203@my_sip_server | 56924536@my_sip_server | 14:00:30 X.X.X.X
2005-09-25 20:45:30 |56924356@my_sip_server | 43234123@my_sip_server| 4:00:30 X.X.X.X
I get the same number as the origination number which was the destination number some moments before, when in reality it is not possible to call from that particular number. But this only happens when the calling volume is really large. Does anyone have any idea regarding this. If you want to see the query I can do that. pls share if there is some better query to generate the CDR..
I have also downloaded the latest version 0.10.x from CVS head. Can somebody tell me how stable is it for the production environment.
thanx jayesh
--------------------------------- Yahoo! for Good Click here to donate to the Hurricane Katrina relief effort.
jayesh nambiar wrote:
hi everybody, I've just put my openser 0.9.5 in the production environment and it works well. For now, I jus use a query to extract the CDR as "call_date", "orig_number", "termination_number", "duration" and "src_ip". but when the volume is very large I get the following problem. The scenario is as follows.
call_date | orig_number | term_number | duration | src_ip 2005-09-25 20:45:30 | 203@my_sip_server | 56924536@my_sip_server | 14:00:30 X.X.X.X
2005-09-25 20:45:30 |56924356@my_sip_server | 43234123@my_sip_server | 4:00:30 X.X.X.X
I get the same number as the origination number which was the
they are different: 56924536@my_sip_server 56924356@my_sip_server ^^
are they real different or is this a type?
I always used the SQL query from serweb (the accouting tab) to match CDRs.
regards klaus
destination number some moments before, when in reality it is not possible to call from that particular number. But this only happens when the calling volume is really large. Does anyone have any idea regarding this. If you want to see the query I can do that. pls share if there is some better query to generate the CDR..
I have also downloaded the latest version 0.10.x from CVS head. Can somebody tell me how stable is it for the production environment.
thanx jayesh
Yahoo! for Good Click here to donate http://store.yahoo.com/redcross-donate3/ to the Hurricane Katrina relief effort.
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Klaus, They are same, that was a typing mistake. Sorry for that. If possible can you share the query used in SERWEB. I never used serweb, it will help me even if you provide some links to it.
Even I think that the latest version should not have any problems in the normal usage. I thinking of deploying it in my production environment.
Thanks, jayesh
Klaus Darilion klaus.mailinglists@pernau.at wrote:jayesh nambiar wrote:
hi everybody, I've just put my openser 0.9.5 in the production environment and it works well. For now, I jus use a query to extract the CDR as "call_date", "orig_number", "termination_number", "duration" and "src_ip". but when the volume is very large I get the following problem. The scenario is as follows.
call_date | orig_number | term_number | duration | src_ip 2005-09-25 20:45:30 | 203@my_sip_server | 56924536@my_sip_server | 14:00:30 X.X.X.X
2005-09-25 20:45:30 |56924356@my_sip_server | 43234123@my_sip_server | 4:00:30 X.X.X.X
I get the same number as the origination number which was the
they are different: 56924536@my_sip_server 56924356@my_sip_server ^^
are they real different or is this a type?
I always used the SQL query from serweb (the accouting tab) to match CDRs.
regards klaus
destination number some moments before, when in reality it is not possible to call from that particular number. But this only happens when the calling volume is really large. Does anyone have any idea regarding this. If you want to see the query I can do that. pls share if there is some better query to generate the CDR..
I have also downloaded the latest version 0.10.x from CVS head. Can somebody tell me how stable is it for the production environment.
thanx jayesh
Yahoo! for Good Click here to donate to the Hurricane Katrina relief effort.
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
--------------------------------- Yahoo! for Good Click here to donate to the Hurricane Katrina relief effort.
jayesh nambiar wrote:
Hi Klaus, They are same, that was a typing mistake. Sorry for that. If possible can you share the query used in SERWEB. I never used serweb, it will help me even if you provide some links to it.
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/serweb/serweb/modules/accounting/m...
Take a look at function acc_prepare_SQL(){
klaus
Even I think that the latest version should not have any problems in the normal usage. I thinking of deploying it in my production environment.
Thanks, jayesh
*/Klaus Darilion klaus.mailinglists@pernau.at/* wrote:
jayesh nambiar wrote: > hi everybody, > I've just put my openser 0.9.5 in the production environment and it > works well. For now, I jus use a query to extract the CDR > as "call_date", "orig_number", "termination_number", "duration" and > "src_ip". > but when the volume is very large I get the following problem. The > scenario is as follows. > > call_date | orig_number | > term_number | duration | src_ip > 2005-09-25 20:45:30 | 203@my_sip_server | > 56924536@my_sip_server | > 14:00:30 X.X.X.X > > 2005-09-25 20:45:30 |56924356@my_sip_server | 43234123@my_sip_server > | 4:00:30 X.X.X.X > > I get the same number as the origination number which was the they are different: 56924536@my_sip_server 56924356@my_sip_server ^^ are they real different or is this a type? I always used the SQL query from serweb (the accouting tab) to match CDRs. regards klaus > destination number some moments before, when in reality it is not > possible to call from that particular number. > But this only happens when the calling volume is really large. Does > anyone have any idea regarding this. > If you want to see the query I can do that. > pls share if there is some better query to generate the CDR.. > > I have also downloaded the latest version 0.10.x from CVS head. Can > somebody tell me how stable is it for the production environment. > > thanx > jayesh > > ------------------------------------------------------------------------ > Yahoo! for Good > Click here to donate to the > Hurricane Katrina relief effort. > > > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > Users@openser.org > http://openser.org/cgi-bin/mailman/listinfo/users
Yahoo! for Good Click here to donate http://store.yahoo.com/redcross-donate3/ to the Hurricane Katrina relief effort.
jayesh nambiar wrote:
hi everybody,
I have also downloaded the latest version 0.10.x from CVS head. Can somebody tell me how stable is it for the production environment.
I still notice 2 crashes which does not occour in normal usage, but only occour if you make conformance tests (protos sip test suite).
regards klaus