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

Roman Bedros (JIRA) noreply at issues.asterisk.org
Tue Dec 6 06:25:09 CST 2016


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

Roman Bedros updated ASTERISK-26643:
------------------------------------

    Description: 
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 which fixes this issue was created (it will be attached if possible), but I'm not sure that it doesn't break anything else.

  was:
h4. Description
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 which fixes this issue was created (it will be attached if possible), but I'm not sure that it doesn't break anything else.


> 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
>
> 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 which fixes this issue was created (it will be attached if possible), but I'm not sure that it doesn't break anything else.



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



More information about the asterisk-bugs mailing list