Solved Best way to handle Multiple caller id/display names

[FridayIT]

Long story short, we have received requests for different line's of business's to have their caller ID's handled "differently"

Since (Please correct me if I am wrong) 3cx only has one spot to handle caller id, and the "from name" and "dialed number" are in two spots I am unable to do this on a per extension basis. I wanted to reach out to see how other admins are handling this.

Currently, we simply passthrough the employee's name for an external call. However, we mask the outgoing phone number to our main line for certain extensions. this uses up the "outbound caller id" field within the extensions which means I can only manipulate the display name, or the caller id but not both.

My current train of thought would be to use multiple outgoing rules, with those who want their numbers edited to edit them within that field, and use the extension outbound caller ID for the caller ID name instead? This way I can use the extension outbound caller id as the "name" and then use a per extension basis, or extension group basis in the outgoing rules to change the callerID.

Just curious if I am missing a simple solution to this? I should be able to make all but one department happy with this (there is one department that uses call forwarding to forward to a non 3cx setup cellphone, and wants the original caller id to flow through rather than the manipulated one)

 

[NickD_3CX]

We never had the intention of giving the ability to set the "Caller Name" on a per extension basis, like we do with the "Caller ID".

Back to your idea though, technically speaking it could possibly work by carefully playing with the Outbound Parameters of your SIP Trunk.
I would though highly advise you be very careful with how you set this up, because as I mentioned, you will have to use some of the Outbound Parameters in a way that they were not intended to work.

 

[FridayIT]

We never had the intention of giving the ability to set the "Caller Name" on a per extension basis, like we do with the "Caller ID".

Back to your idea though, technically speaking it could possibly work by carefully playing with the Outbound Parameters of your SIP Trunk.
I would though highly advise you be very careful with how you set this up, because as I mentioned, you will have to use some of the Outbound Parameters in a way that they were not intended to work.

Understood,

I will definitely be testing this during off hours to make sure I don't break production. Does it seem feasible for me to ask our 3cx distributer to open this as an "Idea" on the forums?

That being said, if there is a better way to do this I'm all ears, the only reason why I am thinking of doing it this way is it was the only way I could think of.

I also agree on being careful, up here in Canada if you set a letter in the caller id number field the system rejects it and it turns into "unknown number" lol

 

[NickD_3CX]

I will definitely be testing this during off hours to make sure I don't break production. Does it seem feasible for me to ask our 3cx distributer to open this as an "Idea" on the forums?

You could, yes, however I must say that although we examine most of the threads in the Ideas section, the "Caller Name" cannot be set on most providers in the other countries, this is mostly common with providers is US and CA, so it would need some thought...

That being said, if there is a better way to do this I'm all ears, the only reason why I am thinking of doing it this way is it was the only way I could think of.

Not that I can think of currently.

 

[FridayIT]

You could, yes, however I must say that although we examine most of the threads in the Ideas section, the "Caller Name" cannot be set on most providers in the other countries, this is mostly common with providers is US and CA, so it would need some thought...



Not that I can think of currently.

Understood, that makes sense. Caller ID is very... interesting and indeed does change on a country or even SIP provider basis. I think providing a secondary field in the extension would be the best fix for supported providers, but I also agree that it will only work on certain providers depending if they "pass through" the information.

Feel free to mark this thread as solved. I'll get in touch with our reseller to see if they can open an idea for this, I genuinely do appreciate your feedback on this.