o Alex Balashov on 11/16/2011 12:11 AM:
I think I've figured it out. When routing the initial INVITE, I had it
hairpinned through the SBC under the 'transparent' profile because it
comes from a trusted source. The BYE that's being challenged is coming
from the callee, which is not trusted by the caller/dialog initiator.
I think that routing the initial INVITE transparently means the dialog
is associated with that profile, and that sequential requests will
take the same path. I can't selectively apply 'auth_b2b' only to an
in-dialog request when the dialog was created within 'transparent'
processing, right?
no, either you enable authentication for a call, or you don't.
but this sounds like you want to do authentication for the a leg, so
you'd have to set enable_aleg_auth:
## authentication for A (caller) leg:
#enable_aleg_auth=yes
#auth_aleg_user=$P(au)
#auth_aleg_pwd=$P(ap)
Stefan
--
tel:+491621366449
sip:[email protected]
mailto/xmpp:[email protected]
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
