[Pidgin] #17414: SIP SIMPLE plugin doesn't authenticate when challenged

Pidgin trac at pidgin.im
Tue Oct 1 08:55:18 EDT 2019


#17414: SIP SIMPLE plugin doesn't authenticate when challenged
-----------------------------+--------------------
 Reporter:  brian_j_murrell  |      Owner:
     Type:  defect           |     Status:  new
Milestone:                   |  Component:  SIMPLE
  Version:  2.13.0           |   Keywords:
-----------------------------+--------------------
 Trying to send a SIP MESSAGE to a SIP server, pidgin doesn't authenticate
 when challenged:


 {{{
 (08:49:16) stun: using server
 (08:49:16) simple:

 sending - Tue Oct  1 08:49:16 2019

 ######
 MESSAGE sip:my_sip_account SIP/2.0
 Via: SIP/2.0/TCP 192.168.122.1:5060;branch=z9hG4bK266874BDC079E9B9E701
 From: <sip:pidgin at pbx.example.com>;tag=1513954998;epid=1234567890
 To: <sip:my_sip_account>
 Max-Forwards: 10
 CSeq: 7 MESSAGE
 User-Agent: Purple/2.13.0
 Call-ID: 8E56g6255aDC0Ci7C25m2A70tD2CCb41CBx5C5Ex
 Content-Type: application/im-iscomposing+xml
 Content-Length: 322

 <?xml version="1.0" encoding="UTF-8"?>
 <isComposing xmlns="urn:ietf:params:xml:ns:im-iscomposing"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:ietf:params:xml:ns:im-composing iscomposing.xsd">
 <state>active</state>
 <contenttype>text/plain</contenttype>
 <refresh>60</refresh>
 </isComposing>
 ######

 (08:49:16) simple: received a incomplete sip msg: ,qop="auth"
 Server: Asterisk PBX 13.28.1
 Content-Length:  0

 (08:49:17) simple:

 sending - Tue Oct  1 08:49:17 2019

 ######
 MESSAGE sip:my_sip_account SIP/2.0
 Via: SIP/2.0/TCP 192.168.122.1:5060;branch=z9hG4bKB8FAB42DD671DA7548AC
 From: <sip:pidgin at pbx.example.com>;tag=2063662055;epid=1234567890
 To: <sip:my_sip_account>
 Max-Forwards: 10
 CSeq: 8 MESSAGE
 User-Agent: Purple/2.13.0
 Call-ID: 5C66gE98EaBFB7iD831mF1A7t69A2b9957xAABCx
 Content-Type: text/plain
 Content-Length: 5

 hello
 ######

 (08:49:17) stun: using server
 (08:49:17) simple:

 sending - Tue Oct  1 08:49:17 2019

 ######
 MESSAGE sip:my_sip_account SIP/2.0
 Via: SIP/2.0/TCP 192.168.122.1:5060;branch=z9hG4bKB1C45D5CC5443D069CE3
 From: <sip:pidgin at pbx.example.com>;tag=1336260332;epid=1234567890
 To: <sip:my_sip_account>
 Max-Forwards: 10
 CSeq: 9 MESSAGE
 User-Agent: Purple/2.13.0
 Call-ID: DB8Bg5605a0E8Di7936m79F9t9267b4EC5xA72Dx
 Content-Type: application/im-iscomposing+xml
 Content-Length: 320

 <?xml version="1.0" encoding="UTF-8"?>
 <isComposing xmlns="urn:ietf:params:xml:ns:im-iscomposing"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:ietf:params:xml:ns:im-composing iscomposing.xsd">
 <state>idle</state>
 <contenttype>text/plain</contenttype>
 <refresh>60</refresh>
 </isComposing>
 ######

 (08:49:17) simple: received a incomplete sip msg: ,qop="auth"
 Server: Asterisk PBX 13.28.1
 Content-Length:  0

 (08:49:17) simple: received a incomplete sip msg: ,qop="auth"
 Server: Asterisk PBX 13.28.1
 Content-Length:  0

 (08:49:18) simple: buddy resub
 (08:49:18) simple: buddy resub
 }}}

 Looks like it's tripping on the authentication challenge from the server:

 {{{
 WWW-Authenticate: Digest
 realm="asterisk",nonce="[redacted]/[redacted]",opaque="3cb78cf26cb36db9",algorithm=md5,qop="auth"
 }}}

 Notice at the end of that header, the ,qop="auth" that pidgin is
 complaining about in the above debug log.

--
Ticket URL: <https://developer.pidgin.im/ticket/17414>
Pidgin <https://pidgin.im>
Pidgin


More information about the Tracker mailing list