Toggle sidebar Toggle sidebar

3CX SIP Server... failed

Status
Not open for further replies.

Network Emad

Joined
Oct 27, 2017
Messages
33
Reaction score
3
hello
i got this when i run firewall check:


testing 3CX SIP Server... failed (How to resolve?)
  • stopping service... done
  • detecting SIP ALG... failed (How to resolve?)
  • testing port 5060... done
all ports down are green just these two showing red

i'm sure that all required ports opened correctly
 
As the message explains - It means you have SIP ALG turned on on your firewall and you have to turn it off. Follow the link right behind the message for more information
 
  • Like
Reactions: Network Emad
Nick Galea said:
As the message explains - It means you have SIP ALG turned on on your firewall and you have to turn it off. Follow the link right behind the message for more information
Click to expand...

yes I stopped the SIP ALG on the firewall but still this message appear like that (Failed)
 
What make/model router are you using.? There may be additional settings that require changing.. Some routers don't "play well" with SIP.
 
  • Like
Reactions: Network Emad
leejor said:
What make/model router are you using.? There may be additional settings that require changing.. Some routers don't "play well" with SIP.
Click to expand...
Cyberoam firewall 50ing
i have the same model in my head office, 3CX working with Cyberoam here without any mistakes. i tried to do the same steps that applied here to other branch but i got this message.
 
Network Emad said:
Cyberoam firewall 50ing
i have the same model in my head office, 3CX working with Cyberoam here without any mistakes. i tried to do the same steps that applied here to other branch but i got this message.
Click to expand...


today i ran firewall checker and i got this message:

Start test, v.1.0.4
Extension 222 is registered
REQ_MAKE_CALL has failed with code 603: Caller is forbidden
ERROR: Echo test failed
Possible causes:
1. SIP ALG or a SIP Proxy has been detected between this computer/network and the target 3CX PhoneSystem. This will cause problems.
SIP ALG needs to be disabled or the Proxy needs to be removed/fixed.
Check the firewall's user manual on how to disable any running SIP ALG functionality or contact the firewall's support department.
2. 3CX Phone System might have an incorrect configuration.
Confirm that 3CX Phone System has a public Static IP Address - does not change and Not dynamic - changes.
Confirm that the network interface is correctly configured by accessing the 3CX Management Console > Settings > Network Settings> Stun Server and that the public ip address is correctly entered.
Disable Stun in this case and run the test again.
3. Confirm that you have performed the 3CX Phone System Firewall checker and that the test passes completely.
To do this access the 3CX Management Console and go to General Settings > Firewall Checker > Run Firewall Checker.
4. The firewall of this network from where the 3CX firewall Checker is running is very unreliable and unable to remember port mappings and keep them open.
At this stage it would be best to use 3CX Tunnel, 3CX Session Border Controller or try and switch to TCP Traffic instead of UDP as this will help keep the port mappings open.
 
Network Emad said:
i have the same model in my head office, 3CX working with Cyberoam here without any mistakes. i tried to do the same steps that applied here to other branch but i got this message.
Click to expand...

Does that router connect to the same 3Cx server that fails from the other location?

Something, somewhere, has changed to cause the site to begin failing. Were any software/firmware upgrades done (automatically?). Could someone have changed a firewall setting/network configuration without your knowledge? Could it be something that changed at your providers end?

I find that "things; don't just "stop working", without a reason. It doesn't take much of a change to cause a problem. you have to use process of elimination to narrow down which end, and what is causing the problem.

The "caller is forbidden" message may have something to do with a setting against an extension. Does it keep cropping up?
 
  • Like
Reactions: Network Emad
Hi All,
Please I have a similar issue and have been looking out for a solution. Anyone who has an answer kindly help me out here: Just finished with the installation and about to do other configuration. I did run the Firewall test and here was what I got. very disturbing:

Code: 
resolving 'stun-us.3cx.com'... done
resolving 'stun2.3cx.com'... done
resolving 'stun3.3cx.com'... done
resolving 'sip-alg-detector.3cx.com'... done
testing 3CX SIP Server... failed (How to resolve?)
stopping service... done
detecting SIP ALG... not detected
testing port 5060... full cone test failed (How to resolve?)
starting service... done
testing 3CX Tunneling Proxy... failed (How to resolve?)
stopping service... done
testing port 5090... full cone test failed (How to resolve?)
starting service... done
testing 3CX Media Server... failed (How to resolve?)
stopping service... done
testing ports [9000..9255]... failed (How to resolve?)
testing port 9000... full cone test failed (How to resolve?)
testing port 9001... full cone test failed (How to resolve?)
testing port 9002... full cone test failed (How to resolve?)
testing port 9003... full cone test failed (How to resolve?)
testing port 9004... full cone test failed (How to resolve?)
testing port 9005... full cone test failed (How to resolve?)
testing port 9006... full cone test failed (How to resolve?)
testing port 9007... full cone test failed (How to resolve?)
testing port 9008... full cone test failed (How to resolve?)
testing port 9009... full cone test failed (How to resolve?)
testing port 9056... full cone test failed (How to resolve?)
testing port 9057... full cone test failed (How to resolve?)
testing port 9058... full cone test failed (How to resolve?)
testing port 9059... full cone test failed (How to resolve?)
testing port 9060... full cone test failed (How to resolve?)
testing port 9061... full cone test failed (How to resolve?)
.
.
testing port 9132... full cone test failed (How to resolve?)
testing port 9133... full cone test failed (How to resolve?)
testing port 9134... full cone test failed (How to resolve?)
testing port 9135... full cone test failed (How to resolve?)
testing port 9136... full cone test failed (How to resolve?)
testing port 9137... full cone test failed (How to resolve?)
testing port 9138... full cone test failed (How to resolve?)
testing port 9139... full cone test failed (How to resolve?)
testing port 9140... full cone test failed (How to resolve?)
testing port 9141... full cone test failed (How to resolve?)
testing port 9142... full cone test failed (How to resolve?)
testing port 9143... full cone test failed (How to resolve?)
testing port 9144... full cone test failed (How to resolve?)
testing port 9145... full cone test failed (How to resolve?)
testing port 9146... full cone test failed (How to resolve?)
testing port 9147... full cone test failed (How to resolve?)
testing port 9197... full cone test failed (How to resolve?)
testing port 9198... full cone test failed (How to resolve?)
testing port 9199... full cone test failed (How to resolve?)
testing port 9200... full cone test failed (How to resolve?)
testing port 9201... full cone test failed (How to resolve?)
testing port 9202... full cone test failed (How to resolve?)
testing port 9252... full cone test failed (How to resolve?)
testing port 9253... full cone test failed (How to resolve?)
testing port 9254... full cone test failed (How to resolve?)
testing port 9255... full cone test failed (How to resolve?)
starting service... done

Tried to resolve it: Turned off the SIP ALG and port forwarded these ranges /numbers to the 3CX server - Port 5000 - 5100 Protocol = Both; Port 9000 - 9500, Protocol = UDP and Port 443, Protocol = TCP

Also, I did make configure Port Trigger with the same values in above:

I need assistance from anyone who could kindly do that for me.

Thanks
 
  • Like
Reactions: Network Emad
leoane said:
Hi All,
Please I have a similar issue and have been looking out for a solution. Anyone who has an answer kindly help me out here: Just finished with the installation and about to do other configuration. I did run the Firewall test and here was what I got. very disturbing:

Code: 
resolving 'stun-us.3cx.com'... done
resolving 'stun2.3cx.com'... done
resolving 'stun3.3cx.com'... done
resolving 'sip-alg-detector.3cx.com'... done
testing 3CX SIP Server... failed (How to resolve?)
stopping service... done
detecting SIP ALG... not detected
testing port 5060... full cone test failed (How to resolve?)
starting service... done
testing 3CX Tunneling Proxy... failed (How to resolve?)
stopping service... done
testing port 5090... full cone test failed (How to resolve?)
starting service... done
testing 3CX Media Server... failed (How to resolve?)
stopping service... done
testing ports [9000..9255]... failed (How to resolve?)
testing port 9000... full cone test failed (How to resolve?)
testing port 9001... full cone test failed (How to resolve?)
testing port 9002... full cone test failed (How to resolve?)
testing port 9003... full cone test failed (How to resolve?)
testing port 9004... full cone test failed (How to resolve?)
testing port 9005... full cone test failed (How to resolve?)
testing port 9006... full cone test failed (How to resolve?)
testing port 9007... full cone test failed (How to resolve?)
testing port 9008... full cone test failed (How to resolve?)
testing port 9009... full cone test failed (How to resolve?)
testing port 9056... full cone test failed (How to resolve?)
testing port 9057... full cone test failed (How to resolve?)
testing port 9058... full cone test failed (How to resolve?)
testing port 9059... full cone test failed (How to resolve?)
testing port 9060... full cone test failed (How to resolve?)
testing port 9061... full cone test failed (How to resolve?)
.
.
testing port 9132... full cone test failed (How to resolve?)
testing port 9133... full cone test failed (How to resolve?)
testing port 9134... full cone test failed (How to resolve?)
testing port 9135... full cone test failed (How to resolve?)
testing port 9136... full cone test failed (How to resolve?)
testing port 9137... full cone test failed (How to resolve?)
testing port 9138... full cone test failed (How to resolve?)
testing port 9139... full cone test failed (How to resolve?)
testing port 9140... full cone test failed (How to resolve?)
testing port 9141... full cone test failed (How to resolve?)
testing port 9142... full cone test failed (How to resolve?)
testing port 9143... full cone test failed (How to resolve?)
testing port 9144... full cone test failed (How to resolve?)
testing port 9145... full cone test failed (How to resolve?)
testing port 9146... full cone test failed (How to resolve?)
testing port 9147... full cone test failed (How to resolve?)
testing port 9197... full cone test failed (How to resolve?)
testing port 9198... full cone test failed (How to resolve?)
testing port 9199... full cone test failed (How to resolve?)
testing port 9200... full cone test failed (How to resolve?)
testing port 9201... full cone test failed (How to resolve?)
testing port 9202... full cone test failed (How to resolve?)
testing port 9252... full cone test failed (How to resolve?)
testing port 9253... full cone test failed (How to resolve?)
testing port 9254... full cone test failed (How to resolve?)
testing port 9255... full cone test failed (How to resolve?)
starting service... done

Tried to resolve it: Turned off the SIP ALG and port forwarded these ranges /numbers to the 3CX server - Port 5000 - 5100 Protocol = Both; Port 9000 - 9500, Protocol = UDP and Port 443, Protocol = TCP

Also, I did make configure Port Trigger with the same values in above:

I need assistance from anyone who could kindly do that for me.

Thanks
Click to expand...
 
@leoane

What make/ model router are you using?
 
leejor said:
Does that router connect to the same 3Cx server that fails from the other location?

Something, somewhere, has changed to cause the site to begin failing. Were any software/firmware upgrades done (automatically?). Could someone have changed a firewall setting/network configuration without your knowledge? Could it be something that changed at your providers end?

I find that "things; don't just "stop working", without a reason. It doesn't take much of a change to cause a problem. you have to use process of elimination to narrow down which end, and what is causing the problem.

The "caller is forbidden" message may have something to do with a setting against an extension. Does it keep cropping up?
Click to expand...


thank you already it's working properly now. all ports now configured correctly and firewall checker showing green sign for all services. its ok now
thank you
 
  • Like
Reactions: YiannisH_3CX
leoane said:
Hi All,
Please I have a similar issue and have been looking out for a solution. Anyone who has an answer kindly help me out here: Just finished with the installation and about to do other configuration. I did run the Firewall test and here was what I got. very disturbing:

Code: 
resolving 'stun-us.3cx.com'... done
resolving 'stun2.3cx.com'... done
resolving 'stun3.3cx.com'... done
resolving 'sip-alg-detector.3cx.com'... done
testing 3CX SIP Server... failed (How to resolve?)
stopping service... done
detecting SIP ALG... not detected
testing port 5060... full cone test failed (How to resolve?)
starting service... done
testing 3CX Tunneling Proxy... failed (How to resolve?)
stopping service... done
testing port 5090... full cone test failed (How to resolve?)
starting service... done
testing 3CX Media Server... failed (How to resolve?)
stopping service... done
testing ports [9000..9255]... failed (How to resolve?)
testing port 9000... full cone test failed (How to resolve?)
testing port 9001... full cone test failed (How to resolve?)
testing port 9002... full cone test failed (How to resolve?)
testing port 9003... full cone test failed (How to resolve?)
testing port 9004... full cone test failed (How to resolve?)
testing port 9005... full cone test failed (How to resolve?)
testing port 9006... full cone test failed (How to resolve?)
testing port 9007... full cone test failed (How to resolve?)
testing port 9008... full cone test failed (How to resolve?)
testing port 9009... full cone test failed (How to resolve?)
testing port 9056... full cone test failed (How to resolve?)
testing port 9057... full cone test failed (How to resolve?)
testing port 9058... full cone test failed (How to resolve?)
testing port 9059... full cone test failed (How to resolve?)
testing port 9060... full cone test failed (How to resolve?)
testing port 9061... full cone test failed (How to resolve?)
.
.
testing port 9132... full cone test failed (How to resolve?)
testing port 9133... full cone test failed (How to resolve?)
testing port 9134... full cone test failed (How to resolve?)
testing port 9135... full cone test failed (How to resolve?)
testing port 9136... full cone test failed (How to resolve?)
testing port 9137... full cone test failed (How to resolve?)
testing port 9138... full cone test failed (How to resolve?)
testing port 9139... full cone test failed (How to resolve?)
testing port 9140... full cone test failed (How to resolve?)
testing port 9141... full cone test failed (How to resolve?)
testing port 9142... full cone test failed (How to resolve?)
testing port 9143... full cone test failed (How to resolve?)
testing port 9144... full cone test failed (How to resolve?)
testing port 9145... full cone test failed (How to resolve?)
testing port 9146... full cone test failed (How to resolve?)
testing port 9147... full cone test failed (How to resolve?)
testing port 9197... full cone test failed (How to resolve?)
testing port 9198... full cone test failed (How to resolve?)
testing port 9199... full cone test failed (How to resolve?)
testing port 9200... full cone test failed (How to resolve?)
testing port 9201... full cone test failed (How to resolve?)
testing port 9202... full cone test failed (How to resolve?)
testing port 9252... full cone test failed (How to resolve?)
testing port 9253... full cone test failed (How to resolve?)
testing port 9254... full cone test failed (How to resolve?)
testing port 9255... full cone test failed (How to resolve?)
starting service... done

Tried to resolve it: Turned off the SIP ALG and port forwarded these ranges /numbers to the 3CX server - Port 5000 - 5100 Protocol = Both; Port 9000 - 9500, Protocol = UDP and Port 443, Protocol = TCP

Also, I did make configure Port Trigger with the same values in above:

I need assistance from anyone who could kindly do that for me.

Thanks
Click to expand...

send u the router model that you are using in ur LAN.
 
Dear Emad,
can we contact with you we have the same issue . and we need to know how you resolve it. we are in Egypt 01095608400
 

Attachments

  • 111111.png
    111111.png
    10 KB · Views: 12
  • Like
Reactions: Network Emad
econ said:
Dear Emad,
can we contact with you we have the same issue . and we need to know how you resolve it. we are in Egypt 01095608400
Click to expand...

you are welcome any time
econ said:
Dear Emad,
can we contact with you we have the same issue . and we need to know how you resolve it. we are in Egypt 01095608400
Click to expand...


ok i'll try to contact with you today afternoon send me ur WhatsApp number.
 
the same No. i mentioned in the post
 
Please use the personal message functionality to share personal info. Do not share them in public forums.
 
Which model Arris? it would appear that some have built in ATAs, which may very cause port conflicts with 3CX.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,880
Messages
589,533
Members
164,733
Latest member
HLISolutions
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom