Outbound Caller IDs for more than 2 SIP Trunks on 3CX

[vincent Kavila]

I have 3 SIP trunks on my 3CX and need to configure them in such a way that every time a user initiates an outbound call, 3CX picks an outbound ID for his assigned DID from each of the 3 SIPs:
Example:
User A:
Main SIP 1 TRUNK: 0112344400
SIP 1 DID: 0112344453

Main SIP 2 TRUNK: 0732912000
SIP 2 DID: 0732912053

I want every time user A makes an outbound call, the Outbound caller ID that shows is either for SIP 1 DID or SIP 2 DID depending on which SIP he uses.

I hope my description is clear.

Please comment if you know how to go about it.

Thank you

 

[NicholasP_3CX]

Te Caller ID defined for a user is very specific, but you can create an outbound rule that allows a user to go out on a SIP trunk and use a Caller ID for each rule

 

[vincent Kavila]

The caller ID defined for a user is very specific, but you can create an outbound rule that allows a user to go out on an SIP trunk and use a Caller ID for each rule

View attachment 40847

Thank you, Nicholas, I have tried this, but it's not what I'm looking for.
Each of my SIP has a provision for like 100 DIDs which I have mapped each to a user for inbound calls.

 

[vincent Kavila]

Te Caller ID defined for a user is very specific, but you can create an outbound rule that allows a user to go out on a SIP trunk and use a Caller ID for each rule

View attachment 40847

This will display the main trunk number for all outbound calls, I am not looking for that. I needed 3CX to pick the caller ID as per the DID assigned to the user.

Thank you

 

[NicholasP_3CX]

This will display the main trunk number for all outbound calls, I am not looking for that. I needed 3CX to pick the caller ID as per the DID assigned to the user.

Thank you

Not necessarily.

Ensure that the DIDs are defined in the format the providers require. And when defining your outbound rule the provider will take the Caller ID from the outbound rule and pass it through.

Ensure that the caller IDs are properly defined and these will be passed through.

In another post, I posted what might happen when a provider takes a Caller ID which is not assigned to it's account, or in an invalid format

Quoting other post https://www.3cx.com/community/threa...so-ring-my-mobile-checked.126304/#post-597490

Caller ID passthrough can be sent by 3CX. The SIP field entry for sending the Original Caller's ID is "OriginatorCallerId"

However, it is solely and entirely up to the provider to accept this.

Many providers do not allow you to send a caller ID that is not assigned to your account to prevent spoofing, and/or fraud attempts.

What may happen if a "foreign" caller ID is sent to a provider that does not allow CLIP No screening:

1. Reject the call outright
2. Send the call out with "Anonymous" as the Caller ID
3. Send the call out with a random Caller ID from their pool (This may even be a number from a different country)
4. Send out your main account number (usually your main trunk number) as the Caller ID.

Generally, if you have any caller ID issues, please contact your SIP Provider.

 

[vincent Kavila]

Not necessarily.

Ensure that the DIDs are defined in the format the providers require. And when defining your outbound rule the provider will take the Caller ID from the outbound rule and pass it through.

Ensure that the caller IDs are properly defined and these will be passed through.

In another post, I posted what might happen when a provider takes a Caller ID which is not assigned to it's account, or in an invalid format

Quoting other post https://www.3cx.com/community/threa...so-ring-my-mobile-checked.126304/#post-597490

Caller ID passthrough can be sent by 3CX. The SIP field entry for sending the Original Caller's ID is "OriginatorCallerId"

However, it is solely and entirely up to the provider to accept this.

Many providers do not allow you to send a caller ID that is not assigned to your account to prevent spoofing, and/or fraud attempts.

What may happen if a "foreign" caller ID is sent to a provider that does not allow CLIP No screening:

1. Reject the call outright
2. Send the call out with "Anonymous" as the Caller ID
3. Send the call out with a random Caller ID from their pool (This may even be a number from a different country)
4. Send out your main account number (usually your main trunk number) as the Caller ID.

Generally, if you have any caller ID issues, please contact your SIP Provider.

Still not working as I need

 

[vincent Kavila]

Not necessarily.

Ensure that the DIDs are defined in the format the providers require. And when defining your outbound rule the provider will take the Caller ID from the outbound rule and pass it through.

Ensure that the caller IDs are properly defined and these will be passed through.

In another post, I posted what might happen when a provider takes a Caller ID which is not assigned to it's account, or in an invalid format

Quoting other post https://www.3cx.com/community/threa...so-ring-my-mobile-checked.126304/#post-597490

Caller ID passthrough can be sent by 3CX. The SIP field entry for sending the Original Caller's ID is "OriginatorCallerId"

However, it is solely and entirely up to the provider to accept this.

Many providers do not allow you to send a caller ID that is not assigned to your account to prevent spoofing, and/or fraud attempts.

What may happen if a "foreign" caller ID is sent to a provider that does not allow CLIP No screening:

1. Reject the call outright
2. Send the call out with "Anonymous" as the Caller ID
3. Send the call out with a random Caller ID from their pool (This may even be a number from a different country)
4. Send out your main account number (usually your main trunk number) as the Caller ID.

Generally, if you have any caller ID issues, please contact your SIP Provider.

Still not working as I need, it only works when I configure the DID under Outbound Caller ID on user configurations

 

[vincent Kavila]

Te Caller ID defined for a user is very specific, but you can create an outbound rule that allows a user to go out on a SIP trunk and use a Caller ID for each rule

View attachment 40847

Hi Nicholas,
Does this mean I have to create outbound caller IDs for each user?

Please advise?

 

[NicholasP_3CX]

Hi Nicholas,
Does this mean I have to create outbound caller IDs for each user?

Please advise?

To get the functionality you want for this scenario, yes.

 

[vincent Kavila]

To get the functionality you want for this scenario, yes.

I have over 2000 users

 

[VoIPTools]

Hi Vincent,

How about this approach -- we create a server-side service that monitors all outbound calls. When it sees extension 100 has placed a call, the service automatically updates the extension with a new caller ID from a pool of available phone numbers. That way, the next call will display a different phone number, as well as the next, and the next... rotating the outbound caller ID number with each new call.

This is custom development, but we can build you a solution to implement precisely what you need.

 

[vincent Kavila]

I have over 2000 users

Hi @NicholasP_3CX ,
I can't achieve this through the SIP outbound parameters without having to create outbound IDs for each user.

Please advise.

Thank you

 

[VoIPTools]

There are only two ways you can control the outbound caller ID number in 3CX:

1. Assign a static caller ID to an outbound rule and control which outbound rule the call uses.
   
   For example, you could create an outbound rule that checks for dial numbers starting with 88888. The rule would strip the 88888 from the dialed phone number and pass the remaining digits to the SIP provider along with the assigned caller ID.
   
   The challenge with this approach is that you would need an outbound rule for every DID you want to use, and the user would need to remember all the codes to select the desired caller ID number.
   
   
2. Adjust the users Caller ID. This is straightforward, but the user would have to change the number assigned to their extension before each call.

If you have a large number of DIDs you want to us, and you want an automated way of cycling through a list of DIDs, you will need custom development. 3CX cannot do it out-of-the-box.