sipgate.co.uk registration timeout (constant)

Discussion in '3CX Phone System - General' started by AlecM, Aug 24, 2007.

  1. AlecM

    Joined:
    Aug 24, 2007
    Messages:
    52
    Likes Received:
    0
    Hi.
    3CX Version: 3.1.2434.0 (Free).
    Installed on a test PC: XP Pro SP2, 2 x P3-650's, 512Mb RAM.

    I have a Sipgate.co.uk VoIP account.
    On the 3CX box I have registered this VoIP line using the Sipgate pre-configured template, added my sipgate credentials, and added the outgoing dialing rule #, with mask r.

    I have only seen the line "register" once - and only for a few seconds. The rest of the time it is "unregistered".

    Example of what the 3CX server log indicates (I've edited out my actual number):

    16:43:39.011 ClientRegs::eek:nRequestRetry [CM113008] Registration attempt for Ln:10000@SipGate 0845 xxx xxxx is scheduled in 120 sec.
    16:43:38.700 ClientRegs::eek:nFailure [CM113010] Next registration will be attempted in 10 minutes
    16:43:38.700 ClientRegs::eek:nFailure [CM113006] Registration of sip:xxxxxxx@sipgate.co.uk has failed; reason=Request Timeout

    We have a SonicWALL 2040 Pro firewall, which has been configured to allow SIP (a prebuilt rule), plus I have added the 3CX ports of 9000-9499 to this rule.

    I have added the SIP DNS entries for the 3CX server to my Active Directory.

    Can anyone guide me as to what might be causing the failure of the registration? (I have posted on the Sipgate help about this as well).

    Thanks for any help!
    Al
     
  2. AlecM

    Joined:
    Aug 24, 2007
    Messages:
    52
    Likes Received:
    0
    I should add the we have a 2Mb managed leased line (not ADSL or cable!), so our end of the connection should not be an issue.
     
  3. AlecM

    Joined:
    Aug 24, 2007
    Messages:
    52
    Likes Received:
    0
    Another additonal note:
    After a reboot, the connection state remains unregistered, but in the running server status log, it is attempting to register almost constantly.

    I presume a successful registration is indicated by:

    17:35:22.943 ExtLine::Register [CM110004] Send registration for <sip:xxxxxxx@sipgate.co.uk>
    17:35:22.943 ExtLine::Register [CM110001] Use External IP for device line registration DN='10000' device='SipGate 0845 xxx xxxx'

    But this registration seems to fail immediately (lasting only a second or so), as the log updates a few seconds later and it's back to the Request Timeout message entry.

    Should the 3CX system be continually renewing the VoIP registration? I don't see anything about this in the system guide PDF.

    Thx
     
  4. gbarnes

    Joined:
    Aug 3, 2007
    Messages:
    83
    Likes Received:
    0
    sip

    Does your (firewall) sip rule include 5060?

    Do not have a proxy entry with sipgate. Leave blank.

    I use sipgate.co.uk and it works fine, using 5060, UDP ports 8000 - 8050, NO PROXY (ie blank) and register two-way calls.

    Try looking at the 5060 port, is that set in firewall and 3cx?

    Graeme.
     
  5. AlecM

    Joined:
    Aug 24, 2007
    Messages:
    52
    Likes Received:
    0
    sip

    Hi Graeme,

    Thanks for your feedback. Will double-check this when back in the office next week. I know the firewall includes 5060 as I specifically checked for that. But I did have to add custom rules for the UDP ports 9000-9499. I will perhaps have to check that they are bidirectional though....

    You say you're using ports 8000 - 8050. This seems to differ from the 3CX config documentation. Is this an undocumented setting, or a deliberate change on your behalf?

    Al
     
  6. gbarnes

    Joined:
    Aug 3, 2007
    Messages:
    83
    Likes Received:
    0
    9000 port

    I think 9000 is the default 3cx, no I just had these ports already in the firewall, so I changed 3cx.. Nothing to worry about!

    Do you have STUN set to give your real IP..

    You can use the 3cx or sipgate stun server.

    Let me know how you are doing?

    Graeme
     
  7. CreativeHubLtd

    Joined:
    Aug 15, 2007
    Messages:
    37
    Likes Received:
    0
    Hi AlecM

    I had some registration problems with Sipgate today, this is how I resolved the problem :

    "The only way I could get the Sipgate line registered was to change the setting in Line Management - Manage Gateways and Providers - Sipgate - Registration Settings - Which IP to use in 'Contact' field for registration: from External (STUN Resolved) to Both (external and internal) and the line now works fine ! "

    Hope this helps

    Kev
     
  8. AlecM

    Joined:
    Aug 24, 2007
    Messages:
    52
    Likes Received:
    0
    Sipgate registration

    Hi Kev,

    thanks for your post- that change of setting to the Contact registration seems to have helped for me as well. The (sipgate) VoIP line is now staying registered. Just have to figure out the correct outbound rules now!

    Am using the 3CX softphone for a trial, but it keeps coming back "protocol error, layer 2". If configured to use my sipgate account directly, it is quite happy, so seems it is something to do with the 3CX server config.

    Alec
     
  9. CreativeHubLtd

    Joined:
    Aug 15, 2007
    Messages:
    37
    Likes Received:
    0
    Hi Alec

    Glad I have helped with part of the problem, I never changed my outgoing rule, I used the default and it worked fine, this is how mine is configured :

    Rule Name : Outgoing rule for "Sipgate"
    Calls to Numbers starting with : 9
    VOIP Provider : Sipgate
    Transform mask : r

    I will download the 3CX softphone and try configuring it, I have used the SJPhone Softphone on my PDA without any problems. The extension you are configuring the softphone I assume is an internal extension ?

    Kev
     
  10. AlecM

    Joined:
    Aug 24, 2007
    Messages:
    52
    Likes Received:
    0
    3CX softphone

    Hi Kev,
    Yes, I've set the ssoftphone to register on an internal extension number (102 in my test case). this comes up with the green light for registered Ok. The 3CX server line status confirms this as well (along with the VoIP line registered now!).

    I think I still may have issues with the firewall rules. Although I think I've configured the VOIP rules for SIP, etc as required (including ports 5060, 9000-9499, etc, etc, etc), the firewall log is saying port 5060 udp connection is dropped.

    Example from log today (note USA date format):

    [Date/time Priority Category Message Source Destination Note]
    09/05/2007 12:11:05.224 Notice Network Access UDP packet dropped 217.10.79.23, 5060, X1 62.232.57.107, 6385, X1 UDP Port: 6385
    09/05/2007 12:09:55.080 Notice Network Access UDP packet dropped 217.10.79.23, 5060, X1 62.232.57.107, 5790, X1 UDP Port: 5790

    I have to confess that I'm absolutely no expert when it comes to the firewall! (SonicWALL 2040 Pro)

    Al
     
  11. CreativeHubLtd

    Joined:
    Aug 15, 2007
    Messages:
    37
    Likes Received:
    0
    Hi Alec

    I have configured the 3CX softphone without any problems as an internal extension on my LAN. In your last post both the IP addresses that you list from your firewall log are public IP addresses, is your 3CX server and your softphone extension on the same LAN or is there the internet and a firewall in the middle ?

    Kev
     
  12. AlecM

    Joined:
    Aug 24, 2007
    Messages:
    52
    Likes Received:
    0
    Hi Kev,

    The 3CX server and my PC using the softphone are on same LAN and subnet. In my tests, I'm simply trying to get the softphone to call my work mobile and vice-versa.

    At the moment, the mobile just gets a "line busy" tone. The softphone cancels dialling after approx 30 seconds. There are two different reasons given. As previously noted, the "protocol error layer 2" occurs, but now the most common is "102:Recovery on timer expiry", where 102 is my extension.

    To be thorough, I suppose I ought to add a second internal softphone installation and check I can call that extension, but at the moment I'm less concerned with that config. I would not expect the firewall to cause any issue in that case though, as the call should remain local to the 3CX server LAN.

    Al
     
  13. CreativeHubLtd

    Joined:
    Aug 15, 2007
    Messages:
    37
    Likes Received:
    0
    Hi Alec

    It would be worth setting up an additional softphone on the LAN just to test extension to extension calling.

    Can you send a snippet of the server log so I can see whats happening when you try to call your work mobile ?

    Are you able to recieve incoming calls to your extension from your work mobile ?

    Kev
     
  14. AlecM

    Joined:
    Aug 24, 2007
    Messages:
    52
    Likes Received:
    0
    Hi Kev,

    Checking the firewall log this morning, I have noted that there is a recurring process (frequency about 20 minutes) that is related. (I hadn't seen these before as the VOIP rule group wasn't originally being logged.)

    To answer your other question, no, my mobile calling to my sip number is getting a line busy tone, so I'm guessing any number trying to call it will get same result.

    Log extract 1 (VOIP filter):
    =========

    09/06/2007 09:21:07.576 Debug VOIP VoIP 10.0.0.22:5060 (SIP) Endpoint removed
    2 09/06/2007 09:17:01.768 Debug VOIP VoIP 10.0.0.22:5060 (SIP) 8677053@sipgate.co.uk Endpoint removed
    3 09/06/2007 09:16:33.192 Debug VOIP SIP Response 217.10.79.23, 5060, X1 10.0.0.22, 5060, X0 SIP REGISTER (401 Unauthorized) (8677053@sipgate.co.uk)
    4 09/06/2007 09:16:33.128 Warning VOIP SIP Register expiration exceeds configured Signaling inactivity time out 10.0.0.22, 5060, X0 217.10.79.23, 5060, X1 8677053@sipgate.co.uk using expiration of 3600 secs.
    5 09/06/2007 09:16:33.128 Debug VOIP SIP Request 10.0.0.22, 5060, X0 217.10.79.23, 5060, X1 SIP REGISTER (8677053@sipgate.co.uk)
    6 09/06/2007 09:16:07.832 Debug VOIP VoIP 10.0.0.22:5060 (SIP) Endpoint added


    And also, incoming UDP packets from port 5060 still being dropped.
    (X1 is our WAN interface with public IP on the firewall)
    ======

    09/06/2007 09:43:46.128 Notice Network Access UDP packet dropped 217.10.79.23, 5060, X1 62.232.57.107, 34656, X1 UDP Port: 34656
    4 09/06/2007 09:42:35.800 Notice Network Access UDP packet dropped 217.10.79.23, 5060, X1 62.232.57.107, 34656, X1 UDP Port: 34656
    ...
    09/06/2007 09:26:54.064 Notice Network Access UDP packet dropped 217.10.79.23, 5060, X1 62.232.57.107, 33986, X1 UDP Port: 33986


    I guess I'm going to have to spend more time with the firewall manual!
    It's annoying, as I'm certain I've got the rules set up, but I'm obviously missing something somewhere!

    The firewall allows configuration of service groups. It comes with a preconfigured VOIP service, to which I've added the 3CX UDP port range.
    The rules protocol grouping is below, with my custom entry appearing last in the list. Format is description, packet type, port range:

    VOIP

    H323 Call Signaling TCP 1720 1720
    H323 Gatekeeper Discovery UDP 1718 1718
    H323 Gatekeeper RAS UDP 1719 1719
    MGCP TCP TCP 2428 2428
    MGCP UDP UDP 2427 2427
    SIP UDP 5060 5061
    Skinny TCP 2000 2000
    T120 (Whiteboard+A43) TCP 1503 1503
    3CX Required UDP UDP 9000 9499

    There is a complementary higher-level grouping (created by the config wizard) that allows a server to host more than one set of services.

    3CX-SIP Services
    -> VOIP

    And the associated access rule that tells the firewall to route traffic matching the above protocol grouping to our internal 3CX server.

    Access Rules (WAN > LAN)
    Source, Destination, Service, Action, Users
    Any, WAN Primary IP, 3CX-SIP Services, Allow, All

    (Destination in this case means the incoming destination from Internet, from any external source)
     
  15. CreativeHubLtd

    Joined:
    Aug 15, 2007
    Messages:
    37
    Likes Received:
    0
    Hi Alec

    Sorry I haven't replied sooner, I think you are right some more time with the manual may be required, you are almost there, I will have a closer look through you logs later when I have more time.

    Kev
     
  16. CreativeHubLtd

    Joined:
    Aug 15, 2007
    Messages:
    37
    Likes Received:
    0
    Hi Alec

    Have you made any progress with this ?

    Kev
     
  17. AlecM

    Joined:
    Aug 24, 2007
    Messages:
    52
    Likes Received:
    0
    Hi Kev,

    Not as yet - have some other projects to get on with.

    I have progressed on the FXO side though - set up with a Grandstream GXW-4104, plus three Grandstream BT200 phones for a trial stage. This has all worked great - particularly in conjunction with Call Assistant to plug the gaps of the BT200 (primarily line and extension status).

    Will hopefully be returning to the Firewall config soon though and see if I can get that (hopefully last?) step sorted.

    I've been demonstrating the 3CX capabilities to my Directors and they are mighty impressed with it over our current (sometimes problematic and certainly restrictive) LG PBX, so hopefully will get more dedicated project time on it.

    I will post my progess!

    Al
     
  18. CreativeHubLtd

    Joined:
    Aug 15, 2007
    Messages:
    37
    Likes Received:
    0
    Hi Alec

    Glad you have progressed on the FXO side, I haven't really used that side much myself.

    I now have 3 Sipgate numbers working on my server, 2 x 0845 and a local std code and all is good.

    Let me know how you get on.

    Kev
     
  19. AlecM

    Joined:
    Aug 24, 2007
    Messages:
    52
    Likes Received:
    0
    Well I've made a small amount of progress.

    I can make calls out from 3CX through Sipgate to an external number - e.g. my mobile. (I would guess therefore that an outward SIP to SIP will work, but haven't tested this yet.)

    However, when I try the reverse path of an external number in to my Sipgate number, which should then route onwards to my 3CX server, I just get a line busy signal.

    I am sure this is the firewall settings, as I'm still seeing UDP packets being dropped. I have now posted on the SonicWALL forum in hope of guidance from someone more knowledgable on that kit.

    For complete coverage, I've pasted in below my firewall message, just in case anyone on this forum may be able to help.

    Al
     
  20. CreativeHubLtd

    Joined:
    Aug 15, 2007
    Messages:
    37
    Likes Received:
    0
    Hi Alec

    I am not suprised that you can make outgoing calls or that you have registered with Sipgate OK, as normally (I think) by default your firewall will allowing outgoing connections on any port.

    Here is a full list of my incoming firewall rules :
    VOIP - UDP - 5060-5062
    VOIP STUN - UDP - 3478
    SIPGATE STUN - UDP 10000
    VOIP LINES - UDP - 9000-9007

    Do you have any rules on the firewall that looks for port scans etc that say something like "if a port gets probed 5 times in 5 mins and it is not a port I have a firewall rule for then drop the packet or deny access" ?

    Kev
     

Share This Page