Issue with making calls on new install

[fburnat]

Hi,

I'm new to 3CX and I'm running into an issue with placing calls. I get a "Not Found" message every time I try to place an outside call. Calls within the organization work perfectly;

I'm using 3CX on version 16.0.4.493, on a remote Windows 10 Server 2019 with a static IP. The phone I'm using is a Yealink T46S with the latest firmware.

Provisioning is STUN, Trunk provided by OVH. Firewall verification is OK and I'm not using any personalized template for the phones.

My extension is correctly registered on the SIP Server.

However, the Error message I get is the following:
Call or Registration to PHONENUMBER@(Ln.10000@Paris) has failed. 91.121.129.23 replied: 403 Wrong login or password; from IP:91.121.129.23:5060

Any idea?

Thanks a lot in advance for your help,
Florian

 

[AWS2P]

did you set almost one outbound rule?

 

[AWS2P]

Wrong login or password; from IP:91.121.129.23:5060

Your OVH trunk is registred green?

Your PBX is not on same site as you are with your T46S, so for STUN mode did you set properly firewall on location where phones are ?
SIP port for phone
Static IP for phones
Range of RTP ports

 

[fburnat]

Your OVH trunk is registred green?

Yes it is

 

[fburnat]

Your PBX is not on same site as you are with your T46S, so for STUN mode did you set properly firewall on location where phones are ?
SIP port for phone
Static IP for phones
Range of RTP ports

Hmm that's maybe where the issue is. We have a specific firewall for our firm and I'm not sure I would be able to actually open the appropriate ports. This implies I would need to have an in-house server to avoid the issue right?

But apologies for the newbie question, if the phone is correctly provisioned by the server, doesn't that mean that the firewall settings are correct?

I've tried placing a call through the iOS app as well and it didn't go through although it wasn't connected to the on-premise network.

 

[AWS2P]

do you have several phones to use remotely on the same site?
If so then a SBC is your answer

You didn't answer about outbound rule , do you have set one?

 

[AWS2P]

I've tried placing a call through the iOS app as well and it didn't go through although it wasn't connected to the on-premise network.

App use tunnel 5090 port to access PBX so it should work, do you have green on top right corner and available for calls displayed in APP?

 

[fburnat]

App use tunnel 5090 port to access PBX so it should work, do you have green on top right corner and available for calls displayed in APP?

I do but again it shows not found when I try to place a call

 

[AWS2P]

answer me please about outbound rule, do you have set one?

If no rule set PBX has no route granted for outgoing calls

call *777 (echo service) speak, can you hear you back?

 

[fburnat]

Echo service works.

I did indeed set up an outbound rule. I just noticed that I didn't assign any extension to this rule.
No extension => "Not found" error message
Extension put in => "Forbidden" error message

 

[AWS2P]

can you paste a screen copy of your rule

 

[fburnat]

Here it is:

There is no backup rule set.

 

[AWS2P]

remove ext 101, is Paris name of your trunk sip?
add lenght 2-16

 

[fburnat]

Paris is indeed the name of my trunk SIP.
I removed the extension number and add the length but to no avail I'm afraid. Still says Forbidden

 

[AWS2P]

understood why you had not found previously , it was no criteria in your rule before you add ext 101

 

[AWS2P]

see messages in log now

 

[AWS2P]

on OVH trunk I'm pretty sure you need to send caller ID number, has your trunk been set with a 3CX template or manually? what do send in caller ID ? if empty or not OVH number not sure OVH grant you for outgoing calls, so forbidden now is surely coming from Trunk

 

[fburnat]

Here's the latest log:
Call or Registration to PHONENUMBER@(Ln.10000@Paris) has failed. 91.121.129.23 replied: 403 Wrong login or password; from IP:91.121.129.23:5060

 

[AWS2P]

phone to OVH support this is something misconfigurated on your side.
PHONENUMBER is the good one ? is it with something starting +33xxxxx ?

 

[AWS2P]

do you have caller id set in your extension 101 ?
remove it and do a call test