IP based Auth SIP Trunk State

[NTSer]

Hy everyone
I successfully connected a Yeastar TG100 gateway to 3cx.
with this manual: Https://support.yeastar.com/hc/en-u...How-to-Connect-Yeastar-TG-VoIP-Gateway-to-3CX - as far this works perfectly.

Unfortunately, an "IP based Auth" SIP trunk is not actively monitored by 3cx, and possibly marked as down.
First, I would like to be informed by mail, if the SIP trunk goes down, and second, for outgoing rules the SIP trunk as a primary Link, this will probably not work?

Is it possible to actively monitor an IP based Auth SIP trunk from 3cx?
Or does anyone have experience connecting to a Yeastar TG100 Gateway with User based Auth? ... To monitor the SIP Trunk

Thank you very much
Greeting A

 

[Lee Cramman]

Couldn't you change the auth method to IP+username and password?

 

[NTSer]

I can, but after i changed, the SIP Trunk remains down.

3cx -> request OPTION to Yeastar = 200 OK
But other way round:
Yeastar TG100 -> 3cx = 404 user unknown

On yeastar side i used following settings:
Domain: 3cx.domain.com
Authorization Name: user
User Name: user
Password: the_password

On 3cx Side:
Authentication ID: user
Password: the_password

 

[cobaltit]

You probably want to work with Yeastar support since it's not a 3CX supported gateway. I've only setup one Yeastar gateway and I went the IP authenticated route.

 

[Lee Cramman]

OK, you threw me by saying you successfully connected it so I assumed it was simply a monitoring problem.

The error message suggests an authentication problem. Are you completing both username and authentication ID (as well as password) and, if so, do you have them the right way around?

edit: Just re-read your original post. An IP auth trunk should not show as down if it is up so if it does there is possibly a mis-config somewhere. Throwing additional auth into the equation just confuses the issue until you get this resolved.

 

[NTSer]

I changed the Trunk on Yeastar side to a simple SIP Account with username and password.
It is working fine now.
After my tests, it would work with IP based auth as well - the trunk remains green on 3cx side, but if you place a call, you have aprx. 30 sec till the 2nd trunk in list is used.
We leave as it is now. I think it work as expected.

 

[Lee Cramman]

Good news