On 11/22/2011 05:31 PM, Alex Vishnev wrote:
Your registration should have also have the flow
PEER ASTERISK
REGISTER------->
<----------------------401
REGISTER(nonce) ->
<------------------------200OK
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).
Hope that helps
Alex
I've already captured with Wireshark, but what to do with it if I don't
know what I'm looking for ??
Registration goes without problem, but every INVITE is answered with a
401-Unauthorized.
Like I already said : there is no problem with Avaya, Panasonic and
Alcatel-Lucent.
The only difference I see between an INVITE from Avaya and the INVITE
from Aastra PBX is the presence of the SIP-header : "P-Behind-Gsi:
192.168.6.1".
Could this header mess up Asterisk ?
Jonas.
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
