Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds a parameters= option to the Routing: response from radius #39

Closed

Conversation

twmobius
Copy link
Contributor

The contents of the parameters= attribute are expected to be key=value pairs that are then sent with each following accounting radius event, back to the radius server.

See also related issue #37

… from radius. The contents of the parameters= attribute are expected to be key=value pairs that are then sent with each following accounting radius event back to the radius server
@sobomax sobomax closed this Aug 1, 2024
@sobomax sobomax reopened this Aug 1, 2024
@sobomax
Copy link
Member

sobomax commented Aug 1, 2024

Opps, sorry wrong link. This one is still pending.

@sobomax
Copy link
Member

sobomax commented Aug 11, 2024

Hi,

Thanks for submission and sorry it took long time to process. As with the --pre_auth_proc, I ended up adding a generalized processor, which is called before the outbound call leg is initiated. It can be employed by returning "po_proc" attribute in the routing string, i.e. po_proc=VAL2Xattrs[x-attr=val1,y-attr=val2].

@sobomax sobomax closed this Aug 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants