Summary: | ASTERISK-26494: Inconsistent case for some field names in CEL data, collected via ManagerInterface | ||
Reporter: | Alex (neiroman2k) | Labels: | |
Date Opened: | 2016-10-21 13:42:06 | Date Closed: | |
Priority: | Major | Regression? | |
Status: | Open/New | Components: | Core/ManagerInterface |
Versions: | 11.6.0 13.11.2 14.0.2 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Centos 6.4 x64 | Attachments: | |
Description: | I collect and parse CEL events from Asterisk certified/11.6-cert13
Unique call identifier field is named as "Uniqueid" but in some events like a "CEL,Dial,CoreShowChannel,MusicOnHold,Voicemail" is named as "UniqueID" Casesensitive search in source files for "UniqueID: %s" found calls to ast_manager_event only in "CEL,Dial,CoreShowChannel,MusicOnHold,Voicemail" modules and few more. My events {noformat} Event: 'Newchannel', Privilege: 'call,all', Channel: 'SIP/user5-00000507', ChannelState: '0', ChannelStateDesc: 'Down', CallerIDNum: '105', CallerIDName: 'Alex', AccountCode: 'office', Exten: '9999', Context: 'context', Uniqueid: 'node9-1477074987.1911' Event: 'CEL', Privilege: 'call,all', EventName: 'CHAN_START', AccountCode: 'office', CallerIDnum: '105', CallerIDname: 'Alex', CallerIDani: '', CallerIDrdnis: '', CallerIDdnid: '', Exten: '633445', Context: 'context', Channel: 'SIP/user5-00000507', Application: '', AppData: '', EventTime: '2016-10-21 21:36:27', AMAFlags: 'DOCUMENTATION', UniqueID: 'node9-1477074987.1911', LinkedID: 'node9-1477074987.1911', Userfield: '', Peer: '', PeerAccount: 'office', Extra: '' {noformat} Edit by Rusty Newton - I also see inconsistency with CallerIDNum/CallerIDnum and CallerIDName/CallerIDname. So, not just an issue with Uniqueid/UniqueID. | ||
Comments: | By: Asterisk Team (asteriskteam) 2016-10-21 13:42:10.399-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]. By: Rusty Newton (rnewton) 2016-10-21 14:33:06.981-0500 Changing the summary as I also see inconsistency with CallerIDNum/CallerIDnum and CallerIDName/CallerIDname. So, not just an issue with Uniqueid/UniqueID. Thanks for the report! By: Rusty Newton (rnewton) 2016-10-21 14:47:06.447-0500 Turns out the keys for manager actions and events are case insensitive: https://wiki.asterisk.org/wiki/display/AST/AMI+v2+Specification#AMIv2Specification-MessageLayout However, I can see this still being annoying. Do you want to submit a patch and push it onto Gerrit? By: Alex (neiroman2k) 2016-10-21 16:06:57.738-0500 Asterisk 12 but im on Asterisk 11 cert By: Richard Mudgett (rmudgett) 2016-10-21 17:17:34.236-0500 That specification formalized much of what was already happening with the basic syntax already. By: Alex (neiroman2k) 2016-11-01 04:49:41.931-0500 In all events CDR(accountcode) named as 'AccountCode' but only in 'Status' event field key is 'Account' event: 'Status', privilege: 'Call' channel: 'SIP/trunkIn-000abbf5' calleridnum: '125' calleridname: '<unknown>', connectedlinenum: '124' connectedlinename: 'BDD' account: 'office' By: Rusty Newton (rnewton) 2016-11-01 09:18:44.078-0500 11 cert is supported through support agreements with Digium. https://www.digium.com/products/asterisk/certified-asterisk The straight 11 branch no longer receives general bug fixes (only security issues). If you want you can submit a patch to a newer branch that is supported for bug fixes (13, 14). |