<br><br><div class="gmail_quote">2009/7/17 Alan Lord (News) <span dir="ltr"><<a href="mailto:alanslists@gmail.com">alanslists@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 17/07/09 17:20, Danny Nicholas wrote:<br>
> Not that this will really help, but in my CDR, I get this find of format<br>
> Xxx incoming_number s context caller_id incoming_tech/line<br>
> target_tech/line function command time1 time2 time3. It seems that<br>
> you could look to the target_tech/line for the information you need.<br>
<br>
</div>Yeah I know what you mean. That is the "destination channel" which does<br>
contain something like SIP/101-9u1exdo8, even though the "Destination"<br>
contains just "s".<br>
<br>
I am working on some CRM integration code and really don't want to have<br>
to parse this stuff if I can help it. Some of our extensions will/could<br>
be on Zap/ or IAX/context/blah-hsdjgdjf-.<br>
<br>
It get's really hard to to try and deal with all the possibilities reliably.<br>
<br>
IMHO, the "Destination" field *should* contain simply the number of the<br>
destination ext. of the call; as it rightly does when digits are<br>
actually dialled by the caller. Why it doesn't when the call is<br>
generated by the dialplan IVR is just plain inconsistent.<br>
<font color="#888888"><br>
Alan<br>
</font><div><div></div><div class="h5"></div></div></blockquote><div> </div></div>Hi Alan,<br><br>did you find the way to solve this issue?<br><br>regards,<br>Maxi<br><br><br>