New posts

Toggle sidebar Toggle sidebar

V20 Update 10 Alpha Learn more

3cx connetion problems (request timeout)

Thread starter netural
Start date Jul 30, 2007

Status: Not open for further replies.

netural

Jul 30, 2007

#1

hello,

i try to get my 3xc installation working, cause we want move in our company from normal calling system to 3cx ip calling system.

i tried 2 different provider (sipgate, sipcall) but both dont work with my configuration.

i named my external ip adress directly cuz i had an "couldnt resolve ip adress error", but now it also dont work.

the port 5060 is successful forwarded and open (i tried to access iis temporarely on that port from external and that worked) - so i dont have any idea what else i could do.

are there any other ports i have to forward/open for the pure registration process?? atm i only care about 5060.

i get following error messages:

12:36:27.584 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:27.584 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:26.647 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:26.647 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:25.756 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:25.756 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:25.443 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:25.443 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:25.443 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:25.443 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:25.443 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:25.443 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:25.443 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:25.443 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:25.443 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:25.443 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:25.443 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:25.443 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:25.443 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:25.443 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:25.443 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:25.443 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:23.803 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:23.803 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:23.787 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:23.787 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:23.787 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:23.787 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:22.521 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:22.521 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:22.209 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:22.209 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:22.209 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:22.209 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:22.209 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:22.209 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:22.209 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:22.209 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:22.209 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:22.209 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:20.943 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:20.943 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:20.928 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:20.928 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:20.912 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:20.912 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:20.896 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:20.896 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:20.881 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:20.881 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:20.818 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:20.818 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:20.818 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:20.818 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:20.818 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:20.818 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:20.818 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:20.818 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:20.818 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:20.818 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:20.490 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:20.490 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:20.162 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:20.162 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:20.146 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:20.146 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:36:16.052 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:16.052 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:14.177 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:14.177 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:14.162 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:14.162 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:14.146 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:14.146 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:10.677 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:10.677 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:10.662 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:10.662 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:10.646 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:10.646 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:10.630 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:10.630 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:10.615 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:10.615 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:09.615 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:09.615 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:04.302 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:04.302 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:36:04.286 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:04.286 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:36:04.271 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:04.271 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:36:04.255 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:36:04.255 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:36:02.646 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.646 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:02.646 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.646 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:02.646 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.646 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:02.646 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.646 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:02.646 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.646 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:02.646 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.646 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:02.646 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.646 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:02.333 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.333 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:02.333 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.333 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:02.021 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.021 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:02.021 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.021 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:02.021 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.021 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:02.021 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.021 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:02.021 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:02.021 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:01.396 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:01.396 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:00.770 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:00.770 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:00.770 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:00.770 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:00.770 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:00.770 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:36:00.770 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:36:00.770 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:35:59.786 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:59.786 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:59.770 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:59.770 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:57.567 ClientRegs:

nFailure [CM113010] Next registration will be attempted in 10 minutes
12:35:57.567 ClientRegs:

nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Request Timeout
12:35:55.364 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:55.364 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:53.786 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:53.786 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:53.458 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:53.458 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:53.130 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:53.130 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:35:53.114 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:53.114 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:35:53.098 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:53.098 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:35:53.083 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:53.083 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:35:53.083 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:53.083 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:35:53.067 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:53.067 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:35:53.051 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:53.051 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:35:53.051 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:53.051 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:35:51.661 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:51.661 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:35:50.317 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:50.317 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10001' device='SIPGATE'
12:35:49.973 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:49.973 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:49.973 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:49.973 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:49.958 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:49.958 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:49.942 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:49.942 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:49.926 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:49.926 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:48.614 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:48.614 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:48.598 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:48.598 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:48.582 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:48.582 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:48.567 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:48.567 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'
12:35:48.551 ExtLine::Register [CM110004] Send registration for <sip:[email protected]>
12:35:48.551 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='SIPCALL'

archie

3CX Support

Jul 30, 2007

#2

If you have "couldnt resolve ip adress error" -- this means, that port 5060 IS NOT forwarded correctly, or you have a symmetric NAT. 3CX can not work behind symmetric NAT, and I suppose even providing specific IP for registration wouldn't help in this case.

netural

Jul 30, 2007

#3

what is symetric nat? we have a server/gateway with one official ip adress (what is all userss external ip) and every user have a internal ip adress. the ip of server on which the 3cx service is running is used for the port forward of 5060 UDP/TCP. And the forword work definitely, cuz when i use 5060 for any other service like webserver it work perfect.

so...

archie

3CX Support

Jul 30, 2007

#4

No, webserver won't fit. You try to connect with SIP phone

I did. And what did I see? Sip Express router meets me there and refuse registration. So, I didn't get to 3CX PBX. It may be a cause of problem.

Symmetric NAT makes binding IP

ort <-> IP

ort, and for each IP on remote end it will make different port mapping on local end.

netural

Jul 30, 2007

#5

i cant follow your answer. internal connects work, 3 testuser are connected with their ip phone to the 3cx software. but the 3cx software can not connect with a sip service provider like sipgate.

tahs my problem

netural

Jul 30, 2007

#6

now i rebooted the server, and it seems he dont connect. i dont know why, the SIP Provider is in the system but he dont try to register.

all what happen is following:

14:00:06.655 ServRegs:

nAdd [CM113002] Registered: Ext.035
13:56:08.935 ListenConnect [CM114000] SL: connected NLNZ3CX1:0/PHPExtension_0 at [NLNZ3CX1]/PHPExtension_0
13:49:06.953 ListenConnect [CM114000] SL: connected NLNZ3CX1:0/VoiceBoxManagerService at [NLNZ3CX1]/VoiceBoxManagerService
13:49:05.562 MediaServerConnected [CM112000] Media Server is connected
13:49:05.562 ListenConnect [CM114000] SL: connected NLNZ3CX1:0/MediaServer at [NLNZ3CX1]/MediaServer
13:49:05.046 CallMgr::Stack::thread [CM106001] ** Enter Stack Loop **
13:49:05.031 CallMgr:

umThread::thread [CM100004] ** Enter DUM Thread **
13:49:05.015 DBA [CM109000] ** Database connection Ok **
13:49:04.984 CallMgr::Stack::Initialize [CM106000] ** Adding transports **
13:49:04.984 CallMgr::Initialize [CM100003] ** Initializing SIP stack **
13:49:04.984 CallMgr::Initialize [CM100002] Default Local IP address: 10.28.200.50:5060
13:49:04.890 IVRConnected [CM111000] IVR Server is connected
13:49:04.890 ListenConnect [CM114000] SL: connected NLNZ3CX1:5483/IVRServer at [NLNZ3CX1]/IVRServer
13:49:04.640 CallMgr::Initialize [CM100001] Version: 3.0.2328.0
13:49:04.640 CallMgr::Initialize [CM100000] Start 3CX PhoneSystem Call Manager
13:49:01.546 LoadLicenceInfo [CM100008] Licence loading error

archie

3CX Support

Jul 30, 2007

#7

netural said:
we have a server/gateway with one official ip adress (what is all userss external ip) and every user have a internal ip adress.

I think here's the problem. You have Sip Express router installed on that server. And I suspect it fiddles with SIP packets it receives. You should set it up correctly, or disable it (at least to check).

netural

Jul 30, 2007

#8

uhhhhhhhhhhh .... ^^

what is sip express router? and how can i disable it? OO i just installed the standard installation of 3CX and added the provider and few clients for test.

but how can it be that now no error appear and it still dont work? it just dont register? oo

and btw how u could u know if i have SIP EXPRESS ROUTER installed? i didnt post my ip here O.O

archie

3CX Support

Jul 30, 2007

#9

Isn't it your IP: 212.117.200.148??

If not, than I actually don't know about your system. I've just tried to connect to it with SIP phone and see responces, and responses was from express router, not 3CX.

archie

3CX Support

Jul 30, 2007

#10

Yeah, I'm sorry. It's my fault, by some reason I thought that is your IP, but it isn't, I see now.

So, than I suggest to try and set up STUN resolution for your 3CX system.

netural

Jul 30, 2007

#11

STUN only resolve the external ip? then its same when i just type it manual in the system. but i still get the same error.

pah, i will try another system - maybe its just not compatible. anyway thanks for your help!

archie

3CX Support

Jul 30, 2007

#12

BTW, try to ping STUN server you're using from the console. May be it just not running atm.

netural

Jul 30, 2007

#13

i tried now different stun servers. there appear no error that that stun servers dont work, but it seems he cant resolve ip. but why no error then? all ports for stun are definitely open and forwarded. TT

14:54:32.281 ExtLine::Register [CM010002] Line DN='10000' device='sipgate' can not be registered. External IP isn't resolved.
14:54:32.281 ExtLine::Register [CM110001] Use External IP for device line registration DN='10000' device='sipgate'
14:54:31.874 ListenConnect [CM114000] SL: connected NLNZ3CX1:0/PHPExtension_0 at [NLNZ3CX1]/PHPExtension_0
14:54:18.499 ListenConnect [CM114000] SL: connected NLNZ3CX1:0/VoiceBoxManagerService at [NLNZ3CX1]/VoiceBoxManagerService
14:54:18.499 IVRConnected [CM111000] IVR Server is connected
14:54:18.499 ListenConnect [CM114000] SL: connected NLNZ3CX1:5483/IVRServer at [NLNZ3CX1]/IVRServer
14:54:17.890 CallMgr::Stack::thread [CM106001] ** Enter Stack Loop **
14:54:14.499 MediaServerConnected [CM112000] Media Server is connected
14:54:14.499 ListenConnect [CM114000] SL: connected NLNZ3CX1:0/MediaServer at [NLNZ3CX1]/MediaServer
14:54:14.437 CallMgr:

umThread::thread [CM100004] ** Enter DUM Thread **
14:54:14.421 DBA [CM109000] ** Database connection Ok **
14:54:14.390 CallMgr::Stack::Initialize [CM106000] ** Adding transports **
14:54:14.390 CallMgr::Initialize [CM100003] ** Initializing SIP stack **
14:54:14.390 CallMgr::Initialize [CM100002] Default Local IP address: 10.28.200.50:5060
14:54:14.233 CallMgr::Initialize [CM100001] Version: 3.0.2328.0
14:54:14.233 CallMgr::Initialize [CM100000] Start 3CX PhoneSystem Call Manager
14:54:14.218 LoadLicenceInfo [CM100008] Licence loading error

archie

3CX Support

Jul 30, 2007

#14

Really strange. Try to look into 3CXPhoneSystem.trace.log.
Also, check your settings for 'Timeout time for STUN response (ms)' in General settings/STUN server options.

netural

Jul 30, 2007

#15

timeout is: 2000
and in that log appear nothing about stun or sipgate

archie

3CX Support

Jul 30, 2007

#16

I don't know, it never happens before. May be you should try to reboot the PC.

Status: Not open for further replies.

Share:

Facebook X LinkedIn Reddit WhatsApp Email Link

Latest Posts

What are the exact rules governing the archival of 3CX Chat Messages?
- Latest: AndrewSotiris
- 3 minutes ago
SMS
Google Workspace Storage Integration Issue
- Latest: necdetkt
- 13 minutes ago
Phone System / PBX
Forwarding Originator's Caller ID
- Latest: HIS-Nhenry
- Today at 4:38 PM
Phone System / PBX
Adding a 3CX Customer Service AI Agent Into Your Workflow
- Latest: UCMUserAZ
- Today at 4:33 PM
Product Releases
Solved v20 inbound caller id includes info we can't seem to change?
- Latest: stechtn
- Today at 4:25 PM
Phone System / PBX

Forum statistics

Threads: 111,911

Messages: 589,703

Members: 164,780

Latest member: JoeMiller

Top Bottom