Hello list, A while ago it was clear that uac_auth is of limited utility, due to the SIP RFC which requires that each message has a unique cseq. Calling uac_auth from failure_route produced a new INVITE with a proxy-auth header that didn't have a new cseq however.
Since the dialog module appeared, I'm wondering how if scripts can be tweaked to use uac_auth in a SIP RFC compliant way. ...or is it still true that doing uac_auth() in failure_route fills in the proxy-auth header of a INVITE message that has already expired its cseq (no longer valid in the dialog)? How can uac_auth be used with INVITE messages in a SIP RFC compliant way? Regards, Brian _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
