Unsupported Troubles with custom trunk - wind.it

[yetopen]

Hi.
We're trying to use a custom trunk with 3CX, it's a landline DSL provider which also assigns a virtual number. We tested the configuration with Zoiper and works fine. In 3CX we're able to receive calls but not to make outbound.

This is the message we get in logs:

10/06/2021 12:36:26 PM - Call to T:Line:10001>>333123123123@[Dev:sip:[email protected]:5060] from L:29.1[Extn:032] failed, cause: Cause: 407 Proxy Authentication Required/INVITE from 151.6.93.169:5060

(151.6... is the SIP trunk, 333123 is the called number, 10001 is the line id in 3CX).

Our speculation is that the sip:[email protected]:5060 param is wrong, it should probably be the caller (our) phone number. We tried changing From: User Part and Remote Party ID - Calling Party: User Part setting them to AuthID but didn't change anything.

It's almost certainly an outbound parameter which needs to be fixed to comply with the SIP provider, but so far we were unable to find which one. Any suggestion?
thanks

 

[YiannisH_3CX]

Hi @yetopen

The error suggests that the provider requests authentication but its failing at some point so I am guessing you need to add your trunk credentials correctly for calls to succeed.
Of course I would urge you try one of our supported SIP trunk providers to avoid all the guessing work of having to manually adjust all the settings in the trunk.

 

[yetopen]

The error suggests that the provider requests authentication but its failing at some point so I am guessing you need to add your trunk credentials correctly for calls to succeed.

Credentials are correct, as I said incoming calls are received correctly.
I was just asking how is the INVITE composed, at least to know what parameters to change.

Thanks

 

[YiannisH_3CX]

I was just asking how is the INVITE composed, at least to know what parameters to change.

3CX has a lot of customization you can do to the outbound parameters to compose an Invite so you will need to ask your provider what they are expecting or give you an example so you can match that in 3CX.