Dear all, We are attempting to use to OpenSIPS to connect to Cisco unified call manager (abbreviated as CUCM). The architecture looks like ``clients <-> OpenSIPS outbound proxy <-> CUCM'' Clients register and make calls to CUCM via OpenSIPS outbound proxy. Due to the limitation of CUCM, for each client, the OpenSIPS outbound proxy needs to use a separate port to register to CUCM (CUCM does not allow different clients to register using the same IP:port).
To address this issue, we would like to modify the source code of OpenSIPS (we know the license issue and will release the modified code if we accomplish it). The idea of modification is that we would create processes inside OpenSIPS and write some APIs to interact with the main processes. For example, when the main process finished handling a request, it will use the API to make the request be sent to the CUCM by our created process; when receiving the response from CUCM, our created process to use the API to delegate the main process to handle the response. In short, we hope that our created processes won't affect the operations of the main process while achieving our goal. I am seeking any comments on this issue. Any response is greatly appreciated. Best regards, Chen-Che -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Register-to-Cisco-call-manager-on-behalf-of-clients-tp7601683.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
