[asterisk-bugs] [JIRA] (ASTERISK-26494) Inconsistent case for some field names in CEL data, collected via ManagerInterface

[Rusty Newton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233233#comment-233233 ] 

Rusty Newton commented on ASTERISK-26494:
-----------------------------------------

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).


> Inconsistent case for some field names in CEL data, collected via ManagerInterface
> ----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26494
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26494
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface
>    Affects Versions: 11.6.0, 13.11.2, 14.0.2
>         Environment: Centos 6.4 x64
>            Reporter: Alex
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)