Possible variables in altMessenging url

[ph4xo]

Hey guys,

in the documentation I can find the following example: "url": "https://meet.jit.si/myserver-{0}". Right now, it is not clear for me where this variable comes from and which others are usable here.

The background of my question is, we have local PBX server (3CX) that offers a individual quick meeting URL for each users. The URL looks like https://FQDN:5001/meet/USERNAME and we can change USERNAME to anything we like. Usually, this is the full name of the user, without any spaces. For example, the user John Doe has the quick meeting URL https://FQDN:5001/meet/johndoe.

I would like to use the Real Name of the current MeshCentral user here, without any spaces. This would be exactly the format we are using for the quick meeting.

Is this possible?

Cheers, Timo

[Ylianst]

Sure, I just made improvements to this feature. In v1.0.54 try this:

      "altmessenging": [
        {
          "name": "Meet",
          "url": "https://FQDN:5001/meet/{2}",
          "type": "user"
        }
      ]

There is a new "type" you can set to "user" or "device" to only show that button in the user panel or device panel. When you are in the user panel:

{0} = userid bob {1} = full user id user-domain-bob {2} = real name with no spaces RobertSmith {3} = real name with dashes Robert-Smith

Let me know if that helps.

[ph4xo]

Hi @Ylianst,

may I do not understand the new type correctly. We want to set the url on the device tab to https://FQDN:5001/meet/USERNAME, where USERNAME is the real name of the currently logged in supporter. So that when the supporter clicks on the button, the browser on the remote device opens https://FQDN:5001/meet/USERNAME, the personal meeting room of the supporter.

So do the new variables also work on the device tab?

Cheers, Timo

[Ylianst]

Oh, got it. I will put in another fix. If you don't put in the type, the chat button will also show up in the "My Users" tab here:

[Ylianst]

Ok, once MeshCentral v1.0.54 is out, try exactly this:

      "altmessenging": [
        {
          "name": "3CX Meeting",
          "url": "https://FQDN:5001/meet/{6}",
          "type": "device"
        }
      ]

It should do exactly what you want.

[ph4xo]

Hi @Ylianst

it works quite nice but found one litte problem that was not clear to me before and I'm really sorry about that. The URL opens correctly in the mentioned format https://FQDN:5001/meet/RobertSmith but the URL is case sensitive 😒. I never stumbled over this because we manually set the meeting URL to the user part of the mail address, every time a new extension is created. So one option would be to have a variable with small letters or another option would be to have a variable for the user part of the mail address.

Cheers, Timo

[dinger1986]

@si458 @silversword411 needs docs but can close