Solved SIP Trunk - is it possible to send the internal extension of the user making a call in the SIP information

[cmarston1500]

I am working on a PCI-DSS integration and it would be useful if we could send the user extension making the call in a contact or other field in the SIP message sent out to our PCI platform. Does anyone know if that is possible? Even if it was another value that was unique to the agent making the call that would also work.

 

[YiannisH_3CX]

Hi @cmarston1500

I am assuming that you are using a SIP Trunk to connect to your integration. Generally speaking sending the internal extension to an outside call should be avoided for security purposes however there is a way to so it but it will apply to all your SIP Trunks. You can set the extension number as the extensions outbound caller ID under the extension settings.
Then in your trunk settings --> Outbound parameters you can set the SIP header you want to either "OutboundCallerId" or "OriginatorCallerID". That way the trunk will set the caller ID to the extensions number.

 

[cmarston1500]

Hi @YiannisH_3CX. Thanks for your response. Yes, correct we have a custom sip profile connecting to the PCI service platform and that platform is acting as the SIP Carrier in this scenario routing calls to/from allocated telephone numbers onto/from 3CX. I see your note about the extension number being visible on all SIP trunks. We can strip that out on the PCI platform before we pass the call onto the SIP carrier of our customers so that should work well. I will make the change and we can see what we get. I will report back.

 

[cmarston1500]

@YiannisH_3CX. Will this result in a change to the SIP URl? The reason I ask is we use the IP address the call comes from as asecurity andmatch value and the phone number calling to match the businesses account with the PCI platform. Ideally I want to keep all the current SIP header information and also send the user ext as well.

 

[cmarston1500]

OK we tried the suggested. Unfortunately 3CX replaces the main telephone number we want to keep as the calling party with the users ext number (inserted into the outbound DDI section of EXT). So fail unfortunately.

 

[YiannisH_3CX]

There are other combinations you can try using the trunks outbound parameters. For example, if you only need one main telephone number being sent you can set it as the main trunk number of the trunk you created and in the outbound parameters set the From: UserPart as "LineNumber" External number of line and set the PAI header to "OutboundCallerId" so you can sent the extension name.

Actually if you want to know what each parameters does check out the following link and perhaps you can make something happen that will suit your needs.
https://www.3cx.com/docs/sip-trunk-outbound-calls/

 

[leejor]

Are you currently using a Generic SIP trunk? Have you tried using a Bridge trunk?

 

[cmarston1500]

@YiannisH_3CX. Will this result in a change to the SIP URl? The reason I ask is we use the IP address the call comes from as asecurity andmatch value and the phone number calling to match the businesses account with the PCI platform. Ideally I want to keep all the current SIP header information and also send the user ext as well. We ahve tried quite a few of the otehr drop down opions and none seem to result in waht we wanted to achieve.

 

[cmarston1500]

Are you currently using a Generic SIP trunk? Have you tried using a Bridge trunk?

Yes this is generic SIP. We have the calls working great in and out. I am just trying to see how clever we could be in understanding which user has placed the active call. I will take a look at Bridge trunk.

 

[cmarston1500]

I checked out Bridge, but that will not be the way customers and we will want to go. We have the ability for customers to bring their own SIP trunk and 3CX system so we offer the part in the middle of the call that allows consumers paying by card to do so on the call without the agent asking for the card details to be read out. This means we need to keep it generic SIP so we pass the number dialled and the calling party as a relay to the SIP trunk provider. We will keep testing different settings.

 

[cmarston1500]

The best we got was using the "Remote Party ID - Called Party : Display Name" in Outbound Parameters under the SIP trunk. At least it is pulling from the right field. I can now change my first name to ext first name and we get that ext as part of the RID "100 Craig Marston"<sip:anonymous>;party=called details in.

Ideally it would be great if we had a rule for pulling out the EXT number from the User EXT profile and sending this is a SIP field, but this might do for now.

 

[YiannisH_3CX]

Glad to see you were able to have a working result.