[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=234085#comment-234085 ] 

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

Seems to not be the manager, since "core show channel" in the console also gives duplicated IDs:

Manger: 

Event: CoreShowChannel
Channel: SIP/0313-000200d0
ChannelState: 6
ChannelStateDesc: Up
CallerIDNum: 8016181494
CallerIDName: Patty Cazer
ConnectedLineNum: 7046506171
ConnectedLineName: Esther Schilling
Language: en
AccountCode: 1481050885.207192
Context: macro-dialout
Exten: s
Priority: 9
Uniqueid: 1481050885.207192
Linkedid: 1481050885.207192
Application: Dial
ApplicationData: SIP/17046506171 at yak
Duration: 00:17:09
BridgeId: 82de99bc-1569-4b8c-8bcd-b6fec02a707c

Console:

voip*CLI> core show channel SIP/0313-000200d0
 -- General --
           Name: SIP/0313-000200d0
           Type: SIP
       UniqueID: 1481050885.207192
       LinkedID: 1481050885.207192
      Caller ID: 8016181494
 Caller ID Name: Patty Cazer
Connected Line ID: 7046506171
Connected Line ID Name: Esther Schilling
Eff. Connected Line ID: 7046506171
Eff. Connected Line ID Name: Esther Schilling
    DNID Digits: 7046506171
       Language: en
          State: Up (6)
  NativeFormats: (ulaw)
    WriteFormat: ulaw
     ReadFormat: ulaw
 WriteTranscode: No 
  ReadTranscode: No 
 Time to Hangup: 0
   Elapsed Time: 0h17m57s
      Bridge ID: 82de99bc-1569-4b8c-8bcd-b6fec02a707c
 --   PBX   --
        Context: macro-dialout
      Extension: s
       Priority: 9
     Call Group: 0
   Pickup Group: 0
    Application: Dial
           Data: SIP/17046506171 at yak
 Call Identifer: [C-00013dca]
      Variables:
BRIDGEPVTCALLID=68bfd8545edb926843d685b04324137e at 192.168.252.2:5060
BRIDGEPEER=SIP/yak-000200d1
DIALEDPEERNUMBER=17046506171 at yak
DIALEDPEERNAME=SIP/yak-000200d1
DIALSTATUS=ANSWER
DIALEDTIME=
ANSWEREDTIME=
MACRO_DEPTH=1
SIP_CODEC_OUTBOUND=ulaw
SIP_CODEC_INBOUND=ulaw
MACRO_PRIORITY=2
MACRO_CONTEXT=authorized-outgoing
MACRO_EXTEN=7046506171
ARG1=17046506171
AGISTATUS=SUCCESS
RCID=7046506171
RNAM=Esther Schilling
NEW_CID=8016181494
ORIG_SRC=0313
SIPADDHEADER03=X-dest:17046506171
SIPADDHEADER02=X-from:0313
SIPADDHEADER01=X-accountcode:1481050885.207192
SIPCALLID=160b93cf-f0fc27fc-c6690fa5 at 192.168.252.221
SIPDOMAIN=sip.voip.te
SIPURI=sip:0313 at 192.168.252.221
  CDR Variables:
level 1: calledsubaddr=
level 1: callingsubaddr=
level 1: dnid=7046506171
level 1: clid="Patty Cazer" <8016181494>
level 1: src=8016181494
level 1: dst=s
level 1: dcontext=macro-dialout
level 1: channel=SIP/0313-000200d0
level 1: dstchannel=SIP/yak-000200d1
level 1: lastapp=Dial
level 1: lastdata=SIP/17046506171 at yak
level 1: start=1481050885.726460
level 1: answer=1481050897.195821
level 1: end=0.000000
level 1: duration=1076
level 1: billsec=1065
level 1: disposition=8
level 1: amaflags=3
level 1: accountcode=1481050885.207192
level 1: uniqueid=1481050885.207192
level 1: linkedid=1481050885.207192
level 1: sequence=136680


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