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.

power outage

Discussion in '3CX Phone System - General' started by apan28, Apr 8, 2013.

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

    Joined:
    Apr 8, 2013
    Messages:
    4
    Likes Received:
    0
    Good morning to all. After each power outage, all phones have a red color (Not registered). Had happened before, when I called the man that he did the system installation. He fixed it by doing something to the files of the program and not through the software. This technique however is expensive and I want to know if anyone can help me do this alone. thank you
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,113
    Likes Received:
    329
    How long did you wait? The sets have been told by 3CX to re-register every 30 minutes. If 3CX restarts, then it could be waiting up to 30 minutes for all of the sets to re-register.

    You can ...

    Turn off, then on, all of the sets/ATAs (after 3CX has re-started), causing them to re-register immediately.

    Or

    Buy a UPS for the PC running 3CX (highly recommended)


    If that doesn't sound like the issue you are experiencing, then you need to provide ore detail about your set-up.
     
  3. apan28

    Joined:
    Apr 8, 2013
    Messages:
    4
    Likes Received:
    0
    Thank you for the quick reply. here is the server activity log

    21:00:33.303 [CM506002]: Resolved SIP external IP:port ([ V4 79.103.97.237:5060 UDP target domain=unspecified mFlowKey=0 ]) on Transport [ V4 192.168.10.71:5060 UDP target domain=unspecified mFlowKey=0 ]
    21:00:33.127 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.71:5060 UDP target domain=unspecified mFlowKey=0 ]
    21:00:33.026 IP(s) added:[192.168.10.71]
    21:00:22.925 IP(s) removed:[192.168.10.70]
    20:57:58.932 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    20:37:58.431 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    20:17:58.385 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    19:57:58.384 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    19:37:57.793 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    19:17:57.475 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    18:57:57.399 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    18:37:56.910 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    18:17:56.583 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    17:57:56.559 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    17:37:56.184 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    17:17:55.894 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    16:57:55.802 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    16:37:55.242 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    16:17:55.008 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    15:57:55.003 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    15:37:54.678 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    15:17:54.618 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    14:57:54.584 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    14:37:54.250 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    14:18:04.082 IP(s) added:[192.168.10.70]
    14:18:00.992 [CM504001]: Ext.*1: new contact is registered. Contact(s): [sip:*1@127.0.0.1:40000;rinstance=f483bf4efd9e9f26/*1]
    14:18:00.991 [CM504001]: Ext.*0: new contact is registered. Contact(s): [sip:*0@127.0.0.1:40000;rinstance=de6223d750f4d835/*0]
    14:18:00.883 [CM504001]: Ext.*777: new contact is registered. Contact(s): [sip:*777@127.0.0.1:40000;rinstance=bac589aeeb31bb98/*777]
    14:18:00.640 [CM504001]: Ext.EndCall: new contact is registered. Contact(s): [sip:EndCall@127.0.0.1:40600;rinstance=35d43c4c5010b8a9/EndCall]
    14:18:00.639 [CM504001]: Ext.999: new contact is registered. Contact(s): [sip:999@127.0.0.1:40600;rinstance=d26c34845142634e/999]
    14:17:57.445 [CM102001]: Authentication failed for SipReq: REGISTER 192.168.69.112 tid=ab43c7273e0c5732 cseq=REGISTER contact=DialCode@127.0.0.1:5488 / 2 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
    14:17:55.890 [EC100007]: External application is connected: application:3cx-HP:0/QueueManager local:127.0.0.1:5482 remote:127.0.0.1:49168
    14:17:55.576 [CM504008]: Fax Service: registered as sip:888@192.168.10.70:5060 with contact sip:888@192.168.10.70:5100;user=phone
    14:17:55.009 [EC200002]: Media server is connected: application:3cx-HP:0/MediaServer local:127.0.0.1:5482 remote:127.0.0.1:49166
    14:17:54.931 [EC200005]: Parking Orbit server is connected: application:3cx-HP:0/3CXParkOrbit local:127.0.0.1:5482 remote:127.0.0.1:49165
    14:17:54.851 [EC200004]: IVR server is connected: application:3cx-HP:0/IVRServer local:127.0.0.1:5482 remote:127.0.0.1:49164
    14:17:54.726 [EC200006]: Conference server is connected: application:3cx-HP:0/3CXConferenceRoom local:127.0.0.1:5482 remote:127.0.0.1:49160
    14:17:54.414 [CM506002]: Resolved SIP external IP:port ([ V4 79.103.97.237:5060 UDP target domain=unspecified mFlowKey=0 ]) on Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    14:17:54.196 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 192.198.87.70:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.10.70:5060 UDP target domain=unspecified mFlowKey=0 ]
    14:17:54.086 Failed to obtain short path name for [C:\ProgramData\3CX\Bin\Cert]
    14:17:54.086 [CM501006]: Default Local IP address: [192.168.10.70]
    14:17:54.086 [CM501002]: Version: 10.0.23053.0
    14:17:54.086 [CM501001]: Start 3CX PhoneSystem Call Manager
    14:17:54.086 [CM501010]: License Info: Load Failed - Error licence Licence: 27 System: 2
    14:17:54.008 [CM501007]: *** Started Calls Controller thread ***
    14:17:54.008 [EC200001]: Configuration server is connected: application:3cx-HP:5485/DBProvider local:127.0.0.1:49158 remote:127.0.0.1:5485
     
  4. apan28

    Joined:
    Apr 8, 2013
    Messages:
    4
    Likes Received:
    0
    I was waiting for 3 days.. What is the sets/ATAS that you said. You help is very much appreciated
     
  5. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,113
    Likes Received:
    329
    I assumed that your problem was that after a 3CX power-up, the sets (phones) are not showing as registered. You haven't stated what type of equipment you are using.

    I do see a problem here..

     
  6. apan28

    Joined:
    Apr 8, 2013
    Messages:
    4
    Likes Received:
    0
    I really cannot understand what i have to do. I'm new to that. if you can tell me step by step what i have to do, it's very important for me. My friend you have free week in my hotel (http://www.studiosolympia.gr)!! lol
     
  7. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,113
    Likes Received:
    329
    I've explained what I think is going on, but I'm not really certain if we are on the same page.

    First of all, invest in a small (or large) UPS (Uninterruptable Power Supply), if the AC keeps going off all the time. It could keep the PC running for a half hour depending on the size (current draw) of the PC and the battery capacity on the UPS. It would at least give someone enough time to shut the PC down properly until the power came back on. A UPS can help protect the PC from power surges, and lightening strikes. If you have things such as Modems, routers, switches,gateways or ATA's, you might want to invest in a second unit for those.

    You have not said what type of phones you are using. Are they VoIP sets, or ATA's with standard phones?

    When the 3CX PC is re-started, wait until the PBX program is running, then power up the phones or ATA's, they should then register as long as all network components are also powered back up.
     
  8. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    This looks very suspicious:

    If your phones are set up to register against 192.168.10.70, than it is why they can not register.
    Can you explain why it has .70 IP on start, and than it is replaced with .71 IP?

    Also, note, that your license has not been loaded. License file is absent.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. 3397premier

    Joined:
    Apr 2, 2012
    Messages:
    43
    Likes Received:
    1
    I would definitely look at your license to verify it is active and registered and check the IP blacklist as well. If your phones are being blacklisted then that will keep them from registering.

    **Just as a side note even though I am not sure of your setup, make sure if you have a secondary NIC on your phone server that it is disabled or at least not priority one for the network connection.
     
  10. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,575
    Likes Received:
    304
    I had an instance the other day where I plugged an old phone into the system - but its original extension had been disabled/deleted.
    Eventually (a couple minutes), this phone became blacklisted... it took me a while to figure this out... and when I tried to have it register the new extension it wouldn't. I finally saw in the logs it was blacklisted.

    Does it make sense to put this range (10.0.3.x) into the Blacklist set as ALLOW so this does not happen again - or is that unsecure ?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,113
    Likes Received:
    329
    10.0.x.x is a private IP range. Unless you have some suspicions about people that use your LAN, then I don't see an issue. Someone else may have another opinion.
     
  12. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,575
    Likes Received:
    304
    yes, I do not suspect anyone off the street would walk into the building and try to hack our system from the inside... :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. eagle2

    eagle2 Well-Known Member

    Joined:
    Apr 27, 2011
    Messages:
    1,085
    Likes Received:
    11
    Blacklisting internal addresses is extremely important security feature, otherwise your system could be hacked from infected PC inside your LAN. I don't advise you white-listing the local LAN.

    BR
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.