[OpenSIPS-Users] Routing in opensips
Eric Freeman
eric.freeman at tbwachiat.com
Wed Nov 2 21:40:04 CET 2016
I am not clear of what I am doing. I did some googling.
I added the if nat_uac line to the fix_nated line. It did not fix my issue.
In the Invite Request Packet I see the Owner Address as the 10 address next to the Owner Address section of the packet. The same for the Connection information.Does that mean I didn't set up the fix_nates_sdp correctly? Let me know if you want to see my entire opensips.cfg file.
route[relay] {
# for INVITEs enable some additional helper routes
if (is_method("INVITE")) {
if(nat_uac_test("8")) {
xlog("We have incoming SDP, let's fix if it's behind NAT\n");
fix_nated_sdp("2");
}
t_on_branch("per_branch_ops");
t_on_reply("handle_nat");
t_on_failure("missed_call");
Thank you for all of your help,
Eric Freeman
Technical Director/NA for TBWA\Chiat\Day
TBWA\Chiat\Day New York
488 Madison Ave.
New York NY 10022
United States of America
Tel: +12128041324<tel:%2B12128041324>
________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org>
Sent: Tuesday, November 1, 2016 8:34:05 AM
To: Eric Freeman; users at lists.opensips.org
Subject: Re: [OpenSIPS-Users] Routing in opensips
Eric,
You can simply change it with the fix_nated_sdp() function:
http://www.opensips.org/html/docs/modules/2.2.x/nathelper.html#id294042
But you have to be careful that the IP:port you force in SDP is also valid from IP perspective - like any RTP traffic landing on that IP is actually getting to the right application.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 01.11.2016 14:24, Eric Freeman wrote:
Thank you. I will test with that IP. How do I change the SDP to my public IP address so I can get RTP information back?
Thank you,
Eric Freeman
Technical Director/NA for TBWA\Chiat\Day
TBWA\Chiat\Day New York
488 Madison Ave.
New York NY 10022
United States of America
Tel: +12128041324<tel:%2B12128041324>
________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Tuesday, November 1, 2016 7:10:45 AM
To: Eric Freeman; users at lists.opensips.org<mailto:users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Routing in opensips
Hi Eric,
The outgoing INVITE request looks ok - the RR and VIA headers carry the public IP of your OpenSIPS. You should get back some reply. Not sure how valid is that test server, but you can try sending to sip:opensips.org:5060 ( or 78.46.64.50:5060 ) - this sip server is definitely up .
BTW, the SDP you send out is bogus as it contain only private IPs, so the other end point will not be able to send you ant RTP back.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 31.10.2016 14:21, Eric Freeman wrote:
Please attached pcap file. Is this what you need?
Eric Freeman
Technical Director/NA for TBWA\Chiat\Day
TBWA\Chiat\Day New York
488 Madison Ave.
New York NY 10022
United States of America
Tel: +12128041324<tel:%2B12128041324>
________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Monday, October 31, 2016 6:36:18 AM
To: Eric Freeman; OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Routing in opensips
Hi Eric,
What I'm asking here is to post the full INVITE packet from your opensips server to the external host - I Want to to check the SIP headers and the SDP.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 25.10.2016 16:38, Eric Freeman wrote:
The opensips server is 10.88.23.13 the video conference server is 10.89.71.12. The IP I am trying to connect to 199.48.152.152, I believe is a valid host. I found it on a test SIP site on the Internet
10:02:59.346842 IP 10.89.71.12.sip > 10.88.23.13.sip: SIP: INVITE sip:111 at 199.48.152.152<mailto:sip:111 at 199.48.152.152> SIP/2.0
10:02:59.351769 IP 10.88.23.13.sip > 10.89.71.12.sip: SIP: SIP/2.0 100 Giving a try
10:02:59.352232 IP 10.88.23.13.sip > sj1-con-01-04.bluejeansnet.com.sip: SIP: INVITE sip:111 at 199.48.152.152<mailto:sip:111 at 199.48.152.152> SIP/2.0
10:02:59.352238 IP 10.88.23.13 > sj1-con-01-04.bluejeansnet.com: udp
10:02:59.871480 IP 10.88.23.13.sip > sj1-con-01-04.bluejeansnet.com.sip: SIP: INVITE sip:111 at 199.48.152.152<mailto:sip:111 at 199.48.152.152> SIP/2.0
10:02:59.871489 IP 10.88.23.13 > sj1-con-01-04.bluejeansnet.com: udp
10:03:00.874461 IP 10.88.23.13.sip > sj1-con-01-04.bluejeansnet.com.sip: SIP: INVITE sip:111 at 199.48.152.152<mailto:sip:111 at 199.48.152.152> SIP/2.0
10:03:00.874483 IP 10.88.23.13 > sj1-con-01-04.bluejeansnet.com: udp
10:03:02.877430 IP 10.88.23.13.sip > sj1-con-01-04.bluejeansnet.com.sip: SIP: INVITE sip:111 at 199.48.152.152<mailto:sip:111 at 199.48.152.152> SIP/2.0
10:03:02.877440 IP 10.88.23.13 > sj1-con-01-04.bluejeansnet.com: udp
10:03:03.930697 IP 10.88.23.13.sip > 10.89.71.12.sip: SIP: SIP/2.0 408 Request Timeout
10:03:03.958682 IP 10.89.71.12.sip > 10.88.23.13.sip: SIP: ACK sip:111 at 199.48.152.152<mailto:sip:111 at 199.48.152.152> SIP/2.0
Eric Freeman
Technical Director/NA for TBWA\Chiat\Day
TBWA\Chiat\Day New York
488 Madison Ave.
New York NY 10022
United States of America
Tel: +12128041324<tel:%2B12128041324>
________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Tuesday, October 25, 2016 7:04:15 AM
To: Eric Freeman; OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Routing in opensips
Hi Eric,
By traffic (coming back), you understand RTP or SIP traffic ?
Could you post the INVITE message getting out of your server ? I suspect the INVITE has in SDP a private IP that is not reachable for the end device (where the call is sent).
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 21.10.2016 18:46, Eric Freeman wrote:
Yes, I see Request INVITE going to the device I am calling. I do not see any traffic coming back. I am following up with my Firewall team.
My Firewall team suggested I might need to change the RTP ports to use UDP 2326-2485. Where do I change/check these settings on the OpenSIPs server to see if I have the traffic going out those ports.
Thanks,
Eric Freeman
Technical Director/NA for TBWA\Chiat\Day
TBWA\Chiat\Day New York
488 Madison Ave.
New York NY 10022
United States of America
Tel: +12128041324<tel:%2B12128041324>
________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Monday, October 3, 2016 4:44:26 AM
To: Eric Freeman; OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Routing in opensips
Hi Eric,
Not the OpenSIPs logs I'm looking for, but the actual SIP packet at network level (use ngrep or tcpdump) for the INVITE leaving your OpenSIPS.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 30.09.2016 16:52, Eric Freeman wrote:
Hopefully this is the relevant information you need from the log. I am trying to call 111 at 199.48.152.152<mailto:111 at 199.48.152.152>. The IP of the opensips server si 10.88.23.10 and has a public IP of 204.17.231.3. The IP address of the video conference server is 10.89.71.12.
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_msg: SIP Request:
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_msg: method: <INVITE>
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_msg: uri: <sip:111 at 199.48.152.152><mailto:sip:111 at 199.48.152.152>
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_msg: version: <SIP/2.0>
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_headers: flags=2
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_to: end of header reached, state=10
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_to: display={}, ruri={sip:111 at 199.48.152.152<mailto:sip:111 at 199.48.152.152>}
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:get_hdr_field: <To> [26]; uri=[sip:111 at 199.48.152.152<mailto:sip:111 at 199.48.152.152>]
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:get_hdr_field: to body [<sip:111 at 199.48.152.152><mailto:sip:111 at 199.48.152.152>#015#012]
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:get_hdr_field: cseq <CSeq>: <1> <INVITE>
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_via_param: found param type 235, <rport> = <n/a>; state=6
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bK-57ed3cdd-76b5c304-9584dff>; state=16
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_via: end of header reached, state=5
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_headers: via found, flags=2
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_headers: this is the first via
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:receive_msg: After parse_msg...
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:receive_msg: preparing to run routing scripts...
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_headers: flags=100
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:maxfwd:is_maxfwd_present: value = 70
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:uri:has_totag: no totag
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_headers: flags=78
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:tm:t_lookup_request: start searching: hash=25578, isACK=0
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:tm:matching_3261: RFC3261 transaction matching failed
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:tm:t_lookup_request: no transaction found
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_to_param: tag=2c770a98-c47590a-13c4-45026-57ed3cdd-1bac9941-57ed3cdd
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_to: end of header reached, state=29
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_to: display={"Conference Room"}, ruri={sip:LifeSize at 10.88.23.13;transport=UDP<mailto:sip:LifeSize at 10.88.23.13;transport=UDP>}
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:grep_sock_info: checking if host==us: 11==11 && [10.88.23.13] == [10.88.23.13]
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:grep_sock_info: checking if port 5060 matches port 5060
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_headers: flags=200
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:get_hdr_field: content_length=1759
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:get_hdr_field: found end of header
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:rr:find_first_route: No Route headers found
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:grep_sock_info: checking if host==us: 14==11 && [199.48.152.152] == [10.88.23.13]
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:grep_sock_info: checking if port 5060 matches port 5060
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:grep_sock_info: checking if host==us: 14==11 && [199.48.152.152] == [10.88.23.13]
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:grep_sock_info: checking if port 5060 matches port 5060
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:check_self: host != me
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_headers: flags=ffffffffffffffff
Sep 29 12:10:17 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:do_action_set_adv_address: setting adv address = [204.17.231.3]
Eric Freeman
Technical Director/NA for TBWA\Chiat\Day
TBWA\Chiat\Day New York
488 Madison Ave.
New York NY 10022
United States of America
Tel: +12128041324<tel:%2B12128041324>
________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Friday, September 30, 2016 4:32:01 AM
To: Eric Freeman; OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Routing in opensips
Hi Eric,
As a first step, can you confirm that the INVITE (sent out by your OPenSIPS to the internet) has in VIA hdr the public IP of your NAT ?
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 29.09.2016 19:14, Eric Freeman wrote:
It is still not working, I added my public IP as requested. I do not have any gateways or anything set up. Do I need to add anything?
I added this to the route statement:
if (!uri==myself) {
append_hf("P-hint: outbound\r\n");
set_advertised_address("XXX.XX.XXX.X");
route(relay);
I am still receiving these errors:
Sep 29 12:10:22 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:rr:find_first_route: No Route headers found
Sep 29 12:10:22 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:rr:loose_route: There is no Route HF
Sep 29 12:10:22 cd-ubuntu-opensips /usr/local/sbin/opensips[12878]: DBG:core:parse_headers: flags=78
Eric Freeman
Technical Director/NA for TBWA\Chiat\Day
TBWA\Chiat\Day New York
488 Madison Ave.
New York NY 10022
United States of America
Tel: +12128041324<tel:%2B12128041324>
________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Tuesday, September 20, 2016 8:38:31 AM
To: Eric Freeman; OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Routing in opensips
He Eric,
In the script (generated by menuconfig), you have an IF block with :
append_hf("P-hint: outbound\r\n");
That block is executed if one of your users is dialing an external SIP domain. So, that is the place where the calls will break out to public internet.
As your OpenSIPS has a private IP (not routable in internet), you need to configure it to advertise the public IP of your NAT via the set_advertise_address() - see:
http://www.opensips.org/Documentation/Script-CoreFunctions-2-2#toc46
Put there the public IP of your NAT. Also, be sure you create in your router (running the NAT) a port forwarding from the public IP port 5060 UDP to the private IP of your OpenSIPS port 5060 UDP.
Best regards,
-------------------------------------------------------------------------------
This e-mail is intended only for the named person or entity to which it is addressed and contains valuable business
information that is privileged, confidential and/or otherwise protected from disclosure. If you received this e-mail
in error, any review, use, dissemination, distribution or copying of this e-mail is strictly prohibited. Please notify us
immediately of the error via e-mail to disclaimer at email-abuse.com<mailto:disclaimer at email-abuse.com> and please delete the e-mail from your system,
retaining no copies in any media. We appreciate your cooperation.
-------------------------------------------------------------------disc99999999
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20161102/ee89d69f/attachment-0001.htm>
More information about the Users
mailing list