ocsg custom development

 Let us discuss various ways we can do custom development in ocsg.

1- We write a new communication service when none of the already provided northbound interfaces serve our purpose e.g. parlayx 3.0 account management etc

2- We write a southbound plugin when none of the already provided southbound plugins serve our purpose e.g. if we want 

to use parlayx 3.0 tpc northbound interface with a sip southbound which is not provided out of the box. This way we can reuse SLAs, EDRs etc logic. Correct me if we cannot reuse a northbound interface / service with custom southbound plugin.

3- We write a protocol wrapper when we do not have a protocol implementation in our network. e.g. in case of payment communication service with southbound diameter ro plugin, if we do not have a diameter ro server in our network we can write one that will integrate with ocsg and convert ocsg requests to our newtork specific implementation. This is similar to writing a custom southbound