Loosing extensions after system reboot

Discussion in '3CX Phone System - General' started by tazz, Sep 25, 2007.

  1. tazz

    tazz New Member

    Joined:
    Sep 12, 2007
    Messages:
    124
    Likes Received:
    0
    Any thoughts on why intentions will fall off line after a system reboot? The status lights show in the red. Most importantly why can I not get them to come back on line? I’ve tried deleting them and reinstalling them several times. Strange
     
  2. Mirzab

    Mirzab Member

    Joined:
    Jul 22, 2007
    Messages:
    400
    Likes Received:
    0
    My extensions are analog via 3 PAP2s. If I reboot the server, the PAP2s are usually part way through the 3600 sec refresh interval. I have to reboot these devices after the Server if I wish all extensions green immediately. I expect IP phones are basically the same setup. Just waiting for the 3600 sec interval should restore green across the board.
     
  3. tazz

    tazz New Member

    Joined:
    Sep 12, 2007
    Messages:
    124
    Likes Received:
    0
    I have a combination of IP Phones and Ata's. I've tried that sequence of Power cycling as well
     
  4. Mirzab

    Mirzab Member

    Joined:
    Jul 22, 2007
    Messages:
    400
    Likes Received:
    0
    Take a look at the logs after reboot. Extensions must initiate registration with 3CX, and 3CX must initiate registration with VoIP providers & Gateways. So for extensions, if issue is with 3CX, you should see the registration attempt and subsequent error. No logs, most likely no attempt by the extension device.
     
  5. tazz

    tazz New Member

    Joined:
    Sep 12, 2007
    Messages:
    124
    Likes Received:
    0
    Forgive me but where do I locte these logs?
     
  6. tazz

    tazz New Member

    Joined:
    Sep 12, 2007
    Messages:
    124
    Likes Received:
    0
    This is what I get:18:26:27.031 ServRegs::checkExpiration [CM113000] Registration for sip:1001@192.168.1.104 has expired
     
  7. Mirzab

    Mirzab Member

    Joined:
    Jul 22, 2007
    Messages:
    400
    Likes Received:
    0
    Yep, that is the log :)

    I guess you are using 4 digit extensions. You need to check the extension device 1001 at the same time and see where it is on its renewal cycle. For example on a PAP2 you can see this info from the Web Admin page. Maybe try reducing the renewal interval.
     
  8. tazz

    tazz New Member

    Joined:
    Sep 12, 2007
    Messages:
    124
    Likes Received:
    0
    I have Grandstream products. Could you be possibly speaking of
    keep-alive interval: (in seconds, default 20 seconds)

    This is a copy & Paste

    Why did it work before until reboot?
     
  9. Mirzab

    Mirzab Member

    Joined:
    Jul 22, 2007
    Messages:
    400
    Likes Received:
    0
    Hmmm. I think maybe I got this worng :oops: . After you did a reboot your extensions no longer register period? Or after a reboot they register after some time? If it is that they are not registering at all since reboot I would suggest rebooting again, also reboot Extension Devices after, then copy & paste logs here. Other option, backup server, uninstall, reboot, reinstall, restore from backup - not in manual or recommended process, just my way. And doesn't work always either :oops: .

    Go with option one first :)
     
  10. tazz

    tazz New Member

    Joined:
    Sep 12, 2007
    Messages:
    124
    Likes Received:
    0
    17:26.187 ListenConnect [CM114000] SL: connected Wal-Com:0/PHPExtension_0 at [Wal-Com:0]/PHPExtension_0
    19:16:45.281 ClientRegs::eek:nSuccess [CM113005] Registration of sip:wal-com@sip.voipcheap.co.uk is successful
    19:16:44.031 ClientRegs::eek:nSuccess [CM113005] Registration of sip:wal-com@sip.voipcheap.co.uk is successful
    19:16:43.765 ClientRegs::eek:nSuccess [CM113005] Registration of sip:255007@fwd.pulver.com is successful
    19:16:43.750 ClientRegs::eek:nSuccess [CM113005] Registration of sip:5154890843@sipnumber.net is successful
    19:16:43.750 ClientRegs::eek:nSuccess [CM113005] Registration of sip:255007@fwd.pulver.com is successful
    19:16:43.703 ClientRegs::eek:nSuccess [CM113005] Registration of sip:3192282237@freedigits.net is successful
    19:16:43.687 ClientRegs::eek:nSuccess [CM113005] Registration of sip:16027484133@i2telecom.com is successful
    19:16:43.687 ClientRegs::eek:nSuccess [CM113005] Registration of sip:3192282237@freedigits.net is successful
    19:16:43.687 ClientRegs::eek:nSuccess [CM113005] Registration of sip:5637734435@freedigits.net is successful
    19:16:43.640 ExtLine::Register [CM110004] Send registration for <sip:255007@fwd.pulver.com>
    19:16:43.640 ExtLine::Register [CM110001] Use External IP for device line registration DN='10004' device='Free World Dialup'
    19:16:43.593 ExtLine::Register [CM110004] Send registration for <sip:5154890843@sipnumber.net>
    19:16:43.593 ExtLine::Register [CM110001] Use External IP for device line registration DN='10005' device='Free Digits 515'
    19:16:43.546 ExtLine::Register [CM110004] Send registration for <sip:16027484133@i2telecom.com>
    19:16:43.546 ExtLine::Register [CM110001] Use External IP for device line registration DN='10003' device='Voice Stick'
    19:16:43.515 ExtLine::Register [CM110004] Send registration for <sip:3192282237@freedigits.net>
    19:16:43.515 ExtLine::Register [CM110001] Use External IP for device line registration DN='10002' device='Free Digits 319'
    19:16:43.500 ClientRegs::eek:nSuccess [CM113005] Registration of sip:5154890843@sipnumber.net is successful
    19:16:43.500 ClientRegs::eek:nSuccess [CM113005] Registration of sip:5637734435@freedigits.net is successful
    19:16:43.453 ExtLine::Register [CM110004] Send registration for <sip:5637734435@freedigits.net>
    19:16:43.453 ExtLine::Register [CM110001] Use External IP for device line registration DN='10001' device='Free Digits'
    19:16:43.421 ExtLine::Register [CM110004] Send registration for <sip:wal-com@sip.voipcheap.co.uk>
    19:16:43.421 ExtLine::Register [CM110001] Use External IP for device line registration DN='10000' device='Voip Cheap'
    19:16:43.421 ClientRegs::eek:nSuccess [CM113005] Registration of sip:16027484133@i2telecom.com is successful
    19:16:43.140 ExtLine::Register [CM110004] Send registration for <sip:255007@fwd.pulver.com>
    19:16:43.140 ExtLine::Register [CM110001] Use External IP for device line registration DN='10004' device='Free World Dialup'
    19:16:43.093 ExtLine::Register [CM110004] Send registration for <sip:5154890843@sipnumber.net>
    19:16:43.093 ExtLine::Register [CM110001] Use External IP for device line registration DN='10005' device='Free Digits 515'
    19:16:43.046 ExtLine::Register [CM110004] Send registration for <sip:16027484133@i2telecom.com>
    19:16:43.046 ExtLine::Register [CM110001] Use External IP for device line registration DN='10003' device='Voice Stick'
    19:16:43.000 ExtLine::Register [CM110004] Send registration for <sip:3192282237@freedigits.net>
    19:16:43.000 ExtLine::Register [CM110001] Use External IP for device line registration DN='10002' device='Free Digits 319'
    19:16:42.953 ExtLine::Register [CM110004] Send registration for <sip:5637734435@freedigits.net>
    19:16:42.953 ExtLine::Register [CM110001] Use External IP for device line registration DN='10001' device='Free Digits'
    19:16:40.906 ExtLine::Register [CM110004] Send registration for <sip:wal-com@sip.voipcheap.co.uk>
    19:16:40.906 ExtLine::Register [CM110001] Use External IP for device line registration DN='10000' device='Voip Cheap'
    19:16:40.843 StunClient::process [CM115002] STUN resolved external IP=12.214.12.191:5060 by server 64.69.76.23
    19:16:34.671 StunClient::process [CM115002] STUN resolved external IP=12.214.12.191:5060 by server 64.69.76.23
    19:16:34.421 StunClient::process [CM115001] Send initial STUN request to 64.69.76.23
    19:16:34.234 CallMgr::Stack::thread [CM106001] ** Enter Stack Loop **
    19:16:34.140 CallMgr::DumThread::thread [CM100004] ** Enter DUM Thread **
    19:16:33.390 MediaServerConnected [CM112000] Media Server is connected
    19:16:33.390 ListenConnect [CM114000] SL: connected Wal-Com:0/MediaServer at [Wal-Com:0]/MediaServer
    19:16:33.296 DBA [CM109000] ** Database connection Ok **
    19:16:33.203 IVRConnected [CM111000] IVR Server is connected
    19:16:33.203 ListenConnect [CM114000] SL: connected Wal-Com:5483/IVRServer at [Wal-Com:5483]/IVRServer
    19:16:32.703 CallMgr::Stack::Initialize [CM106000] ** Adding transports **
    19:16:32.703 CallMgr::Initialize [CM100003] ** Initializing SIP stack **
    19:16:32.703 CallMgr::Initialize [CM100002] Default Local IP address: 192.168.1.104:5060
    19:16:32.687 ListenConnect [CM114000] SL: connected Wal-Com:0/VoiceBoxManagerService at [Wal-Com:0]/VoiceBoxManagerService
    19:16:32.453 CallMgr::Initialize [CM100001] Version: 3.1.2434.0
    19:16:32.453 CallMgr::Initialize [CM100000] Start 3CX PhoneSystem Call Manager
    19:16:32.453 LoadLicenceInfo [CM100008] Licence loading error
     
  11. Mirzab

    Mirzab Member

    Joined:
    Jul 22, 2007
    Messages:
    400
    Likes Received:
    0
    Looks like you have 5 "Lines" and 3CX has registered them OK, logs look fine. Nothing in the logs about extensions trying to register, its as if they don't exist. 3CX isn't responsible for registering extensions, the extension devices must perform this task. Any chance Server has its own firewall and its blocking needed ports? They are all on the same LAN I presume?
     
  12. tazz

    tazz New Member

    Joined:
    Sep 12, 2007
    Messages:
    124
    Likes Received:
    0
    I did system restore. That worked. WHY did I have to do this? This is a bummer
     
  13. RobLloyd

    RobLloyd Member

    Joined:
    Oct 13, 2006
    Messages:
    488
    Likes Received:
    0
    Check the firewall settings. If you don't have all the ports open then you have issues with devices registering.

     

Share This Page