Summary: | ASTERISK-26495: Lost CDR Uniqueid | ||
Reporter: | Ivoxs Support (ivoxs) | Labels: | |
Date Opened: | 2016-10-21 16:46:14 | Date Closed: | 2020-01-14 11:21:04.000-0600 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | CDR/General |
Versions: | 11.22.0 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Freepbx last version Avaya CS1000S AsteriskPBX <(T1)> Avaya Nortel | Attachments: | |
Description: | hi, have the next issue i have a macro app this app is execute when the user hit *1 for get information about the call.
when the user execute the *1 i get a UNIQUEID but when the user hangup the call in the cdr i get a diferent UNIQUEID how i can have the same uniqueid ? For example if user from asterisk call a user in the avaya and the user from asterisk hit *1 i get the same uniqueid in the macro app and the cdr but when user from avaya call a user in the asterisk and the avaya user hit *1 the uniqueid in the macro is not the same of the cdr. Macro [macro-test] exten => s,n,Set(channel=${CDR(channel)}) exten => s,n,Set(dstchannel=${CDR(dstchannel)}) exten => s,n,Set(account=${CDR(accountcode)}) exten => s,n,Set(sname=${SYSTEMNAME}) exten => s,n,Set(getuid=${UNIQUEID}) | ||
Comments: | By: Asterisk Team (asteriskteam) 2016-10-21 16:46:14.807-0500 We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. If this issue is actually a bug please use the Bug issue type instead. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Asterisk Team (asteriskteam) 2016-10-21 16:46:16.058-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. |