<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 11/22/2011 05:31 PM, Alex Vishnev wrote:
<blockquote
cite="mid:0C0CC17B-173A-4BFE-897C-5B9ECD124812@gmail.com"
type="cite">Your registration should have also have the flow
<div><br>
</div>
<div>PEER ASTERISK</div>
<div>REGISTER-------></div>
<div><----------------------401</div>
<div>REGISTER(nonce) -></div>
<div><------------------------200OK</div>
<div><br>
</div>
<div>Then the server controls the life of the registration and 200
Expires Header gives you this timeout. If the invite is sent
within that window, then Asterisk should not challenge anymore.
If Invite is challenged and the peer responds with the correctly
calculated NONCE, domain and other Auth params, then something
is wrong with your Authentication. I suggest trapping the
traffic with Ethereal or any other packet capture programs and
examining that carefully from the start of the session (i.e.
register) to the invite. I would also check where the 401 is
coming from (i.e. IP address).</div>
<div><br>
</div>
<div>Hope that helps</div>
<div><br>
</div>
<div>Alex <br>
</div>
</blockquote>
<br>
<br>
I've already captured with Wireshark, but what to do with it if I
don't know what I'm looking for ??<br>
<br>
Registration goes without problem, but every INVITE is answered with
a 401-Unauthorized.<br>
<br>
Like I already said : there is no problem with Avaya, Panasonic and
Alcatel-Lucent.<br>
The only difference I see between an INVITE from Avaya and the
INVITE from Aastra PBX is the presence of the SIP-header : <font
face="Helvetica, Arial, sans-serif"> "P-Behind-Gsi: 192.168.6.1".<br>
<br>
Could this header mess up Asterisk ?<br>
<br>
Jonas.<br>
</font>
</body>
</html>