[Freeswitch-users] Originate - using own uuid
simon at airg.com
Thu May 7 14:18:07 PDT 2009
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
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
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 at lists.freeswitch.org
[mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of
Sent: May 7, 2009 1:51 PM
To: freeswitch-users at 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.
On May 7, 2009, at 3:47 PM, Simon Tang wrote:
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
I experimented and made the following originate call:
...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 at freeswitch.org
-- Meet us at ClueCon! http://www.cluecon.com <http://www.cluecon.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the FreeSWITCH-users