mod_cdr_csv missing timestamps in A-LEG
hello, i'm on latest trunk and for some reason i cannot get timestamps dumped in my cdrs. I use mod_cdr_csv with default settings plus i enabled to get both a and b legs dumped. cdr_csv.conf.xml: <configuration name="cdr_csv.conf" description="CDR CSV Format"> <settings> <!-- 'cdr-csv' will always be appended to log-base --> <!--<param name="log-base" value="/var/log"/>--> <param name="default-template" value="example"/> <!-- This is like the info app but after the call is hung up --> <!--<param name="debug" value="true"/>--> <param name="rotate-on-hup" value="true"/> <!-- may be a b or ab --> <param name="legs" value="ab"/> </settings> <templates> <template name="sql">INSERT INTO cdr VALUES ("${caller_id_name}","${caller_id_number}","${destination_number}","${context}","${s tart_stamp}","${answer_stamp}","${end_stamp}","${duration}","${billsec}","${hangup_cause}","${uuid}","${bleg_uuid}", "${accountcode} ");</template> <template name="example">"${caller_id_name}","${caller_id_number}","${destination_number}","${context}","${start_stamp}","${answ er_stamp}","${end_stamp}","${duration}","${billsec}","${hangup_cause}","${uuid}","${bleg_uuid}","${accountcode}","${read_codec}","${ write_codec}"</template> <template name="snom">"${caller_id_name}","${caller_id_number}","${destination_number}","${context}","${start_stamp}","${answer_ stamp}","${end_stamp}","${duration}","${billsec}","${hangup_cause}","${uuid}","${bleg_uuid}", "${accountcode}","${read_codec}","${wr ite_codec}","${sip_user_agent}","${call_clientcode}","${sip_rtp_rxstat}","${sip_rtp_txstat}","${sofia_record_file}"</template> <template name="linksys">"${caller_id_name}","${caller_id_number}","${destination_number}","${context}","${start_stamp}","${answ er_stamp}","${end_stamp}","${duration}","${billsec}","${hangup_cause}","${uuid}","${bleg_uuid}","${accountcode}","${read_codec}","${ write_codec}","${sip_user_agent}","${sip_p_rtp_stat}"</template> <template name="asterisk">"${accountcode}","${caller_id_number}","${destination_number}","${context}","${caller_id}","${channel_ name}","${bridge_channel}","${last_app}","${last_arg}","${start_stamp}","${answer_stamp}","${end_stamp}","${duration}","${billsec}", "${hangup_cause}","${amaflags}","${uuid}","${userfield}"</template> </templates> </configuration> call flow is the following: CALLER => FS => CALLED FS answers the call from CALLER, plays an announcement and bridges towards CALLED. I get different behavior when the call is released by Caller and by Called. Released by Caller: the CDR is ok having all timestamps OK CDR: Outbound LEG => "016659280","016659280","0914392122","public","2009-09-24 12:02:48","2009-09-24 12:02:54","2009-09-24 12:03:01","13","7","NORMAL_CLEARING","699cc2d0-a8f1-11de-962a-e328afdb9d8d","","","PCMA","PCMA" Inbound LEG => "016659280","016659280","05000403","public","2009-09-24 12:02:27","2009-09-24 12:02:41","2009-09-24 12:03:01","34","20","NORMAL_CLEARING","5d530192-a8f1-11de-962a-e328afdb9d8d","699cc2d0-a8f1-11de-962a-e328afdb9d8d","","PCMA","PCMA" Released by Called: the CDR is NOT OK as timestamps are missing NOT OK CDR: Inbound LEG => "016659280","016659280","0914392122","public","2009-09-24 12:05:20","2009-09-24 12:05:30","2009-09-24 12:05:39","19","9","NORMAL_CLEARING","c479411a-a8f1-11de-962a-e328afdb9d8d","","","PCMA","PCMA" Outbound LEG =>"016659280","016659280","015000403","public",*"","","",* "0","0","NORMAL_CLEARING","b82f2046-a8f1-11de-962a-e328afdb9d8d","c479411a-a8f1-11de-962a-e328afdb9d8d","","PCMA","PCMA" What can be wrong?
Can you get these same values in xml-cdr? I don't think csv was ever intended to work with different cdrs for a and b leg, it was more intended as a more familiar interface for those coming over from asterisk. Mike On Sep 24, 2009, at 6:10 AM, Tihomir Culjaga wrote:
hello,
i'm on latest trunk and for some reason i cannot get timestamps dumped in my cdrs. I use mod_cdr_csv with default settings plus i enabled to get both a and b legs dumped.
cdr_csv.conf.xml:
<configuration name="cdr_csv.conf" description="CDR CSV Format"> <settings> <!-- 'cdr-csv' will always be appended to log-base --> <!--<param name="log-base" value="/var/log"/>--> <param name="default-template" value="example"/> <!-- This is like the info app but after the call is hung up --> <!--<param name="debug" value="true"/>--> <param name="rotate-on-hup" value="true"/> <!-- may be a b or ab --> <param name="legs" value="ab"/> </settings> <templates> <template name="sql">INSERT INTO cdr VALUES ("$ {caller_id_name}","${caller_id_number}","${destination_number}","$ {context}","${s tart_stamp}","${answer_stamp}","${end_stamp}","${duration}","$ {billsec}","${hangup_cause}","${uuid}","${bleg_uuid}", "${accountcode} ");</template> <template name="example">"${caller_id_name}","$ {caller_id_number}","${destination_number}","${context}","$ {start_stamp}","${answ er_stamp}","${end_stamp}","${duration}","${billsec}","$ {hangup_cause}","${uuid}","${bleg_uuid}","${accountcode}","$ {read_codec}","${ write_codec}"</template> <template name="snom">"${caller_id_name}","$ {caller_id_number}","${destination_number}","${context}","$ {start_stamp}","${answer_ stamp}","${end_stamp}","${duration}","${billsec}","$ {hangup_cause}","${uuid}","${bleg_uuid}", "${accountcode}","$ {read_codec}","${wr ite_codec}","${sip_user_agent}","${call_clientcode}","$ {sip_rtp_rxstat}","${sip_rtp_txstat}","${sofia_record_file}"</ template> <template name="linksys">"${caller_id_name}","$ {caller_id_number}","${destination_number}","${context}","$ {start_stamp}","${answ er_stamp}","${end_stamp}","${duration}","${billsec}","$ {hangup_cause}","${uuid}","${bleg_uuid}","${accountcode}","$ {read_codec}","${ write_codec}","${sip_user_agent}","${sip_p_rtp_stat}"</template> <template name="asterisk">"${accountcode}","$ {caller_id_number}","${destination_number}","${context}","$ {caller_id}","${channel_ name}","${bridge_channel}","${last_app}","${last_arg}","$ {start_stamp}","${answer_stamp}","${end_stamp}","${duration}","$ {billsec}", "${hangup_cause}","${amaflags}","${uuid}","${userfield}"</template> </templates> </configuration>
call flow is the following:
CALLER => FS => CALLED
FS answers the call from CALLER, plays an announcement and bridges towards CALLED.
I get different behavior when the call is released by Caller and by Called.
Released by Caller: the CDR is ok having all timestamps
OK CDR:
Outbound LEG => "016659280","016659280","0914392122","public","2009-09-24 12:02:48","2009-09-24 12:02:54","2009-09-24 12:03:01","13","7","NORMAL_CLEARING","699cc2d0-a8f1-11de-962a- e328afdb9d8d","","","PCMA","PCMA" Inbound LEG => "016659280","016659280","05000403","public","2009-09-24 12:02:27","2009-09-24 12:02:41","2009-09-24 12:03:01","34","20","NORMAL_CLEARING","5d530192-a8f1-11de-962a- e328afdb9d8d","699cc2d0-a8f1-11de-962a-e328afdb9d8d","","PCMA","PCMA"
Released by Called: the CDR is NOT OK as timestamps are missing
NOT OK CDR:
Inbound LEG => "016659280","016659280","0914392122","public","2009-09-24 12:05:20","2009-09-24 12:05:30","2009-09-24 12:05:39","19","9","NORMAL_CLEARING","c479411a-a8f1-11de-962a- e328afdb9d8d","","","PCMA","PCMA" Outbound LEG =
"016659280 ","016659280 ","015000403","public","","","","0","0","NORMAL_CLEARING","b82f2046- a8f1-11de-962a-e328afdb9d8d","c479411a-a8f1-11de-962a- e328afdb9d8d","","PCMA","PCMA"
Hi Michael, thanks for your feedback but it's late now :( I had to moved back to 1.0.3 because it is in production. On that version it works as a charm. for some reason i cannot get it right in 1.0.4 and trunk. Actually, what i'm doing is to subscribe to events (within a custom module) and try to get timestamps... I started having issues when i moved to trunk. To be sure that i'm not doing something wrong, i configured mod_cdr_csv to dump CDRs. Well it turned out this module doesn't work as well in the trunk. Can it be because of AMD opteron + Debian 5.0 enviorment? There is something in the 1.0.4/trunk version that is wrong for that kind of event/CDR. T. On Fri, Sep 25, 2009 at 6:44 AM, Michael Jerris <mike@jerris.com> wrote:
Can you get these same values in xml-cdr? I don't think csv was ever intended to work with different cdrs for a and b leg, it was more intended as a more familiar interface for those coming over from asterisk. Mike
On Sep 24, 2009, at 6:10 AM, Tihomir Culjaga wrote:
hello,
i'm on latest trunk and for some reason i cannot get timestamps dumped in my cdrs. I use mod_cdr_csv with default settings plus i enabled to get both a and b legs dumped.
cdr_csv.conf.xml:
<configuration name="cdr_csv.conf" description="CDR CSV Format"> <settings> <!-- 'cdr-csv' will always be appended to log-base --> <!--<param name="log-base" value="/var/log"/>--> <param name="default-template" value="example"/> <!-- This is like the info app but after the call is hung up --> <!--<param name="debug" value="true"/>--> <param name="rotate-on-hup" value="true"/> <!-- may be a b or ab --> <param name="legs" value="ab"/> </settings> <templates> <template name="sql">INSERT INTO cdr VALUES ("${caller_id_name}","${caller_id_number}","${destination_number}","${context}","${s tart_stamp}","${answer_stamp}","${end_stamp}","${duration}","${billsec}","${hangup_cause}","${uuid}","${bleg_uuid}", "${accountcode} ");</template> <template name="example">"${caller_id_name}","${caller_id_number}","${destination_number}","${context}","${start_stamp}","${answ
er_stamp}","${end_stamp}","${duration}","${billsec}","${hangup_cause}","${uuid}","${bleg_uuid}","${accountcode}","${read_codec}","${ write_codec}"</template> <template name="snom">"${caller_id_name}","${caller_id_number}","${destination_number}","${context}","${start_stamp}","${answer_ stamp}","${end_stamp}","${duration}","${billsec}","${hangup_cause}","${uuid}","${bleg_uuid}", "${accountcode}","${read_codec}","${wr
ite_codec}","${sip_user_agent}","${call_clientcode}","${sip_rtp_rxstat}","${sip_rtp_txstat}","${sofia_record_file}"</template> <template name="linksys">"${caller_id_name}","${caller_id_number}","${destination_number}","${context}","${start_stamp}","${answ
er_stamp}","${end_stamp}","${duration}","${billsec}","${hangup_cause}","${uuid}","${bleg_uuid}","${accountcode}","${read_codec}","${ write_codec}","${sip_user_agent}","${sip_p_rtp_stat}"</template> <template name="asterisk">"${accountcode}","${caller_id_number}","${destination_number}","${context}","${caller_id}","${channel_
name}","${bridge_channel}","${last_app}","${last_arg}","${start_stamp}","${answer_stamp}","${end_stamp}","${duration}","${billsec}", "${hangup_cause}","${amaflags}","${uuid}","${userfield}"</template> </templates> </configuration>
call flow is the following:
CALLER => FS => CALLED
FS answers the call from CALLER, plays an announcement and bridges towards CALLED.
I get different behavior when the call is released by Caller and by Called.
Released by Caller: the CDR is ok having all timestamps
OK CDR:
Outbound LEG => "016659280","016659280","0914392122","public","2009-09-24 12:02:48","2009-09-24 12:02:54","2009-09-24 12:03:01","13","7","NORMAL_CLEARING","699cc2d0-a8f1-11de-962a-e328afdb9d8d","","","PCMA","PCMA" Inbound LEG => "016659280","016659280","05000403","public","2009-09-24 12:02:27","2009-09-24 12:02:41","2009-09-24 12:03:01","34","20","NORMAL_CLEARING","5d530192-a8f1-11de-962a-e328afdb9d8d","699cc2d0-a8f1-11de-962a-e328afdb9d8d","","PCMA","PCMA"
Released by Called: the CDR is NOT OK as timestamps are missing
NOT OK CDR:
Inbound LEG => "016659280","016659280","0914392122","public","2009-09-24 12:05:20","2009-09-24 12:05:30","2009-09-24 12:05:39","19","9","NORMAL_CLEARING","c479411a-a8f1-11de-962a-e328afdb9d8d","","","PCMA","PCMA" Outbound LEG =>"016659280","016659280","015000403","public",*"","","",* "0","0","NORMAL_CLEARING","b82f2046-a8f1-11de-962a-e328afdb9d8d","c479411a-a8f1-11de-962a-e328afdb9d8d","","PCMA","PCMA"
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
nothing I can think of, set up a test box that is not in production and lets figure out what is wrong. Mike On Sep 25, 2009, at 7:22 AM, Tihomir Culjaga wrote:
Hi Michael, thanks for your feedback but it's late now :(
I had to moved back to 1.0.3 because it is in production. On that version it works as a charm.
for some reason i cannot get it right in 1.0.4 and trunk. Actually, what i'm doing is to subscribe to events (within a custom module) and try to get timestamps... I started having issues when i moved to trunk. To be sure that i'm not doing something wrong, i configured mod_cdr_csv to dump CDRs. Well it turned out this module doesn't work as well in the trunk.
Can it be because of AMD opteron + Debian 5.0 enviorment?
There is something in the 1.0.4/trunk version that is wrong for that kind of event/CDR.
T.
On Fri, Sep 25, 2009 at 6:44 AM, Michael Jerris <mike@jerris.com> wrote: Can you get these same values in xml-cdr? I don't think csv was ever intended to work with different cdrs for a and b leg, it was more intended as a more familiar interface for those coming over from asterisk.
Mike
On Sep 24, 2009, at 6:10 AM, Tihomir Culjaga wrote:
hello,
i'm on latest trunk and for some reason i cannot get timestamps dumped in my cdrs. I use mod_cdr_csv with default settings plus i enabled to get both a and b legs dumped.
cdr_csv.conf.xml:
<configuration name="cdr_csv.conf" description="CDR CSV Format"> <settings> <!-- 'cdr-csv' will always be appended to log-base --> <!--<param name="log-base" value="/var/log"/>--> <param name="default-template" value="example"/> <!-- This is like the info app but after the call is hung up --> <!--<param name="debug" value="true"/>--> <param name="rotate-on-hup" value="true"/> <!-- may be a b or ab --> <param name="legs" value="ab"/> </settings> <templates> <template name="sql">INSERT INTO cdr VALUES ("$ {caller_id_name}","${caller_id_number}","${destination_number}","$ {context}","${s tart_stamp}","${answer_stamp}","${end_stamp}","${duration}","$ {billsec}","${hangup_cause}","${uuid}","${bleg_uuid}", "$ {accountcode} ");</template> <template name="example">"${caller_id_name}","$ {caller_id_number}","${destination_number}","${context}","$ {start_stamp}","${answ er_stamp}","${end_stamp}","${duration}","${billsec}","$ {hangup_cause}","${uuid}","${bleg_uuid}","${accountcode}","$ {read_codec}","${ write_codec}"</template> <template name="snom">"${caller_id_name}","$ {caller_id_number}","${destination_number}","${context}","$ {start_stamp}","${answer_ stamp}","${end_stamp}","${duration}","${billsec}","$ {hangup_cause}","${uuid}","${bleg_uuid}", "${accountcode}","$ {read_codec}","${wr ite_codec}","${sip_user_agent}","${call_clientcode}","$ {sip_rtp_rxstat}","${sip_rtp_txstat}","${sofia_record_file}"</ template> <template name="linksys">"${caller_id_name}","$ {caller_id_number}","${destination_number}","${context}","$ {start_stamp}","${answ er_stamp}","${end_stamp}","${duration}","${billsec}","$ {hangup_cause}","${uuid}","${bleg_uuid}","${accountcode}","$ {read_codec}","${ write_codec}","${sip_user_agent}","${sip_p_rtp_stat}"</template> <template name="asterisk">"${accountcode}","$ {caller_id_number}","${destination_number}","${context}","$ {caller_id}","${channel_ name}","${bridge_channel}","${last_app}","${last_arg}","$ {start_stamp}","${answer_stamp}","${end_stamp}","${duration}","$ {billsec}", "${hangup_cause}","${amaflags}","${uuid}","${userfield}"</template> </templates> </configuration>
call flow is the following:
CALLER => FS => CALLED
FS answers the call from CALLER, plays an announcement and bridges towards CALLED.
I get different behavior when the call is released by Caller and by Called.
Released by Caller: the CDR is ok having all timestamps
OK CDR:
Outbound LEG => "016659280","016659280","0914392122","public","2009-09-24 12:02:48","2009-09-24 12:02:54","2009-09-24 12:03:01","13","7","NORMAL_CLEARING","699cc2d0-a8f1-11de-962a- e328afdb9d8d","","","PCMA","PCMA" Inbound LEG => "016659280","016659280","05000403","public","2009-09-24 12:02:27","2009-09-24 12:02:41","2009-09-24 12:03:01","34","20","NORMAL_CLEARING","5d530192-a8f1-11de-962a- e328afdb9d8d","699cc2d0-a8f1-11de-962a-e328afdb9d8d","","PCMA","PCMA"
Released by Called: the CDR is NOT OK as timestamps are missing
NOT OK CDR:
Inbound LEG => "016659280","016659280","0914392122","public","2009-09-24 12:05:20","2009-09-24 12:05:30","2009-09-24 12:05:39","19","9","NORMAL_CLEARING","c479411a-a8f1-11de-962a- e328afdb9d8d","","","PCMA","PCMA" Outbound LEG =
"016659280 ","016659280 ","015000403","public","","","","0","0","NORMAL_CLEARING","b82f2046- a8f1-11de-962a-e328afdb9d8d","c479411a-a8f1-11de-962a- e328afdb9d8d","","PCMA","PCMA"
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
should i move this to the DEV mailing list ? T. On Fri, Sep 25, 2009 at 4:12 PM, Michael Jerris <mike@jerris.com> wrote:
nothing I can think of, set up a test box that is not in production and lets figure out what is wrong. Mike
On Sep 25, 2009, at 7:22 AM, Tihomir Culjaga wrote:
Hi Michael, thanks for your feedback but it's late now :(
I had to moved back to 1.0.3 because it is in production. On that version it works as a charm.
for some reason i cannot get it right in 1.0.4 and trunk. Actually, what i'm doing is to subscribe to events (within a custom module) and try to get timestamps... I started having issues when i moved to trunk. To be sure that i'm not doing something wrong, i configured mod_cdr_csv to dump CDRs. Well it turned out this module doesn't work as well in the trunk.
Can it be because of AMD opteron + Debian 5.0 enviorment?
There is something in the 1.0.4/trunk version that is wrong for that kind of event/CDR.
T.
On Fri, Sep 25, 2009 at 6:44 AM, Michael Jerris <mike@jerris.com> wrote:
Can you get these same values in xml-cdr? I don't think csv was ever intended to work with different cdrs for a and b leg, it was more intended as a more familiar interface for those coming over from asterisk. Mike
On Sep 24, 2009, at 6:10 AM, Tihomir Culjaga wrote:
hello,
i'm on latest trunk and for some reason i cannot get timestamps dumped in my cdrs. I use mod_cdr_csv with default settings plus i enabled to get both a and b legs dumped.
cdr_csv.conf.xml:
<configuration name="cdr_csv.conf" description="CDR CSV Format"> <settings> <!-- 'cdr-csv' will always be appended to log-base --> <!--<param name="log-base" value="/var/log"/>--> <param name="default-template" value="example"/> <!-- This is like the info app but after the call is hung up --> <!--<param name="debug" value="true"/>--> <param name="rotate-on-hup" value="true"/> <!-- may be a b or ab --> <param name="legs" value="ab"/> </settings> <templates> <template name="sql">INSERT INTO cdr VALUES ("${caller_id_name}","${caller_id_number}","${destination_number}","${context}","${s tart_stamp}","${answer_stamp}","${end_stamp}","${duration}","${billsec}","${hangup_cause}","${uuid}","${bleg_uuid}", "${accountcode} ");</template> <template name="example">"${caller_id_name}","${caller_id_number}","${destination_number}","${context}","${start_stamp}","${answ
er_stamp}","${end_stamp}","${duration}","${billsec}","${hangup_cause}","${uuid}","${bleg_uuid}","${accountcode}","${read_codec}","${ write_codec}"</template> <template name="snom">"${caller_id_name}","${caller_id_number}","${destination_number}","${context}","${start_stamp}","${answer_ stamp}","${end_stamp}","${duration}","${billsec}","${hangup_cause}","${uuid}","${bleg_uuid}", "${accountcode}","${read_codec}","${wr
ite_codec}","${sip_user_agent}","${call_clientcode}","${sip_rtp_rxstat}","${sip_rtp_txstat}","${sofia_record_file}"</template> <template name="linksys">"${caller_id_name}","${caller_id_number}","${destination_number}","${context}","${start_stamp}","${answ
er_stamp}","${end_stamp}","${duration}","${billsec}","${hangup_cause}","${uuid}","${bleg_uuid}","${accountcode}","${read_codec}","${ write_codec}","${sip_user_agent}","${sip_p_rtp_stat}"</template> <template name="asterisk">"${accountcode}","${caller_id_number}","${destination_number}","${context}","${caller_id}","${channel_
name}","${bridge_channel}","${last_app}","${last_arg}","${start_stamp}","${answer_stamp}","${end_stamp}","${duration}","${billsec}", "${hangup_cause}","${amaflags}","${uuid}","${userfield}"</template> </templates> </configuration>
call flow is the following:
CALLER => FS => CALLED
FS answers the call from CALLER, plays an announcement and bridges towards CALLED.
I get different behavior when the call is released by Caller and by Called.
Released by Caller: the CDR is ok having all timestamps
OK CDR:
Outbound LEG => "016659280","016659280","0914392122","public","2009-09-24 12:02:48","2009-09-24 12:02:54","2009-09-24 12:03:01","13","7","NORMAL_CLEARING","699cc2d0-a8f1-11de-962a-e328afdb9d8d","","","PCMA","PCMA" Inbound LEG => "016659280","016659280","05000403","public","2009-09-24 12:02:27","2009-09-24 12:02:41","2009-09-24 12:03:01","34","20","NORMAL_CLEARING","5d530192-a8f1-11de-962a-e328afdb9d8d","699cc2d0-a8f1-11de-962a-e328afdb9d8d","","PCMA","PCMA"
Released by Called: the CDR is NOT OK as timestamps are missing
NOT OK CDR:
Inbound LEG => "016659280","016659280","0914392122","public","2009-09-24 12:05:20","2009-09-24 12:05:30","2009-09-24 12:05:39","19","9","NORMAL_CLEARING","c479411a-a8f1-11de-962a-e328afdb9d8d","","","PCMA","PCMA" Outbound LEG =>"016659280","016659280","015000403","public",*"","","",* "0","0","NORMAL_CLEARING","b82f2046-a8f1-11de-962a-e328afdb9d8d","c479411a-a8f1-11de-962a-e328afdb9d8d","","PCMA","PCMA"
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (2)
-
Michael Jerris
-
Tihomir Culjaga