El Tuesday 19 August 2008 14:26:31 Iñaki Baz Castillo escribió: > How does B2BUA it has already authentiacted A before?
I mean: "How does B2BUA it has already authentiacted A before?" > The behaviour is what you describe but: > - When 403 from B arrives to B2BUA, B2BUA could resend the request > with Authorization header since B2BUA is a UAC when talking with B. In this case B2BUA doesn't terminate transaction/dialog in leg A so A just needs to send credentials once (for "realm_b2bua"). > Anyway B2BUA could also send the 403 to A (it's implementator > decission). In this case B2BUA is acting more or like as a proxy and breaks both legs (A and B), so A must re-send credentials to B2BUA. -- Iñaki Baz Castillo [EMAIL PROTECTED] _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
