February 2009 - freeswitch-dev@lists.freeswitch.org

[Freeswitch-dev] mod_radius_cdr behavior and questions
by Apostolos Pantsiopoulos 12 Feb '09

12 Feb '09

Hi, I am tweaking the mod_radius_cdr module to archive the behavior that most NASes have (i.e. accounting packets are sent in a separate thread so that the submission does not interfere with the execution of the call). While doing that, however, I bumped into another behavior of the module that I think is not desirable (at least by me) : While on a bridge, the module sends one acct start packet at the beginning of the originating leg (on_routing event handler) and two acct stop packets at the end of each leg (inbound and outbound). My opinion is that it should send one accounting start packet at the beginning of each call leg (inbound, outbound) resulting to a total number of two acct start packets. It is generally accepted that acct start/stop packets come in pairs so that billing applications can handle them accordingly. Some NAS's radius radius implementations have some other configuration modes like the Cisco's RADIUS Packet Suppression. When in this mode the Cisco NAS sends only an accounting start/stop pair at the end of a final dialpeer attempt (and suppresses all the previous failed dialpeer attempts) thus resulting to less network traffic. Other NASes (such as MERA MVTS) can send a start/stop pair for each leg OR a start/stop pair for each end to end call, depending on the configuration. Opensips follows the star/stop pair by call leg paradigm. No matter what the implementation, all of them always send a acct start/stop pair. This is a common thing. And all the billing platforms can deal only with paired start/stops. The current module behavior (one start two stops) can complicate things since the radius server would not know how to match the second stop packet with its equivalent start. Before I get the infamous answer "pathes welcomed" I would like to state that I am already involved in changing this behavior (through a patch). So my real question is this : I noticed that the module uses the switch_core_add_state_handler function to register its handler table : switch_core_add_state_handler(&state_handlers); So the on_routing ( or the on_execute) event happens only when the inbound call is started. When the outbound call is initiated no handler is available to hook up a function and send the proper acct start packet. Should the module register its handlers using the switch_channel_add_state_handler() function instead? And if yes, how could the module pass the channel as a parameter to the function since channels are created and destroyed dynamically (and the module when initialized does not have that info). I would greatly appreciate your help in pinpointing a proper way to call my event handling routines on a per call leg basis. -- ------------------------------------------- Apostolos Pantsiopoulos Kinetix Tele.com R & D email: regs(a)kinetix.gr -------------------------------------------

5 26

[Freeswitch-dev] Some Sample C programs in using FreeSwitch APIs
by Scott Shen 12 Feb '09

12 Feb '09

Can any one provide some C programs showing how to use FreeSwitch APIs to build an UAC or UAS? Thanks & Regards Scott

3 4

[Freeswitch-dev] Freeswitch on Debian repository
by Nicholas Santos 06 Feb '09

06 Feb '09

Hi, I'm the current owner of the Freeswitch package on Debian Testing (Lenny). I'm just beginning to package it, if there's something that I should know before I package it, just say it. I'm here to do my best on this that I consider a great step. Thanks in advance, Nicholas Amorim. PS: By the way, what a great piece of software! :)

6 18

[Freeswitch-dev] Manual Attended Transfer using 3 channels
by David Dikman (a05davdi) 05 Feb '09

05 Feb '09

Hi, I'm currently implementing an operator to direct calls with using freeswitch and event socket. The operator should be able to do an attended transfer, that is the operator is supposed to be able to recieve a call, call another party and switch back and forward between these to before eventually bridging them together. (I cannot use att_xfer since it doesn't have the behaviour we wish). I've gotten everything to work fine up 'till the point where the operator has called a second party and whishes to switch back to the first party and this is where I need some help. I use event socket for sending the api commands but if I could just get a hint of how to do it manually (with console) I could probably convert it (or how to do it in js). These are the steps I go through now: (notice that I'm trying to use only 3 channels so that the operator needn't park channels on phone) * Originate call between inbound call and operator (Gives me what i'll refer to as Leg A and Leg B) * Hold Leg A (gives music to Leg A) * Transfer Leg B to Ext XX (Gives me Leg C, now I've got one call from A-B and one from B-C) * Unhold Leg B (I can talk between B and C) What should be the next step? I've tried holding C and then bridging, transfering, intercepting etc but nothing works. Whatever I do the call between Leg A and Leg B disappears and no sound between the two. I can bridge A->C and get them to talk to each other but I would also like to be able to switch back from B->C to A-B. I've been guessing my way around this for quite some time now and I would really appreciate some help.

3 4

[Freeswitch-dev] Cisco 7975G and XML options for G722
by Brian West 01 Feb '09

01 Feb '09

I'm digging for the option in the XML to enable G722 on the 7975G, It says "Enterprise Advertise G.722, Disabled", "Device Advertise G.722, Use System Default" So what options to turn G722 on? Anyone? Anyone? Thanks, /b

1 0