Unable to register D-Link DPH-540 IP Phone

Discussion in '3CX Phone System - General' started by fischershaw, Jan 12, 2007.

  1. fischershaw

    Joined:
    Jan 3, 2007
    Messages:
    16
    Likes Received:
    0
    Phone loops forever trying to register and being refused, just like the D-Link VoIP Gateway. 3CX appears to think the nonce used by the phone is stale, even though it just received it and replied immediately.

    Repro:
    Create extension
    Number = 10
    Id = 10
    Password = 666

    On DPH
    Edit the Default SIP account
    Phone Number = 10
    Auth ID = 10
    Auth Password = 666
    SIP Domain = 192.168.1.1
    Proxy Address = 192.168.1.1
    No change to Advanced settings

    Message exchange follows:

    REGISTER sip:192.168.1.1 SIP/2.0
    Max-Forwards: 70
    Content-Length: 0
    Via: SIP/2.0/UDP 192.168.2.11:5060;branch=z9hG4bK43dabe787
    Call-ID: 71d90c5564bf63e2d4a9541a4f0e3fcf@192.168.2.11
    From: 10 <sip:10@192.168.1.1>;tag=6e874ea52370c44
    To: 10 <sip:10@192.168.1.1>
    CSeq: 1253342995 REGISTER
    Contact: 10 <sip:10@192.168.2.11:5060>;expires=3600
    Allow: NOTIFY, REFER, OPTIONS, INVITE, ACK, CANCEL, BYE
    User-Agent: Callctrl/1.6.0.0 MxSF/v3.5.3.4


    REGISTER sip:192.168.1.1 SIP/2.0
    Max-Forwards: 70
    Content-Length: 0
    Via: SIP/2.0/UDP 192.168.2.11:5060;branch=z9hG4bK43dabe787
    Call-ID: 71d90c5564bf63e2d4a9541a4f0e3fcf@192.168.2.11
    From: 10 <sip:10@192.168.1.1>;tag=6e874ea52370c44
    To: 10 <sip:10@192.168.1.1>
    CSeq: 1253342995 REGISTER
    Contact: 10 <sip:10@192.168.2.11:5060>;expires=3600
    Allow: NOTIFY, REFER, OPTIONS, INVITE, ACK, CANCEL, BYE
    User-Agent: Callctrl/1.6.0.0 MxSF/v3.5.3.4


    SIP/2.0 407 Proxy Authentication Required
    Via: SIP/2.0/UDP 192.168.2.11:5060;branch=z9hG4bK43dabe787
    Proxy-Authenticate: Digest nonce="12813115818:e875932a2df2037ca1049bd765a80c26",algorithm=MD5,realm="3CXPhoneSystem"
    To: "10"<sip:10@192.168.1.1>;tag=6a46336b
    From: "10"<sip:10@192.168.1.1>;tag=6e874ea52370c44
    Call-ID: 71d90c5564bf63e2d4a9541a4f0e3fcf@192.168.2.11
    CSeq: 1253342995 REGISTER
    Content-Length: 0


    SIP/2.0 407 Proxy Authentication Required
    Via: SIP/2.0/UDP 192.168.2.11:5060;branch=z9hG4bK43dabe787
    Proxy-Authenticate: Digest nonce="12813115818:e875932a2df2037ca1049bd765a80c26",algorithm=MD5,realm="3CXPhoneSystem"
    To: "10"<sip:10@192.168.1.1>;tag=6a46336b
    From: "10"<sip:10@192.168.1.1>;tag=6e874ea52370c44
    Call-ID: 71d90c5564bf63e2d4a9541a4f0e3fcf@192.168.2.11
    CSeq: 1253342995 REGISTER
    Content-Length: 0


    REGISTER sip:192.168.1.1 SIP/2.0
    Max-Forwards: 70
    Content-Length: 0
    Via: SIP/2.0/UDP 192.168.2.11:5060;branch=z9hG4bKe7855201e
    Call-ID: 71d90c5564bf63e2d4a9541a4f0e3fcf@192.168.2.11
    From: 10 <sip:10@192.168.1.1>;tag=6e874ea52370c44
    To: 10 <sip:10@192.168.1.1>
    CSeq: 1253342996 REGISTER
    Contact: 10 <sip:10@192.168.2.11:5060>;expires=3600
    Allow: NOTIFY, REFER, OPTIONS, INVITE, ACK, CANCEL, BYE
    Proxy-Authorization:Digest response="1d73dfedc9691e5a3a7282b025aba9c5",username="10",realm="3CXPhoneSystem",nonce="12813115818:e875932a2df2037ca1049bd765a80c26",algorithm=MD5,uri="sip:192.168.1.1"
    User-Agent: Callctrl/1.6.0.0 MxSF/v3.5.3.4


    REGISTER sip:192.168.1.1 SIP/2.0
    Max-Forwards: 70
    Content-Length: 0
    Via: SIP/2.0/UDP 192.168.2.11:5060;branch=z9hG4bKe7855201e
    Call-ID: 71d90c5564bf63e2d4a9541a4f0e3fcf@192.168.2.11
    From: 10 <sip:10@192.168.1.1>;tag=6e874ea52370c44
    To: 10 <sip:10@192.168.1.1>
    CSeq: 1253342996 REGISTER
    Contact: 10 <sip:10@192.168.2.11:5060>;expires=3600
    Allow: NOTIFY, REFER, OPTIONS, INVITE, ACK, CANCEL, BYE
    Proxy-Authorization:Digest response="1d73dfedc9691e5a3a7282b025aba9c5",username="10",realm="3CXPhoneSystem",nonce="12813115818:e875932a2df2037ca1049bd765a80c26",algorithm=MD5,uri="sip:192.168.1.1"
    User-Agent: Callctrl/1.6.0.0 MxSF/v3.5.3.4


    SIP/2.0 407 Proxy Authentication Required
    Via: SIP/2.0/UDP 192.168.2.11:5060;branch=z9hG4bKe7855201e
    Proxy-Authenticate: Digest nonce="12813115818:e875932a2df2037ca1049bd765a80c26",algorithm=MD5,realm="192.168.1.1",stale=true
    To: "10"<sip:10@192.168.1.1>;tag=0617a41e
    From: "10"<sip:10@192.168.1.1>;tag=6e874ea52370c44
    Call-ID: 71d90c5564bf63e2d4a9541a4f0e3fcf@192.168.2.11
    CSeq: 1253342996 REGISTER
    Content-Length: 0


    SIP/2.0 407 Proxy Authentication Required
    Via: SIP/2.0/UDP 192.168.2.11:5060;branch=z9hG4bKe7855201e
    Proxy-Authenticate: Digest nonce="12813115818:e875932a2df2037ca1049bd765a80c26",algorithm=MD5,realm="192.168.1.1",stale=true
    To: "10"<sip:10@192.168.1.1>;tag=0617a41e
    From: "10"<sip:10@192.168.1.1>;tag=6e874ea52370c44
    Call-ID: 71d90c5564bf63e2d4a9541a4f0e3fcf@192.168.2.11
    CSeq: 1253342996 REGISTER
    Content-Length: 0

    The same exchange continues forever.
     
  2. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,720
    Likes Received:
    41
    Its based you post the server status log instead, only then can we see why the registration is being refused
     
  3. fischershaw

    Joined:
    Jan 3, 2007
    Messages:
    16
    Likes Received:
    0
    10:43:24.125 ??: SL: connected redfish:0/PHPExtension_0 at [redfish]/PHPExtension_0
    10:43:16.000 AuthMgr::eek:nAuthSuccess: Extension "FischerShaw_Main"<sip:89714@192.168.1.1:5060> has been registered successfully
    10:42:51.984 AuthMgr::eek:nAuthSuccess: Extension "FischerShaw_Unused"<sip:80000@192.168.1.1:5060> has been registered successfully
    10:42:51.984 AuthMgr::eek:nAuthSuccess: Extension "FischerShaw_Gate"<sip:80001@192.168.1.1:5060> has been registered successfully
    10:42:51.875 AuthMgr::eek:nAuthSuccess: Extension "FischerShaw_Fax"<sip:89503@192.168.1.1:5060> has been registered successfully
    10:42:51.875 AuthMgr::eek:nAuthSuccess: Extension "FischerShaw_Main"<sip:89714@192.168.1.1:5060> has been registered successfully
    10:42:51.765 Registrar::eek:nFailure: Registration failure: <sip:227151@207.229.110.25> for sip:227151@207.229.110.25
    10:40:32.156 MediaServerConnected: Media Server is connected
    10:40:32.156 ??: SL: connected redfish:0/MediaServer at [redfish]/MediaServer
    10:40:25.203 SessionMgr::thread: ** Entering Main Loop **
    10:40:25.203 SessionMgr::run: ** Start Session Manager **
    10:40:25.187 SessionMgr::run: ** Initialize Status Monitor **
    10:40:25.140 LineImpl::update: Line: register line 227151
    10:40:24.953 DBA: ** Database connection Ok **
    10:40:24.921 SessionMgr::run: ** Initialize Lines Manager **
    10:40:24.921 SessionMgr::run: STUN resolved external IP: 207.229.110.25
    10:40:24.765 SessionMgr::run: ** Initialize Client Authentication **
    10:40:24.765 SessionMgr::run: ** Initialize Server Authentication **
    10:40:24.765 SessionMgr::run: ** Initialize DUM **
    10:40:24.281 SessionMgr::run: ** Adding transports **
    10:40:24.265 SessionMgr::run: Version: 2.0.913.0
     

Share This Page