Solved Outbound Caller Id always shows main (trunk) number instead of individual outbound caller ids on remote phone

[johnranger2]

This is on newest 3CX V16.1.

I have just realized that - no mather what I have configured in the outbound caller id field in any of our extensions, when they call to an outside phone, always the main number of the trunk is shown to the called remote phone and not the one configured in each individual extension.

I have read in another thread here that the default caller id has to be deleted on the sip trunk. This I have now made but without any change to the situation.

Also in the "outbound parameters" on the sip trunk under "From: Display Name" it is configured like this: "Outbound caller id taken from extension settings in management console".

I know that this has worked properly some longer time ago (either with V14 or even with V15). But as I have checked today this did not work anymore.

Question:
What could otherwise be checked to find out why always the trunk main number is snet to the remote party instead of the configured Outbound Caller ID?

Thanks for any help in this case.

With kind regards,

John

 

[Saqqara]

Check with the SIP provider, to see if there allow you to overwrite the outgoing ID.

 

[johnranger2]

Ok, good suggestion. Thanks for such an extremely fast reply.

John

 

[Cytranic]

If its a supported trunk, it should work. If its 3rd party, adjust the P.asserted identity

 

[johnranger2]

Thanks - I will look into that also - as it is a not supported trunk.

John

 

[johnranger2]

Changing anything under P.asserted identity didn't change anything shown on the destination - I have now contacted our SIP provider and wait for their feedback.

 

[johnranger2]

Hi Carlos,

thanks for this additional info. The two settings in our setup are already the same as in your screenshot.

I believe that our VoiP provider currently blocks the ovewriting of the outbound caller id - but it surely has worked a year or two ago when I had last checked this.

With kind regards,

John

 

[johnranger2]

Hi Carlos,

thanks again - In the mean time I have taken a network trace outgoing from the 3CX to our provider and there it is clearly visible in the relevant SIP packet that the outbound caller id ("DisplayName" and "From") contains the correct outbound caller id (the one we have set in the 3CX extensions).

That means that either our VoiP provider or their upstream VoiP provider override our set outbound caller Id.

This info I have sent early this afternoon to our VoiP provider and they are now not asking anymore questions but told me that they are investigating... (good thing I have learned by this incident is that they for themselfs also use 3CX - so I am on good supported ground )

With kind regards,

John

 

[johnranger2]

Update: Our VoiP Provider - together with their upstream VoiP provider - has adjusted something on their side and now it works.

Thanks for all your help here in the forum which pointed me into the right direction.

With kind regards,

John