[asterisk-dev] Relating Monitor Recording to a Call Unique ID

Steve Totaro stotaro at asteriskhelpdesk.com
Tue Jun 15 20:18:37 CDT 2010


On Tue, Jun 15, 2010 at 7:55 AM, Dave Woolley <david.woolley at bts.co.uk>wrote:

> Steve Totaro wrote:
>
> > How can I relate the Asterisk call initiating UniqueID to
> > the monitor audio recording filename - with certainty? It to
> > appears the monitor files are a collection of values, one part to
> > of which seems to be a one-off of the Asterisk call originating to
> > UniqueID. Do these relate the same every time. I cannot tell if to
> > the monitor file will contain the call initiating UniqueID + 1 to
> > every time or if this is an inconsistent process. Please let me to
> > know. Also, please let me know if clarification is needed.
>
> You would need to look up the bridged peer at run time.  The unique-ID
> is composed of the time, to the second, and a sequential integer.  The
> time part might differ if the incoming and outgoing channels were
> created across a second boundary, and the sequence number might differ
> from being one greater if another channel creation intervened.  You
> really need to treat this value as opaque.
>
> I'm not sure if this is more of a support question than a developer one.
>
> As this is a public list, the confidentiality part of the following
> doesn't apply.
> --
> David Woolley
> BTS Holdings Plc
> Tel: +44 (0)20 8401 9000 Fax: +44 (0)20 8401 9100
> http://www.bts.co.uk


If you are replying to my post, II am not sure what you are talking about.
 I had someone modify the OrecX code to put all the output files into a
single folder and use the sipcallid as the GUID.

I also stuffed callerID with a sequential number so that we could reconcile
with/againts out sourced call centers but you could use channel variables
that are rarely used, like RDNIS.

Thanks,
Steve Totaro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20100615/58e0469f/attachment.htm 


More information about the asterisk-dev mailing list