yes, you are right. we are receiving the reply. but, we are using socket outbound and manage all calls over this socket. we also measure the durations (like variable_duration and variable_billsec) and count all outgoing calls over the socket. but, if the originate (without an inbound call) will not start the socket, we can not count up, how many calls failed because of "user busy" or how long the platform was in use.
a possible workarround: is it possible to trigger a dialplan over the cli (like our default dialplan, which starts the socket), so that the dialplan starts the originates? the basic problem for us, that, if we just want to make dialouts, we are missing the inbound call to start the socket. kind regards dennis 2009/2/9 Anthony Minessale <anthony.miness...@gmail.com>: > when an originate is unsuccessful the failure and the cause code is returned > as the reply to the originate request. > > > On Mon, Feb 9, 2009 at 9:16 AM, Dennis <oderm...@googlemail.com> wrote: >> >> hi, >> >> i am using socket outbound with fs. >> >> if i do an originate over the console, for starting an outbound call >> without having an inbound call, and send the originate directly to the >> socket, the socket is first started, if the call is in answer or >> ringing state. >> before this, i will not receive any event, because the socket was not >> started. therefore i will not know, if the target is "busy" (hangup, >> hangup cause: user busy). >> >> it would be very helpful, if the socket would start immediately on an >> event like "channel originate". >> >> >> thanks for the help >> dennis _______________________________________________ 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