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?
--
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
