Re: [Serusers] sipsak, notify, sipura ata

Gerd Feiner wrote: The reason for the `unsupported authentication algorithm` message is because sipsak is case sensitive. The Sipura returns `algorithm=md5` but sipsak expects `algorithm=MD5` A quick change in the source to sipsak, to make it case insensitve in this area, and recompile gets rid of the message. But the sipura still won't accept the authentication. The password is meant to be the Line password set on the sipura - according to sipura documentation. If anybody does have a way of successfully making a sipura resync by SIP NOTIFY, I would be very grateful if the secret can be shared :) sipsak -f ../notify-resync.txt -G -a <password> -s sip:<sip url> Where notify-resync.txt is: NOTIFY sip:$user$@$dsthost$ SIP/2.0 From: sip:$srchost$:$port$ To: sip:$user$@$dsthost$ Call-ID: 46324764346@$srchost$ CSeq: 1 NOTIFY Max-Forwards: 70 Event: resync User-Agent: sipsak Content-Length: 0 -- Tim Bray Technology Manager, ProVu Communications, Marsden, Huddersfield, UK. http://www.provu.com/ Phone: +44 1484 840048 IP videophones, IP Telephones, IP Communications Solutions ***** If it is important, just phone *****