CalledNum > To: User Part

[sfgdgdth]

Hi,

I am trying to show the DID number called by an external caller on the softphone and handset. In the outbound parameters I have this set to "To: User Part" and a wireshark trace confirms that the DID number is shown in this field. I understand that the inbound rule name can be appended and shown as the display name and have done this however this does not suit my purpose.

I have Yealink handsets and softphone users. The Yealink handsets have an available line to show the DID number and the softphones have available space. Presently the handsets show the extension number during in inbound call. How do I make it show the DID number? Ie, how do I make the "To: User Part" in the invite header from the sip trunk to 3xc pass through to the "To: User Part" in the invite header between 3cx and the extension?

I have tried many parameters in the inbound parameters screen and "To: User Part" is the exact data that I need however 3cx does not allow this to be presented to the extension. Bizarrely, 3cx lets me set the DID as the ANI making it look like I am calling myself however it won't let me put this in the To: User Part even though it is configured that way. Is it possible to include the DID in the sip invite header between 3cx and the extension as the "To: User Part" rather than the extension number?

Any help is appreciated!

 

[YiannisH_3CX]

Hello @sfgdgdth

The short answer is no you cannot. The phones will show the caller ID and not the called ID. As you mentioned you can add the Inbound rule name to the Invite and have the phones display that. The inbound rule name can be the DID number.

When a call arrives at the PBX it contains the DID called information. The PBX then initiates an Invite to the configured destination but this is a different leg of the call. The Invite between the PBX and the extension contains the extension number in the TO: field and not the DID so even if you configured the phone to display the To: UserPart field it would just show its own extension number.

 

[sfgdgdth]

Thanks for the reply. Why does the variable exist on the outbound parameters if it can't be used?

I understand that it is a different leg of the call and that it isn't necessary for the DID to be present in that leg for routing purposes but it would serve a purpose for my application.

Is it possible for the DID to be in any other field without upsetting the ANI? I appreciate that 3cx needs to specify the relevant extension for that leg of the call but it would be great to have the DID in there somewhere.

On the basis of your reply does that also mean that 3cx does not support DNIS?

 

[YiannisH_3CX]

Thanks for the reply. Why does the variable exist on the outbound parameters if it can't be used?

Outbound parameters are for outbound calls to the provider. What you are describing is an Inbound call.

Is it possible for the DID to be in any other field without upsetting the ANI? I appreciate that 3cx needs to specify the relevant extension for that leg of the call but it would be great to have the DID in there somewhere.

No it is not possible.

On the basis of your reply does that also mean that 3cx does not support DNIS?

The PBX can route the calls to specific destinations based on the dialled number so in essence identifies the dialled number and acts accordingly. Passing the dialled number to the end destination is a different story however.

 

[sfgdgdth]

Outbound parameters are for outbound calls to the provider. What you are describing is an Inbound call.

Sorry, I meant why does it exist on the Inbound parameters if it cannot be used?

 

[YiannisH_3CX]

The inbound parameters are used by the PBX. You specify the SIP field the PBX needs to read the information from. The PBX reads the called number from the specified SIP field and routes the call to the specified destination.

 

[sfgdgdth]

Thanks!

However, it doesn't matter at all what the CalledNum is set to as 3cx will use whatever is in the request uri regardless.

Is it something that 3cx would consider implementing? I've always found that giving clients what they want is good for business.

 

[YiannisH_3CX]

However, it doesn't matter at all what the CalledNum is set to as 3cx will use whatever is in the request uri regardless.

It does matter. If the SIP field is not correct the routing will fail and the call will most likely go the main trunk number destination because of the catch all functionality.

Is it something that 3cx would consider implementing? I've always found that giving clients what they want is good for business.

I would recommend posting this as a feature request to our ideas section of the forum. All posts are reviewed by their corresponding Departments and, if feasible and voted for by other users as well, may be implemented in an upcoming service pack or update.

 

[sfgdgdth]

What I mean is: No matter what I set the CalledNum to - it makes absolutely no difference - ie it does not matter what I set this parameter to as it uses the request uri. I can't even break it - there is no setting I can select that will make the call fail.

This is coming out of frustration of wasting many, many hours on trying to make this work.

I'll have a look at the idea section and hope that it has a quick turnaround. I've been following some dynamic caller ID ideas in there that were accepted 5 years ago!

All that aside, thanks for your response as I will now stop trying this method and find another way.

 

[YiannisH_3CX]

Hello @sfgdgdth

I came across a scenario that might help you achieve the desired configuration. It is not the correct configuration to have and it prevent you from seeing the callers name (if the provider is sending one).
Navigate to the inbound parameters of your trunk and change the ""CallerName" caller's name (default: From->display name) " to "To: User Part".
If the provider sends your DID in that field the PBX will consider it as the callers name and will pass it to the extension.

If however a contact is matched the device will override the callers name with the contacts name.