Client cannot register correct account to SIP server

Discussion in 'Windows' started by ztengn, Aug 3, 2008.

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

    Joined:
    Aug 3, 2008
    Messages:
    3
    Likes Received:
    0
    I have configured correct account and server information on SIP client, but registeration fails because server feedback "423 Registration Too Brief" error. Who can tell me the real reason?

    Thanks a lot!
     
  2. Anonymous

    Anonymous Guest

    Can you give us settings and client?

    Thanks,
     
  3. ztengn

    Joined:
    Aug 3, 2008
    Messages:
    3
    Likes Received:
    0
    I attach the registeration information below, please help me analyze it. Thanks!

    23:03:38,031: T: 210.51.195.49:5060
    REGISTER sip:210.51.195.49 SIP/2.0
    Via: SIP/2.0/UDP 192.168.10.102;branch=z9hG4bK0041922fa460dd11a5cd0013022b344f
    From: #0*028136 <sip:#0*028136@210.51.195.49>;tag=12717
    To: <sip:#0*028136@210.51.195.49>
    Call-ID: 807DC82D-A460-DD11-A5CD-0013022B344F@192.168.10.102
    CSeq: 1 REGISTER
    Contact: <sip:#0*028136@192.168.10.102>
    Max-Forwards: 70
    User-Agent: SIPPER for 3CX Phone
    Expires: 900
    Content-Length: 0


    -------------------------------------------
    23:03:38,406: R: 210.51.195.49:5060
    SIP/2.0 401 Unauthorized
    Via: SIP/2.0/UDP 192.168.1.29;received=190.241.15.11;branch=z9hG4bK0041922fa460dd11a5cd0013022b344f
    To: <sip:#0*028136@210.51.195.49>
    From: "#0*028136"<sip:#0*028136@210.51.195.49>;tag=12717
    Call-ID: 807DC82D-A460-DD11-A5CD-0013022B344F@192.168.1.29
    CSeq: 1 REGISTER
    User-Agent: ZTE-SoftSwitch
    WWW-Authenticate: Digest realm="sip",
    nonce="71dd1c3e5fb4cd3b8c8b055b48ebae23",
    ZTE-ID=e4b7cabcafebe8617854a27b59912a42
    Content-Length: 0


    -------------------------------------------
    23:03:38,437: T: 210.51.195.49:5060
    REGISTER sip:210.51.195.49 SIP/2.0
    Via: SIP/2.0/UDP 192.168.10.102;branch=z9hG4bK0041922fa460dd11a5ce0013022b344f
    From: #0*028136 <sip:#0*028136@210.51.195.49>;tag=19597
    To: <sip:#0*028136@210.51.195.49>
    Call-ID: 807DC82D-A460-DD11-A5CD-0013022B344F@192.168.10.102
    CSeq: 2 REGISTER
    Contact: <sip:#0*028136@192.168.10.102>
    Authorization: Digest username="#0*028136", realm="sip", nonce="71dd1c3e5fb4cd3b8c8b055b48ebae23", uri="sip:210.51.195.49", response="c3eeaa77e917ce39dac65d84f3e06cbb", algorithm=MD5
    Max-Forwards: 70
    User-Agent: SIPPER for 3CX Phone
    Expires: 900
    Content-Length: 0


    -------------------------------------------
    23:03:38,828: R: 210.51.195.49:5060
    SIP/2.0 423 Registration Too Brief
    Via: SIP/2.0/UDP 192.168.10.102;received=190.241.15.11;branch=z9hG4bK0041922fa460dd11a5ce0013022b344f
    To: <sip:#0*028136@210.51.195.49>
    From: "#0*028136"<sip:#0*028136@210.51.195.49>;tag=19597
    Call-ID: 807DC82D-A460-DD11-A5CD-0013022B344F@192.168.10.102
    CSeq: 2 REGISTER
    Min-Expires: 3600
    User-Agent: ZTE-SoftSwitch
    Content-Length: 0


    -------------------------------------------
    23:03:53,156: R: 210.51.195.49:5060
    OPTIONS sip:%230*028136@210.51.195.49 SIP/2.0
    Via: SIP/2.0/UDP 210.51.195.49:5060;branch=z9hG4bK7f8217bc272026b1
    Max-Forwards: 70
    To: <sip:%230*028136@210.51.195.49>
    From: BgwLinkTest267634310<sip:bgw@210.51.195.49>;tag=200307191120
    Call-ID: 1596200307191120@210.51.195.49
    CSeq: 10000 OPTIONS
    Accept: application/sdp
    Content-Length: 0


    -------------------------------------------
    23:03:53,156: T: 210.51.195.49:5060
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 210.51.195.49:5060;branch=z9hG4bK7f8217bc272026b1
    From: BgwLinkTest267634310 <sip:bgw@210.51.195.49>;tag=200307191120
    To: <sip:#0*028136@210.51.195.49>;tag=80128338a460dd11a5ce0013022b344f
    Call-ID: 1596200307191120@210.51.195.49
    CSeq: 10000 OPTIONS
    Contact: <sip:#0*028136@192.168.10.102>
    Max-Forwards: 70
    Server: SIPPER for 3CX Phone
    Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY
    Content-Length: 0
     
  4. Anonymous

    Anonymous Guest

    Hi there,

    You seem to be using the 3CX Client to connect directly to an (unsupported) VoIP provider. This falls outside our support - there is no fault by the PBX.

    What you can try is to register with the provider using X-Lite, and see how that works.

    Thanks,
     
  5. ztengn

    Joined:
    Aug 3, 2008
    Messages:
    3
    Likes Received:
    0
    Hi,

    You mean that 3CX client cannot connect with VOIP provider directly?

    I have done the same configuration on as on X-lite, X-lite seems to work properly except disconnection during 1-2 minutes.

    But why 3XC client cannot work properly as x-lite? I have known that 423 error means the during of reregisteration is too short, but I donot know how to change this value longer even I can change this value to 3600 on Register Setting of x-lite.
     
  6. Chris

    Joined:
    Sep 10, 2008
    Messages:
    1
    Likes Received:
    0
    I have had the same problem trying to register the 3CX client to the 3CX PBX. Eventually I found that on the 3CX client, the My VoiceMail PIN setting under File-Login is infact the authentication number and should match the vaule in Authentication Password in the 3CX PBX. So if you are using a different PIN for voice mail to the client authentication PIN, and you have put your Voicemail PIN in the "My VoiceMail PIN" field on the client, it will not authenticate. As a work around, you need to put the client authentication PIN into the client "My VoiceMAil PIN" and it will work. IE the value you enter in My VoiceMail PIN must match the value in "Password" under "Authentication" on the 3CX phone system.....Can we fix this rather confusing bug in the client please?
     
Thread Status:
Not open for further replies.