VIDEOCHAT  ::   FAQ  ::   Поиск  ::   Регистрация  ::   Вход

pjsip & auth inbound call

Проблемы Asterisk без вэб-оболочек и их решения

Модераторы: april22, Zavr2008

Ответить
kt72ru
Сообщения: 23
Зарегистрирован: 09 ноя 2016, 13:35

pjsip & auth inbound call

Сообщение kt72ru »

Добрый день!

Пытаюсь настроить работу chan_pjsip с многопортовым шлюзом.
На шлюзе стоит режим "регистрироваться как екстеншен на уд. сервере".
Со стороны asterisk прописан соответствующий endpoint.

Код: Выделить всё

    [6250156]
    type=endpoint
    transport=0.0.0.0-udp
    context=from-pstn
    disallow=all
    allow=ulaw,alaw
    aors=6250156
    auth=6250156

    [6250156]
    type=aor
    qualify_frequency=60
    max_contacts=1

    [6250156]
    type=auth
    auth_type=userpass
    password=6250156
    username=6250156
также прописан входящий маршрут на DID 06250156.
Согласно дебага не проходит аутентификация входящего вызова "Endpoint found for '6250156' but 'auth_username' method not supported'".
Не могу найти, где я допустил ошибку.

Код: Выделить всё

    [2016-11-08 21:25:16] VERBOSE[2190] res_pjsip_logger.c: <--- Received SIP request (853 bytes) from UDP:192.168.0.5:5060 --->
    INVITE sip:06250156@192.168.0.3:5060;transport=udp SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.5:5060;rport;branch=z9hG4bK21222118
    From: "3459935" <sip:3459935@192.168.0.3:5060>;tag=423662678
    To: <sip:06250156@192.168.0.3>
    Call-ID: 1907798878@192.168.0.5
    CSeq: 2 INVITE
    Contact: <sip:3459935@192.168.0.5:5060>
    Max-Forwards: 30
    User-Agent: dble
    Remote-Party-ID: "3459935" <sip:3459935@192.168.0.3>;party=calling;screen=no;privacy=off
    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REFER, REGISTER, MESSAGE, INFO, SUBSCRIBE
    Content-Type: application/sdp
    Content-Length:   230

    v=0
    o=dble 1478629516 1478629516 IN IP4 192.168.0.5
    s=dble
    c=IN IP4 192.168.0.5
    t=0 0
    m=audio 16384 RTP/AVP 8 0 101
    a=rtpmap:8 PCMA/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-15
    a=ptime:20

    [2016-11-08 21:25:16] DEBUG[2190] res_pjsip/pjsip_distributor.c: Could not find matching transaction for Request msg INVITE/cseq=2 (rdata0x7f40a4093b18)
    [2016-11-08 21:25:16] DEBUG[2190] res_pjsip/pjsip_distributor.c: Calculated serializer pjsip/distributor-0000002b to use for Request msg INVITE/cseq=2 (rdata0x7f40a4093b18)
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '203-identify'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '204-identify'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '210-identify'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '250-identify'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '208-identify'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '206-identify'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '209-identify'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '201-identify'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '207-identify'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '205-identify'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '211-identify'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '222-identify'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '202-identify'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_ip.c: '192.168.0.5:5060' did not match any identify section rules
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_user.c: Attempting identify by From username '3459935' domain '192.168.0.3'
    [2016-11-08 21:25:16] DEBUG[16578] res_pjsip_endpoint_identifier_user.c: Endpoint not found for From username '3459935' domain '192.168.0.3'
    [2016-11-08 21:25:16] NOTICE[16578] res_pjsip/pjsip_distributor.c: Request 'INVITE' from '"3459935" <sip:3459935@192.168.0.3>' failed for '192.168.0.5:5060' (callid: 1907798878@192.168.0.5) - No matching endpoint found
    [2016-11-08 21:25:16] VERBOSE[16578] res_pjsip_logger.c: <--- Transmitting SIP response (494 bytes) to UDP:192.168.0.5:5060 --->
    SIP/2.0 401 Unauthorized
    Via: SIP/2.0/UDP 192.168.0.5:5060;rport=5060;received=192.168.0.5;branch=z9hG4bK21222118
    Call-ID: 1907798878@192.168.0.5
    From: "3459935" <sip:3459935@192.168.0.3>;tag=423662678
    To: <sip:06250156@192.168.0.3>;tag=z9hG4bK21222118
    CSeq: 2 INVITE
    WWW-Authenticate: Digest  realm="asterisk",nonce="1478629516/261df6169e94825282a9433e2281fe1b",opaque="12fc5dea2bab19c8",algorithm=md5,qop="auth"
    Server: FPBX-13.0.190.2(13.12.1)
    Content-Length:  0


    [2016-11-08 21:25:16] VERBOSE[2190] res_pjsip_logger.c: <--- Received SIP request (319 bytes) from UDP:192.168.0.5:5060 --->
    ACK sip:06250156@192.168.0.3:5060;transport=udp SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.5:5060;rport;branch=z9hG4bK21222118
    From: "3459935" <sip:3459935@192.168.0.3>;tag=423662678
    To: <sip:06250156@192.168.0.3>;tag=z9hG4bK21222118
    Call-ID: 1907798878@192.168.0.5
    CSeq: 2 ACK
    Content-Length: 0


    [2016-11-08 21:25:16] DEBUG[2190] res_pjsip/pjsip_distributor.c: Could not find matching transaction for Request msg ACK/cseq=2 (rdata0x7f40a4093b18)
    [2016-11-08 21:25:16] DEBUG[2190] res_pjsip/pjsip_distributor.c: Calculated serializer pjsip/distributor-0000002b to use for Request msg ACK/cseq=2 (rdata0x7f40a4093b18)
    [2016-11-08 21:25:16] VERBOSE[2190] res_pjsip_logger.c: <--- Received SIP request (1134 bytes) from UDP:192.168.0.5:5060 --->
    INVITE sip:06250156@192.168.0.3:5060;transport=udp SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.5:5060;rport;branch=z9hG4bK2113691051
    From: "3459935" <sip:3459935@192.168.0.3>;tag=423662678
    To: <sip:06250156@192.168.0.3>
    Call-ID: 1907798878@192.168.0.5
    CSeq: 3 INVITE
    Contact: <sip:3459935@192.168.0.5:5060>
    Authorization: Digest username="6250156", realm="asterisk", nonce="1478629516/261df6169e94825282a9433e2281fe1b", uri="sip:06250156@192.168.0.3", response="38f239f08cb9384bbae900cf52c27881", algorithm=md5, cnonce="5822188c", opaque="12fc5dea2bab19c8", qop=auth, nc=00000001
    Max-Forwards: 30
    User-Agent: dble
    Remote-Party-ID: "3459935" <sip:3459935@192.168.0.3>;party=calling;screen=no;privacy=off
    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REFER, REGISTER, MESSAGE, INFO, SUBSCRIBE
    Content-Type: application/sdp
    Content-Length:   230

    v=0
    o=dble 1478629516 1478629516 IN IP4 192.168.0.5
    s=dble
    c=IN IP4 192.168.0.5
    t=0 0
    m=audio 16384 RTP/AVP 8 0 101
    a=rtpmap:8 PCMA/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-15
    a=ptime:20

    [2016-11-08 21:25:16] DEBUG[2190] res_pjsip/pjsip_distributor.c: Could not find matching transaction for Request msg INVITE/cseq=3 (rdata0x7f40a4093b18)
    [2016-11-08 21:25:16] DEBUG[2190] res_pjsip/pjsip_distributor.c: Calculated serializer pjsip/distributor-0000002b to use for Request msg INVITE/cseq=3 (rdata0x7f40a4093b18)
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '203-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '204-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '210-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '250-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '208-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '206-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '209-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '201-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '207-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '205-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '211-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '222-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '202-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: '192.168.0.5:5060' did not match any identify section rules
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_user.c: Attempting identify by From username '3459935' domain '192.168.0.3'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_user.c: Endpoint not found for From username '3459935' domain '192.168.0.3'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '203-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '204-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '210-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '250-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '208-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '206-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '209-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '201-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '207-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '205-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '211-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '222-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: Source address 192.168.0.5:5060 does not match identify '202-identify'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_ip.c: '192.168.0.5:5060' did not match any identify section rules
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_user.c: Attempting identify by From username '3459935' domain '192.168.0.3'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_user.c: Endpoint not found for From username '3459935' domain '192.168.0.3'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_user.c: Attempting identify by Authorization username '6250156' realm 'asterisk'
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_endpoint_identifier_user.c: Endpoint found for '6250156' but 'auth_username' method not supported'
    [2016-11-08 21:25:16] NOTICE[10813] res_pjsip/pjsip_distributor.c: Request 'INVITE' from '"3459935" <sip:3459935@192.168.0.3>' failed for '192.168.0.5:5060' (callid: 1907798878@192.168.0.5) - No matching endpoint found
    [2016-11-08 21:25:16] DEBUG[10813] res_pjsip_authenticator_digest.c: Calculated nonce 1478629516/261df6169e94825282a9433e2281fe1b. Actual nonce is 1478629516/261df6169e94825282a9433e2281fe1b
    [2016-11-08 21:25:16] NOTICE[10813] res_pjsip/pjsip_distributor.c: Request 'INVITE' from '"3459935" <sip:3459935@192.168.0.3>' failed for '192.168.0.5:5060' (callid: 1907798878@192.168.0.5) - Failed to authenticate
    [2016-11-08 21:25:16] VERBOSE[10813] res_pjsip_logger.c: <--- Transmitting SIP response (498 bytes) to UDP:192.168.0.5:5060 --->
    SIP/2.0 401 Unauthorized
    Via: SIP/2.0/UDP 192.168.0.5:5060;rport=5060;received=192.168.0.5;branch=z9hG4bK2113691051
    Call-ID: 1907798878@192.168.0.5
    From: "3459935" <sip:3459935@192.168.0.3>;tag=423662678
    To: <sip:06250156@192.168.0.3>;tag=z9hG4bK2113691051
    CSeq: 3 INVITE
    WWW-Authenticate: Digest  realm="asterisk",nonce="1478629516/261df6169e94825282a9433e2281fe1b",opaque="3a80797d3c4911e8",algorithm=md5,qop="auth"
    Server: FPBX-13.0.190.2(13.12.1)
    Content-Length:  0
Вернуться к началу
ded
Сообщения: 15629
Зарегистрирован: 26 авг 2010, 19:00

Re: pjsip & auth inbound call

Сообщение ded »

Инвайт идёт от юзера 3459935@192.168.0.3
а юзер то вот какой - 6250156
Along the way, the logic in res_pjsip_registrar was corrected to match
most-specific to least-specific as res_pjsip_endpoint_identifier_user does.

The order is:

username@domain
username@domain_alias
username
http://lists.digium.com/pipermail/aster ... 75198.html
Вернуться к началу
kt72ru
Сообщения: 23
Зарегистрирован: 09 ноя 2016, 13:35

Re: pjsip & auth inbound call

Сообщение kt72ru »

Спасибо за подсказку!
После прописывания identify_by=username,auth_username все чудесно заработало.
Вернуться к началу
Ответить

Вернуться в «Конфигурация и настройка Asterisk»

© 2008 — 2025 Asterisk.ru
Digium, Asterisk and AsteriskNOW are registered trademarks of Digium, Inc.
Design and development by PostMet-Netzwerk GmbH