Outbound Caller ID debugging

[richardatncp]

I believe i have configured the outbound Caller ID correctly, but all i am seeing on the remote device when dialled is the default number set in the SIP trunk providers admin.

In 3CX I have set a value in 'Outbound Caller ID' on the extension setup - 768

On the trunk Caller ID, Outbound i have created a rule
(768) 44<the number>

Should i expect to see the replacement value in the activity log when i make a call??
I have set 'medium' log level

In the SIP invite the 'From' contains the extension and not the Caller ID

 

[AWS2P]

In 3CX I have set a value in 'Outbound Caller ID' on the extension setup - 768

did you set up something else in trunk settings ?

 

[richardatncp]

I have set the outbound Caller ID translation.

What else were you thinking of?

 

[AWS2P]

if you set something on trunk settings then what you set in extension (s) is not used, so it's always trunk CID setting which is sent

 

[JohnS_3CX]

In your trunk's outbound parameters, what is set under From: User Part?

 

[richardatncp]

These are the current settings

 

[NickD_3CX]

These are the current settings

View attachment 18226

This seems to probably be the problem. Although I can't guarantee it will work, try changing the "From : User Part" to the same value the "From : Display Name" is.

Also, what SIP Trunk provider are you using? Is it one of the supported ones? If so we could check to see how what you want is possible.

 

[richardatncp]

Hello,

I have tried this and the call wont go through. In the activity log I see:

0xxxxxxxxx1] is terminated: Cause: 403 Username in From Field required/INVITE from 217.xxx.yyy.zzz:5060

The SIP trunk provider is Sipgate

 

[JohnS_3CX]

Should i expect to see the replacement value in the activity log when i make a call??
In the SIP invite the 'From' contains the extension and not the Caller ID

This provider (As per our template) will receive the ID in this field, so if you run a capture and analyze the call going to the provider you should find it there.

 

[richardatncp]

I am not quite sure what you mean. I am seeing the extension number in the 'From' part of the invite

 

[JohnS_3CX]

Check the invite leaving the PBX, destined for the provider.

Not the invite leaving from the phone towards the PBX.

 

[JohnS_3CX]

So the invite from the PBX to the provider needs to have the number in the P-Preferred Identity User Part, and the phone number format should appear 49xxxxxxxxxxxx so they will accept it.

Delete and recreate the trunk using our default template if you want to be 100% sure that it works just like we tested it with the provider during the certification phase.

You will need to capture traffic on the PBX interface
https://www.3cx.com/docs/capture-network-traffic/

 

[richardatncp]

I believe that is what i am looking at

I can see a line in the log that looks like this

T:Line:10000>>07xxxxxxxx1@[Dev:sip:[email protected]]

The 'from' part on the same line contains the extension number and not the Caller ID i am expecting

 

[JohnS_3CX]

Like I mentioned earlier, it will not be in the From part. It will be in the P-Preferred Identity User Part and you can see it if you run a packet capture to see exactly what left your PBX and went to the provider.

 

[leejor]

To be clear, you set the extension number, and not a DID, in the Outbound caller Id. for the extension...

In 3CX I have set a value in 'Outbound Caller ID' on the extension setup - 768

...and, you are expecting your provider, to send that 3 digit number as the caller ID?

 

[richardatncp]

leejor - i followed the guide on the 3CX website for setting up outbound Caller ID using this guide
https://www.3cx.com/docs/multiple-outbound-caller-ids/

JohnS - i have enabled a capture on our Fortigate fw and the value for P-preferred-Identity is
[email protected]

 

[JohnS_3CX]

Ok then you are clearly sending 768 as your outbound ID.

If you want a normal DID to be sent out, you need to define it here.
You should probably ask the provider to tell you what format they want it in
i.e 0044xxxxxxxx or 44xxxxxxxxxx or 07xxxxxxxxxxxxx
(and make sure they allow you to do this in the first place)

 

[richardatncp]

I asked the question of Sipgate support and they said E.164 format.

I have now tried this and it seems to work. I must have put 00 in front when i first tried it

I haven't got the 00 in the search and replace function - but that doesnt seem to work - where have i gone wrong with the setup?