[Home]

Summary:ASTERISK-24223: Gibberish Call-ID on Local channel on origination
Reporter:Mark Michelson (mmichelson)Labels:
Date Opened:2014-08-12 16:54:04Date Closed:2014-11-15 12:01:53.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Core/Logging
Versions:12.4.0 13.0.0-beta1 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Attachments:
Description:Steps to reproduce:

# Set up a phone of some sort. In my case, I set up a PJSIP endpoint called "205"
# Create the following in your dialplan:
{noformat}
[default]
exten => 205,1,Dial(PJSIP/205)
{noformat}
# Perform the following CLI command:
{noformat}
channel originate Local/205@default application Echo
{noformat}
# Answer the ringing phone
# Now issue a {{core show channel}} command to view the ;1 half of the local channel. Here is what happened for me:
{noformat}
*CLI> core show channel Local/205@default-00000000;1
-- General --
          Name: Local/205@default-00000000;1
          Type: Local
      UniqueID: 1407872772.0
      LinkedID: 1407872772.0
     Caller ID: (N/A)
Caller ID Name: (N/A)
Connected Line ID: (N/A)
Connected Line ID Name: (N/A)
Eff. Connected Line ID: (N/A)
Eff. Connected Line ID Name: (N/A)
   DNID Digits: (N/A)
      Language: en
         State: Up (6)
 NativeFormats: (slin)
   WriteFormat: slin
    ReadFormat: slin
WriteTranscode: No
 ReadTranscode: No
Time to Hangup: 0
  Elapsed Time: 0h0m33s
     Bridge ID: (Not bridged)
--   PBX   --
       Context: default
     Extension: 205
      Priority: 1
    Call Group: 0
  Pickup Group: 0
   Application: Echo
          Data: (Empty)
Call Identifer: Wt��� 0ֿ�/ֿ�'� o�����
     Variables:
 CDR Variables:
level 1: calledsubaddr=
level 1: callingsubaddr=
level 1: dnid=
level 1: clid=""
level 1: dst=205
level 1: dcontext=def
level 1: channel=Loc
level 1: lastapp=Ech
level 1: start=140
level 1: answer=140
level 1: end=0.0
level 1: duration=33
level 1: billsec=31
level 1: disposition=8
level 1: amaflags=3
level 1: uniqueid=140
level 1: linkedid=140
level 1: sequence=0
{noformat}

Notice the messed Call Identifier? That likely is not the sign of good things happening on that Local channel, though aside from the gibberish on the CLI, I haven't seen any other ill effects.
Comments: