On 07/02/2010 03:22 AM, "Ján ONDREJ (SAL)" wrote:
I use defaults, so looks like I use automatic restore. I don't know, how to
send it manually, so auto looks to be a good choice. uac_restore_from can't
be used from reply route.
If you are using the "auto" restore mode, it is not necessary to c
On Fri, Jul 02, 2010 at 03:05:40AM -0400, Alex Balashov wrote:
> On 07/02/2010 02:54 AM, Ján ONDREJ (SAL) wrote:
>
> >My target is checking for their domain in From: header. Can I use some
> >transactional rewrite, which can automatically rewrite this change back?
> >I tryed to use t_on_reply with
On 07/02/2010 02:54 AM, Ján ONDREJ (SAL) wrote:
My target is checking for their domain in From: header. Can I use some
transactional rewrite, which can automatically rewrite this change back?
I tryed to use t_on_reply without success yet.
It is not something a proxy is supposed to be able to d
> > Is something wrong in my configuration? How these authenticate packets
> > should look?
>
> I never used uac_auth() so far, but normally you send a request like an
> INVITE
> to the host, its then challenged with e.g. a 401 including a nonce and some
> other parameters, you ACK it, and then
On Thursday 01 July 2010, Ján ONDREJ (SAL) wrote:
> > ok, i'll change it in the code.
>
> Thank you.
Hello Jan,
> Even if it's better, it still don't work for me.
>
> Here is what is logged in log:
>
> 0(1515) DEBUG: uac [auth_hdr.c:409]: hdr is username="07500", realm="BroadWorks",
> non
Am 01.07.2010 15:14, schrieb Ján ONDREJ (SAL):
But I con't find any response in ACK packet send to our provider:
The ACK is just to finalize the rejected INVITE. Kamailio should send
another INVITE request with proper credentials.
regards
Klaus
On Tue, Jun 29, 2010 at 12:24:03PM +0200, Henning Westerholt wrote:
> On Friday 18 June 2010, Iñaki Baz Castillo wrote:
> > 2010/6/18 Iñaki Baz Castillo :
> > > 2010/6/17 Klaus Darilion :
> > >> looks like the header is buggy, it should be "Digest":
> > >>> challenge = ("Digest" LWS dig
On Friday 18 June 2010, Iñaki Baz Castillo wrote:
> 2010/6/18 Iñaki Baz Castillo :
> > 2010/6/17 Klaus Darilion :
> >> looks like the header is buggy, it should be "Digest":
> >>> challenge = ("Digest" LWS digest-cln *(COMMA digest-cln))
> >
> > The header is not buggy as 99.9% of SIP A
2010/6/18 Stefan Sayer :
> but is that also true if the "Digest" appears as is in the ABNF?
>
> just curious
Yes, there is no special reason for it.
RFC 3261 - 25.1
-
Many SIP header field values consist of words separated by LWS or
special characters. Unless othe
2010/6/18 Iñaki Baz Castillo :
> 2010/6/17 Klaus Darilion :
>> looks like the header is buggy, it should be "Digest":
>>> challenge = ("Digest" LWS digest-cln *(COMMA digest-cln))
>
> The header is not buggy as 99.9% of SIP ABNF grammar is case
> insensitive. In fact the only case sensi
2010/6/17 Klaus Darilion :
> looks like the header is buggy, it should be "Digest":
>> challenge = ("Digest" LWS digest-cln *(COMMA digest-cln))
The header is not buggy as 99.9% of SIP ABNF grammar is case
insensitive. In fact the only case sensitive are the SIP methods
(INVITE, REGIST
Am 17.06.2010 15:51, schrieb Ján ONDREJ (SAL):
WWW-Authenticate: DIGEST
realm="BroadWorks",qop="auth",algorithm=MD5,nonce="BroadWorksXgajlo4shTqsrkgdBW".
looks like the header is buggy, it should be "Digest":
> challenge = ("Digest" LWS digest-cln *(COMMA digest-cln))
In module
Hello,
our voip provider requires autentication to voip services. Trying to use
UAC module, I get "401 Unauthorized" packet, but looks like all ser based
programs have problems to parse this packet. Can somebody make a patch to
fix this?
Here is message from logs:
Jun 17 15:01:42 kamailio /u
13 matches
Mail list logo
