Hi folks,
I just committed on CVS head support for call-leg accounting. The documentation was already updated both on CVS and site (http://www.openser.org/docs/modules/0.10.x/acc.html).
this feature is quite useful when a call gets to have several legs ( for example, due call forwarding services). Having detailed accounting of the call leg will allow easy and proper CDR generation and billing.
the feature is available for syslog, DB and RADIUS accounting (DIAMETER still missing).
Any suggestions/comments regarding the way it works or it's implemented are welcomed. Also problem reports :)
regards, Bogdan
Bogdan-Andrei Iancu writes:
Any suggestions/comments regarding the way it works or it's implemented are welcomed. Also problem reports :)
this feature is only needed if call forwarding takes place within a single pass through the proxy. it is not needed if forwarded call will be routed back to the proxy, because then two (or more) accounting records are produced automatically.
-- juha
Juha Heinanen wrote:
Bogdan-Andrei Iancu writes:
Any suggestions/comments regarding the way it works or it's implemented are welcomed. Also problem reports :)
this feature is only needed if call forwarding takes place within a single pass through the proxy. it is not needed if forwarded call will be routed back to the proxy, because then two (or more) accounting records are produced automatically.
agreed, but call forwarding as spiral is not all the time the best approach - too many resources (memory for transaction chain) are consumed, messages are getting bigger (due multiple Via RR headers) and too much time overhead (parsing and assembling the requests/replies at each spiral).
with this feature you have the liberty to do forwarding without spiralling the request on server - it will be more efficient ;)
regards, bogdan
Bogdan-Andrei Iancu writes:
with this feature you have the liberty to do forwarding without spiralling the request on server - it will be more efficient ;)
i agree that it will be more efficient, but will also result in more complicated ser.cfg.
-- juha
Juha Heinanen wrote:
Bogdan-Andrei Iancu writes:
with this feature you have the liberty to do forwarding without spiralling the request on server - it will be more efficient ;)
i agree that it will be more efficient, but will also result in more complicated ser.cfg.
I gave it a try and believe me, it pays off the effort ...first as efficiency and second as possibilities - more thing are easier to handle since all processing is concentrated in only one pass through - if spiralling if some info needs to be preserved during the whole processing, you need to save it inside the SIP message...
regards, bogdan
-
Bogdan-Andrei Iancu -
Juha Heinanen