SPA921 not registering automatically after PBX Restart

Discussion in '3CX Phone System - General' started by pbnet, Aug 7, 2008.

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

    Joined:
    Oct 25, 2007
    Messages:
    12
    Likes Received:
    0
    Hello everybody,
    I have the following problem:
    - 3CX PBX 6 running on a Windows 2003 R2 machine
    - a Linksys SPA91 SIP Phone
    - a cisco ATA 186 SIP Adaptor
    the problem is that if I restart the server or the 3CX PBX service, the SPA 921 does not register automatically to the PBX. This problem is only solved if I initiate a call from the SPA 921.
    This problem was not present in 3CX 3.1
    Any ideas would be greatly appreciated.

    Thanks.
     
  2. alexmallia

    alexmallia New Member
    3CX Support

    Joined:
    Aug 4, 2008
    Messages:
    130
    Likes Received:
    0
    Please ensure that the SPA921 has been set up correctly according to the instruction on http://www.3cx.com/sip-phones/linksys-SPA-921.html and that the settings have been set as per the screenshot in this link.

    regards

    Alex Mallia
    Technical Support Engineer
    3CX - Developers of IP PBX software
    http://www.3cx.com
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. galal202

    galal202 New Member

    Joined:
    Jun 23, 2008
    Messages:
    235
    Likes Received:
    0
    Hello,
    restore spa to factory set defaults then Follow the instructions from 3cx spa page
    I think if you reduce registration exired time to 300 second will help
     
  4. amygoda

    amygoda Member

    Joined:
    Sep 18, 2006
    Messages:
    436
    Likes Received:
    0
    Hello,
    I advice you not for 3CX only but for all software
    fresh instal new version is better than update
     
  5. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,937
    Likes Received:
    250
    For the phone to re-register, you need to restart the phone or wait for the re-registration interval to kick in (set on phone). Making outbound call probably causes the phone to re register as well which is why its not an issue. It doesnt have anything to do with the phone system version.....
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. pbnet

    Joined:
    Oct 25, 2007
    Messages:
    12
    Likes Received:
    0
    Thank you all for your kind replies.
    The problem still exists even after reset to factory defaults and setting the reg time to 300.
    Here is the registration log:

    06:58:31.984 FaxCfg::updateContact [CM504009]: Fax Service: changed contact to sip:100@172.17.77.140:5100;user=phone
    06:58:25.156 Extension::printEndpointInfo [CM505001]: Ext.100: Device info: Device Identified: [Man: Linksys;Mod: SPA-921;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA921-5.1.8] Transport: [sip:172.17.77.140:5060]
    06:58:21.343 CallCtrl::eek:nIncomingCall [CM503001]: Call(1): Incoming call from Ext.100 to [sip:999@172.17.77.140]
    06:55:46.203 ExtnCfg::updateContact [CM504001]: Ext.802: new contact is registered. Contact(s): [sip:802@127.0.0.1:40600;rinstance=a238366baf16a632/802]
    06:55:45.921 ExtnCfg::updateContact [CM504001]: Ext.801: new contact is registered. Contact(s): [sip:801@127.0.0.1:40600;rinstance=2f624367c2577f73/801]
    06:55:45.296 ExtnCfg::updateContact [CM504001]: Ext.800: new contact is registered. Contact(s): [sip:800@127.0.0.1:40600;rinstance=a51a122c40331555/800]
    06:55:44.671 ExtnCfg::updateContact [CM504001]: Ext.999: new contact is registered. Contact(s): [sip:999@127.0.0.1:40600;rinstance=f32b675cb022e84a/999]
    06:53:48.562 FaxCfg::updateContact [CM504008]: Fax Service: registered as sip:100@172.17.77.140 with contact sip:100@172.17.77.178:5060
    06:53:44.968 ExtnCfg::updateContact [CM504001]: Ext.101: new contact is registered. Contact(s): [sip:101@172.17.77.177:5060;user=phone;transport=udp/101]
    06:53:43.828 ClientRegs::eek:nSuccess [CM504004]: Registration succeeded for: 10003@SIPNUMBER
    06:53:43.640 ClientRegs::eek:nSuccess [CM504004]: Registration succeeded for: 10004@ORBTALK-UK
    06:53:43.609 ClientRegs::eek:nSuccess [CM504004]: Registration succeeded for: 10002@NETMASTER VoIP
    06:53:43.593 ClientRegs::eek:nSuccess [CM504004]: Registration succeeded for: 10001@IDILIS VoIP
    06:53:43.484 ClientRegs::eek:nSuccess [CM504004]: Registration succeeded for: 10000@ZAPP VoIP
    06:53:43.484 ClientRegs::Register [CM504003]: Sent registration request for 10004@ORBTALK-UK
    06:53:43.468 ClientRegs::Register [CM504003]: Sent registration request for 10003@SIPNUMBER
    06:53:43.453 ClientRegs::Register [CM504003]: Sent registration request for 10001@IDILIS VoIP
    06:53:43.437 ClientRegs::Register [CM504003]: Sent registration request for 10002@NETMASTER VoIP
    06:53:43.296 ClientRegs::Register [CM504003]: Sent registration request for 10000@ZAPP VoIP
    06:53:42.921 ClientRegs::eek:nSuccess [CM504004]: Registration succeeded for: 10003@SIPNUMBER
    06:53:42.875 StunClient::process [CM506002]: Resolved SIP external IP:port (89.136.157.14:5060) on Transport 172.17.77.140:5060
    06:53:42.812 ClientRegs::eek:nSuccess [CM504004]: Registration succeeded for: 10004@ORBTALK-UK
    06:53:42.640 StunClient::eek:nInitTests [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 75.101.138.128:3478 over Transport 172.17.77.140:5060
    06:53:41.562 ClientRegs::eek:nSuccess [CM504004]: Registration succeeded for: 10001@IDILIS VoIP
    06:53:41.562 ClientRegs::Register [CM504003]: Sent registration request for 10003@SIPNUMBER
    06:53:41.453 ClientRegs::Register [CM504003]: Sent registration request for 10004@ORBTALK-UK
    06:53:41.406 ClientRegs::Register [CM504003]: Sent registration request for 10001@IDILIS VoIP
    06:53:32.781 FaxCfg::updateContact [CM504008]: Fax Service: registered as sip:100@172.17.77.140:5060 with contact sip:100@172.17.77.140:5100;user=phone
    06:53:32.171 ExtnCfg::updateContact [CM504001]: Ext.*1: new contact is registered. Contact(s): [sip:*1@127.0.0.1:40000;rinstance=2338ba6f0d1a1b5f/*1]
    06:53:31.578 ExtnCfg::updateContact [CM504001]: Ext.*0: new contact is registered. Contact(s): [sip:*0@127.0.0.1:40000;rinstance=d42b41229c2dd44d/*0]
    06:53:29.328 CallMgr::eek:nAddIPs IP(s) added:[172.17.77.140]
    06:53:18.625 DBA [CM501003]: Connected: Database
    06:53:17.171 CallMgr::findLocalIPs [CM501006]: Default Local IP address: [172.17.77.140]
    06:53:16.625 CallCtrl::thread [CM501007]: *** Started Calls Controller thread ***
    06:53:16.625 CallMgr::Initialize [CM501002]: Version: 6.0.650.0
    06:53:16.625 CallMgr::Initialize [CM501001]: Start 3CX PhoneSystem Call Manager
    06:53:16.406 MediaServerConnected [CM112000] Media Server is connected
    06:53:16.218 LoadLicenceInfo [CM501010]: License Info: Load Failed

    Any other ideas would be greatly appreciated.
     
Thread Status:
Not open for further replies.