<div class="gmail_quote">On Mon, May 18, 2009 at 3:39 PM, Russell Bryant <span dir="ltr"><<a href="mailto:russell@digium.com">russell@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The unique ID field on a channel is what uniquely identifies it from<br>
others that had the same name. The unique ID field is a monotonically<br>
increasing integer, a timestamp, and optionally, a system name.<br>
<font color="#888888"><br>
</font></blockquote><div><br>I did recently notice that the unique ID isn't copied during a channel masq and had been wondering if that was intentional. For what I was doing, it would have been much more convenient if it did copy. The way it is now, the same channel name (e.g. SIP/foo-xxxx), representing the same actual call leg, will change uniqueid's (because it isn't copied into the channel struct on masq) during the lifetime of the call if certain events happen.<br>
<br>Is that on purpose or an oversite? If it's intentional, you might want to add that quirk to the documentation.<br><br>--Tim<br></div></div>