Hi DanB,
Interesting setup you have there. I might give it a try as well. Had
never heard of b2bua.org before but I see it could be useful.
Back to the problem:
I've compared your scenario with mine and I noticed a difference in
authentication handling. Your 'proxy' (b2bua) is sending a 401
(Unauthorized) where in my case it's sending a 407 (Proxy Authentication
Required).
Then I found this in the code of click2dial (Click2Dial.cpp line 256:)
if(reply.code == 407 && cred.get() != NULL) {
AmB2BSession::onB2BEvent(ev);
return;
}
So it's handling a 407 (Proxy Authentication Required) there. It doesn't
mention a 401 (Unauthorized) like it's receiving in your setup. I think
the click2dial app is getting confused there and is trying to handle the
401 in the first call leg. And ultimately (when it failes to handle it
properly) it's sending the BYE.
You could try modifying the code a bit to look like:
if( (reply.code == 401 || reply.code == 407) && cred.get() !=
NULL) {
AmB2BSession::onB2BEvent(ev);
return;
}
Let's see what that does...
Alternatively you could try to persuade (force) your proxy to send a 407
in stead of a 401. Let me know how this works out for you!
Regards,
Tom van der Geer
-------- Originele bericht --------
Onderwerp: Re: [Sems] click2dial auth issues
Van: Dan-Cristian Bogos <[email protected]>
Aan: [email protected]
Datum: 31-1-2009 12:26
Hey Tom,
I use B2bua as interface to all the traffic leaving my voip network to
PSTN termination. Therefore it is there where all the accounts are
checked, credit time limited and clean accounting done (actually it is
the radius the clever brain). There are more applications under the
protection of b2bua software and it's a clean way of removing all the
headers which could disclosure any kind of internal architecture of my
network or my client's ips (since it's money and competition involved my
customers do require this - don't want to start again a dispute on
whether b2bua software should be used or not).
So my architecture in this case is following:
XmlrpcClient -> SEMS -> B2bua -> PSTN provider
Again, the problem I get:
*SEMS connecting the first call right (all the auth and media
established properly).
*SEMS trying to establish the second call, it get's challenged by the
B2bua and sends out properly the new invite with credentials.
*Right after this (INVITE with auth headers sent for the second call),
it will issue a BYE to the first call (without any error in the logs, or
maybe saying something which I cannot spot out - here would appreciate
any good eye catching it from the logs I have originally sent).
I should mention that the complete scenario works smooth without
authentication.
Cheers,
DanB
On Sat, 2009-01-31 at 12:00 +0100, [email protected] wrote:
Re: [Sems] click2dial auth issues
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
