| Summary: | ASTERISK-27191: CDR: An extra character in the CDR "userfield" when it is populated with data from Sub called in Dial application | ||||
| Reporter: | Denis Pantsyrev (StuxForce) | Labels: | |||
| Date Opened: | 2017-08-09 06:05:19 | Date Closed: | |||
| Priority: | Minor | Regression? | |||
| Status: | Open/New | Components: | CDR/cdr_adaptive_odbc | ||
| Versions: | 13.17.0 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | CentOS Linux release 7.3.1611 (Core) 3.10.0-514.26.2.el7.x86_64 | Attachments: | ( 0) debug_example_1.txt ( 1) debug_example_2.txt | ||
| Description: | I have dialplan below. Phone 7777 call to 8888, 8888 answer.
At the moment of the answer the subAnswer is executed. In (example 1) I saw ";:subAnswer:moreData" where ";" at the beginning is an extra character In (example 2) I saw ":buh;:subAnswer:moreData" where ";" after the ":buh" is an extra character Debug files are attached below {code:title=sip.conf|borderStyle=solid} [7777] type=friend host=dynamic secret=7777 context=buh callerid="ExtUser" <7777> [8888] type=friend host=dynamic secret=8888 context=ato callerid="OneUser" <8888> {code} {code:title=extensions.conf (example 1)} [buh] exten => _XXXX,1,NoOP ; same => n,Set(CDR(userfield)=${CDR(userfield)}:buh) same => n,Dial(SIP/${EXTEN},20,tirU(subAnswer)) same => n,Hangup [subAnswer] exten => s,1,NoOP same => n,Set(CDR(userfield)=${CDR(userfield)}:subAnswer) same => n,Set(CDR(userfield)=${CDR(userfield)}:moreData) same => n,Return {code} {code:title=extensions.conf (example 2)} [buh] exten => _XXXX,1,NoOP same => n,Set(CDR(userfield)=${CDR(userfield)}:buh) same => n,Dial(SIP/${EXTEN},20,tirU(subAnswer)) same => n,Hangup [subAnswer] exten => s,1,NoOP same => n,Set(CDR(userfield)=${CDR(userfield)}:subAnswer) same => n,Set(CDR(userfield)=${CDR(userfield)}:moreData) same => n,Return {code} | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2017-08-09 06:05:20.588-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]. | ||||