2009/7/17 Alan Lord (News) <alansli...@gmail.com> > On 17/07/09 17:20, Danny Nicholas wrote: > > Not that this will really help, but in my CDR, I get this find of format > > Xxx incoming_number s context caller_id incoming_tech/line > > target_tech/line function command time1 time2 time3. It seems > that > > you could look to the target_tech/line for the information you need. > > Yeah I know what you mean. That is the "destination channel" which does > contain something like SIP/101-9u1exdo8, even though the "Destination" > contains just "s". > > I am working on some CRM integration code and really don't want to have > to parse this stuff if I can help it. Some of our extensions will/could > be on Zap/ or IAX/context/blah-hsdjgdjf-. > > It get's really hard to to try and deal with all the possibilities > reliably. > > IMHO, the "Destination" field *should* contain simply the number of the > destination ext. of the call; as it rightly does when digits are > actually dialled by the caller. Why it doesn't when the call is > generated by the dialplan IVR is just plain inconsistent. > > Alan >
Hi Alan, did you find the way to solve this issue? regards, Maxi
_______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users