7 apr 2009 kl. 18.26 skrev Florian Hackenberger:
> On Tuesday 07 April 2009, Olle E. Johansson wrote:
>> I don't see any problems there. YOu still have devices with states,
>> as you would have with authentication. Of course, it still depends on
>> your configuration. But authentication should no
On Tuesday 07 April 2009, Olle E. Johansson wrote:
> I don't see any problems there. YOu still have devices with states,
> as you would have with authentication. Of course, it still depends on
> your configuration. But authentication should not affect states.
Ok, thanks for that, I'll have a look a
7 apr 2009 kl. 11.49 skrev Florian Hackenberger:
> On Tuesday 07 April 2009, Olle E. Johansson wrote:
>> Well, you can have OpenSER doing the authentication and turn it
>> off in Asterisk, but still match a device.
> Ok, but what about sip device state? Will that work? Will asterisk
> report the
On Tuesday 07 April 2009, Olle E. Johansson wrote:
> Well, you can have OpenSER doing the authentication and turn it
> off in Asterisk, but still match a device.
Ok, but what about sip device state? Will that work? Will asterisk
report the device as busy when the sip device is engaged in a call?
6 apr 2009 kl. 09.58 skrev Florian Hackenberger:
> Hi Philipp!
>
> On Sunday 05 April 2009, Philipp von Klitzing wrote:
>> Take a look at these two links:
> Thanks for the links! So one option is to implement domain based
> authentication, which would be quite a bit of work. Another option
> whic
Hi Philipp!
On Sunday 05 April 2009, Philipp von Klitzing wrote:
> Take a look at these two links:
Thanks for the links! So one option is to implement domain based
authentication, which would be quite a bit of work. Another option
which is quite popular is using an openSER (one of the two forks)
Hi Florian!
> > yes, that's Asterisk's problem but it seems OP is talking here about
> > something else that produces that particular message "check_auth:
> > username mismatch, have <7705>, digest has <7736>"
>
> I debugged the source code a bit and it is indeed an asterisk bug.
> However, I sus
On Saturday 04 April 2009 18:40:11 Martin wrote:
> yes, that's Asterisk's problem but it seems OP is talking here about
> something else that produces that particular
> message "check_auth: username mismatch, have <7705>, digest has <7736>"
I debugged the source code a bit and it is indeed an aste
4 apr 2009 kl. 19.31 skrev Benny Amorsen:
> Martin writes:
>
>> yes, that's Asterisk's problem but it seems OP is talking here about
>> something else that produces that particular
>> message "check_auth: username mismatch, have <7705>, digest has
>> <7736>"
>
> I really believe it's the same
Martin writes:
> yes, that's Asterisk's problem but it seems OP is talking here about
> something else that produces that particular
> message "check_auth: username mismatch, have <7705>, digest has <7736>"
I really believe it's the same bug. That is exactly what Asterisk says
if you have two pe
yes, that's Asterisk's problem but it seems OP is talking here about
something else that produces that particular
message "check_auth: username mismatch, have <7705>, digest has <7736>"
Martin
On Sat, Apr 4, 2009 at 4:10 AM, Benny Amorsen wrote:
> Martin writes:
>
>> The SNOM evidently has a bu
Martin writes:
> The SNOM evidently has a bug. When it originates the call as user 7705
> then it should also authenticate
> as user 7736. Asterisk doesn't like it. You'd have to patch your
> asterisk to remove that check.
Snom doesn't have a bug, Asterisk does. If you have multiple peer
account
Hi
On Fri, Apr 3, 2009 at 1:57 PM, Florian Hackenberger
wrote:
> Hi!
>
> When using multiple identities on one physical phone (Snom 320), I get
>
> check_auth: username mismatch, have <7705>, digest has <7736>
The SNOM evidently has a bug. When it originates the call as user 7705
then it should a
Hi!
When using multiple identities on one physical phone (Snom 320), I get
check_auth: username mismatch, have <7705>, digest has <7736>
messages when placing a call from a different account than the first
one. From reading the asterisk source, I can see that the problem is
that peer authentic
14 matches
Mail list logo
