With-hold CLI by default.

Status
Not open for further replies.

shedster99

Silver Partner
Advanced Certified
Joined
Aug 3, 2009
Messages
32
Reaction score
1
By the current default, callerID is sent out with an outbound call unless someone dials *5 as a prefix to with-hold it....on demand.

Is there any way we can set all calls to have their outbound callerID with-held but if there is a callerID set at extension level, this is sent instead of with-held ?

TIA
 
Hello @shedster99

By the current default, callerID is sent out with an outbound call unless someone dials *5 as a prefix to with-hold it....on demand.

Is there any way we can set all calls to have their outbound callerID with-held but if there is a callerID set at extension level, this is sent instead of with-held ?

Yes and no, as you can set your outbound caller ID as Anonymous in the trunk settings which will be replaced by the outbound caller ID of the extensions but when using *5 the PBX does not only replace the numbers with Anonymous but also uses a Privacy sip field to let the provider know that the call is Anonymous.
Also for this to succeed you need to have a provider that supports clip no screening so that Anonymous without the privacy Id is accepted.

If all requirements are met then you can set the outbound caller ID as Anonymous in the trunk settings / Options, and set the required SIP fields as Outbound Caller ID taken from extension settings in the outbound parameters of the trunk.

I would recommend contacting your provider before you do any changes though and ask them if they would accept this and what sip fields do they read the outbound caller ID from so you know what to change. And take a screenshot of your current settings as changes in the outbound rules could cause outbound calling capability to fail.
 
when using *5 the PBX does not only replace the numbers with Anonymous but also uses a Privacy sip field to let the provider know that the call is Anonymous.

Yeah, we need the Privacy:ID header added along with the P-Asserted-ID header.

Is there anything in the Provider template we can edit to force these fields with set values (not variables) on every call ?
 
Last edited:
Have you spoken with your provider about blocking your number on all calls? There may then be a prefix that would allow the number to be displayed, on a call, when required. Many providers now offer services where calls will not go through unless you allow your number to be sent, so having the ability to un-block may be necessary.
 
Have you spoken with your provider about blocking your number on all calls? There may then be a prefix that would allow the number to be displayed, on a call, when required. Many providers now offer services where calls will not go through unless you allow your number to be sent, so having the ability to un-block may be necessary.

Yeah, on it Leejor, awaiting feedback. The provider needs P-Asserted-ID sent which is fine but looks like I essentially need to setup a single "Anonymous" trunk for a handful of users, the other users will route out via a standard trunk but the "Anonymous" one should be exactly that but without the need for a prefix.
 
Is there anything in the Provider template we can edit to force these fields with set values (not variables) on every call ?
I am afraid not as the Anonymous is triggered by *5 regardless of the providers template. It comes from the system and cannot be forced by the template.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,885
Messages
589,545
Members
164,744
Latest member
johnblackwood1