Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

public_ip setting not used on RTCP interface #52

Open
marcinkowalczyk opened this issue Jan 26, 2017 · 2 comments
Open

public_ip setting not used on RTCP interface #52

marcinkowalczyk opened this issue Jan 26, 2017 · 2 comments

Comments

@marcinkowalczyk
Copy link

marcinkowalczyk commented Jan 26, 2017

Hi,
I've just noticed, that when public_ip setting is used internal IP is send in rtcp offer.

Local IP 10.23.248.104 resolves to public 34.249.138.180
o= and c= contains proper public IP, but a=rtcp has internal one.

Please have a look into trace i took

#
U 10.23.248.104:5060 -> 213.218.x.y:5060
INVITE sip:[email protected] SIP/2.0.
Via: SIP/2.0/UDP 34.249.138.180;branch=z9hG4bKYDJ~hadd;rport.
From: sip:[email protected];tag=69F70F42-5889DF06000D5414-BC92F700.
To: sip:[email protected].
CSeq: 10 INVITE.
Call-ID: 4ecc4f05-db34-4368-8851-151857f18785.
Route: <sip:sip.proxy.com:5060;lr>.
Max-Forwards: 70.
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY.
Supported: path, replaces.
Privacy: none.
Content-Type: application/sdp.
Contact: <sip:34.249.138.180:5060;transport=udp>.
Content-Length: 251.
.
v=0.
o=- 1485402434 1485402435 IN IP4 34.249.138.180.
s=-.
c=IN IP4 34.249.138.180.
t=0 0.
m=audio 30002 RTP/AVP 8 0.
a=rtpmap:8 PCMA/8000.
a=rtpmap:0 PCMU/8000.
a=sendrecv.
a=rtcp-mux.
a=rtcp:30003 IN IP4 10.23.248.104.
a=ptime:20.
a=direction:both.

#
U 213.218.x.y:5060 -> 10.23.248.104:5060
SIP/2.0 403 Forbidden.
Via: SIP/2.0/UDP 34.249.138.180;branch=z9hG4bKYDJ~hadd;rport=5060.
From: sip:[email protected];tag=69F70F42-5889DF06000D5414-BC92F700.
To: sip:[email protected];tag=e671f06608a3bf1703ca55828e9b1338.10fd.
CSeq: 10 INVITE.
Call-ID: 4ecc4f05-db34-4368-8851-151857f18785.
Server: Carrier-eX v.0.9.
Content-Length: 0.
.

#
U 10.23.248.104:5060 -> 213.218.x.y:5060
ACK sip:[email protected] SIP/2.0.
Via: SIP/2.0/UDP 34.249.138.180;branch=z9hG4bKYDJ~hadd;rport.
From: sip:[email protected];tag=69F70F42-5889DF06000D5414-BC92F700.
To: sip:[email protected];tag=e671f06608a3bf1703ca55828e9b1338.10fd.
Call-ID: 4ecc4f05-db34-4368-8851-151857f18785.
CSeq: 10 ACK.
Route: <sip:sip.proxy.com:5060;lr>.
Content-Length: 0.
@dunst0
Copy link
Contributor

dunst0 commented May 25, 2017

Can you please give some insight in your setup and the modules you use?

@marcinkowalczyk
Copy link
Author

marcinkowalczyk commented May 25, 2017

/etc/sems/sems.conf

sip_ip=eth0
sip_port=5060
media_ip=eth0
rtp_low_port=30000
rtp_high_port=66000


sip_nat_handling=no
force_symmetric_rtp=yes
plugin_path=/usr/lib/sems/plug-in/

load_plugins=wav;opus;sbc;session_timer;monitoring;xmlrpc2di;stats;uac_auth
application=sbc
plugin_config_path=/etc/sems/etc/
fork=yes
stderr=no
loglevel=2
syslog_facility=LOCAL0
log_sessions=yes
log_events=yes
max_shutdown_time = 10
shutdown_mode_reply="503 Server shutting down"
cps_limit="100;503;Server overload"
media_processor_threads=2
rtp_receiver_threads=1
session_limit="1000;503;Server overload"
options_session_limit="900;503;Warning, server soon overloaded"
dead_rtp_time=0
use_default_signature=no
signature="SEMS media server 1.0"
single_codec_in_ok=yes
unhandled_reply_loglevel=info
use_raw_sockets=no
proxy_sticky_auth=yes
public_ip=34.249.138.180

/etc/sems/etc/sbc.conf
profiles=from_internal,refuse active_profile=$M($P(domain)=>regex_profile),$M($si=>regex_src_ipmap),refuse session_refresh_method=UPDATE regex_maps=regex_strip_plus,regex_src_ipmap,regex_profile,regex_to_national

call hits sems via private IP and goes out via public one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants