| Summary: | ASTERISK-16537: No CDR with originate from manager and then an redirect to a dial from manager | ||||
| Reporter: | arjan kroon (arjankroon) | Labels: | |||
| Date Opened: | 2010-08-10 07:36:13 | Date Closed: | 2015-02-26 09:23:43.000-0600 | ||
| Priority: | Major | Regression? | No | ||
| Status: | Closed/Complete | Components: | CDR/General | ||
| Versions: | Frequency of Occurrence | ||||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | The ami manager call out with an originate through dadhi to a local number (A). If this call is answered, then the ami manager redirect this call to a dial command. This dial command calls through dadhi to another local number (B). Number B answers this call and number A en B are connected. If number B and number A hangs up, there is will be no CDR be written If the dial command is commented out, (so there is no dial to number B), a CDR will be written. I think this bug is referring to issue https://issues.asterisk.org/view.php?id=17592&nbn=16 The path in this issue is installed on our servers. ****** STEPS TO REPRODUCE ****** - AMI manager does a originate to a local number (number A) is this call is answered and placed in a dialplan. - AMI manager does a redirect for number A to different dialplan, which contains a Dial to another local number (number B). Command: exten => s,n,Dial(DAHDI/g1/0031655871460,30,tgR) - Number B answered this call. - Number B and then Number A hangs up. ****** ADDITIONAL INFORMATION ****** Logging of the Dial command which was used to call number B. (after the redirect) Executing [s@setup_agent:229] Dial("DAHDI/1-1", "DAHDI/g1/0031655871460,30,tgR") in new stack -- Requested transfer capability: 0x00 - SPEECH -- Called g1/0031655871460 -- DAHDI/2-1 is proceeding passing it to DAHDI/1-1 -- DAHDI/2-1 is ringing -- DAHDI/2-1 answered DAHDI/1-1 | ||||
| Comments: | By: arjan kroon (arjankroon) 2010-08-18 01:08:18 Hi, Is there anybody which could tell me more, if this issue is a bug or just a failure by the reporter? Best Regards, Arjan Kroon By: arjan kroon (arjankroon) 2010-09-13 03:25:16 Hi, I saw that this case was related to case ID: 0017592 This patch was added in asterisk version 1.6.2.10 We tried the same test case on asterisk version 1.6.2.11 and we still got no CDR. If we try only an originate (from the ami manager), the CDR will be written after the hangup. We expect that there will be a CDR for the local number A and a seperate CDR for the local number B If there any questions, don't hesitate to mail me. Best regards, Arjan Kroon By: arjan kroon (arjankroon) 2010-09-21 01:22:28 Hi Asterisk, Could anybody give me a note, if there is solution or work-around for the problem mentioned in this case? Best Regard, Arjan Kroon By: wiseguy (wiseguy) 2010-10-20 10:20:52 Hello, I tried with newest version 1.6.2.13, still same get the problem. I am using redirect function and no cdr produced after the call is redirected to SIP peer. By: Matt Jordan (mjordan) 2015-02-26 09:23:36.436-0600 This is technically a duplicate of ASTERISK-16330. | ||||