<div dir="ltr">Yes, my inbound and outbound provider is same.<div>Currently I am trying to forward the register request from my asterisk to my kamailio and then to my SIP provider. I am able to get the request in kamailio but unable to forward it to the provider. Can you suggest how can I forward asterisk OPTIONS and REGISTER messages via kamailio.</div><div>My logic is to use the same Asterisk request and change the source IP to my kamailio IP and forward it to the SIP provider. This would register my kamailio to the provider and hence would send calls to kamailio which I can dispatch to different asterisk servers. Theoretically this makes sense and should be achievable if I am able to forward calls via kamailio which i know is possible but do not know how to do it.</div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, Jan 5, 2019 at 3:57 PM David Villasmil <<a href="mailto:david.villasmil.work@gmail.com">david.villasmil.work@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Is the outbound provider the same as the inbound?<br>In my case the inbound was sending calls to my unregistered kamailio (ip whitelisting)<br>But the outbound provider requires registration.<br><br>In my case, I just added to the gw configuration in freeswitch a proxy with my kamailio. Something like:<br><br>outboundproxy=4.3.2.1<br><br>That should send all outbound regs and calls via your kamailio.<br><br>But if in your case, your provider will use that registration to send YOU calls, this will probably not work. You’d indeed need to register from kamailio. Something I understand is possible, but never been able to do.<br><div class="gmail_quote"><div dir="ltr">On Sat, 5 Jan 2019 at 06:07, Prashant Gupta <<a href="mailto:prashant@farmguide.in" target="_blank">prashant@farmguide.in</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Thanks for the reply. Can you please explain how can I achieve this?<div>In this scenario, will the incoming calls still be routed through the kamailio. What about the outgoing calls? </div><div>My use case to use kamailio was to send separate incoming numbers to separate asterisk servers. Do you think this is feasible with the solution of having asterisk register to SIP via kamailio.</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jan 4, 2019 at 4:18 PM David Villasmil <<a href="mailto:david.villasmil.work@gmail.com" target="_blank">david.villasmil.work@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">This exact same thing happened to me, and I found the easiest is to register from your asterisk. Have kamailio just forward the registrations and every asterisk will be registered normally.<br><br>I know it’s not ideal, but I couldn’t make it work, and at least it’s now working perfectly.<br><br><div class="gmail_quote"><div dir="ltr">On Fri, 4 Jan 2019 at 07:51, Prashant Gupta <<a href="mailto:prashant@farmguide.in" target="_blank">prashant@farmguide.in</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hi,<div>I have the following architecture - SIP provider <-> Kamailio <-> Asterisk servers</div><div>I currently do not have any issues connecting my asterisk servers to Kamailio server. I am however having issues connecting my Kamailio server to my SIP provider. I am using the uac module for registration and have stored my credentials in the uacreg table. When I sniff on my network, I am able to see Register message being send out and receives an OK from my provider. But I am still unable to get incoming messages to Kamailio. Also these SIP responses from the SIP provider do not make it to kamailio route as I have logged any message that enter the request_route.</div><div>SIP Messages from Wireshark - </div><div>1) 19<span style="white-space:pre-wrap"> </span>563.919267<span style="white-space:pre-wrap"> </span>10.67.XXX.XXX<span style="white-space:pre-wrap"> </span>10.232.XXX.XXX<span style="white-space:pre-wrap"> </span>SIP<span style="white-space:pre-wrap"> </span>497<span style="white-space:pre-wrap"> </span>Request: REGISTER sip:<a href="http://ims.airtel.in" target="_blank">ims.airtel.in</a> (1 binding) | <br></div><div><br></div><div>2) 20<span style="white-space:pre-wrap"> </span>564.040917<span style="white-space:pre-wrap"> </span>10.232.XXX.XXX<span style="white-space:pre-wrap"> </span>10.67.XXX.XXX<span style="white-space:pre-wrap"> </span>SIP<span style="white-space:pre-wrap"> </span>480<span style="white-space:pre-wrap"> </span>Status: 401 Unauthorized | </div><div><br></div><div>3) 21<span style="white-space:pre-wrap"> </span>564.041574<span style="white-space:pre-wrap"> </span>10.67.XXX.XXX<span style="white-space:pre-wrap"> </span>10.232.XXX.XXX<span style="white-space:pre-wrap"> </span>SIP<span style="white-space:pre-wrap"> </span>744<span style="white-space:pre-wrap"> </span>Request: REGISTER sip:<a href="http://ims.airtel.in" target="_blank">ims.airtel.in</a> (1 binding) | </div><div><br></div><div>4) 22<span style="white-space:pre-wrap"> </span>564.173338<span style="white-space:pre-wrap"> </span>10.232.XXX.XXX<span style="white-space:pre-wrap"> </span>10.67.XXX.XXX<span style="white-space:pre-wrap"> </span>SIP<span style="white-space:pre-wrap"> </span>649<span style="white-space:pre-wrap"> </span>Status: 200 OK (1 binding) | </div><div><br></div><div>Here 10.232.XXX.XXX is my SIP providers proxy address and 10.67.XXX.XXX is my local IP of the lan connected to the SIP line.</div></div></div></div></div></div>
_______________________________________________<br>
Kamailio (SER) - Development Mailing List<br>
<a href="mailto:sr-dev@lists.kamailio.org" target="_blank">sr-dev@lists.kamailio.org</a><br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
</blockquote></div>
_______________________________________________<br>
Kamailio (SER) - Development Mailing List<br>
<a href="mailto:sr-dev@lists.kamailio.org" target="_blank">sr-dev@lists.kamailio.org</a><br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
</blockquote></div>
_______________________________________________<br>
Kamailio (SER) - Development Mailing List<br>
<a href="mailto:sr-dev@lists.kamailio.org" target="_blank">sr-dev@lists.kamailio.org</a><br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
</blockquote></div>
_______________________________________________<br>
Kamailio (SER) - Development Mailing List<br>
<a href="mailto:sr-dev@lists.kamailio.org" target="_blank">sr-dev@lists.kamailio.org</a><br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
</blockquote></div>