Re-registration problem

Discussion in '3CX Phone System - General' started by levbe, Mar 16, 2010.

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

    Joined:
    Apr 27, 2008
    Messages:
    33
    Likes Received:
    3
    I use 3CX since version 5 without any major issues.
    Since a few weeks now, incoming calls fail.
    Firewall configs seems to be correct (correct port mapping and access rules on a Cisco router).
    After some checks, i've noticed that 3cx do not re-register to the voip providers after the expiration delay (set to 600 sec.)

    I use the last version (8,0,10824) but i've the same problem with the last version 7.
    My provider is 3StarsNet (Belgium) which works fine for more than two years now.

    Here are my logs :

    Code:
    10:58:07.968  Active calls counted toward license limit: []
    10:57:35.968  Active calls counted toward license limit: []
    10:57:03.968  Active calls counted toward license limit: []
    10:56:31.968  Active calls counted toward license limit: []
    10:55:59.968  Active calls counted toward license limit: []
    10:55:48.312  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 94.228.101.70:3478 over Transport 192.168.255.5:5060
    10:55:27.968  Active calls counted toward license limit: []
    10:54:55.968  Active calls counted toward license limit: []
    10:54:23.968  Active calls counted toward license limit: []
    10:53:51.968  Active calls counted toward license limit: []
    10:53:19.968  Active calls counted toward license limit: []
    10:52:47.968  Active calls counted toward license limit: []
    10:52:15.968  Active calls counted toward license limit: []
    10:51:43.968  Active calls counted toward license limit: []
    10:51:11.968  Active calls counted toward license limit: []
    10:50:39.968  Active calls counted toward license limit: []
    10:50:33.453  [CM504001]: Ext.410: new contact is registered. Contact(s): [sip:410@192.168.255.41:5060;user=phone/410]
    10:50:07.968  Active calls counted toward license limit: []
    10:49:35.968  Active calls counted toward license limit: []
    10:49:03.968  Active calls counted toward license limit: []
    10:48:31.968  Active calls counted toward license limit: []
    10:47:59.968  Active calls counted toward license limit: []
    10:47:27.968  Active calls counted toward license limit: []
    10:46:55.968  Active calls counted toward license limit: []
    10:46:23.968  Active calls counted toward license limit: []
    10:46:08.890  [CM504001]: Ext.420: new contact is registered. Contact(s): [sip:420@192.168.255.42:5060/420]
    10:45:51.968  Active calls counted toward license limit: []
    10:45:19.968  Active calls counted toward license limit: []
    10:44:47.968  Active calls counted toward license limit: []
    10:44:15.968  Active calls counted toward license limit: []
    10:43:43.968  Active calls counted toward license limit: []
    10:43:11.968  Active calls counted toward license limit: []
    10:42:39.968  Active calls counted toward license limit: []
    10:42:07.968  Active calls counted toward license limit: []
    10:41:35.968  Active calls counted toward license limit: []
    10:41:03.968  Active calls counted toward license limit: []
    10:40:31.968  Active calls counted toward license limit: []
    10:39:59.968  Active calls counted toward license limit: []
    10:39:27.968  Active calls counted toward license limit: []
    10:38:55.968  Active calls counted toward license limit: []
    10:38:23.968  Active calls counted toward license limit: []
    10:37:51.968  Active calls counted toward license limit: []
    10:37:19.968  Active calls counted toward license limit: []
    10:36:47.968  Active calls counted toward license limit: []
    10:36:34.609  [CM504001]: Ext.584: new contact is registered. Contact(s): [sip:584@192.168.255.40:5060/584]
    10:36:33.171  [CM504001]: Ext.484: new contact is registered. Contact(s): [sip:484@192.168.255.40:5060/484]
    10:36:32.890  [CM504001]: Ext.400: new contact is registered. Contact(s): [sip:400@192.168.255.40:5060/400]
    10:36:30.062  [CM504001]: Ext.MakeCall: new contact is registered. Contact(s): [sip:MakeCall@127.0.0.1:40600;rinstance=3c9a62379750b86b/MakeCall]
    10:36:30.046  [CM504001]: Ext.IVRForward: new contact is registered. Contact(s): [sip:IVRForward@127.0.0.1:40600;rinstance=4c4c523643053fa2/IVRForward]
    10:36:30.031  [CM504001]: Ext.EndCall: new contact is registered. Contact(s): [sip:EndCall@127.0.0.1:40600;rinstance=246aa7b2cd41f382/EndCall]
    10:36:30.015  [CM504001]: Ext.801: new contact is registered. Contact(s): [sip:801@127.0.0.1:40600;rinstance=6bde41681766b0c5/801]
    10:36:30.000  [CM504001]: Ext.800: new contact is registered. Contact(s): [sip:800@127.0.0.1:40600;rinstance=bbc2b3018d901fa7/800]
    10:36:29.953  [CM504001]: Ext.999: new contact is registered. Contact(s): [sip:999@127.0.0.1:40600;rinstance=4b0480631c002ec3/999]
    10:36:17.921  Active calls counted toward license limit: []
    10:36:00.546  [CM504001]: Ext.701: new contact is registered. Contact(s): [sip:701@127.0.0.1:40300;rinstance=54ca93bccb335ad6/701]
    10:36:00.546  [CM504001]: Ext.700: new contact is registered. Contact(s): [sip:700@127.0.0.1:40300;rinstance=7973d999510cba92/700]
    10:36:00.343  [CM504001]: Ext.*1: new contact is registered. Contact(s): [sip:*1@127.0.0.1:40000;rinstance=63ec1641a80a8430/*1]
    10:36:00.343  [CM504001]: Ext.*0: new contact is registered. Contact(s): [sip:*0@127.0.0.1:40000;rinstance=a8b8fb5c1c1ce7d8/*0]
    10:35:57.218  [CM504004]: Registration succeeded for: 10001@3STARS_065
    10:35:57.125  [CM504004]: Registration succeeded for: 10000@3STARS_02
    10:35:55.734  [CM504003]: Sent registration request for 10001@3STARS_065
    10:35:55.734  [CM504003]: Sent registration request for 10000@3STARS_02
    10:35:55.609  IP(s) added:[192.168.255.5]
    10:35:51.843  [EC200004]: IVR server is connected:    application:sx280:0/IVRServer    local:127.0.0.1:5482    remote:127.0.0.1:1344
    10:35:51.828  [EC200005]: Parking Orbit server is connected:    application:sx280:0/3CXParkOrbit    local:127.0.0.1:5482    remote:127.0.0.1:1345
    10:35:51.078  [EC200006]: Conference server is connected:    application:sx280:0/3CXConferenceRoom    local:127.0.0.1:5482    remote:127.0.0.1:1342
    10:35:47.890  *** Connected to sx280:5482/CallManager at 127.0.0.1:5482 ***
    10:35:47.890  [EC200002]: Media server is connected:    application:sx280:0/MediaServer    local:127.0.0.1:5482    remote:127.0.0.1:1340
    10:35:47.687  [CM506002]: Resolved SIP external IP:port (91.176.147.176:5060) on Transport 192.168.255.5:5060
    10:35:47.546  Active calls counted toward license limit: []
    10:35:47.171  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 94.228.101.70:3478 over Transport 192.168.255.5:5060
    10:35:45.546  Failed to obtain short path name for [C:\Documents and Settings\All Users\Application Data\3CX\Bin\Cert]
    10:35:45.546  [CM501006]: Default Local IP address: [192.168.255.5]
    10:35:45.531  [CM501007]: *** Started Calls Controller thread ***
    10:35:45.531  [CM501002]: Version: 8.0.10708.0
    10:35:45.359  [EC200001]: Configuration server is connected:    application:sx280:5485/DBProvider    local:127.0.0.1:1339    remote:127.0.0.1:5485
    When we start-up 3cx, stun resolution is correct, provider registration occurs.
    Stun resolution (set to 1200 sec) is ok every 20min, but no new registration [CM504003] every 600 sec, as it's set.
    At the end of the day, voip lines are not reachable (incoming calls fail) but trunks status remain green.
    We have to force PBX to re-register manually to solve the problem.

    3CX is turning on a WinXP with nothing else on it (no anti-virus, firewall or other softs)... just a DynDNS service to update public IP address (for other applications in our lan, not for 3cx). Does this interfere ?

    Thanks a lot for any advices.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    Why do you think there's no re-registration requests? They are not logged (by design).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. levbe

    Joined:
    Apr 27, 2008
    Messages:
    33
    Likes Received:
    3
    Well, if i start 3cx in the morning, in the evening my voip lines become unreachable and remain until i refresh manually voip provider registration (or restart 3cx).

    So i thought it might be a re-registration problem.

    What can i investigate to solve this ?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    Most reliable way to investigate is to run Wireshark capture and see if it has periodic REGISTER requests from PBX to VoIP provider. Also, if you specified a host of provider as FQDN -- make sure it is resolvable all the time (i.e. there's no failed DNS requests in capture).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    Ah, and another thing we discovered recently: some providers ignores requested registration time and return response with time of their choice. I.e. you may want to re-register every 600 sec, and outgoing REGISTER will have Expiry: 600, but in answer you may get 'expired=1800' or something else. In that case PBX respects answer from provider and will try to re-registered in time specified in the answer, i.e. in our example in half hour.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. levbe

    Joined:
    Apr 27, 2008
    Messages:
    33
    Likes Received:
    3
    Ok, thanks, i'll check all these and come back with results.

    My provider says that there is no need to re-register (???).

    When incoming calls fail, there is no lines in 3cx logs, provider status is still green and i can make outgoing calls without any difficulty. So, i thing, the problem is at the provider and not in my 3cx configs. I wrote to them and waiting for answers.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    3CX PBX renews registrations silently. If (re)registration fails - you will see corresponding message in the log.
    If PBX receives request from outside and cannot process it then it explains reasons in the log.

    If network layer fails to deliver request to PBX host, then it requires further investigations and should be done on the lower layer (router/switch). The duty of PBX starts after request has arrived on the host where 3cx pbx is running. (can be verified using wireshark)

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. cloidhamer

    Joined:
    Jan 30, 2009
    Messages:
    27
    Likes Received:
    0
    I had this exact same issue. I found that it was due to my firewall timing out the connection. I changed the time out for the rule to a value greater than the re-registration and have had no issues.

    Craig
     
  9. FBW

    FBW New Member

    Joined:
    Nov 19, 2008
    Messages:
    108
    Likes Received:
    0
    We use 3StarsNet as a SIP provider as well but only for outgoing calls. Incoming calls are treated by another Belgian SIP provider.
    We have seen in the last month that sometimes outbound calls are routed over our second route, and this on a nearly daily basis. This means, according to me, that at that momont we have a registration problem at 3Stars.
    So maybe you might want to do some tests with a secondary provider. Of course you won't be able to test the incoming calls given the fact that you depend on them for that.
    Do you run into the same problems on outgoing calls?

    Diederik
    http://www.fbw.be
    [​IMG]
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. levbe

    Joined:
    Apr 27, 2008
    Messages:
    33
    Likes Received:
    3
    Hi Diederik,

    Nice to see another 3starsnet user here, it might be helpful.
    No, i've not noticed any outgoing problems, i'll investigate.
    Have you asked anything from 3stars and did you get any answer ? Because, in my side, no answer for my daily questions about my issue.

    Lev
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. levbe

    Joined:
    Apr 27, 2008
    Messages:
    33
    Likes Received:
    3
    Sorry, i'm really beginner so i don't follow you exactly. Can you explain step by step what do you mean and how i can check and fix it ?

    Thanks,
    lev
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Try to do following:
    Open the list of "Global options" and tick "Enable Keepalives". Restart 3CX Phone system service.

    Caution: it may cause other type of problems. Please don't do it in environment where connection with your VoIP provider is critical.

    Thanks

    P.S. It can fix the "fantasticality" of behavior which is peculiar to your firewall/NAT device/network gateway...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. FBW

    FBW New Member

    Joined:
    Nov 19, 2008
    Messages:
    108
    Likes Received:
    0
    We have opened no issue at 3Stars ecause we can still fall back on our other SIP provider. Of course if you depend on them for incoming calls you might want to open a ticket with them. Pitty though you don't get an answer. Are you 3Stars reseller? Otherwise, we might open a ticket for you.

    FYI, we have 'Keepalives' enabled in 3CX (like support suggests). Maybe that might help you.
    Diederik
    http://www.fbw.be
    [​IMG]
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. levbe

    Joined:
    Apr 27, 2008
    Messages:
    33
    Likes Received:
    3
    Thanks SY, but i've already tried 'keep alive' option without any results.
    I definitively think that it's something wrong with my provider.
    I can still make outgoing calls but no incoming calls arrives at all now, even after restarting 3cx and re-register...
    I'll set up wireshark this week-end and check what's going on.

    Diederik, no i'm not 3stars reseller.
    I'm in contact with Lieve (i think it's Lieve), usually i get quick answer but not this time...
    I come back to you after my wireshark tests.
    Whats your other voip provider ?
    Thanks a lot,

    Lev
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. FBW

    FBW New Member

    Joined:
    Nov 19, 2008
    Messages:
    108
    Likes Received:
    0
    Hi Lev,

    Lieve should indeed be the contact person at 3Stars.
    We use Weepee as alternative provider. If you want you can get a free € 2 test account via our site:
    http://www.fbw.be/Francais/Pages/voip.aspx
    Unfortunately the subscription part is only in Dutch. I'll add some explanation in French on our site to help you out :wink:

    Hope this helps you along a bit.
    Diederik
    http://www.fbw.be
    [​IMG]
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. levbe

    Joined:
    Apr 27, 2008
    Messages:
    33
    Likes Received:
    3
    I made some tests this week-end.

    First of all, the pc running 3cx (with WinXP Pro Edition, SP3) runs only one other application ; the DynDns Updater (with his specific service). This is my only PC which is on all day and night that's the reason why i put this service on it. But it's nothing to do with 3cx use.

    So, first I turned of this DynDns Updater service and since the situation became quite better. Now, 3CX register at startup to my Voip provider and remain reachable for the next 36 hours (my external IP changes every 36 hours). Silent re-registration occurs every 600 sec as configured and seems to be ok (following the logs in wireshark).

    But, when my IP changes, and after the new address is resolved by STUN, a new re-registration occurs (and Voip providers server answers OK) but from that time, i'm not reachable or in a very random way. Incoming calls fails but outgoing calls works. After many external IP changes, sometimes anything works sometime not.

    I've tried all this with and without the "keep alive" option, and i've got the same results.

    Can someone advise me what to do next ? How can I investigate deeply this situation ?

    Thanks,
    Lev
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. mposse

    Joined:
    Feb 9, 2010
    Messages:
    7
    Likes Received:
    0
    Hello
    Having the same problem, working with Gafachi.
    I've got a registration that last for about 600 to 1800 seconds, but when the registration expires, I get disconnected.
    On the System Console, the port is still green though.
    I have chanced the frequency of the registration and have keep alives enabled.
    Have anyone found a solution to this problem?

    Thanks!!!
     
  18. levbe

    Joined:
    Apr 27, 2008
    Messages:
    33
    Likes Received:
    3
    Problem solved by SP4 update :

    "Fixed :
    Re-registration of VoIP providers when STUN resolved address has changed"
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.