<p dir="ltr">Hi,<br>
I am wondering that even if you accomplish it one way or another wouldn't you be limited by the number of ports a system can handle per OpenSIPS box ? </p>
<p dir="ltr">Regards,<br>
Sammy</p>
<div class="gmail_quote">On Mar 13, 2016 7:25 PM, "Adrian Georgescu" <<a href="mailto:ag@ag-projects.com">ag@ag-projects.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If you get rid of CUCM, your life would be much much easier.<br>
<br>
Adrian<br>
<br>
<br>
> On 25 Feb 2016, at 05:11, Chen-Che Huang <<a href="mailto:acmicrox@gmail.com">acmicrox@gmail.com</a>> wrote:<br>
><br>
> Dear all,<br>
><br>
> We are attempting to use to OpenSIPS to connect to Cisco unified call<br>
> manager (abbreviated as CUCM). The architecture looks like ``clients <-><br>
> OpenSIPS outbound proxy <-> CUCM''<br>
> Clients register and make calls to CUCM via OpenSIPS outbound proxy. Due to<br>
> the limitation of CUCM, for each client, the OpenSIPS outbound proxy needs<br>
> to use a separate port to register to CUCM (CUCM does not allow different<br>
> clients to register using the same IP:port).<br>
><br>
> To address this issue, we would like to modify the source code of OpenSIPS<br>
> (we know the license issue and will release the modified code if we<br>
> accomplish it). The idea of modification is that we would create processes<br>
> inside OpenSIPS and write some APIs to interact with the main processes. For<br>
> example, when the main process finished handling a request, it will use the<br>
> API to make the request be sent to the CUCM by our created process; when<br>
> receiving the response from CUCM, our created process to use the API to<br>
> delegate the main process to handle the response.<br>
><br>
> In short, we hope that our created processes won't affect the operations of<br>
> the main process while achieving our goal. I am seeking any comments on this<br>
> issue. Any response is greatly appreciated.<br>
><br>
> Best regards,<br>
> Chen-Che<br>
><br>
><br>
><br>
> --<br>
> View this message in context: <a href="http://opensips-open-sip-server.1449251.n2.nabble.com/Register-to-Cisco-call-manager-on-behalf-of-clients-tp7601683.html" rel="noreferrer" target="_blank">http://opensips-open-sip-server.1449251.n2.nabble.com/Register-to-Cisco-call-manager-on-behalf-of-clients-tp7601683.html</a><br>
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.<br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
<br>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div>