Need: different from and contact header

VitalPBX
1

Hello,

I am currently testing the Vitalpbx 4 (same with Vital 3) with a German provider and pjsip!
Incoming calls work, but for outgoing calls it is rejected.

The provider requires the following for outgoing calls:

“From” = caller number
“To” = Number to call
“Contact” = Provider SIP user
“P-Preferred-Identity” = Billing number Provider.

If I don’t enter anything in the trunk settings for “From User” the “Contact” is output as follows sip:asterisk@192.168.1....!

But if I enter the Provider SIP-User in the Trunk Settings at "From User
the “Contact” is output as follows sip:+491967383737...@192.168.1.... which is correct but in the “From” the provider SIP user is also entered, which is not correct because in the field “From” the caller number must be entered!

Any Idea how to get all those headers different?
On the advanced tab in trunks it will only append and not replace the header. This will not work.

Thanks a lot.

2

Who can help? Thanks.

2022-08-22 um 16.29.27
2022-08-22 um 16.29.271813×1131 257 KB

3

For the contact, you can set it on the Trunk
image

However, I tested this on VitalPBX 3.2.3-2, and it seems like VitalPBX does not add the contact_user=pitzkey to the PJSIP endpoint. So either wait until they fix it. (perhaps it even works on your machine, I only tested on one VM) or add it to a custom file.

For the PAI, disable PAI for the Trunk device profile and manually add it on the Trunk header tab

1 Like
4

If I recall correctly, that’s applied when the parameter “Require Registration” is set to “Yes”

5

Well, it shouldn’t be that way. You should allow setting the contact name regardless to the registration method.

6

If From User is set then it will overwrite the Contact Header.
But the contact_user will not be used even if it is set.

signal-2022-08-23-083016_002
signal-2022-08-23-083016_0021127×271 18.5 KB

Without From User:

signal-2022-08-23-083016_004
signal-2022-08-23-083016_0041496×869 120 KB

With From User:

signal-2022-08-23-083016_003
signal-2022-08-23-083016_0031496×869 135 KB

7

The contact_user is NOT used by VitalPBX even when “Require Registration” is set to yes.
This is the problem.
Are you able to fix this please?
Thanks

Edit: somehow the contact_user is used but not visible in SNGREP. It is not completely ignored. But somehow it is messed up somewhere.

8

What makes you say that?

9

We tested a call with the provider. It was not working without the contact_user. Rejected.
As soon as the contact_user is set the call works. But the issues we said still persist.

10

How did you set the contact header? If it is not in sngrep then it wasn’t properly set.

11

Thought the contact_user will be the contact header?
Otherwise please send screenshots how we should/could proceed and set it correctly.
Thanks a lot!

12

See what I said above:

13

Example for the custom file would be great.
Thx

14 
[trunk endpoint name](+type=endpoint)
contact_user=whatever
15

Yes, this is what we would need.
In Vitalpbx the conatct_user is NOT written to type=endpoint.

We added the contact_user to the type=endpoint and this would work.

Another question:
its like that in the pjsip__…_trunk conf:

[trunk endpoint name](p13)
type=endpoint

Is that right then?

[trunk endpoint name](p13)(+type=endpoint)
contact_user=whatever
16

It seems there are two types of contact users. Check the links below.

17

Can you please make both work in the next version?
We need it for type=endpoint

Thanks

18

No, remove the (p13)

1 Like
19

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.