So as far as I understand, you receive a request and you want Freeswitch
to route it back to OpenSIPS. There is no SIP mechanism that can achieve
this - you need to configure Freeswitch so that when it gets a message
from OpenSIPS, determine the gateway, and send it back. Note that you
need to set opensips's IP in the destination URI, not the request URI,
otherwise OpenSIPS will not know the destination GW.
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 12/15/2016 01:33 PM, M. Salman wrote:
Hi,
Generally there are three ways of doing this:
1) Use SIP sever as an Edge Proxy (check rfc5626, should be a quick read)
2) Create spiral, route SIP call from proxy to your media-server and
then back to proxy from media server.
3) Use SIP sever as a registrar and then forward registrations to
media sever and maintaining it. (cheap way though)
Regards,
Salman
On Thu, Dec 15, 2016 at 4:12 PM, Muhammad Naseer Bhatti
<nbha...@gmail.com <mailto:nbha...@gmail.com>> wrote:
So the call hits the proxy and dispatched to the media server.
Media server makes the gateway selection and now need to send the
call to the provider. Instead of the signaling to be sent directly
from the media server and the provider I and trying to pass the
signaling back through the proxy so the outgoing connections to
the provider will be seen by the proxy IP address not the media
server. Both the proxy and media servers are not behind nat.
--
Sent with Airmail
From: Răzvan Crainea <raz...@opensips.org>
<mailto:raz...@opensips.org>
Reply: OpenSIPS users mailling list <users@lists.opensips.org>
<mailto:users@lists.opensips.org>
Date: December 15, 2016 at 12:55:18 PM
To: users@lists.opensips.org <mailto:users@lists.opensips.org>
<users@lists.opensips.org> <mailto:users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to Keep OpenSIPS in reverse path
I am sorry, but I don't understand your call flow. Please present
here the call flow you have now, and the expected one.
PS: not sure why you are looking at the Via header, that's only
used for replies, not for requests.
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com <http://www.opensips-solutions.com>
On 12/14/2016 07:53 PM, Muhammad Naseer Bhatti wrote:
Hi Razvan,
I am not using REGISTER, but I guess add_path() wont’ work for
me, I am using record_route() for the INVITE though.
…
if (is_method("INVITE")) {
record_route();
}
…
On the media server I see the Via header,
INVITE sip:6054775550@64.58.228.102:3333
<http://sip:6054775550@64.58.228.102:3333> SIP/2.0
Record-Route:
<sip:64.58.228.102:3333;lr=on;ftag=CT60RBHd.BRAp6IAQSKwtAN3Mjj2bPKL>
Via: SIP/2.0/UDP
64.58.228.102:3333;branch=z9hG4bK31d2.b8fe57fe9c7545e354a93f391a1d0704.0
Via: SIP/2.0/UDP
172.16.0.101:52207;received=172.16.0.101;rport=52207;branch=z9hG4bKPjyGufepGSH2zMGfp6J.CIKvEgl87YIPFN
but when the media server sends
recv 1432 bytes from udp/[64.58.228.89]:3333 at 12:44:12.709234:
------------------------------------------------------------------------
INVITE sip:6054775550@23.29.112.144:15080
<http://sip:6054775550@23.29.112.144:15080> SIP/2.0
Via: SIP/2.0/UDP
64.58.228.89:3333;rport;branch=z9hG4bKF8jFHt4maUBeQ
Max-Forwards: 68
From: "Naseer" <sip:1234@64.58.228.89
<mailto:sip%3A1234@64.58.228.89>>;tag=45yZ9S13S47HF
Not sure what I am doing wrong. Here is my script,
http://pastebin.com/Cmnxnf4c <http://pastebin.com/Cmnxnf4c>
--
Sent with Airmail
From: Răzvan Crainea <raz...@opensips.org>
<mailto:raz...@opensips.org>
Reply: OpenSIPS users mailling list <users@lists.opensips.org>
<mailto:users@lists.opensips.org>
Date: December 14, 2016 at 8:34:22 PM
To: users@lists.opensips.org <mailto:users@lists.opensips.org>
<users@lists.opensips.org> <mailto:users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to Keep OpenSIPS in reverse path
Hi, Muhammad!
The add_path() function should only be called on REGISTER
messages, and it adds a Path header (not a Via). Do you see
this header in your REGISTER message?
For sequential requests, you should use the record_route()
mechanism.
Best regards,
Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com
<http://www.opensips-solutions.com>
On 12/14/2016 06:39 PM, Muhammad Naseer Bhatti wrote:
I am using dispatcher to distribute calls to multiple media
servers, but also want the reply to go through OpenSIPS. So
far I have tried add_path() function which add the Via header
but FreeSWITCH sends the call directly to the gateway not
sending the call back through OpenSIPS. I am not sure if I am
doing something wrong, how can I achieve that?
--
Sent with Airmail
_______________________________________________ Users mailing
list Users@lists.opensips.org
<mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
_______________________________________________ Users mailing
list Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
_______________________________________________
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
_______________________________________________ Users mailing
list Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
_______________________________________________ Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
--
Regards
M. Salman VoIP Professional
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
