Problem with 3CX and Peoplefone. Cannot etablish communication with SIP trunk (5060)

[IT_VBO]

Hello,

I tried many configuration's changes. I never can etablish/register to the SIP trunk provider.

06/10/2017 12:15:07 - Registration attempt for Lc:10000(@peoplefone[<sip:[email protected]:5060>]) is scheduled in 40 sec.


Testing 3CX SIP Server... failed (How to resolve?)

• stopping service... done
• detecting SIP ALG... failed (How to resolve?)
• testing port 5060... full cone test failed (How to resolve?)
• starting service... done

We have a Forigate Firewall and i followed the recommendation's from 3CX. Change nothing.

Peoplefone SIP provider saying having a problem on 3CX side or Firewall Side.

I opened a support ticket at Fortinet.

But i would check the configuration of 3CX too.

 

[dab]

3CX is running fine with a peoplephone.ch trunk and Fortigate v5.4.x
There must be a configuration problem on the Fortigate, on 3cx you can't do anything wrong with the provided trunk config.
To get the Firewall Test green you have to do things on the Fortigate you won't like for security reason. But you can get a fully running and secure config.

 

[OCWI]

Any sip ALG on the ISP side? Those Fortigates can be very odd, make sure there isnt any sort of "dynamic" ports or anything like that going on.

The other idea would be to backup the PBX, spin up a hosted PBX (use OVH or google, or AWS - tons of guides on here) and restore from backup.

Then throw in a raspberry pi border controller provision the phones to that. That should successfully traverse your firewall issues and eliminate your issues.

 

[IT_VBO]

Finally i was able to do the SIP connection, but now, i can ear the caller (or if i call it), but the caller cannot ear me.

Is like having only one way, not both way.

 

[StefanW]

this still indicates that the firewall re-writes or blocks traffic in the exchange with the provider. Very Important is in the Fortigate guide the bottom part and to delete/disable those rules!

 

[IT_VBO]

But at the port 5040 ? 9000-9255 ?

Apparently internal call made same. I suspect an local anti-virus blocking call's.