How to use the name of inbound rules as variable

[Sven von r&s]

Hey there!
I`m using 3CX for about a year. This is my first contact with this forum and I was so far not very succesful with seaching.

I`m trying to find an alternative to the 3CX desktop client. To replace it, the condition would be to use the name of inbound rules as a variable in a called url. As I see it, the 3CX CRM template Generator is no solution for my task. Any possibilities or ideas?

 

[edossantos]

Unfortunately the inbound rule name is not available in any variable, not for CRM templates, or with any 3CX client.

 

[Sven von r&s]

Unfortunately the inbound rule name is not available in any variable, not for CRM templates, or with any 3CX client.

Thank you for this fast reply. Is there anything scheduled in this directions? Or are there any variables supported which relate to the called number and not just to the caller?

 

[edossantos]

Thank you for this fast reply. Is there anything scheduled in this directions?

I'm not aware of any of this on the way.

Or are there any variables supported which relate to the called number and not just to the caller?

Not at the moment, only the caller number, not the called number.

 

[Sven von r&s]

I'm not aware of any of this on the way.


Not at the moment, only the caller number, not the called number.

What a pity! Anyway - thank you for your support.

 

[Evolute IT]

What a pity! Anyway - thank you for your support.

It may come eventually. They know it's requested but not enough people needs that compared to other features, so it is not a priority.

 

[Sven von r&s]

It may come eventually. They know it's requested but not enough people needs that compared to other features, so it is not a priority.

Hope so! Today I use a workaround by writing this data from the current call via the win cmd to a textfile. Works ok. But sucks with every update and is useless if you`re looking for a browser based solution.
And of course I can imagine it`s not the highest priority. On the other hand: all the datas are available and used in the web client. I guess it`s not a big deal to provide some more variables.

 

[Evolute IT]

Hope so! Today I use a workaround by writing this data from the current call via the win cmd to a textfile. Works ok. But sucks with every update and is useless if you`re looking for a browser based solution.
And of course I can imagine it`s not the highest priority. On the other hand: all the datas are available and used in the web client. I guess it`s not a big deal to provide some more variables.

FYI, the inbound rule name is not anywhere on the Webclient but the Caller ID of an incoming call (when append/prepend rule name is enabled.)

That's it. And that's modified before the call reaches the Webclient, so the client itself doesn't know the inbound rule, just knows the caller ID as is and displays it.

 

[Sven von r&s]

FYI, the inbound rule name is not anywhere on the Webclient but the Caller ID of an incoming call (when append/prepend rule name is enabled.)

That's it. And that's modified before the call reaches the Webclient, so the client itself doesn't know the inbound rule, just knows the caller ID as is and displays it.

I think I expressed myself unhappily. At least the inbound rule name is displayed in the queue. That`s what I meant.