Nope. Redirector plugin is where all routing magic happens. It is where a 404 is decided or if a fallback rule needs to be consulted for dialplans. So if the registrar needs to know whether the call can be routed based on current network state of the resource, it has to be done in the registrar. However, it is of course possible for one to totally bypass the registrar and do the decision in the proxy. You may also do it that way. As i've said, that's the way I would do it and doesn't necessarily mean its the best solution or even the correct one for that matter. Here is the currently list of redirectors

SipRedirectorAliasDB.cpp SipRedirectorGateway.cpp SipRedirectorMPT.cpp SipRedirectorSubscribe.cpp SipRedirectorAuthRouter.cpp SipRedirectorISN.cpp SipRedirectorPickUp.cpp SipRedirectorTest.cpp SipRedirectorENUM.cpp SipRedirectorJoin.cpp SipRedirectorPresenceRouting.cpp SipRedirectorTimeOfDay.cpp SipRedirectorFallback.cpp SipRedirectorMapping.cpp SipRedirectorRegDB.cpp SipRedirectorUserParam.cpp


On 03/23/2011 04:47 PM, Henry Dogger wrote:

You say a redirector plugin?

To my understanding these plugins were only used in cases of telephones registering…

CAC needs to decide on every INVITE it gets and not on registering imo…

*From:*Joegen Baclor [mailto:[email protected]]
*Sent:* woensdag 23 maart 2011 1:04
*To:* Henry Dogger
*Cc:* sipXecs developer discussions; Frans Hollander
*Subject:* Re: [sipx-dev] making redirect plugin for CAC

On 03/23/2011 12:44 AM, Henry Dogger wrote:

Or is maintaining our own DB a better option?


Maintaining your own DB is the best option.  I would do it this way.

1. Register your own implementation of SipXProxyCseObserver that writes state information to MongoDB 2. Create a Redirector plugin in the registrar which checks for CAC using the data from the MongoDB 3. Send a 5xx class response if resource towards the destination is depleted. If not let the request propagate to the normal redirectors


_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to