Hi Michael, The problem is that occasionally we see the following in FS log: 2016-04-13 02:33:11.143230 [ERR] mod_xml_cdr.c:385 Got error [0] posting to web server [http://cdrs.example.com/queue] 2016-04-13 02:33:11.143230 [ERR] mod_xml_cdr.c:392 Retry will be with url [ http://cdrs.example.com/queue] When that happens, the CDR gets written to disc (so the CDR is not processed on time, thus our user is not billed for that call yet). We have a task that checks every 5 minutes for failed CDRs and we resubmit them to the processing queue, but I need to find out why FS is failing. I have checked the access logs on the receiving side, but all requests return a 200 OK. Now I have enabled logs in the loadbalancer between FS and the queues to see if I get more vision from there... A workaround was to make API requests directly from the dialplan with the billsec info, but as all suggest going with CDRs, I am now focussed on finding the root cause for that error. Any help/suggestion is more than welcome. Thank you. Best regards, Joel. On Tue, Apr 12, 2016 at 1:42 PM, Michael Jerris <mike@jerris.com> wrote:
I'm probably going to push towards cdr, but what are you trying to actually do with that info?
On Apr 12, 2016, at 2:39 PM, Joel Serrano <joel@gogii.net> wrote:
Hi Michael,
I want to call an API basically with the following info:
sip_from_uri destination_number billsec
I found away using "api_hangup_hook=lua script.lua" + "session_in_hangup_hook=true", but, I don't like it... I would prefer using curl from within the dialplan.
Can you give me your suggestion? I have also asked in IRC and using the CDRs looks like the best way to go, so we will probably follow that, but I would still like to now if it is possible and how.
Thanks! Joel.
On Tue, Apr 12, 2016 at 12:22 PM, Michael Jerris <mike@jerris.com> wrote:
Billsec is set in reporting state, after you are out of dial plan. What are you trying to do based on that, I can suggest a few approaches
On Monday, April 11, 2016, Joel Serrano <joel@gogii.net> wrote:
Hi,
Is it possible to access ${billsec} in the dialplan after the bridge application (having hangup_after_bridge=false)??
I want to log the billsec but currently it is always empty.
I have a workaround in a test server using api_hangup_hook to call a lua script with session_in_hangup_hook=true, and inside the lua script I can access the billsec variable and thus write it to the logs.
Is there no way to do this within the XML dialplan?
Thanks!
Best regards, Joel.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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