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

[Troy Bowman (JIRA)]

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

Troy Bowman commented on ASTERISK-26646:
----------------------------------------

Even if it is the oldest channel it has been bridged with, it is set to the same channel id before it has been bridged, and it retains that old same Linkedid afterwards.

New channel before bridge:

Event: CoreShowChannel
Channel: SIP/0592-0002038b
ChannelState: 4
ChannelStateDesc: Ring
CallerIDNum: 3852444646
CallerIDName: Theo Ceasar
ConnectedLineNum: 8653186652
ConnectedLineName: KNOXVILLE, TN
Language: en
AccountCode: 1481058889.208270
Context: macro-dialout
Exten: s
Priority: 9
Uniqueid: 1481058889.208270
Linkedid: 1481058889.208270
Application: Dial
ApplicationData: SIP/18653186652 at yak
Duration: 00:00:02
BridgeId: 

Same channel after bridge:

Event: CoreShowChannel
Channel: SIP/0592-0002038b
ChannelState: 6
ChannelStateDesc: Up
CallerIDNum: 3852444646
CallerIDName: Theo Ceasar
ConnectedLineNum: 8653186652
ConnectedLineName: KNOXVILLE, TN
Language: en
AccountCode: 1481058889.208270
Context: macro-dialout
Exten: s
Priority: 9
Uniqueid: 1481058889.208270
Linkedid: 1481058889.208270
Application: Dial
ApplicationData: SIP/18653186652 at yak
Duration: 00:00:56
BridgeId: 58d59c26-901c-4d59-bc1d-3eb2c559571d


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