Thanks, Michael! Your advise seemed to be a workaround to most events although not all (missing some new, init and few others). I'll update to the newest version as soon as there's a fix for the win32 build (doesn't work for me either). Btw, Will that little race fixing allow me to correlate the BGPAI JOB-UUID to these missing events? It's not that I don't get those events - I just don't know what request initiated them... Cheers, UV -----Original Message----- From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Michael Jerris Sent: Tuesday, April 15, 2008 2:30 AM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] event BACKGROUND too late in ORIGINATEscenario? You can set your own unique id reference as a variable to the originate using the {my_uuid=1234567ABCD} syntax and then track all events off that variable that should be included on every event. http://wiki.freeswitch.org/wiki/Freeswitch_IVR_Originate Also, we just fixed a little race that might have allowed you to get events before you got the background uuid so you probably want to update to most recent code. Mike On Apr 14, 2008, at 11:39 AM, UV wrote:
We're busy integrating a heavy-duty call-control engine on top of the Freeswitch and I'm not sure if what's happening is by design or a bug:
When originating a call via the "bgapi originate" call (mod_commands) the BACKGROUND event invoked only AFTER the call successfully terminated (answered/rejected). Because only the BACKGROUND event has the correlation between the JOB-UUID of the BGAPI command and the UNIQUE-ID, it's impossible to intercept all the events until that point (create, outgoing, ring, codec-exchange, etc).
This becomes a real problem when originating multiple calls in a short time. It's impossible to distinguish which event belongs to which origination request. Resorting to pull that info from the DB or through SHOW CHANNELS might still cost missing few events.
Anyone has any ideas on how to track an ORIGINATE call setup flow?
Here's an extract from the log (just took the relevant parts): bgapi originate sofia/default/1001 &park
Reply-Text: +OK Job-UUID: <UUID-A>
Channel-State: CS_NEW Unique-ID: <UUID-B> Event-Name: CHANNEL_CREATE
Channel-State: CS_INIT Unique-ID: <UUID-B> Event-Name: CHANNEL_OUTGOING
Channel-State: CS_INIT Unique-ID: <UUID-B> Event-Name: CHANNEL_ORIGINATE
Channel-State: CS_INIT Unique-ID: <UUID-B> Event-Name: CHANNEL_STATE
Channel-State: CS_RING Unique-ID: <UUID-B> Event-Name: PRESENCE_IN
Channel-State: CS_RING Unique-ID: <UUID-B> Event-Name: CHANNEL_STATE
Channel-State: CS_HOLD Unique-ID: <UUID-B> Event-Name: PRESENCE_IN
Channel-State: CS_HOLD Unique-ID: <UUID-B> Event-Name: CHANNEL_STATE
Channel-State: CS_HOLD Unique-ID: <UUID-B> Event-Name: CODEC
Channel-State: CS_HOLD Unique-ID: <UUID-B> Event-Name: CODEC
Channel-State: CS_HOLD Unique-ID: <UUID-B> Event-Name: CHANNEL_ANSWER
API-Command: originate Event-Name: API
Job-UUID: <UUID-A> Job-Command: originate Event-Name: BACKGROUND_JOB +OK <UUID-B>
Channel-State: CS_EXECUTE Unique-ID: <UUID-B> Event-Name: PRESENCE_IN
Channel-State: CS_EXECUTE Unique-ID: <UUID-B> Event-Name: CHANNEL_STATE
Thanks, UV
No virus found in this outgoing message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.12 - Release Date: 10- Apr-08 12:00 AM
_______________________________________________ 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 No virus found in this incoming message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.12 - Release Date: 10-Apr-08 12:00 AM No virus found in this outgoing message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.12 - Release Date: 10-Apr-08 12:00 AM