SIP provider registration problems 503 & 408

[haywardi]

Hi,

Can someone help me please.

I'm in the process of trying to find a new IPPBX provider and downloaded the FREE version of this software to evaluate it.

Everything went really well and my phone (a Seimens C475IP) registered without a problem and so did my SIP provider Draytel.
Well I say the SIP provider went well, because it did for Friday & Saturday.

However, I checked the status on 3cx today and it said I wasn't registered with my sip provider. (server log below).

Initially I thought there was a problem with the SIP provider, so I went back to my original IPPBX to see if it could register, IT COULD. I then tried the SIP handset, IT COULD.

So I came back to 3CX and it still couldn't register.....

My first thought, reboot the server- NO EFFECT still couldn't register.
Next I deleted the second SIP provider - Draytel still couldn't register.
Deleted Draytel and re-entered - Still wouldn't register.

Now what do I do? DrayTel holds my company telephone number and it doesn't appear to be the problem....

HELP!

Kind Regards
Iain

 

[haywardi]

Oops, forgot to add the server log

21:32:45.985 [CM504002]: Ext.100: a contact is unregistered. Contact(s): []
21:27:46.526 [CM504007]: Next attempt to register 10000@Draytel is scheduled in 10 minutes
21:27:46.526 [CM504005]: Registration failed for: 10000@Draytel; Cause: 408 Request Timeout; internal
21:25:09.886 [CM504003]: Sent registration request for 10000@Draytel
21:18:56.192 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.1.11:5060
21:15:09.833 [CM504007]: Next attempt to register 10000@Draytel is scheduled in 10 minutes
21:15:09.833 [CM504005]: Registration failed for: 10000@Draytel; Cause: 408 Request Timeout; internal
21:12:53.286 [CM504005]: Registration failed for: 10000@Draytel; Cause: 408 Request Timeout; internal
21:12:33.146 [CM504003]: Sent registration request for 10000@Draytel
21:12:00.932 [CM504005]: Registration failed for: 10000@Draytel; Cause: 408 Request Timeout; internal
21:11:28.718 [CM504003]: Sent registration request for 10000@Draytel
21:10:00.661 [CM504003]: Sent registration request for 10000@Draytel
21:09:11.877 [CM504007]: Next attempt to register 10000@Draytel is scheduled in 10 minutes
21:09:11.865 [CM504005]: Registration failed for: 10000@Draytel; Cause: 408 Request Timeout; internal
21:06:56.333 [CM504005]: Registration failed for: 10000@Draytel; Cause: 503 Service Unavailable; warning: ; internal
21:06:35.218 [CM504003]: Sent registration request for 10000@Draytel
21:05:46.724 [CM504003]: Sent registration request for 10000@Draytel
21:01:13.776 [CM504005]: Registration failed for: 10001@draytel; Cause: 408 Request Timeout; internal
20:58:56.352 [CM504003]: Sent registration request for 10001@draytel
20:58:56.243 [CM506002]: Resolved SIP external IPort (91.85.219.192:38532) on Transport 192.168.1.11:5060

 

[davidbenwell]

Hi Lain

Welcome to the forum.

Could you run the firewall checker and let me know if all passes ok?

within the 3CX console, stop the 3cx server and then goto

Settings - Firewall Checker

if you get any errors, please post them back on here.

 

[abc123]

This is going to be a firewall problem.

A 408 message is saying that it timed out. This probably means that you are sending the request but not getting the response.

Your logs say you are using STUN. And NAT. This is not ideal for a PBX. Sometimes you cannot avoid NAT but you can port forward. If you go to your gateway firewall and do some port forwarding (also make sure you were not port forwarding to your old IPPBX by mistake) to your new 3cx PBX and preferably get a static ip it will work. The port forward rather than port translate (which is what STUN is really doing) is much cleaner and no chance of a mistake. Forward the ports you need (5060, 5090 for tunnel, 9000 - 9049 UDP for audio, 10000 for fax etc.) that are in the manual to the PBX and you should register with no problems and have good audio too.

 

[haywardi]

Thank you for your help.

The firewall was the problem, I disabled it when I first installed hence why everything worked, but then I rebooted the server (nothing to do with the pbx) and the firewall restarted and blocked all the ports arrrg, but all my fault!

Feeling somewhat sheepish now baaaar.
Iain

 

[davidbenwell]

pleased its all working. hope you enjoy the benefits of 3CX