Hi - wanted to follow up here. Maybe I can start with a more direction question.
I've been combing through the documentation trying to understand sprout better. I must be missing something because I can't seem to find anything that talks about how sprout routes requests. To upstream servers. Could someone explain that - basically I would need to customize that routing process. Thanks, Colin On Sat, Jun 4, 2016 at 9:19 AM Colin Morelli <[email protected]> wrote: > Hey all, > > I've been looking around for a good, horizontally scalable SIP edge proxy, > transaction-stateful proxy, and registration for a bit. So far CW appears > to be the best option. I'm trying to understand if it'll work well for my > use case, where I have FS as a media server (being controlled by my API), > and need an edge proxy + registrar and stateful proxy. > > The first challenge is that for registration, many of my devices register > with JSON Web Tokens. In my prototype, FS calls my API with all of the > headers in the SIP register request and I verify the token in my > application. Is this something I can do with CW's registrar? > > The second "challenge" is selecting the appropriate FS instance for a > call. Ideally each time a new dialog is created CW can call out to my > application to see which FS instance to proxy that request to. I have some > business rules around where to place certain calls. > > I'd love any pointers to the docs (if available) on how I can accomplish > these things, or examples from your own experiences if anyone else has had > similar requirements. Thanks in advance. > > Best, > Colin >
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
