[asterisk-bugs] [JIRA] (ASTERISK-26646) CoreShowChannel seems to intermittently get the same Uniqueid Linkedid

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-26646:
-----------------------------------------

In the future it will help us out if you can attach debug via "More > Attach Files" (as .txt extension). All the debug in the comment fields results in a lot of scrolling and huge E-mail notifications.  Thanks in advance!

https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> CoreShowChannel seems to intermittently get the same Uniqueid Linkedid
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-26646
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26646
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface
>    Affects Versions: 13.10.0
>         Environment: Gentoo, Vanilla Asterisk
>            Reporter: Troy Bowman
>            Severity: Minor
>
> I seem to be intermittently getting the same Uniqueid and Linkedid for bridged channels from CoreShowChannels, for example:
> Event: CoreShowChannel
> Channel: SIP/yak-00020025
> ChannelState: 6
> ChannelStateDesc: Up
> CallerIDNum: 9257274345
> CallerIDName: Carlos Campos
> ConnectedLineNum: 0525
> ConnectedLineName: Tanner Bills
> Language: en
> AccountCode: 1481048062.131383
> Context: go_queueops
> Exten: s
> Priority: 12
> Uniqueid: 1481048062.206932
> Linkedid: 1481048062.206932
> Application: Queue
> ApplicationData: contractor,,,clients,,,,go_queue_accept,,
> Duration: 00:02:14
> BridgeId: e5443a38-fa3b-4060-870b-7cebd3a9767a
> I tried looking for a cause but I got lost in the rabbit hole as it seems to come from a deeply defined stasis channel cache of who knows what message.
> Sorry for not testing this on a later version, this is the version I'm running in production right now, and I can't really see any changes that may affect channel_state in later 13.13.



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