Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#164 closed баг (fixed)

ua PhonerLite не может зарегистрироваться на ve-01

Reported by: san Owned by: alx
Priority: средний Milestone: 2 очередь
Component: any Keywords:
Cc:

Description

Ошибка: Invalid password provided
http://phonerlite.de/index_en.htm

Change History (5)

comment:1 by alx, 8 years ago

12:18:52.492930 IP (tos 0x0, ttl 128, id 64434, offset 0, flags [none], proto UDP (17), length 592)
    192.168.0.5.5060 > 192.168.0.69.5060: SIP, length: 564
        REGISTER sip:192.168.0.69 SIP/2.0
        Via: SIP/2.0/UDP 192.168.0.5:5060;branch=z9hG4bK0071be8d28fbe511bcf66fc081a32b99;rport
        From: <sip:1@192.168.0.69>;tag=1063466567
        To: <sip:1@192.168.0.69>
        Call-ID: 0071BE8D-28FB-E511-BCF4-6FC081A32B99@192.168.0.5
        CSeq: 1 REGISTER
        Contact: <sip:1@192.168.0.5:5060>;+sip.instance="<urn:uuid:8017E329-9F39-E511-9878-22D40735D8E6>"
        Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE, UPDATE
        Max-Forwards: 70
        Allow-Events: org.3gpp.nwinitdereg
        User-Agent: SIPPER for PhonerLite
        Expires: 60
        Content-Length: 0

12:18:52.512774 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 505)
    192.168.0.69.5060 > 192.168.0.5.5060: SIP, length: 477
        SIP/2.0 407 Proxy Authentication Required
        Via: SIP/2.0/UDP 192.168.0.5:5060;branch=z9hG4bK0071be8d28fbe511bcf66fc081a32b99;rport=5060
        Proxy-Authenticate: Digest nonce="1460031532:4f7b5f4c298241934946911475ed2ec4",algorithm=MD5,realm="192.168.0.69",qop="auth,auth-int
"
        To: <sip:1@192.168.0.69>;tag=73342f3a
        From: <sip:1@192.168.0.69>;tag=1063466567
        Call-ID: 0071BE8D-28FB-E511-BCF4-6FC081A32B99@192.168.0.5
        CSeq: 1 REGISTER
        User-Agent: repro 1.9.10
        Content-Length: 0

12:18:52.514877 IP (tos 0x0, ttl 128, id 64437, offset 0, flags [none], proto UDP (17), length 863)
    192.168.0.5.5060 > 192.168.0.69.5060: SIP, length: 835
        REGISTER sip:192.168.0.69 SIP/2.0
        Via: SIP/2.0/UDP 192.168.0.5:5060;branch=z9hG4bK0071be8d28fbe511bcfa6fc081a32b99;rport
        From: <sip:1@192.168.0.69>;tag=1063466567
        To: <sip:1@192.168.0.69>
        Call-ID: 0071BE8D-28FB-E511-BCF4-6FC081A32B99@192.168.0.5
        CSeq: 3 REGISTER
        Contact: <sip:1@192.168.0.5:5060>;+sip.instance="<urn:uuid:8017E329-9F39-E511-9878-22D40735D8E6>"
        Proxy-Authorization: Digest username="1", realm="192.168.0.69", nonce="1460031532:4f7b5f4c298241934946911475ed2ec4", uri="sip:192.16
8.0.69", response="fd4f35a2f83dcf60e8769bc4c2155c29", algorithm=MD5, cnonce="0071be8d28fbe511bcf96fc081a32b99", qop=auth-int, nc=00000001
        Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE, UPDATE
        Max-Forwards: 70
        Allow-Events: org.3gpp.nwinitdereg
        User-Agent: SIPPER for PhonerLite
        Expires: 60
        Content-Length: 0

12:18:52.551821 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 366)
    192.168.0.69.5060 > 192.168.0.5.5060: SIP, length: 338
        SIP/2.0 403 Invalid password provided
        Via: SIP/2.0/UDP 192.168.0.5:5060;branch=z9hG4bK0071be8d28fbe511bcfa6fc081a32b99;rport=5060
        To: <sip:1@192.168.0.69>;tag=4413ba2e
        From: <sip:1@192.168.0.69>;tag=1063466567
        Call-ID: 0071BE8D-28FB-E511-BCF4-6FC081A32B99@192.168.0.5
        CSeq: 3 REGISTER
        User-Agent: repro 1.9.10
        Content-Length: 0

comment:2 by alx, 8 years ago

Есть предположение, что изменение в конфиг-файле /etc/repro.conf строки DisableAuthInt = false на DisableAuthInt = true решит данную проблему. Требуется проверка.

comment:3 by alx, 8 years ago

Как показала проверка, DisableAuthInt = true решает проблему. Кто-то неверно вычисляет response. Но кто именно - PhonerLite или repro - я определить не могу. Пока в качестве workaround в дефолтном конфиге установлю DisableAuthInt = true.

comment:4 by alx, 8 years ago

Resolution: fixed
Status: newclosed

In 1026/sip_ua:

Параметр DisableAuthInt установлен в значение true, так как есть подозрение
что repro неверно вычисляет ответ при проверке аутентификации. Closes #164.

comment:5 by alx, 8 years ago

Как показала дальнейшая проверка, sipp аутентифицируется с использованием qop=auth-int нормально. Следовательно, проблема в PhonerLite - он неверно вычисляет ответ.
В r1033 параметр DisableAuthInt вернули в значение false.

Note: See TracTickets for help on using tickets.