On 11/16/2011 06:17 AM, Stefan Sayer wrote:
Question about this:
If I route an initial INVITE request through auth_b2b, will the
credentials supplied there in, say, P-App-Param, be kept in memory and
reused for all subsequent authentication challenges within that
dialog, e.g. BYE? Or do I still have to explicitly provide the
yes
credentials needed to answer a challenge to subsequent requests?
no
Well, here's my inbound scenario: A calls B through SEMS. B trusts
SEMS via IP, does not challenge the INVITE or anything, but I still
run the call through auth_b2b. However, when A does not IP-trust
SEMS, so when B hangs up on A, A challenges the BYE.
(This is ignoring, for the sake of simplicity, other A-leg challenges
for other in-dialog requests that can arise from the receiving end.)
If no digest challenge authentication occurred on the initial INVITE,
what is the appropriate way to handle this situation in the other
direction for the BYE? Should I provide credentials in the
P-App-Param header in the BYE originating from B, with A leg
authentication enabled as you indicated? Or something else?
Thanks for the insights!
-- Alex
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
