OVH Trunk Template issue ?

[AWS2P]

We have a 3cx server in 16.0.1.273. connected to 2 SIP trunks OVH.
Until yesterday no real worries, but we had to change PWD from one of the 2 trunks.

Obviously we did it OVH and 3CX side but now, even if the link appears UP (trunk to green), at the time of the emission of the calls we have the following messages:

Call or Registration to 06xxxxxxxx @ (Ln.10001@OVH-forfait-1) has failed. 91.xxx.xxx.23 replied: 403Wrong login or password; from IP: 91.xxx.xxx.23: 5060

In doubt we tested the OVH given credentials with a vulgar SIPphone directly on the trunk and it works.

If i change PWD on both trunks, it works.

Is it possible issue on OVH trunk template?

 

[JohnS_3CX]

Hi @aws2p

So you have two trunks that use the same credentials, or different unique credentials and DIDs?

 

[AWS2P]

No, all different , but with call package included on both.

If Pwd is changed on only one , it becomes green after change, but no call is possible, the other with old PWD is working fine same time.
If pwd is set the same on both i retrieve 2 trunk working.

Problem occurs only when one PWD is changed

 

[JohnS_3CX]

Ok so if changed on both trunks it works. And when you change it on both via the OVH portal, do you use the same password for both trunks or unique password per each trunk?

 

[AWS2P]

If Pwd are differents the 2 trunks are up but only one is fully working , the second one is able to receive incoming calls but no outgoing.
At the time we set same Pwd on both it works fine for all

 

[JohnS_3CX]

It might be a good idea to raise this question with OVH, because the PBX capable of supporting two accounts with two different passwords (at least as tested with other providers).

 

[AWS2P]

OVH Support remains evasive and suggests that it is the 3CX PBX that is involved.
For the moment we will be satisfied with 2 identical passwords