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

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-26646:
--------------------------------------------

We appreciate the difficulties you are facing, however this does not appear to be a bug report and your request or comments would be better served in a different forum.

The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors.

Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker.

Thanks!

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

I'm not seeing a problem here and this sounds more like a support issue best handled elsewhere.

* Before a channel is bridged the linkedid and uniqueid of a channel are the same.
* The linkedid is the uniqueid of the oldest channel a channel has been bridged with.  For normal calls this is usually the calling channel.
* The accountcode is a string that you set for your own tracking purposes.

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