I don’t think Xlite is capable of authenticating the upstream system, which is probably why it ignores the badly configured authentication.
I don’t think Asterisk allows an inbound authentication user that doesn’t match the section name, so you still have to rename your section to [anonymous] or get the SIP provider to disable authentication, or use a sensible name.
Which version are you using? There is no “insecure=very” for 1.6.1, not even as legacy support in the code. Maybe you are forcing them to try to authenticate when they are not really prepared to do so.
Outgoing calls works,
but ingoing calls (from world to asterisk) don’t work --> always budy.
I’ve see that the problem come from Asterisk and not x-lite : “Failed to authenticate device “Anonymous” sip:anonymous@anonymous.invalid;tag=30126-NQ-2a23ab05-206455063”
It’s very strange, with this … this works :
i removed the “trunk” from sip.conf and just keeped “register”.
but with this i can only have one “trunk” …
sip.conf
[forfait-ovh] ; nom du plan
exten => s,1,Ringing(1) ; Attendre une seconde en faisant retentir la sonnerie du telephone de l'apellant
exten => s,2,Answer ; Repond a l'appel
exten => s,3,Playback(hello-world)
exten => s,4,Hangup(16) ; La communication est termine
If it works, you have a security problem, and need to fix the setting of allowguest.
The reason it is working is that you have no secret defined for guests, so, although you don’t have “insecure” set, Asterisk cannot insist on the peer authenticating.
You need to go back to the original and use a valid setting for insecure. Settings which include “very”, including the one you were recently given, are not valid for the version of Asterisk that you are using. insecure=invite may well be sufficient.
You may also find you don’t need a secret in the peer entry, only in the register.