Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Trouble registering VOIP provider

Discussion in '3CX Phone System - General' started by vale, May 20, 2008.

Thread Status:
Not open for further replies.
  1. vale

    Joined:
    Nov 2, 2007
    Messages:
    9
    Likes Received:
    0
    Hey there everyone.

    I am currently trying to register my sipgate account with my 3CX server. This was working a while ago but I came into work one day to find that the server will no longer register the line with sipgate. I have tried over and over to get this going. I have confirmed that all the ports are open and the firewall tests report success. There are no errors in my logs to suggest something is wrong.

    When the server tries to register the line the server logs just state that the line is unregistered, logs are below:

    13:06:41.033 LineMgr::eek:nRegUpdAor Unregistered line: L:500(Sipgate)
    13:06:41.033 ClientRegs::eek:nRequestRetry Registration attempt for L:500(Sipgate) is scheduled in 60 sec.
    13:05:28.474 LineMgr::eek:nRegUpdAor Unregistered line: L:500(Sipgate)
    13:05:28.474 ClientRegs::eek:nRequestRetry Registration attempt for L:500(Sipgate) is scheduled in 40 sec.
    13:04:36.085 LineMgr::eek:nRegUpdAor Unregistered line: L:500(Sipgate)
    13:04:36.085 ClientRegs::eek:nRequestRetry Registration attempt for L:500(Sipgate) is scheduled in 20 sec.
    13:04:03.930 ClientRegs::Register [CM504003]: Sent registration request for 500@Sipgate
    13:04:03.290 CallMgr::eek:nAddIPs IP(s) added:[192.168.111.4]
    13:03:59.306 ClientRegs::Register [CM504003]: Sent registration request for 500@Sipgate
    13:03:58.993 ExtnCfg::updateContact [CM504001]: Ext.208: new contact is registered. Contact(s): [sip:208@192.168.111.208:5060;transport=udp/208]
    13:03:58.665 FaxCfg::updateContact [CM504008]: Fax Service: registered as sip:888@3CXPhoneSystem with contact sip:888@192.168.111.4:5100;user=phone
    13:03:58.337 StunClient::process [CM506002]: Resolved SIP external IP:port (222.111.22.11:5060) on Transport 192.168.111.4:5060
    13:03:58.274 ListenConnect SL: connected ics2:0/VoiceBoxManagerService at [ics2]/VoiceBoxManagerService
    13:03:58.274 IVRConnected [CM501004]: Connected: IVR Service
    13:03:58.274 ListenConnect SL: connected ics2:5483/IVRServer at [ics2]/IVRServer
    13:03:58.196 StunClient::eek:nInitTests [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 217.10.79.2:3478 over Transport 192.168.111.4:5060
    13:03:54.275 MediaServerConnected [CM112000] Media Server is connected
    13:03:54.275 ListenConnect SL: connected ics2:0/MediaServer at [ics2]/MediaServer
    13:03:53.900 DBA [CM501003]: Connected: Database
    13:03:53.556 CallMgr::findLocalIPs [CM501006]: Default Local IP address: [192.168.111.4]
    13:03:53.540 CallCtrl::thread [CM501007]: *** Started Calls Controller thread ***
    13:03:53.212 CallMgr::Initialize [CM501002]: Version: 5.0.3790.0
    13:03:53.212 CallMgr::Initialize [CM501001]: Start 3CX PhoneSystem Call Manager
    13:03:53.212 LoadLicenceInfo [CM501010]: License Info: Load Failed

    I'm not sure what the cause of this is. I am running a ISA firewall on SBS server 2003 premium. The 3CX pbx is running on server 2003 elsewhere on the network. I have used wireshark to determine that the registration requests are leaving the network but I don't seem to get anything back. I have tried registering a different VOIP provider (freespeech) with also no success.

    Can anyone offer me any help on the matter??

    Thanks very much.

    James.
     
  2. coelhopsi

    Joined:
    May 7, 2008
    Messages:
    84
    Likes Received:
    0
    ISA Server is kind of troublesome regarding the port mapping needed for SIP (http://www.3cx.com/support/isa-server.html). I don't believe this is related, since the port mapping that ISA would cause trouble is not related to registration. However, did this problem start after installing the ISA server? Is it possible for you to completely disable the ISA server to test if registration then succeeds?
     
  3. vale

    Joined:
    Nov 2, 2007
    Messages:
    9
    Likes Received:
    0
    The ISA server has always been present and it was working at one point, its unusual that it decided to stop working. I could maybe put the 3CX server into the DMZ on my router and by pass the ISA server altogether.
     
  4. coelhopsi

    Joined:
    May 7, 2008
    Messages:
    84
    Likes Received:
    0
    If possible, try to put the server in the DMZ just to test if it works and isolate the problem.
     
  5. vale

    Joined:
    Nov 2, 2007
    Messages:
    9
    Likes Received:
    0
    Hey there.

    Time for a bit of a update. I have now got my 3CX server in the DMZ, it has fixed the issues I was having with the firewall and all tests seem to be passing with out any issues but I still cant seem to register my SIPGate account on the server. The servers logs are below:

    11:12:12.236 LineMgr::eek:nRegUpdAor Unregistered line: L:500(Sipgate)
    11:12:12.236 ClientRegs::eek:nRequestRetry Registration of L:500(Sipgate) has failed, attempt to repeat is scheduled in 600 sec.
    11:11:18.317 ListenConnect SL: connected ics2:0/PHPExtension_0 at [ics2]/PHPExtension_0
    11:10:51.943 LineMgr::eek:nRegUpdAor Unregistered line: L:500(Sipgate)
    11:10:51.943 ClientRegs::eek:nRequestRetry Registration attempt for L:500(Sipgate) is scheduled in 80 sec.
    11:09:51.493 LineMgr::eek:nRegUpdAor Unregistered line: L:500(Sipgate)
    11:09:51.493 ClientRegs::eek:nRequestRetry Registration attempt for L:500(Sipgate) is scheduled in 60 sec.
    11:09:11.136 LineMgr::eek:nRegUpdAor Unregistered line: L:500(Sipgate)
    11:09:11.136 ClientRegs::eek:nRequestRetry Registration attempt for L:500(Sipgate) is scheduled in 40 sec.
    11:08:50.824 LineMgr::eek:nRegUpdAor Unregistered line: L:500(Sipgate)
    11:08:50.824 ClientRegs::eek:nRequestRetry Registration attempt for L:500(Sipgate) is scheduled in 20 sec.
    11:08:50.668 ClientRegs::Register [CM504003]: Sent registration request for 500@Sipgate
    11:08:50.262 CallMgr::eek:nAddIPs IP(s) added:[192.168.222.11]
    11:08:48.731 ClientRegs::Register [CM504003]: Sent registration request for 500@Sipgate
    11:08:48.403 StunClient::process [CM506002]: Resolved SIP external IP:port (222.111.22.11:5060) on Transport 192.168.222.11:5060
    11:08:48.246 StunClient::eek:nInitTests [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 75.101.138.128:3478 over Transport 192.168.222.11:5060
    11:08:40.778 ListenConnect SL: connected ics2:0/VoiceBoxManagerService at [ics2]/VoiceBoxManagerService
    11:08:40.778 IVRConnected [CM501004]: Connected: IVR Service
    11:08:40.778 ListenConnect SL: connected ics2:5483/IVRServer at [ics2]/IVRServer
    11:08:40.778 MediaServerConnected [CM112000] Media Server is connected
    11:08:40.778 ListenConnect SL: connected ics2:0/MediaServer at [ics2]/MediaServer
    11:08:40.387 DBA [CM501003]: Connected: Database
    11:08:40.341 CallMgr::findLocalIPs [CM501006]: Default Local IP address: [192.168.222.11]
    11:08:40.341 CallCtrl::thread [CM501007]: *** Started Calls Controller thread ***
    11:08:40.169 CallMgr::Initialize [CM501002]: Version: 5.0.3790.0
    11:08:40.169 CallMgr::Initialize [CM501001]: Start 3CX PhoneSystem Call Manager
    11:08:40.169 LoadLicenceInfo [CM501010]: License Info: Load Failed

    It then just constantly tries to register the voip line (500).

    Could sipgate have blocked my account details due to my server trying to register so often? Or is something else wrong that I am not seeing?
     
  6. vale

    Joined:
    Nov 2, 2007
    Messages:
    9
    Likes Received:
    0
    Also I would just like to mention that I am using the 3CX stun server and not the sipgate stun sever.
     
  7. vale

    Joined:
    Nov 2, 2007
    Messages:
    9
    Likes Received:
    0
    Another little update.

    I have also added another voip provider (voiptalk) to the system and that is also displaying the same problems. I am wondering if the problem could be that demon is blocking the traffic on port 5060? Has anyone had any issues with this before?
     
  8. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    You should use 5 digit long virtual extension numbers for lines. I.e. 10500 instead of 500.
    Also, it would be better to upgrade 5.0 to at least 5.1.4150, or even V6 beta.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. vale

    Joined:
    Nov 2, 2007
    Messages:
    9
    Likes Received:
    0
    I have seemed to rectified the issue I was having now. I believe it was a combination of issues.

    If anyone is interested. Here is was I did below:

    First off I changed to my spare router and placed my sbs server into the DMZ on that router. I believe there is a firmware issue on my current router with the DMZ.

    Next I created a access rule for outgoing sip calls which the ports 9000-9015, 5060 and 3478 in my ISA Firewall. Directed from anywhere internally on my network to the out side world.
    I then creted a server publishing rule to allow incoming data on ports 9000-9015, 5060 and 3478 in my ISA Firewall. This was directed from the outside world directly to my 3CX server IP address.

    These firewall entries allow my 3CX server to recieve and send data on these ports through a ISA firewall. I also enabled non-sequental RTP ports on the 3CX server as it is reccomended for ISA firewalls.

    I also upgraded my 3CX server to the latest version(5.1). Everything now seems to work correctly.

    I would like to thank everyone who posted on my thread to help me with my issue.

    James.
     
  10. Anonymous

    Anonymous Guest

    Hi James,

    glad to hear you solved your problem. I noticed that you are using ISA as your firewall - can you please advise if you have encountered any issues with ISA and 3CX? Also, would it be possible for you to supply us with further information as to how you created the access rules and the publishing rules since I have more than 50 clients which use ISA?

    Regards,

    Jonathan
     
Thread Status:
Not open for further replies.