22 Jun
2005
22 Jun
'05
12:27 p.m.
hi,
i know this might be the wrong list for that question, but i know
there are many good people in here using ser and sipura atas. i am
trying to send a NOTIFY message to a sipura ata, containing a resync
request. i do this via sipsak and a textfile containing the NOTIFY
message with an event of resync;tftp ... blah.
i then get, as mentioned on sipura website a 401 unauthorized
challenge back from the box. now i am supposed to send account
password computed with md5.
questions: which account password? the one for the account
configured on the box? or the admin password of the box? and how do
i send that to the box after the challenge arrived? don't i have to
set the correct message-ids and stuff?
does someone have a working example of messages and commands to get a
sipura nbox to resync its profile?
any help would be appreciated.
Brgds,
Gerd
22 Jun
22 Jun
9:02 p.m.
Hello,
On Wednesday 22 June 2005 12:27, Gerd Feiner wrote:
i know this might be the wrong list for that question,
but i know
there are many good people in here using ser and sipura atas. i am
trying to send a NOTIFY message to a sipura ata, containing a resync
request. i do this via sipsak and a textfile containing the NOTIFY
message with an event of resync;tftp ... blah.
i then get, as mentioned on sipura website a 401 unauthorized
challenge back from the box. now i am supposed to send account
password computed with md5.
questions: which account password? the one for the account
configured on the box? or the admin password of the box? and how do
i send that to the box after the challenge arrived? don't i have to
set the correct message-ids and stuff?
theoretically you only have to provide the right password via the -a option to
sipsak, then sipsak should try to answer the challenge for you. But I can not
answer your question which password is the right on. Just try one after
another ;-)
Regards
Nils
24 Jun
24 Jun
3:46 p.m.
Ok,
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
???
notify-resync.txt is like this:
NOTIFY <sip-uri> SIP/2.0
Via: SIP/2.0/UDP <sip-server>:5060
From: <sip-server-uri>
To: <sip-uri>
Contact: <sip-server-uri>
Call-ID: 4d61cf9e505d40e905032a18329d61ec at <sip-server>
CSeq: 1 NOTIFY
User-Agent: SipSak
Event: resync;tftp://<tftp-server>/spa$MA.cfg
Content-Type: application/simple-message-summary
Content-Length: 0
( with the two following blank lines )
Brgds,
Gerd
Am 22.06.2005 um 21:02 schrieb Nils Ohlmeier:
Hello,
On Wednesday 22 June 2005 12:27, Gerd Feiner wrote:
i know this might be the wrong list for that
question, but i know
there are many good people in here using ser and sipura atas. i am
trying to send a NOTIFY message to a sipura ata, containing a resync
request. i do this via sipsak and a textfile containing the NOTIFY
message with an event of resync;tftp ... blah.
i then get, as mentioned on sipura website a 401 unauthorized
challenge back from the box. now i am supposed to send account
password computed with md5.
questions: which account password? the one for the account
configured on the box? or the admin password of the box? and how do
i send that to the box after the challenge arrived? don't i have to
set the correct message-ids and stuff?
theoretically you only have to provide the right password via the -
a option to
sipsak, then sipsak should try to answer the challenge for you. But
I can not
answer your question which password is the right on. Just try one
after
another ;-)
Regards
Nils
15 Jul
15 Jul
11:05 p.m.
Gerd Feiner wrote:
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
--
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 *****
11:28 p.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
6873
days inactive
6896
days old
4 comments
3 participants
participants (3)
-
Gerd Feiner -
Nils Ohlmeier -
Tim Bray