if you make your own uuids you could set them in the originate string with
{origination_uuuid=foo}
where foo is a real uuid.
if you have no other way to make them you can ask FS for one with the create_uuid api call.
On 2/10/09 10:50 AM, Anthony Minessale wrote:> {job_uuid=1234}sofia/internal/foo@bar.com <mailto:foo@bar.com>
> if you pick your own job-uuid you can set it in the originate too
>
> send
>
> job-uuid: 1234
>
> in your bgapi event
>
> and
>
>Does the job-uuid get used as the actual call uuid? The problem is that
> in your dial string.
>
> *shrug* i am not sure exactly what the goal is so maybe it's not a
> useful suggestion...
the uuid for the call changes once it's answered (or hungup etc) and
that the mapping doesn't come till after occasionally.
I'm getting the job uuid no problem, but it's the replacement of the
job-uuid with a call-uuid that is the issue.
If this doesn't make too much sense I can post an example.
--
Cheers,
Matt Riddell
Director
_______________________________________________
http://www.venturevoip.com/news.php (Daily Asterisk News)
http://www.venturevoip.com/st.php (SmoothTorque Predictive Dialer)
http://www.venturevoip.com/c3.php (ConduIT3 PABX Systems)
_______________________________________________
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