Coming from traditional TDM systems, I know there were ways (feature codes) to control outgoing CID on a per-call basis. The only way I know of to do this is to have multiple user accounts on the phone - each with a different outgoing CID assigned to that extension number, and the user would pick the line account to alter its outgoing CID. (Samsung had a TCLIP feature key)
Is there a better way to do this?
I usually adjust the caller id with the outbound route in use. I have a location with 14 different DIDs tied to the trunk, and each one goes out as expected. I have only had one location where a user wanted a different outbound caller id for some calls and I did what you did @marty and just gave them a different extension to dial out on the same phone. It was easier then setting up outbound rules for one phone/user. That being said every sip provider does it differently though, there can being settings that adjust the caller id after it leaves the UCM. I know in my case I can go to my providers portal and say for this trunk, always use this caller id, and it does not matter what the UCM sends to it.
@williehowe has a video from a few years ago about inbound/outbound routes.
2 Likes
You can also use an identifier like 9 in front of any number.
You will create a set of outbound routes with 9NXXNXXXXXX, 91NXXNXXXXXX, 9XXX for example and in the outbound caller id you add the number you want to outpulse. Don’t forget to strip 1 as well.
The user can just dial 9+Number to send whatever caller id that is assigned.
They can just dial the normal Number without the 9 to use other outbound routes with different caller id.
We do this alot for sites with multiple companies using the UCM.
There are a bunch of ways to control outbound caller id in the UCM and it really depends on the carrier as certain carriers may want caller id sent in specific ways.
3 Likes