Cant Upload Custom provider template

[Ehsan Shahid]

Uploaded template file has incorrect structure
header / template - This field is required

Any clues how to fix this problem?
The V20 has no options to export any existing template, all i did copy the generic provider template, past on notepad++ and save as xx.pv.xml
Please help.

 

[Colby D.]

I get the same thing when doing the exact same process, manually copied an existing template, saved, tried to upload, and then get the header / template this field is required error.

 

[fxbastler]

You can export any SIP trunk integrated and used in 3CX.
If a generic SIP trunk is set up, you can also export it afterwards. You will then see the XML tag template in the header with the value GenericVoIPProvider.pv.xml .

 

[Ehsan Shahid]

You can export any SIP trunk integrated and used in 3CX.
If a generic SIP trunk is set up, you can also export it afterwards. You will then see the XML tag template in the header with the value GenericVoIPProvider.pv.xml .

How Can I export? My 3cx is hosted by 3cx, no access to ssh or server? If you can give me a correct exported xml i will be happy to use that. Email: [email protected]

 

[fxbastler]

^ not possible?

 

[Ehsan Shahid]

Well, updating the provider template doesnt solve the issue. See bellow, how do i allow the blocked useragent?

 

[fxbastler]

how do i allow the blocked useragent?

There is certainly a good reason why this user agent is also blocked in every 3CX per default.

 

[fxbastler]

oh, the picture is gone, here again:

 

[Ehsan Shahid]

oh, the picture is gone, here again:
View attachment 49628

Thanks for the help, however, 3cx still giving same error, even I have added to ignore this user agent

 

[fxbastler]

even I have added to ignore this user agent

you may have to remove this entry ...

 

[Ehsan Shahid]

you may have to remove this entry ...

Thanks, I have removed, now getting these wired response: Any help will be appreciated

10/07/2025 11:52:57.656 AM	Reply to out-of-dialog request: OOD.Resp Send 200/OPTIONS from 0.0.0.0:0 tid=U6FDcKegDyyaD Call-ID=889a3497-1e38-123f-45bb-000c29d9b8bf: SIP/2.0 200 OK Via: SIP/2.0/UDP 205.205.133.119;rport=5060;branch=z9hG4bKU6FDcKegDyyaD To: <sip:68.183.197.253>;tag=a11d2953 From: <sip:68.183.197.253>;tag=K99XNZ1tFFaXm Call-ID: 889a3497-1e38-123f-45bb-000c29d9b8bf CSeq: 105337811 OPTIONS Accept: application/sdp Accept-Language: en Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE Supported: replaces, timer Allow-Events: message-summary, dialog, call-info, line-seize Content-Length: 0
10/07/2025 11:52:57.656 AM	Incoming out-of-dialog request: OOD.Req Recv Req OPTIONS from 205.205.133.119:5060 tid=U6FDcKegDyyaD Call-ID=889a3497-1e38-123f-45bb-000c29d9b8bf: OPTIONS sip:68.183.197.253;transport=udp SIP/2.0 Via: SIP/2.0/UDP 205.205.133.119;rport=5060;branch=z9hG4bKU6FDcKegDyyaD Max-Forwards: 70 To: <sip:68.183.197.253> From: <sip:68.183.197.253>;tag=K99XNZ1tFFaXm Call-ID: 889a3497-1e38-123f-45bb-000c29d9b8bf CSeq: 105337811 OPTIONS Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, NOTIFY Supported: timer, path, replaces User-Agent: ISPT_b2bua Allow-Events: talk, hold, conference, refer Content-Length: 0
10/07/2025 11:52:57.656 AM	Creating unknown ADS for UnkADS Recv Req OPTIONS from 205.205.133.119:5060 tid=U6FDcKegDyyaD Call-ID=889a3497-1e38-123f-45bb-000c29d9b8bf: OPTIONS sip:68.183.197.253;transport=udp SIP/2.0 Via: SIP/2.0/UDP 205.205.133.119;rport=5060;branch=z9hG4bKU6FDcKegDyyaD Max-Forwards: 70 To: <sip:68.183.197.253> From: <sip:68.183.197.253>;tag=K99XNZ1tFFaXm Call-ID: 889a3497-1e38-123f-45bb-000c29d9b8bf CSeq: 105337811 OPTIONS Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, NOTIFY Supported: timer, path, replaces User-Agent: ISPT_b2bua Allow-Events: talk, hold, conference, refer Content-Length: 0

 

[fxbastler]

Are you sure this is your provider?

I already wrote it:

There is certainly a good reason why this user agent is also blocked in every 3CX per default.

Basically, it is the case that you should only allow SIP port forwarding from the SIP trunk provider to your 3CX, if at all.

 

[bitn2]

This entry cant be removed... Its synced again from 3cx. As @fxbastler already said, there is a good reason why this is blocked.