BLF and Lines for web client

[retlas]

Checking with the experts in case I have missed something...

It would not appear as though BLF works with the web client as I can't find any way to select a different outbound line - or even view the BLF.

My hope was that the BLF would allow me to select the extension (line) that I wanted to dial out on.

The web client seems as though it is hobbled by only being able to dial out from one extension.

Is there another setting that would allow me to select the outbound line I wanted to use?

My use case is Company A and Company B would have different outbound CIDs, plus we'd like to record all calls made from B, but not A.

 

[Alphabetic]

Unfortunately you can only log in to one EXT per webclient. So, you would have to have seperate tabs for the different extensions you wanted to log in to.

You could set up different outbound rules prefixed with different digits to change caller ID/routing to be able to displaying your caller ID?

As for the recording, simply turn off call recording on those extensions. However, if you're dialling from one extension and using the prefix method to change your caller ID then you would either have to manually turn off recording via the button in the web client or set up a CFD which would turn it off based on prefix dialled.

 

[VoIPTools]

1. Open browser and login to web client with your first extension
2. Open 2nd browser and start an incognito session. Login with the second extension

 

[retlas]

@kieferschild darn, 3CX looked so promising. I am surprised that multi line is not supported in either the web client or in provisioning of hardware (so I have read). Rather disappointing. Kind of a non-started for us.
I have read many feature requests going back years. I really can't believe they don't support it given that their competition does.

 

[retlas]

1. Open browser and login to web client with your first extension
2. Open 2nd browser and start an incognito session. Login with the second extension

Hi @VoIPTools , we have 5 lines per user - but I appreciate your idea.

 

[VoIPTools]

Hang on. There are other ways to handle this.

For example, you can use a prefix number to designate and "outside line" (we all understand that with VoIP phone systems the idea of "lines" does not really exist. That is not a 3CX thing, it is a SIP thing).

In the old days we used to configure phone systems where the user would press "9" to get an outside line. You can do the same thing with 3CX. Use "9" for "line" 1, "8" for "line" 2, etc. Then use outbound rules to control the trunk used and the Caller ID number presented.

If you need even further control over your outbound caller ID, you may want to consider looking at our 3CX Caller ID tool. With our tool you select the "named" Caller ID you wish to use (rather than memorizing a large list of phone numbers). After all, using the prefix approach can get unwieldy if you need to choose from a large list of Caller IDs.

Controlling which calls are recorded, given that they are initiated by the same extension, is a little harder nut to crack. You could manually initiate the recording of the call, but that's probably not ideal. Alternatively, we could let 3CX record all calls for the extension, but have a custom service delete the recordings that don't match the desired criteria. This approach could be further extended to only "record" inbound queue calls, or any other criteria you wanted to specify.

 

[retlas]

Hang on. There are other ways to handle this.

For example, you can use a prefix number to designate and "outside line" (we all understand that with VoIP phone systems the idea of "lines" does not really exist. That is not a 3CX thing, it is a SIP thing).

In the old days we used to configure phone systems where the user would press "9" to get an outside line. You can do the same thing with 3CX. Use "9" for "line" 1, "8" for "line" 2, etc. Then use outbound rules to control the trunk used and the Caller ID number presented.

If you need even further control over your outbound caller ID, you may want to consider looking at our 3CX Caller ID tool. With our tool you select the "named" Caller ID you wish to use (rather than memorizing a large list of phone numbers). After all, using the prefix approach can get unwieldy if you need to choose from a large list of Caller IDs.

Controlling which calls are recorded, given that they are initiated by the same extension, is a little harder nut to crack. You could manually initiate the recording of the call, but that's probably not ideal. Alternatively, we could let 3CX record all calls for the extension, but have a custom service delete the recordings that don't match the desired criteria. This approach could be further extended to only "record" inbound queue calls, or any other criteria you wanted to specify.

Some great points. We would use click to call, from our web app, so dialling a prefix would be a chore.
Does your CID tool appear in the 3cx web client, or at a different URL?

 

[VoIPTools]

You would open our 3CX Caller ID tool in the same browser in a separate tab. Our Caller ID tool modifies the extension properties so using the click to call feature would work for you. The process would be (1) select the desired Caller ID from the list, then (2) use Click to Call to place the call. When you are finished making calls to company A, then you can revert your caller ID back to the extension's default (if needed).

 

[SteveITS]

5 lines per user

Incognito/private can only do one additional session, but just for discussion, Firefox has a container system and add-on that would allow multiple sessions all within the same browser (color coded or named tabs, etc.). I use it almost daily for keeping Microsoft accounts from leaking into each other.