outbound Unauthorized (401)

[juntec]

did a fresh install of v20 onto a fresh server 2019 nothing else on it.
so when a extension tries to ring out it gets

Call or Registration to 041xx@(Ln.10000@Hosttel) has failed. sip:103.177.160.3:5060;lr replied: Unauthorized (401)
and you get the voice message from 3cx "call number does not exist"

When i check with Hosttel support they saying the system tries to send them SIP id with username/password

Odd thing i input the same trunk details onto a upgraded 3cx or an restore from backup 3cx the trunk works and i am able to ring out no problems.

Should i do a re-install or there is a setting that needs to be done?

notes: we are receiving incoming calls, the phones can buzz each other, its only outgoing. i have default setting +,0-9 ALL

 

[Guillaume Bourgeois]

Is this a 3CX supported SIP Trunk providers ?
https://www.3cx.com/partners/sip-trunks/

If not, you should request support from your service provider, not from us.

There are excellent reasons why 3CX certifies SIP Trunk providers—it’s to ensure they meet certain standards.

 

[juntec]

Is this a 3CX supported SIP Trunk providers ?
https://www.3cx.com/partners/sip-trunks/

If not, you should request support from your service provider, not from us.

There are excellent reasons why 3CX certifies SIP Trunk providers—it’s to ensure they meet certain standards.

No they are not 3CX supported SIP trunk providers. But odd thing is if i put the same SIP details onto another 3CX v20 restore from v18 backup, and allow 1 extension to ring out to that trunk it works. I have a feeling there is a setting from v18 that overrides the v20 on restore for generic SIP trunk providers to call out

 

[Guillaume Bourgeois]

No they are not 3CX supported SIP trunk providers. But odd thing is if i put the same SIP details onto another 3CX v20 restore from v18 backup, and allow 1 extension to ring out to that trunk it works. I have a feeling there is a setting from v18 that overrides the v20 on restore for generic SIP trunk providers to call out

Indeed, it’s quite possible.
This parameter should not have been customized by your SIP Trunk provider. If 3CX blocked this setting, it’s likely because it caused issues, which isn’t the case with supported SIP Trunks.

I’m not saying your current provider can’t work…

What I’m saying is that your provider should comply with 3CX standards.

https://www.3cx.com/docs/sip-trunk-test-plan/

It’s not 3CX’s responsibility to conform to the Trunk provider.

Think about it… many providers have gone through the effort to comply with 3CX—why hasn’t your provider done the same?

 

[juntec]

defo good point and i just sent them an email about becoming a certified SIP trunk provider.

 

[Guillaume Bourgeois]

In the meantime, although I’m nearly convinced this won’t solve the problem, you can export the configuration from a working v20 SIP trunk and import it into the other PBXs.

If it works, consider it a “band-aid” solution—there’s a strong chance it will stop working eventually.

 

[juntec]

v18 i can export and import provider info but in v20 there isnt an option, have they moved it somewhere?

 

[Guillaume Bourgeois]

Yes, look to the right of your trunk name, there are three vertical dots.
The EXPORT option is there.

To import, go to "Admin > Advanced > Templates > Provider Templates".

 

[juntec]

Thanks bud, it rings out now. my next problem is its showing up private number even i have put the caller ID everywhere i can see

 

[Guillaume Bourgeois]

Please take a screenshot.

 

[juntec]

it could be voice provider issue, my tech support contact is sick today so will buzz him monday

 

[Guillaume Bourgeois]

Switch to custom field and force the information you need.