Dmitry Sinina wrote on 01/17/2015 09:32 PM: > On 01/12/2015 04:01 PM, John Nash wrote: >> Dear Stefan, >> >> I am using SBC application and want to use it to log CDR for connected >> as well as failed calls. I saw syslog_cdr module I have following questions >> >> 1- In syslog CDR conf file I can specify >> cdr_format=$ltag,$start_tm,$connect_tm,$end_tm,$duration,MyHeader >> >> from "myheader" do you mean whatever header are part of Invite message >> including custom headers? Also what about additional information which yes, but I think you have to configure it in the call control configuration, e.g. call_control=cdr cdr_module=cc_syslog_cdr cdr_MyHeader=$H(MyHeader)
>> is not in the Invite but comes later like hangup direction, disconnect >> cause code/reason etc. try $hangup_cause, $hangup_initiator and $disposition >> >> 2- Is there any way we can log CDR to postgresql database? you'll have to post-process from syslog (e.g. with rsyslogd). >> > > > You can try SEMS based solution for this: > http://yeti-switch.org/ > > We implemented such features by patching core and SBC module. > that's interesting. is the sems part also open source? thanks! Stefan _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
