[asterisk-bugs] [JIRA] (ASTERISK-26643) Extra new line in Device field of DeviceStateChange AMI Event after restart of Asterisk

[George Joseph (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Joseph updated ASTERISK-26643:
-------------------------------------

    Target Release Version/s: 15.0.0

> Extra new line in Device field of DeviceStateChange AMI Event after restart of Asterisk
> ---------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26643
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26643
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Functions/func_devstate
>    Affects Versions: 14.2.0
>         Environment: OpenSUSE 13.2 32bit
>            Reporter: Roman Bedros
>            Severity: Minor
>      Target Release: 13.15.0, 14.4.0, 15.0.0
>
>         Attachments: ami_devstate.diff
>
>
> h4. Symptoms
> DeviceStateChange AMI Event contains an extra new-line character in the Device field after restart of the Asterisk.
> h4. Steps to reproduce:
> # Add a custom device state from CLI:
> {{devstate change Custom:test INUSE}}
> # Restart Asterisk
> {{service asterisk restart}}
> # Connect to Asterisk via AMI
> {{telnet XX.XX.XX.XX 5038}}
> # Login
> {{Action:Login}}
> {{Username:xxxxx}}
> {{Secret:xxxxx}}
> # Request device states
> {{Action:DeviceStateList}}
> Asterisk replies by the following messages:
> {quote}
> Response: Success
> EventList: start
> Message: Device State Changes will follow
> Event: DeviceStateChange
> Device: Custom:test
> State: INUSE
> Event: DeviceStateListComplete
> EventList: Complete
> ListItems: 1
> {quote}
> There is an extra empty line in DeviceStateChange event message.
> If step 2 is skipped, Asterisk responds without an extra new line.
> h4. Patch
> A patch (attached in a comment) which fixes this issue was created, but I'm not sure that it doesn't break anything else.



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