[asterisk-bugs] [JIRA] (ASTERISK-22239) [patch] Missing extra line break running AMI action SIPPeers

Michael L. Young (JIRA) noreply at issues.asterisk.org
Thu Aug 1 13:09:08 CDT 2013


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

Michael L. Young updated ASTERISK-22239:
----------------------------------------

    Summary: [patch] Missing extra line break running AMI action SIPPeers  (was: SIPPeers AMI action result events merged)
    
> [patch] Missing extra line break running AMI action SIPPeers
> ------------------------------------------------------------
>
>                 Key: ASTERISK-22239
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22239
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.23.0
>            Reporter: Jacek Konieczny
>         Attachments: asterisk-ami_sippeers_separator.patch
>
>
> Results of AMI 'Action: SIPPeers' are returned without blank lines between events. This break parsers which expect the empty lines.
> The '\r\n\r\n' sequences used to be there in older 1.8.x releasese, especially in 1.8.21.0.
> The regression seems to be introduced in r387133.
> Example:
> {noformat}
> Action: SIPPeers
> Response: Success
> EventList: start
> Message: Peer status list will follow
> Event: PeerEntry
> Channeltype: SIP
> ObjectName: dev1n1
> ChanObjectType: peer
> IPaddress: 10.28.45.27
> IPport: 5060
> Dynamic: no
> Forcerport: yes
> VideoSupport: no
> TextSupport: no
> ACL: no
> Status: UNREACHABLE
> RealtimeDevice: no
> Event: PeerEntry
> Channeltype: SIP
> ObjectName: dev1n2
> ChanObjectType: peer
> IPaddress: 10.28.45.72
> IPport: 5060
> Dynamic: no
> Forcerport: yes
> VideoSupport: no
> TextSupport: no
> ACL: no
> Status: Unmonitored
> RealtimeDevice: no
> Event: PeerlistComplete
> EventList: Complete
> ListItems: 2
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list