Solved (Debian Beta) Latest upgrade causes Cisco phone issues

Discussion in '3CX Phone System - General' started by JST, Feb 28, 2017.

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

    JST New Member

    Joined:
    Jan 8, 2017
    Messages:
    107
    Likes Received:
    1
    I have updated to the latest Debian version (beta) last Friday and found that my Cisco phone is no longer registering.

    The log shows the following:
    02/28/2017 9:43:05 AM - [CM102001]: Authentication failed for AuthFail Recv Req REFER from 192.168.1.236:52589 tid=a0263fdb Call-ID=0021d8ba-40590002-3cdbe554-d06feb0f@192.168.1.236: REFER sip:192.168.1.30 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.236:5060;branch=z9hG4bKa0263fdb Max-Forwards: 70 Require: norefersub Contact: <sip:0021d8ba4059@192.168.1.236:5060> To: <sip:192.168.1.30> From: <sip:0021d8ba4059@192.168.1.236>;tag=0021d8ba40590002e7bd3f06-490432c9 Call-ID: 0021d8ba-40590002-3cdbe554-d06feb0f@192.168.1.236 CSeq: 1001 REFER Expires: 10 Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, UPDATE, SUBSCRIBE Content-Disposition: session;handling=required Content-ID: <9f2428b0@192.168.1.236> Content-Type: application/x-cisco-alarm+xml Date: Tue, 28 Feb 2017 17:43:04 GMT Proxy-Authorization: Digest username="1010",realm="3CXPhoneSystem",uri="sip:192.168.1.30",response="4c72e61d14269a60c7875435c3f351a3",nonce="414d535958b5b6a928:afd17ba03394a79cffdea0c88184701b",algorithm=MD5 User-Agent: Cisco-CP7975G/9.3.1 Refer-To: cid:9f2428b0@192.168.1.236 Referred-By: <sip:0021d8ba4059@192.168.1.236> Content-Length: 1309 <?xml version="1.0" encoding="UTF-8"?> <x-cisco-alarm> <Alarm Name="LastOutOfServiceInformation"> <ParameterList> <String name="DeviceName">SEPxxxxxxxxxxxx</String> <String name="DeviceIPv4Address">192.168.1.236/24</String> <String name="IPv4DefaultGateway">192.168.1.1</String> <String name="DeviceIPv6Address"></String> <String name="IPv6DefaultGateway"></String> <String name="ModelNumber">CP-7975G</String> <String name="NeighborIPv4Address">192.168.1.69</String> <String name="NeighborIPv6Address"></String> <String name="NeighborDeviceID">GS1900</String> <String name="NeighborPortID"></String> <Enum name="DHCPv4Status">1</Enum> <Enum name="DHCPv6Status">0</Enum> <Enum name="TFTPCfgStatus">1</Enum> <Enum name="DNSStatusUnifiedCM1">4</Enum> <Enum name="DNSStatusUnifiedCM2">0</Enum> <Enum name="DNSStatusUnifiedCM3">0</Enum> <String name="VoiceVLAN">4095</String> <String name="UnifiedCMIPAddress">192.168.1.30</String> <String name="LocalPort">51181</String> <String name="TimeStamp">14881351581691464972996522</String> <Enum name="ReasonForOutOfService">12</Enum> <String name="LastProtocolEventSent"></String> <String name="LastProtocolEventReceived">Rcvd:SIP/2.0 404 User Cseq:1001 REFER CallId:0021d8ba-40590002-4a98694c-68ac18dd@192.168.1.236</String> </ParameterList> </Alarm> </x-cisco-alarm>; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings


    The log claims that the credentials don't match, but I have compared the auth id and password in the provisioning file with the extension and it matches.

    Is this a known issue?
     
  2. JST

    JST New Member

    Joined:
    Jan 8, 2017
    Messages:
    107
    Likes Received:
    1
    I found that the configuration file was corrupted. While it had the correct authentication information, some other areas were incorrect. It all went back to normal when I restored the XML file from a backup.

    This thread can be closed. Non issue!
     
  3. GiannosC_3CX

    GiannosC_3CX Guest

    Hi JST,

    Glad to hear the issue is resolved and thanks for sharing the solution :)
     
Thread Status:
Not open for further replies.