VoIP Mailing List Archives

[simon at airg.com]

Hi there,

I know there's a "feature" that allows us to create a uuid and then use
that uuid to do an originate (api create_uuid). Is there any badness if
I don't do the "create_uuid" and just do the originate using my own
uuid.

I experimented and made the following originate call:

api originate
{origination_caller_id_number=16041234567,originate_timeout=60,originati
on_uuid=abcdefg}sofia/gateway/icall/16041234567 &park

...and this works, but just want to make sure if there's any badness of
doing so...that is, if I can guarantee that the origination_uuid I will
be passing in *WILL* be unique.



_______________________________________________
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

[brian at freeswitch.org]

I would use real UUID's not something as simple as abcdefg cuz FS will hang up on you if you collide.

/b

On May 7, 2009, at 3:47 PM, Simon Tang wrote:

[andrew at hijacked.us]

On Thu, May 07, 2009 at 01:47:26PM -0700, Simon Tang wrote:

[brian at freeswitch.org]

Yah kinda gets messy when trying to track down something if the same uuid gets used over and over in a short period of time.

/b

On May 7, 2009, at 4:02 PM, Andrew Thompson wrote:

[simon at airg.com]

Abcdefg was an example...I was suggesting that I can guarantee uniqueness forever and if I collide, it’s my fault and I take the consequences

Anyway, I will use create_uuid...I was exploring this option before because I thought I couldn't use create_uuid because I made some wrong assumptions.

I was assuming that I wouldn't get the response for the create_uuid because I would have applied a Unique-ID filter for the existing session prior to calling create_uuid, which in turn, would filter out the uuid response. But this assumption was incorrect because the UUID *is* the response to the "api create_uuid" call and won't be filtered and is only visible on the socket it was called on (and not others).

From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Brian West
Sent: May 7, 2009 1:51 PM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Originate - using own uuid



I would use real UUID's not something as simple as abcdefg cuz FS will hang up on you if you collide.


/b


On May 7, 2009, at 3:47 PM, Simon Tang wrote:




Hi there,

I know there's a "feature" that allows us to create a uuid and then use
that uuid to do an originate (api create_uuid). Is there any badness if
I don't do the "create_uuid" and just do the originate using my own
uuid.

I experimented and made the following originate call:

api originate
{origination_caller_id_number=16041234567,originate_timeout=60,originati
on_uuid=abcdefg}sofia/gateway/icall/16041234567 &park

...and this works, but just want to make sure if there's any badness of
doing so...that is, if I can guarantee that the origination_uuid I will
be passing in *WILL* be unique.


Brian West

brian@freeswitch.org (brian@freeswitch.org)




-- Meet us at ClueCon! http://www.cluecon.com

[brian at freeswitch.org]

How about something like this :

{origination_caller_id_number=16041234567,originate_timeout=60,origination_uuid=${create_uuid()}}sofia/gateway/icall/16041234567 &park


You can call an api with ${apiname()} and the results will go into its place.


/b

On May 7, 2009, at 4:18 PM, Simon Tang wrote:

[anthony.minessale at g...]

it's up to you what you do,

break it you buy it =D


On Thu, May 7, 2009 at 4:26 PM, Brian West <brian@freeswitch.org (brian@freeswitch.org)> wrote: