16 Jul
2005
16 Jul
'05
12:28 a.m.
Hi Tim,
nice to see you here too :-)
On Friday 15 July 2005 23:05, Tim Bray wrote:
Gerd Feiner wrote:
It seems like you are using an old sipsak version. sipsak-0.9.0 uses case
insensitive comparesing if the functions are available on the system during
compile time.
BTW you can verify if sipsak support case insensitive comparesing by looking
at the compile options from the output of 'sipsak -V'.
Nils
so how's the right syntax then? I'ver
tried
sipsak -f notify-resync.txt -a <password> -s <sip-uri>
but I get just get error: unsupported authentication algorithm
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