What would be very useful to me is having the ability to set the CallerID in an outbound route. That way I can have multiple outbound routes use the same trunk, and yet have different CallerID's. On a similiar note, there are several places within the admin portal where the CallerID is set. Its not very clear as to the precedence of how/when these different CallerID's are used. It would also be extremely helpful if this was simplified a bit.
Thanks;
FSD
While eeman's solution might
While eeman's solution might be correct, this is a 'Features Wanted' section.
To expound on this Feature that I Want, it would be be really cool if in Outbound Routes you could assign the Caller ID you wanted to use for that outbound route.
Yeah I could code that, but that somewhat defeats the purpose have having a portal where I can see it all set up.
Would you want that to always
Would you want that to always override whatever caller id was set via any other options?
I could see a use case here
I could see a use case here for things like settings caller id to match a more local number. Most probable use case would be for domestic vs international calls.
However, the issue with implementation for a management platform like TL as opposed to custom coding is that there are issues surrounding caller id preference.
Does the caller id set at the extension level have precedence or does the outbound route caller id have preference? In most use cases the caller id set on the extension is the one that will need to have preference making the benefit of this feature limited on a large scale and mass market.
its simply a matter of
its simply a matter of cloning the outbound scipt called PASSTHROUGH and adding an argument to set the callerid to a variable argument. No need to add a 'feature' as the needs and applications are too limitless to contain to any one useful application. Also stop resurrecting 5yr old threads. The answer from 2012 is NOT the same answer that exists now. The Passthrough scripts did not even exist in 2012.
I use the passthrough script all the time to manipulate caller ID. One not even considered example is that I have a trunk connection from the office (a tenant on the MTE platform) to my personal TL STE at my house. At my house my extensions are in the 200s and 100s. At work they are in the 500s, so no real conflict there. However, at work, they've decided that off-site extensions, like employees with a desk phone, are to be in the 600s. So my 'extension' is 616. So in my outbound routes at home I use passthrough, modified as a clone, to call, but set the callerid to 616 on that trunk whenever _5XX is matched. Conversely when they dial 616 it actually sends the 10digit DID to my PBX that I have setup for work calls. This is probably something no-one would consider when someone asks how to set callerid.
A most common used example of this is masquerading as other numbers. One customer runs a virtual receptionist service for small businesses (Joe The Plumber types). They forward their number to a special DID at the company who's inbound route calls a callerID name prepend of the company sent to a hunt list. So they know to answer the call 'Joe the Plumber, how may I help you'. When they need to make a call they dial *67+11-digits for whoever they are calling which masquerades the callerid to Joe's official telephone number. This process is repeated for 20 some-odd customers on their system, each with a unique callerID.
this already exists, been doing it for years.. learn to code, learn the framework