Registration

Discussion in '3CX Phone System - General' started by agnetman, Mar 11, 2009.

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

    Joined:
    Oct 2, 2007
    Messages:
    24
    Likes Received:
    0
    I have a 3CX PBX installed on a remote (very) Windows 2003 server that has been running fine for months, with 20 internal extensions and 2 outside VoIP lines. After restarting the 3CX services the 2 VoIP lines won't register, in fact they don't even attempt to register.

    The Windows firewall is turned off.

    A packet sniffer on the remote server shows there aren't even attempts to connect to the VoIP providers server.

    Any help or advice would be welcomed.

    Thanks.
     
  2. LeonidasG

    LeonidasG Support Team
    Staff Member 3CX Support

    Joined:
    Nov 19, 2008
    Messages:
    1,473
    Likes Received:
    94
    Even if you do this it still wont try to register? :p

    *attachment below*
     

    Attached Files:

    • aaa.JPG
      aaa.JPG
      File size:
      34.8 KB
      Views:
      2,115
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. agnetman

    Joined:
    Oct 2, 2007
    Messages:
    24
    Likes Received:
    0
    No matter what I try, forcing registration, restarting all of the 3CX services and restarting the server itself no attempt is made to register i.e. no packets are seen by the packet sniffer to the VoIP provider's server.
     
  4. LeonidasG

    LeonidasG Support Team
    Staff Member 3CX Support

    Joined:
    Nov 19, 2008
    Messages:
    1,473
    Likes Received:
    94
    I did a few tries to try and reproduce this though it's a bit hard.

    Try and Delete the Voip Provider and Re-Adding it, this should help.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. agnetman

    Joined:
    Oct 2, 2007
    Messages:
    24
    Likes Received:
    0
    Tried that as well and it makse no difference, there's still no attempt made to register. No packets are seen by Wireshark on the server or by the firewall.
     
  6. William400

    William400 Well-Known Member

    Joined:
    Aug 21, 2006
    Messages:
    1,005
    Likes Received:
    0
    Hi

    From the sounds of it you may have a STUN resolution issue which would generate the situation you are reporting.

    Can you please paste the Verbose logs of 3CX Server Status or the 3CXphonesystem.log file right after a machine restart please? This will allow us to confirm this.

    Also, if you are running V7.1 you may wish to try disabling of STUN. See points 2 and 4 of http://wiki.3cx.com/Home/voip-provider-configuration/general-voip-provider-config-guide to disable STUN within your current setup.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. agnetman

    Joined:
    Oct 2, 2007
    Messages:
    24
    Likes Received:
    0
    I'm having the log file sent to me.

    Stun is and always has been turned off, its never been needed and worked fine without it.

    How can I get around this? I delete and recreate VoIP provider settings but there's never any attempt to register.
     
  8. agnetman

    Joined:
    Oct 2, 2007
    Messages:
    24
    Likes Received:
    0
    Here's the detail from the 3CXPhoneSystem.log file after a resstart.


    15:28:08.421|.\CallMgr.cpp(1057)|Log2||LoadLicenceInfo:[CM501010]: License Info: Load Failed<br>
    15:28:09.203|.\SLServer.cpp(870)|Error1||??:Unknown system [DBProvider] tries to connect!<br>
    15:28:12.984|.\CallMgr.cpp(147)|Log2|CallManager|CallMgr::Initialize:[CM501001]: Start 3CX PhoneSystem Call Manager<br>
    15:28:12.984|.\CallMgr.cpp(148)|Log2|CallManager|CallMgr::Initialize:[CM501002]: Version: 7.0.4025.0<br>
    15:28:13.000|.\CallCtrl.cpp(21)|Log2||CallCtrl::thread:[CM501007]: *** Started Calls Controller thread ***<br>
    15:28:16.843|.\CallMgr.cpp(725)|Log2|CallManager|CallMgr::findLocalIPs:[CM501006]: Default Local IP address: [172.16.160.7]<br>
    15:28:39.984|.\CallMgr.cpp(849)|Log2|CallManager|CallMgr::eek:nAddIPs:IP(s) added:[172.16.160.7]<br>
    15:28:40.656|.\VExtMgr.cpp(78)|Log2|DataBase|FaxCfg::updateContact:[CM504008]: Fax Service: registered as sip:888@172.16.160.7:5060 with contact sip:888@172.16.160.7:5100;user=phone<br>
    15:28:45.640|.\MSInterface.cpp(734)|Log2||MediaServerConnected:[CM112000] Media Server is connected<br>
    15:29:27.281|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.*0: new contact is registered. Contact(s): [sip:*0@127.0.0.1:40000;rinstance=57f4abf092ce7e1e/*0]<br>
    15:29:27.421|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.*1: new contact is registered. Contact(s): [sip:*1@127.0.0.1:40000;rinstance=6087e6f37f8f764e/*1]<br>
    15:29:52.109|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.999: new contact is registered. Contact(s): [sip:999@127.0.0.1:40600;rinstance=72e82fd09dac0760/999]<br>
    15:33:40.718|.\VExtMgr.cpp(78)|Log2|DataBase|FaxCfg::updateContact:[CM504008]: Fax Service: registered as sip:888@172.16.160.7:5060 with contact sip:888@172.16.160.7:5100;user=phone<br>
    15:38:40.906|.\VExtMgr.cpp(78)|Log2|DataBase|FaxCfg::updateContact:[CM504008]: Fax Service: registered as sip:888@172.16.160.7:5060 with contact sip:888@172.16.160.7:5100;user=phone<br>
    15:40:15.687|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.808: new contact is registered. Contact(s): [sip:808@172.16.160.208:5060/808]<br>
    15:40:16.140|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.817: new contact is registered. Contact(s): [sip:817@172.16.160.217:5060/817]<br>
    15:40:16.203|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.806: new contact is registered. Contact(s): [sip:806@172.16.160.206:5060/806]<br>
    15:40:16.781|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.818: new contact is registered. Contact(s): [sip:818@172.16.160.218:5060/818]<br>
    15:40:20.390|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.802: new contact is registered. Contact(s): [sip:802@172.16.160.202:5060/802]<br>
    15:40:21.718|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.816: new contact is registered. Contact(s): [sip:816@172.16.160.216:5060/816]<br>
    15:40:27.250|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.815: new contact is registered. Contact(s): [sip:815@172.16.160.215:5060/815]<br>
    15:40:27.984|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.813: new contact is registered. Contact(s): [sip:813@172.16.160.213:5060/813]<br>
    15:40:28.968|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.805: new contact is registered. Contact(s): [sip:805@172.16.160.205:5060/805]<br>
    15:40:33.718|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.811: new contact is registered. Contact(s): [sip:811@172.16.160.211:5060/811]<br>
    15:40:34.296|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.814: new contact is registered. Contact(s): [sip:814@172.16.160.214:5060/814]<br>
    15:40:36.234|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.804: new contact is registered. Contact(s): [sip:804@172.16.160.204:5060/804]<br>
    15:40:36.671|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.807: new contact is registered. Contact(s): [sip:807@172.16.160.207:5060/807]<br>
    15:40:37.359|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.803: new contact is registered. Contact(s): [sip:803@172.16.160.203:5060/803]<br>
    15:40:37.421|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.820: new contact is registered. Contact(s): [sip:820@172.16.160.220:5060/820]<br>
    15:40:38.187|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.819: new contact is registered. Contact(s): [sip:819@172.16.160.219:5060/819]<br>
    15:42:06.093|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.801: new contact is registered. Contact(s): [sip:801@172.16.160.201:5060/801]<br>
    15:43:40.921|.\VExtMgr.cpp(78)|Log2|DataBase|FaxCfg::updateContact:[CM504008]: Fax Service: registered as sip:888@172.16.160.7:5060 with contact sip:888@172.16.160.7:5100;user=phone<br>
    15:48:41.031|.\VExtMgr.cpp(78)|Log2|DataBase|FaxCfg::updateContact:[CM504008]: Fax Service: registered as sip:888@172.16.160.7:5060 with contact sip:888@172.16.160.7:5100;user=phone<br>
    15:53:41.140|.\VExtMgr.cpp(78)|Log2|DataBase|FaxCfg::updateContact:[CM504008]: Fax Service: registered as sip:888@172.16.160.7:5060 with contact sip:888@172.16.160.7:5100;user=phone<br>
    15:55:44.187|.\CallCtrl.cpp(135)|Log2||CallCtrl::eek:nIncomingCall:[CM503001]: Call(1): Incoming call from Ext.816 to "Finance Manager"<sip:803@172.16.160.7><br>
    15:55:44.906|.\Extension.cpp(922)|Log3||Extension::printEndpointInfo:[CM505001]: Ext.816: Device info: Device Identified: [Man: Linksys;Mod: SPA-922;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA922-5.2.8] Transport: [sip:172.16.160.7:5060]<br>
    15:55:44.906|.\CallCtrl.cpp(295)|Log3||CallCtrl::eek:nSelectRouteReq:[CM503010]: Making route(s) to "Finance Manager"<sip:803@172.16.160.7><br>
    15:55:44.906|.\CallCtrl.cpp(404)|Log2||CallCtrl::eek:nSelectRouteReq:[CM503004]: Call(1): Calling: Ext:Ext.803@[Dev:sip:803@172.16.160.203:5060]<br>
    15:55:56.781|.\CallCtrl.cpp(212)|Log3||CallCtrl::eek:nAnsweredCall:[CM503002]: Call(1): Alerting sip:803@172.16.160.203:5060<br>
    15:55:56.781|.\Extension.cpp(922)|Log3||Extension::printEndpointInfo:[CM505001]: Ext.803: Device info: Device Identified: [Man: Linksys;Mod: SPA-922;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA922-5.2.8] Transport: [sip:172.16.160.7:5060]<br>
    15:55:56.781|.\CallCtrl.cpp(524)|Log2||CallCtrl::eek:nLegConnected:[CM503007]: Call(1): Device joined: sip:816@172.16.160.216:5060<br>
    15:55:56.921|.\CallCtrl.cpp(524)|Log2||CallCtrl::eek:nLegConnected:[CM503007]: Call(1): Device joined: sip:803@172.16.160.203:5060<br>
    15:56:45.609|.\Call.cpp(760)|Log2||Call::Terminate:[CM503008]: Call(1): Call is terminated<br>
    15:56:45.609|.\Call.cpp(760)|Log2||Call::Terminate:[CM503008]: Call(1): Call is terminated<br>
    15:58:41.250|.\VExtMgr.cpp(78)|Log2|DataBase|FaxCfg::updateContact:[CM504008]: Fax Service: registered as sip:888@172.16.160.7:5060 with contact sip:888@172.16.160.7:5100;user=phone<br>
     
  9. LeonidasG

    LeonidasG Support Team
    Staff Member 3CX Support

    Joined:
    Nov 19, 2008
    Messages:
    1,473
    Likes Received:
    94

    That's a fairly old build, have you tried any of the newest versions?

    Try this one, we probably have fixed a few hundred bugs over the build you are using, the problem you currently have might be one of the ones that have been fixed.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. agnetman

    Joined:
    Oct 2, 2007
    Messages:
    24
    Likes Received:
    0
    Okay, I could try that. Is it possible to install over the top of the current version, or is it necessary to uninstall first?
     
  11. LeonidasG

    LeonidasG Support Team
    Staff Member 3CX Support

    Joined:
    Nov 19, 2008
    Messages:
    1,473
    Likes Received:
    94

    You would need to Uninstall the Old one First and Clear all Traces if any remain.

    Use this to Detect any Possible Leftover Traces.
    http://www.3cx.com/downloads/3CXInstallationChecker.exe

    And if any...
    Use this Guide to remove them.
    http://www.3cx.com/support/installation-checker.html

    Take a Backup of your System and you are good to go.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. agnetman

    Joined:
    Oct 2, 2007
    Messages:
    24
    Likes Received:
    0
    Okay here's what I've done.

    Backed up the configuration.
    Uninstalled the 3CX server application.
    Rebooted the server.
    Run the 3CX sysem cleaner utility and completed the necessary action (step 3 delete 3 CX) folder.
    Installed the latest version.
    Restored the configuration.
    3CX server has started okay.
    All of the 20 extensions fail to register with the server.
    The VoIP line still makes no attempt to register with the provider.
    The situation has worsened by following the suggestion to update to the latest version. Now the internal system isn't working.

    Here's the text from the 3CXPhoneSystem Log file

    12:34:21.984|.\CallMgr.cpp(1061)|Log2||LoadLicenceInfo:[CM501010]: License Info: Load Failed<br>
    12:34:22.265|.\SLServer.cpp(870)|Error1||??:Unknown system [DBProvider] tries to connect!<br>
    12:34:26.953|.\CallMgr.cpp(147)|Log2|CallManager|CallMgr::Initialize:[CM501001]: Start 3CX PhoneSystem Call Manager<br>
    12:34:26.953|.\CallMgr.cpp(148)|Log2|CallManager|CallMgr::Initialize:[CM501002]: Version: 7.0.4708.0<br>
    12:34:27.546|.\CallCtrl.cpp(21)|Log2||CallCtrl::thread:[CM501007]: *** Started Calls Controller thread ***<br>
    12:34:27.656|.\CallMgr.cpp(729)|Log2|CallManager|CallMgr::findLocalIPs:[CM501006]: Default Local IP address: [172.16.160.7]<br>
    12:34:36.968|.\CallMgr.cpp(853)|Log2|CallManager|CallMgr::eek:nAddIPs:IP(s) added:[172.16.160.7]<br>
    12:34:37.515|.\MSInterface.cpp(734)|Log2||MediaServerConnected:[CM112000] Media Server is connected<br>
    12:34:45.609|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.*0: new contact is registered. Contact(s): [sip:*0@127.0.0.1:40000;rinstance=c2d88cecc80cefc9/*0]<br>
    12:34:45.750|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.*1: new contact is registered. Contact(s): [sip:*1@127.0.0.1:40000;rinstance=3d2d0e15e49531b4/*1]<br>
    12:34:47.734|.\Extension.cpp(310)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.999: new contact is registered. Contact(s): [sip:999@127.0.0.1:40600;rinstance=5bd9145f1257c8a9/999]<br>
    12:35:00.500|.\VExtMgr.cpp(78)|Log2|DataBase|FaxCfg::updateContact:[CM504008]: Fax Service: registered as sip:888@172.16.160.7:5060 with contact sip:888@172.16.160.7:5100;user=phone<br>
    12:35:06.437|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-bb9cc6a8 cseq=REGISTER contact=815@172.16.160.215:5060 / 15010 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:09.453|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-3e08e504 cseq=REGISTER contact=813@172.16.160.213:5060 / 61549 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:09.906|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-5e12123e cseq=REGISTER contact=814@172.16.160.214:5060 / 52870 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:10.890|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-6a5517b9 cseq=REGISTER contact=820@172.16.160.220:5060 / 60293 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:11.625|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-2b635047 cseq=REGISTER contact=819@172.16.160.219:5060 / 57635 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:13.609|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-c0083269 cseq=REGISTER contact=804@172.16.160.204:5060 / 39646 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:14.062|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-3794b18f cseq=REGISTER contact=803@172.16.160.203:5060 / 49104 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:14.937|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-c12068d8 cseq=REGISTER contact=811@172.16.160.211:5060 / 8142 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:20.015|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-4c1d3066 cseq=REGISTER contact=817@172.16.160.217:5060 / 9844 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:20.203|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-17a76887 cseq=REGISTER contact=807@172.16.160.207:5060 / 41113 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:22.281|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-2e60e2a4 cseq=REGISTER contact=801@172.16.160.201:5060 / 41832 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:26.984|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-6688dbf0 cseq=REGISTER contact=805@172.16.160.205:5060 / 53682 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:27.234|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-4e2a9606 cseq=REGISTER contact=806@172.16.160.206:5060 / 7937 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:27.765|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-8d939d62 cseq=REGISTER contact=818@172.16.160.218:5060 / 20416 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:28.843|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-e03a5554 cseq=REGISTER contact=802@172.16.160.202:5060 / 29592 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:28.859|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-37337e2 cseq=REGISTER contact=816@172.16.160.216:5060 / 10664 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:35:32.656|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-fa96395b cseq=REGISTER contact=808@172.16.160.208:5060 / 20608 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:39:59.609|.\VExtMgr.cpp(78)|Log2|DataBase|FaxCfg::updateContact:[CM504008]: Fax Service: registered as sip:888@172.16.160.7:5060 with contact sip:888@172.16.160.7:5100;user=phone<br>
    12:44:59.734|.\VExtMgr.cpp(78)|Log2|DataBase|FaxCfg::updateContact:[CM504008]: Fax Service: registered as sip:888@172.16.160.7:5060 with contact sip:888@172.16.160.7:5100;user=phone<br>
    12:49:59.843|.\VExtMgr.cpp(78)|Log2|DataBase|FaxCfg::updateContact:[CM504008]: Fax Service: registered as sip:888@172.16.160.7:5060 with contact sip:888@172.16.160.7:5100;user=phone<br>
    12:54:59.937|.\VExtMgr.cpp(78)|Log2|DataBase|FaxCfg::updateContact:[CM504008]: Fax Service: registered as sip:888@172.16.160.7:5060 with contact sip:888@172.16.160.7:5100;user=phone<br>
    12:55:06.703|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-5dd491ee cseq=REGISTER contact=815@172.16.160.215:5060 / 15012 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:09.703|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-d5c2db5b cseq=REGISTER contact=813@172.16.160.213:5060 / 61551 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:10.156|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-d5d77e8d cseq=REGISTER contact=814@172.16.160.214:5060 / 52872 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:11.109|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-895f3552 cseq=REGISTER contact=820@172.16.160.220:5060 / 60295 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:11.843|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-aba95ff0 cseq=REGISTER contact=819@172.16.160.219:5060 / 57637 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:13.859|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-783b53ee cseq=REGISTER contact=804@172.16.160.204:5060 / 39648 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:14.312|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-c3c6b94f cseq=REGISTER contact=803@172.16.160.203:5060 / 49106 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:15.203|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-7a50eab1 cseq=REGISTER contact=811@172.16.160.211:5060 / 8144 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:20.171|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-65f10bb cseq=REGISTER contact=817@172.16.160.217:5060 / 9846 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:20.500|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-25603d9a cseq=REGISTER contact=807@172.16.160.207:5060 / 41115 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:22.562|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-a138f28b cseq=REGISTER contact=801@172.16.160.201:5060 / 41834 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:27.171|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-5ff4c589 cseq=REGISTER contact=805@172.16.160.205:5060 / 53684 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:27.515|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-e4649ccf cseq=REGISTER contact=806@172.16.160.206:5060 / 7939 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:28.046|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-a26c1f1c cseq=REGISTER contact=818@172.16.160.218:5060 / 20418 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:29.000|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-b0096d2a cseq=REGISTER contact=802@172.16.160.202:5060 / 29594 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:29.031|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-8ee35173 cseq=REGISTER contact=816@172.16.160.216:5060 / 10666 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    12:55:32.984|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 172.16.160.7 tid=-eedbe51a cseq=REGISTER contact=808@172.16.160.208:5060 / 20610 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
     
  13. agnetman

    Joined:
    Oct 2, 2007
    Messages:
    24
    Likes Received:
    0
    I tried re-enabling STUN and restarting the 3CX phone service.This does cause an attempt to register with the VoIP provider.

    I deleted the VoIP details, disabled STUN stopped and restarted 3CX phone service, renetered the VoIP details and still it refuses to even attempt registration.

    Why will 3CX only work with STUN enabled?

    Why after backing up, installing a new version and restoring the configuration have I lost all 20 internal extensions?

    I appreciate that this is a free version and I would be encouraged to upgrade to a paid for version in 20 plus overseas locations if the trial version worked.

    These are fundamental issues.
     
  14. LeonidasG

    LeonidasG Support Team
    Staff Member 3CX Support

    Joined:
    Nov 19, 2008
    Messages:
    1,473
    Likes Received:
    94
    What make are the phones exactly? Also Send us the backup file please.
    Can you also send logs so we see why the extensions are not registering?

    Do you see the extensions in the list? From which version of 3CX did you make a backup?

    Also 3CX can work without stun no problem - you can switch off stun. Depends on what your provider prefers. Who is the provider?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. agnetman

    Joined:
    Oct 2, 2007
    Messages:
    24
    Likes Received:
    0
    Dear LeonidasG I have just spoken with Chris and explained the background.

    The 3CX server is in Iraq, I'm in the UK. Connecting and carrying out any remote work takes time, including getting the logs.

    I've posted above the 3CXPhoneSystem log file, "authentication failed check authorization ID and password mact the ones in extension settings".

    Clearly the backup of the earlier version 7 configuration and the restore into the new version did not work, if it had then the exentsions would have registered.

    The phones are Linysys SPA922.

    I do see the extensions listed.

    The VoIP provider doens not require STUN, it worked for 3 months without STUN. The 3CX server is behind a Cisco ASA5510.

    The 3CX doesn't even attempt to register with the VoIP provider, there are no outbound packets from the 3CX server to the VoIP provider.
     
  16. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,127
    Likes Received:
    152
    Hi

    Those logs are not enough - Authentication is Failing Yes - we agree on this - But we want to know WHY the phone is not accepting the authentication. And to know why we need a backup file. Or at least a registration capture.

    Also try the following

    Go to Advanced / Custom Parameters and set FORCEAUTH to 0 instead of 1.
    Without the trace files This is complete guess work.

    About the Provider - If you want to get this resolved quickly do the following:

    Set to verbose.
    Start wireshark
    Restart the 3cxphonesystem service.
    Wait for 30 seconds and stop wireshark.

    generate Support info (should not take you more than 1 minute and send the capture + logs directly to nb@3cx.com

    Nicky.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. agnetman

    Joined:
    Oct 2, 2007
    Messages:
    24
    Likes Received:
    0
    Nicky,

    Clearly the backup of the configuration followed by the restore has made some changes, if it hadn't made any changes then the authentication of the extensions would just work without any intervention. This seems like a bug and I'll let you sort it out. Its actaully quicker for me to remotely connect to all 20 Linsksys SPA922 in the Iraq office and change the password on each of them. When I do this the phone registers with the 3CX server.

    I repeat, in the previous version that was backed up no password was set.

    Next, Chris Martin called and then emailed me asking that I download and install on the server in Iraq the latest version (7.1) of the 3CX server, which I duly did.

    Now I have a repeat of the issue where the phones don't register with the server, again. No problem I thought, I'll do what I did last time and on each phone I'll set the password to match the ID. But this doesn't work! When I try to do this a pop up window appears with the message "Please enter valid values for SIP ID".

    Okay I thought I'll leave that and try to set up the registration of the VoIP lines, starting with turning off STUN, which was the reason that Chris Martin asked me to download and install version 7.1.

    Under the STUN tab I had to enter a public IP address and then restart the service. I did this and now although all services are shown as running in Services Status when I check in the Server Activity Log the server is shown as 'Shutdown'.

    So to sum up, I can't register any extensions even by entering a password on each of them. The configured VoIP lines do not even attempt to register, not a single packet is sent to the VOIP provider's server. I don't even know if the 3CX server is running or not, accoriding to the services they are all running, but according the activity log the server is shutdown.
     
  18. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,127
    Likes Received:
    152
    Restart the 3cxphonesystem again - this will solve the shutdown in the logs. (this is only a file lock issue.)

    please enter valid values for SIP ID. yes - We made a change - Sip ID cannot be blank or invalid. I suggest that you add valid sip values to be unique (same as extension number to make it quick), This is something you will only do once.)

    Stun - we will takle later.

    Generate a backup without prompts and music on hold and we will see what the problems are. Also set to verbose, restart the service and generate support info. Once I have this I will tell you exactly what the problems are. At this point this is not classified as a bug. extensions can not register for a number of reasons. Do not change anything in the configuration - otherwise you will hide the problem. (except for the SIP id.)

    You will not get the extensions registered simply because the problem is not in backup and restore - the data is successfully restored. Did you set Force Auth to 0 as I told you before?

    You can know if the service is actually running if you go to services.msc and see the status of the 3cxphonesystem.exe - if it is running - it is running.

    Nicky
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. agnetman

    Joined:
    Oct 2, 2007
    Messages:
    24
    Likes Received:
    0
    The SIP ID was not blank, it was 3 digits.
     
  20. agnetman

    Joined:
    Oct 2, 2007
    Messages:
    24
    Likes Received:
    0
    SIP ID was the extension # e.g. 801 and not blank.
     
Thread Status:
Not open for further replies.