Solved 3CX sip trunk doesn't send caller name on incoming calls (Original post from user Matt Rabbitt, Jan 30, 2018)

[Konkislav]

Hello colleagues,

I have the same problem as the colleague Matt Rabbitt who created a post more than 3 years ago.
In my case I have a SIP trunk between 3CX and OpenScape 4000 (Unify PBX) and when call comes from 3CX, both parties are visible - called sees callers name and vice versa.
When the call is initiated from the OS4K (OpenScape 4000) system, the 3CX does not send the name of the called user.

From what I see in the traces, in the good case, the name of the called is sent from OS4K to 3CX in the second message (180 Ringing) as P-Asserted Identity.
In the bad case, the same is sent from the OS4K but no name is sent from 3CX side - so the user from 3CX sees the name of the OS4K caller, but the OS4K caller sees only the name of the trunk, that is configured between the two systems.

I tried to play with the trunk parameters in 3CX - Incoming, Outgoing... the result is either the same, or the trunk is blocked and needs to be restarted.
Can someone please tell me what am I missing. Many thanks in advance!

Best regards,
Stan

 

[YiannisH_3CX]

Hi @Konkislav

I am a bit confused by the description so some clarification maybe necessary.

When the call is initiated from the OS4K (OpenScape 4000) system, the 3CX does not send the name of the called user.

So this is an inbound call to 3CX from OS4K and you want to see the name of the person that was called? You said that there is trunk connecting the 2 systems so I am assuming that a number is dialed to reach 3CX.

From what I see in the traces, in the good case, the name of the called is sent from OS4K to 3CX in the second message (180 Ringing) as P-Asserted Identity.

If the call is inbound to 3CX then its 3CX that should send ringing and not the OS4K


So from I understand you want the user that makes the call from the OS4K to be able to see the name of the user that answers the call in 3CX? You title mentions the callers name and not the called name so I think its all a bit confusing.

If this is seen as a SIP trunk in 3CX then 3CX will not send the called users name through the trunk when answering a call. That information is only seen in the exchange between the PBX and the extension and is not made public neither there is a setting for this to be made public.

 

[Konkislav]

Hello YiannisH_3CX,

Excuse me for the confusing description. You are right. The correct issue description is: OS4K caller does not receive from 3CX the name of the called 3CX user (during inbound call for 3CX). That is the bad case.

What I gave as good case example is the opposite test - when 3CX user calls OS4K user, the OS4K PBX sends the name of the called(OS4K user) in the 180 Ringing message (from OS4K to 3CX). So 3CX user sees the name of the called OS4K user.

However, when the OS4K user calls the 3CX user, the 3CX PBX does not send any name in the 180 Ringing message (in P-Asserted Identity).

If I understand you correctly, there is now way that we configure 3CX PBX to send via SIP trunk the name of its users, when there is inbound call to 3CX. Do I understand that right?

If yes, that is somehow strange, because when 3CX user calls the OS4K user, the name of the 3CX user is visible for the OS4K user. Although it is send in the INVITE, this is still one situation when 3CX sends the name of its user to external PBX systems via SIP trunk. The only difference is that the call is initiated by 3CX.

 

[YiannisH_3CX]

If I understand you correctly, there is now way that we configure 3CX PBX to send via SIP trunk the name of its users, when there is inbound call to 3CX. Do I understand that right?

That is correct

If yes, that is somehow strange, because when 3CX user calls the OS4K user, the name of the 3CX user is visible for the OS4K user. Although it is send in the INVITE, this is still one situation when 3CX sends the name of its user to external PBX systems via SIP trunk. The only difference is that the call is initiated by 3CX.

That is also correct. During an outbound call from 3CX the callers name can be added in the outbound parameters of the SIP trunk. That is not possible in the 180 Ringing or 200 OK message.
You can control what is being sent when the PBX initiates a call but not what the replies include. Creating a call and answering to a call are very different things so I am afraid that what you want to achieve is not possible through 3CX.

 

[Konkislav]

In this case, I can only thank you for saving me the time and efforts to search further for how to make that possible.
Thanks for the fast replies, too!

Best regards.
Stan