On Origination you may want to set the variable "origination-uuid" to an uuid you previously created by the API command "create-uuid". This way you don't have to worry about which uuid is which. PS: the variable name and the API command are quoted by memory, they probably have slightly different names, check in the wiki. On 5/13/11, Gabriel Gunderson <gabe@gundy.org> wrote:
On Fri, May 13, 2011 at 3:07 PM, Mark Sobkow <m.sobkow@marketelsystems.com> wrote:
However, I'm seeing some unrecognized UUIDs after bridging the call (i.e. that weren't returned by the place call code.)
Are there any events which might indicate that a UUID is being changed by the system, and that I should be watching for a new UUID instead?
The UUID of the channel never changes. If you're using a UUID to originate a call, then you'll have that UUID to work with, but FS will still pick it's own UUID for the channel --and it will not change.
Calls get UUIDs, conferences get UUIDs, channels get UUIDs, so it's just a matter of finding the right one and not worrying too much about the other UUIDs that might show up. Hope that helps.
Best, Gabe
_______________________________________________ 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
-- Sent from my mobile device Sincerely, Giovanni Maruzzelli Cell : +39-347-2665618