Does this have a bug number so I can track it?
Jan Janak wrote:
On 07-11 13:17, John Todd wrote:
From what I can understand of the issue you describe, it sounds like
the problem resides on the remote side, and not Asterisk's side.
You are sending an invalid request in your first query, and
Please confirm this is fixed now in CVS.
Mark
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
Hello,
I have a problem with asterisk when dial out to a SIP
provider.
Asterisk send a INVITE with no credentials, the
provider reply with a 401 Unauthorized.
However, Asterisk DOES NOT resend the invite again
with credentials. But it hangs there (maybe waiting
for a ok)
It is this a bug in
mtm spm wrote:
Hello,
I have a problem with asterisk when dial out to a SIP
provider.
Asterisk send a INVITE with no credentials, the
provider reply with a 401 Unauthorized.
However, Asterisk DOES NOT resend the invite again
with credentials. But it hangs there (maybe waiting
for a ok)
It is
Hi Olle,
--- Olle E. Johansson [EMAIL PROTECTED] wrote:
The first Invite is without credentials, since
digest authentication needs input
from the server to create credentials.
This is also what I understood too from rfc.
I was just confused becouse in the Asterisk code
there was something
Hi Olle,
--- Olle E. Johansson [EMAIL PROTECTED] wrote:
The first Invite is without credentials, since
digest authentication needs input
from the server to create credentials.
This is also what I understood too from rfc.
I was just confused becouse in the Asterisk code
there was something like
mtm spm wrote:
Hi Olle,
--- Olle E. Johansson [EMAIL PROTECTED] wrote:
The first Invite is without credentials, since
digest authentication needs input
from the server to create credentials.
This is also what I understood too from rfc.
I was just confused becouse in the Asterisk code
there was
Asterisk was wrong. Every SIP message can be challenged with 401 or 407,
depending on who is challenging.
If you send a REGISTER message then you can get 407 Proxy
Authentication Required from any proxy along the path of the message.
You can also get 401 Unauthorized from registrar.
The same for
On 07-11 13:17, John Todd wrote:
From what I can understand of the issue you describe, it sounds like
the problem resides on the remote side, and not Asterisk's side.
You are sending an invalid request in your first query, and the
remote side is sending Unauthorized, meaning that it
On 07-11 13:17, John Todd wrote:
From what I can understand of the issue you describe, it sounds like
the problem resides on the remote side, and not Asterisk's side.
You are sending an invalid request in your first query, and the
remote side is sending Unauthorized, meaning that it believes
10 matches
Mail list logo
