<div><br></div>Oh, I see. Is there a reliable way in which people can find an audio file relating to a call? If not by uniqueID, in some other way? Is there a way to inject a custom value into the monitor recording that relates it to the call? It would be just as good for me to place an external record id (of my own) into the recording filename. I just need to be able to find the recording tied to the call. <div>
<br></div><div>Thanks, </div><div><br></div><div>Matthew</div><div><br><div><br></div><div><br><br><div class="gmail_quote">On Tue, Jun 15, 2010 at 7:55 AM, Dave Woolley <span dir="ltr"><<a href="mailto:david.woolley@bts.co.uk">david.woolley@bts.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">Steve Totaro wrote:<br>
<br>
> How can I relate the Asterisk call initiating UniqueID to<br>
</div>> the monitor audio recording filename - with certainty? It to<br>
> appears the monitor files are a collection of values, one part to<br>
> of which seems to be a one-off of the Asterisk call originating to<br>
> UniqueID. Do these relate the same every time. I cannot tell if to<br>
> the monitor file will contain the call initiating UniqueID + 1 to<br>
> every time or if this is an inconsistent process. Please let me to<br>
<div class="im">> know. Also, please let me know if clarification is needed.<br>
<br>
</div>You would need to look up the bridged peer at run time. The unique-ID<br>
is composed of the time, to the second, and a sequential integer. The<br>
time part might differ if the incoming and outgoing channels were<br>
created across a second boundary, and the sequence number might differ<br>
from being one greater if another channel creation intervened. You<br>
really need to treat this value as opaque.<br>
<br>
I'm not sure if this is more of a support question than a developer one.<br>
<br>
As this is a public list, the confidentiality part of the following<br>
doesn't apply.<br>
<font color="#888888">--<br>
David Woolley<br>
BTS Holdings Plc<br>
Tel: +44 (0)20 8401 9000 Fax: +44 (0)20 8401 9100<br>
<a href="http://www.bts.co.uk" target="_blank">http://www.bts.co.uk</a><br>
<br>
This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of the company. If you are not the intended recipient of this email, you must take no action based upon it, nor must you copy or show it to anyone. Please contact the sender if you believe you have received this email in error. In accordance with English Law, email communications may be monitored. All reasonable precautions have been taken to ensure that no viruses are present in this email; however, the company cannot accept responsibility for loss or damage arising from the use of this email. We recommend that you subject this email to your own virus checking procedures. BTS Holdings PLC is registered in England 1517630, VAT No 523 5092 66. Registered office, BTS House, Manor Road, Wallington, SM6 0DD<br>
</font><div><div></div><div class="h5">--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</div></div></blockquote></div><br></div></div>