I don't care about billing, but do care about very detailed realtime and historical call logging and routing system. xml cdr is not an option since it does not handle certain logging scenarios like call transfers, multy party call conversions, custom call events like recording started or stopped, etc. and it does not handle realtime call routing at all. We try to port our IBM Genesys like PBX and Call Center solution from asterisk to freeswitch, but for this I would need hangup detection. Actually I'm just in the learning phase in the migration process and try to use the fastest ways for the initial testing, that's why I try to use lua. Sorry for this long story :) Should this hangup detection work, I mean am I doing something wrong, or this feature is not implemented yet? If not, what language and method do you suggest to implement robust call routing and history? Thank's for your valuable help in advance!
On Jul 13, 2009, at 8:39 AM, rentmycoder rentmycoder wrote:
I don't care about billing, but do care about very detailed realtime and historical call logging and routing system. xml cdr is not an option since it does not handle certain logging scenarios like call transfers, multy party call conversions, custom call events like recording started or stopped, etc. and it does not handle realtime call routing at all.
Its not the job of the CDR to handle rrealtime call routing... what exactly are you going for? XML CDR does stack the caller profiles for every transfer and action that takes place.
We try to port our IBM Genesys like PBX and Call Center solution from asterisk to freeswitch, but for this I would need hangup detection.
Hangup detection? Does the far end not send you a bye?
Actually I'm just in the learning phase in the migration process and try to use the fastest ways for the initial testing, that's why I try to use lua. Sorry for this long story :) Should this hangup detection work, I mean am I doing something wrong, or this feature is not implemented yet?
Can you elaborate on this more ?
If not, what language and method do you suggest to implement robust call routing and history?
You post process the XML CDR to get a full detail of what is going on.
Thank's for your valuable help in advance!
/b
On Mon, Jul 13, 2009 at 6:39 AM, rentmycoder rentmycoder < rentmycoder@gmail.com> wrote:
I don't care about billing, but do care about very detailed realtime and historical call logging and routing system.
Are you building something that monitors call status while the calls are still in progress? If so you really need to be using the event socket.
xml cdr is not an option since it does not handle certain logging scenarios like call transfers, multy party call conversions, custom call events like recording started or stopped, etc. and it does not handle realtime call routing at all.
The XML CDRs have loads of information, including detailed call flow. Documentation is here: http://wiki.freeswitch.org/wiki/Mod_xml_cdr#Reference_Information Of course, like Brian said, the CDR always happens after the call is finished, which is why I was curious about the specifics of your application. You mentioned "very detailed realtime" but I'm not sure if that means "while the call is happening" or "immediately after the call completes."
We try to port our IBM Genesys like PBX and Call Center solution from asterisk to freeswitch, but for this I would need hangup detection. Actually I'm just in the learning phase in the migration process and try to use the fastest ways for the initial testing, that's why I try to use lua. Sorry for this long story :)
No prob. Details help paint the picture. :)
Should this hangup detection work, I mean am I doing something wrong, or this feature is not implemented yet? If not, what language and method do you suggest to implement robust call routing and history?
I recommend you parse a sample XML CDR. If it contains all the information you need then you can use mod_xml_cdr and post-process the calls as soon as they complete. If the XML CDR doesn't contain all the information you need then we'd like to know what it is missing - the devs would be willing to add anything that's missing, assuming it makes sense to do so. If you want absolute, unconditional access to every piece of information for every call as it happens in real-time, live and unedited, then you definitely need to build something that uses the event socket. I'm not sure there's much ROI in this method unless you have a special need to update a database while calls are in progress. Personally, I like mod_xml_cdr because it will post to a web server and create a disk file - a good way to keep your valuable call information safe in case of a web server or db server outage. -MC
participants (3)
-
Brian West
-
Michael Collins
-
rentmycoder rentmycoder