Credentials don't match

Discussion in 'Android' started by Bob Denny, Jun 22, 2010.

Thread Status:
Not open for further replies.
  1. Bob Denny

    Bob Denny New Member

    Joined:
    Feb 21, 2009
    Messages:
    131
    Likes Received:
    2
    This should be so simple! I can't get 3CXPhone for Android to register to my 3CX server. The log says
    Code:
    15:11:58.281  [CM102001]: Authentication failed for SipReq:  REGISTER 70.167.219.233 tid=PjDkwfZ1BQdgOgIAGyCCob3QODhf.E8ksH cseq=REGISTER contact=rdennym@70.219.147.35:5060 / 11540 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
    15:11:58.281  [CM502001]: Source info: From: <sip:rdennym@70.167.219.233>;tag=cy6uuPetfQksunavREy8QALsoiIDSeju; To: <sip:rdennym@70.167.219.233>
    15:11:58.281  [CM302002]: Authentication failed due to unidentified source of: SipReq:  REGISTER 70.167.219.233 tid=PjDkwfZ1BQdgOgIAGyCCob3QODhf.E8ksH cseq=REGISTER contact=rdennym@70.219.147.35:5060 / 11540 from(wire)
    
    I'm 100% certain I have the authentication ID and password correct. I've set up a bunch of other extensions on this 3CX, I am familiar with what these are. I can get SIPDroid to register to the same extension with no problem using the same credentials.
    Code:
    15:01:08.390  [CM504002]: Ext.107: a contact is unregistered. Contact(s): []
    15:00:27.359  [CM504001]: Ext.107: new contact is registered. Contact(s): [sip:rdennym@70.167.219.234:48485;transport=tcp/107]
    
    I've typed them in 5 times (looking at each character in the invisible password as it is entered). Can anyone see anything in the above 1st set of log lines that might help me?
     
  2. Bob Denny

    Bob Denny New Member

    Joined:
    Feb 21, 2009
    Messages:
    131
    Likes Received:
    2
    Using MS Netmon3 (I am used to this not WireShark, sorry). The first REGISTER gets a 407 Proxy Auth Needed, here's the second one with the Authorization in it:
    Code:
      Frame: Number = 51, Captured Frame Length = 676, MediaType = ETHERNET 
    + Ethernet: Etype = Internet IP (IPv4),DestinationAddress:[00-13-72-12-B0-70],SourceAddress:[00-12-D9-54-73-FF]
    + Ipv4: Src = 70.219.147.35, Dest = 70.167.219.233, Next Protocol = UDP, Packet ID = 0, Total IP Length = 662
    + Udp: SrcPort = 5060, DstPort = 5060, Length = 642
    - SIP: Request: REGISTER sip:sip.dc3.com SIP/2.0
      - SipParser: Request: REGISTER sip:sip.dc3.com SIP/2.0
       - RequestLine: REGISTER sip:sip.dc3.com SIP/2.0
          Method: REGISTER
          RequestURI: sip:sip.dc3.com
          SIPVersion: SIP/2.0
       - RequestHeaders: 
        + Via: SIP/2.0/UDP 70.219.147.35:5060;rport;branch=z9hG4bKPjcGmHXmBx3KsQhzQGepsT2rz-EZz8iS0g
          Max-Forwards: 70
        + From: <sip:rdennym@sip.dc3.com>;tag=iUAWaa7ZCvG33FrDSrARVbIIi3X65MrS
        + To: <sip:rdennym@sip.dc3.com>
          CallID: 2fgVcKtDUB8Qukkr5zbjAknLrkFeRj7d
        + CSeq: 21988 REGISTER
          User-Agent: 3CXPhone 1.0.2
        + Contact: <sip:rdennym@70.219.147.35:5060>
          Expires: 1200
        - Authorization: Digest username="rdennym", realm="3CXPhoneSystem", nonce="414d535c0231dba461:28745c9f73d054c38af7a992b7d73270", uri="sip:sip.dc3.com", response="2ac9f93addaa73fcd3e75b77cd83caf9", algorithm=MD5
           scheme: Digest
           UserName: "rdennym"
           Realm: "3CXPhoneSystem"
           nonce: "414d535c0231dba461:28745c9f73d054c38af7a992b7d73270"
           uri: "sip:sip.dc3.com"
           Response: "2ac9f93addaa73fcd3e75b77cd83caf9"
           Algorithm: MD5
    
          ContentLength:  0
          HeaderEnd: CRLF
    
    and here is the 3CX response:
    Code:
      Frame: Number = 53, Captured Frame Length = 406, MediaType = ETHERNET 
    + Ethernet: Etype = Internet IP (IPv4),DestinationAddress:[00-12-D9-54-73-FF],SourceAddress:[00-13-72-12-B0-70]
    + Ipv4: Src = 70.167.219.233, Dest = 70.219.147.35, Next Protocol = UDP, Packet ID = 20620, Total IP Length = 392
    + Udp: SrcPort = 5060, DstPort = 5060, Length = 372
    - SIP: Response: SIP/2.0 404 User unknown.
      - SipParser: Response: SIP/2.0 404 User unknown.
       + StatusLine: SIP/2.0 404 User unknown.
       - ResponseHeaders: 
        + Via: SIP/2.0/UDP 70.219.147.35:5060;rport=5060;branch=z9hG4bKPjcGmHXmBx3KsQhzQGepsT2rz-EZz8iS0g
        + To: <sip:rdennym@sip.dc3.com>;tag=bc072347
        + From: <sip:rdennym@sip.dc3.com>;tag=iUAWaa7ZCvG33FrDSrARVbIIi3X65MrS
          CallID: 2fgVcKtDUB8Qukkr5zbjAknLrkFeRj7d
        + CSeq: 21988 REGISTER
          User-Agent: 3CXPhoneSystem 8.0.11264.0
          ContentLength: 0
          HeaderEnd: CRLF
    
    Can anyone make sense of this? The password ends in '58' in case that helps. Note that although it says "User unknown", the username rdennym is valid for the extension, as shown in my previous post, second log entry, see rdennym successfully register.
     
  3. LeonidasG

    LeonidasG Support Team
    Staff Member 3CX Support

    Joined:
    Nov 19, 2008
    Messages:
    1,406
    Likes Received:
    81
    Hi,

    In case you have some extra long / complex password or username, could you try using plain alphanumberic characters with no special characters?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Bob Denny

    Bob Denny New Member

    Joined:
    Feb 21, 2009
    Messages:
    131
    Likes Received:
    2
    Both are "simple". You can see the username is rdennym. The password is mxxxx58 where the 'x'es are numeric digits.

    Plus the SipDroid phone has no problems logging in with the same credentials. This is driving me crazy :shock:
     
  5. Bob Denny

    Bob Denny New Member

    Joined:
    Feb 21, 2009
    Messages:
    131
    Likes Received:
    2
    Solved(?) Credentials don't match

    By changing the authentication ID and password to '107' in the server and in the phone it registers! I have a vague recollection about having to do this on the Linksys PAP2T FXS extensions as well. Why would the extension number work as a username/password and not something else? This may be a dumb question...

    [edit] The password doesn't have to be '107' or an extension number.
     
  6. mazhar

    Joined:
    Apr 27, 2010
    Messages:
    10
    Likes Received:
    0
    Hi,

    We've just started implementing 3CX and have completed the setup of the firewall. The firewall doesn't report any issues as well.

    However, I'm unable to authenticate an extension using the 3CX Phone over the Internet IP. The 3CX phone works fine on another PC that is on the LAN. I'm using a simple extension as 225 and a simple password.

    Even the same issue happens with 3CX Phone for Android. I get this error.
    "13:58:21.443 [CM102001]: Authentication failed for SipReq: REGISTER X.X.X.X
    tid=f0107499241b7595859cf848e2a0e1b2 cseq=REGISTER contact=225@188.50.98.16 / 22477 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings"

    I dont' find any option to enter the authorzation-ID in the extension settings on the 3CX Phone or 3CX Phone for Android. Only option available is to enter the extension & password.

    Can someone help me out what is going wrong?

    Thanks,
    Mazhar
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. mazhar

    Joined:
    Apr 27, 2010
    Messages:
    10
    Likes Received:
    0
    After a bit of working around with the pix firewall, I was able to get the system up and running. Now all the clients are able to connect to my 3CX system over the internet. Wanted to share the command line configuration for pix firewall for everyone's reference. The guide given on the 3CX wiki site works with the http access which unfortunately didn't work for my firewall. Probably due to some java issues.

    Please replace the **OUTSIDE IP** with your Internet IP.

    global (outside) 1 interface
    nat (inside) 1 10.81.16.0 255.255.240.0


    static (inside,outside) tcp **OUTSIDE IP** sip 10.81.16.3 sip netmask 255.255.255.255
    static (inside,outside) udp **OUTSIDE IP** sip 10.81.16.3 sip netmask 255.255.255.255
    access-list 100 extended permit tcp any host **OUTSIDE IP** eq 5060
    access-list 100 extended permit udp any host **OUTSIDE IP** eq 5060

    static (inside,outside) udp **OUTSIDE IP** 9000 10.81.16.3 9000 netmask 255.255.255.255
    static (inside,outside) udp **OUTSIDE IP** 9001 10.81.16.3 9001 netmask 255.255.255.255
    static (inside,outside) udp **OUTSIDE IP** 9002 10.81.16.3 9002 netmask 255.255.255.255
    static (inside,outside) udp **OUTSIDE IP** 9003 10.81.16.3 9003 netmask 255.255.255.255
    static (inside,outside) udp **OUTSIDE IP** 9004 10.81.16.3 9004 netmask 255.255.255.255
    static (inside,outside) udp **OUTSIDE IP** 9005 10.81.16.3 9005 netmask 255.255.255.255
    access-list 100 extended permit udp any host **OUTSIDE IP** eq 9000
    access-list 100 extended permit udp any host **OUTSIDE IP** eq 9001
    access-list 100 extended permit udp any host **OUTSIDE IP** eq 9002
    access-list 100 extended permit udp any host **OUTSIDE IP** eq 9003
    access-list 100 extended permit udp any host **OUTSIDE IP** eq 9004
    access-list 100 extended permit udp any host **OUTSIDE IP** eq 9005

    static (inside,outside) tcp **OUTSIDE IP** 5090 10.81.16.3 5090 netmask 255.255.255.255
    static (inside,outside) udp **OUTSIDE IP** 5090 10.81.16.3 5090 netmask 255.255.255.255
    access-list 100 extended permit tcp any host **OUTSIDE IP** eq 5090
    access-list 100 extended permit udp any host **OUTSIDE IP** eq 5090

    access-group 100 in interface outside
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. Nattapong

    Joined:
    Jun 21, 2012
    Messages:
    1
    Likes Received:
    0
    I used 3CX verion 2.0.4 on Samsung Galaxy S2. At first I found error same as your post as "Credentials don't match, check that authorization-ID and password match the ones in extension settings". And my phone cannot registered.

    Now I change setting on profile credentials as follow
    User ==> extention
    ID ==> Authentication ID
    Password ==> Authentication password

    Then do regiser again, it's work now.
     
Thread Status:
Not open for further replies.