What is this PJSIP 6830e8e8-506c-4faa-9184-b14db7052433

General Help
1

i installed freePBX 17 and i see under Reports/Asterisk Info/ Channels

PJSIP 6830e8e8-506c-4faa-9184-b14db7052433

PJSIP
PJSIP1782×374 20.9 KB

what is this entry?

2

Usually, it should be an extension number. But it’s weird to get this kind of stuff like this.
Maybe a bug.
Anyway try to create a new PJSIP extension and check again here.

3

It’s formatted as a GUID, so it isn’t just gibberish, although it has no meaning, other than as a name.

I can’t think why FreePBX would need to use one in this context, but I suppose it is just possible that the database primary key is a GUID and it is being used because the defining entry is missing.

I think the first thing I’d do is to read out the full definition, using the Asterisk CLI, and/or looking at the generated .conf files.

My concern is that it could be that the system has been compromised and the attacker is hoping that a GUID will be interpreted as some internal functions, whereas a bogus extension number would be recognizable.

I haven’t looked at the FreePBX to find if it uses GUIDs in a way that could appear in this report.

4

For my part, there is only the extensions and no GUIDs. Weird.

5

this is a fresh install with no extensions or trunks

i could reproduce this by another fresh install ( no configs added, just fresh install)

6

After a fresh install, do you launch any updates?
like for example:
fwconsole ma updateall

For my part, after installing a FreePBX system, I’m updating the system and next all FreePBX modules through the console.
Next I reboot it.

7

yes i did first

apt update && apt upgrade -y

then

fwconsole ma updateall

8

Ok.
If you have the time to install FreePBX 16 and do the same thing, Next, compare the data in this page.
If you’ve got the same result or not.
If the issue is only on FreePBX 17, then I think it’s a bug.
If the issue is present on both systems, the it could be a bug from 16 and not fixed, so can be present into 17 as well.
What happens if you create an extension? This GUID is still present or not?

9

if i import my config from my freepbx16 this PJSIP thing is still there

i have not seen this kind of issue freepbx16 (at least i can´t remember)
but i will run a restore from my freepbx16 and report here in a couple of minutes

10

Hmm so you mean the issue appearing only after restoring the data from 16?
It’s no longer a fresh install so!
For my part a fresh install doesn’t include any data restorations

Maybe an issue with the module Backup and Restore or Core so!

11

NO!

i wrote i did a fresh install and saw this under Reports/Asterisk Info/ Channels
then i did another fresh install no configs imported or anything touched just updates and i see the same thing

then i did import my config to one of the two installs and the PJSIP thing is still there

12

Ha ok, got it.
In this case, it looks like a bug.
Try to create a ticket on Github.
If the issue is not present on 16 and present on 17. No way, it’s a bug.

13

i did restore my freepbx 16 VM an there is nothing like this under Reports/Asterisk Info/ Channels
just my extensions

freepbx16
freepbx161781×659 30.7 KB

14

Yes, like me. Nothing bad.

15

Let me check on my VM too. I’ve got a 17.

16

now i am running a restore of a untouched freepbx17 and then i post the screenshot from there in two minutes

17

here a fresh installed freepbx17

freepbx17
freepbx171772×406 23.2 KB

and here is my running freepbx17 with the imported config from freepbx16

freepbx17 configured
freepbx17 configured1793×380 20.9 KB

EDIT:
these two screenshots are from two separate machines

i opened a new issue on github LINK

1 Like
18

My 17 install is messed up and it’s too old.
I installed it from the first script on 17.
But, you are rigth to create a ticket on Github.

1 Like
19

I think it’s a mystery of ARI (asterisk).

Here is the ARI output:

~# curl -u ariuser:aripass http://localhost:8088/ari/endpoints | jq

[
  {
    "technology": "PJSIP",
    "resource": "dpma_endpoint",
    "state": "offline",
    "channel_ids": []
  },
  {
    "technology": "PJSIP",
    "resource": "1000",
    "state": "offline",
    "channel_ids": []
  },
  {
    "technology": "PJSIP",
    "resource": "01ae1b76-b309-43e1-b59b-85b328b9f633",
    "state": "offline",
    "channel_ids": []
  }
]

And here is what Asterisk shows for endpoints:

~# asterisk -rx "pjsip show endpoints"

 Endpoint:  <Endpoint/CID.....................................>  <State.....>  <Channels.>
    I/OAuth:  <AuthId/UserName...........................................................>
        Aor:  <Aor............................................>  <MaxContact>
      Contact:  <Aor/ContactUri..........................> <Hash....> <Status> <RTT(ms)..>
  Transport:  <TransportId........>  <Type>  <cos>  <tos>  <BindAddress..................>
   Identify:  <Identify/Endpoint.........................................................>
        Match:  <criteria.........................>
    Channel:  <ChannelId......................................>  <State.....>  <Time.....>
        Exten: <DialedExten...........>  CLCID: <ConnectedLineCID.......>
==========================================================================================

 Endpoint:  1000/1000                                            Unavailable   0 of inf
     InAuth:  1000-auth/1000
        Aor:  1000                                               1

 Endpoint:  dpma_endpoint                                        Unavailable   0 of inf


Objects found: 2

Why does ARI see more endpoints than Asterisk CLI? That is a mystery.

edit: did some additional testing and I get the same results with Asterisk 20 and 21, FreePBX 17.

1 Like
20

Yeah, strange…

You could add this to the github issue if you want… LINK