[Serusers] xlite voice session
S Shah
shah at zynergy.com
Tue Nov 16 14:14:00 CET 2004
Here's what my ser.cfg file looks like. I'm still unable to get a voice
conversation going using xlite. I can establish a connection between two
xlite ua, but seems like my rtp packets are blocked somewhere. I have
rtpproxy installed and running. When I run SER it sees rtpproxy running and
enables support for it. I'm running SER in debug mode so I can see the
messages.
Is there something I'm missing or doing wrong in my ser.cfg file?
By the way, I'm running this on Redhat.
Thanks.
================================================
# ----------- global configuration parameters ------------------------
#debug=3 # debug level (cmd line: -dddddddddd)
#fork=yes
#log_stderror=no # (cmd line: -E)
# Uncomment these lines to enter debugging mode
debug=7
fork=no
log_stderror=yes
listen=<my ip address>
# check_via - Turn on or off Via host checking when forwarding replies.
# Default is no. arcane. looks for discrepency between name and
# ip address when forwarding replies.
check_via=yes # (cmd. line: -v)
# dns - Uses dns to check if it is necessary to add a "received=" field
# to a via. Default is no.
#rev_dns - Same as dns but use reverse DNS.
dns=no # (cmd. line: -r)
rev_dns=no # (cmd. line: -R)
port=5060
children=4
# fifo - FIFO special file pathname
fifo="/tmp/ser_fifo"
# syn_branch - Shall the server use stateful synonym branches? It is
# faster but not reboot-safe. Default is yes.
syn_branch=yes
# memlog - Debugging level for final memory statistics report. Default
# is L_DBG -- memory statistics are dumped only if debug is set high.
memlog=3
# sip_warning - Should replies include extensive warnings? By default
# yes, it is good for trouble-shooting.
sip_warning=yes
# server_signature - Should locally-generated messages include server's
# signature? By default yes, it is good for trouble-shooting.
server_signature=yes
# reply_to_via - A hint to reply modules whether they should send reply
# to IP advertised in Via. Turned off by default, which means that
# replies are sent to IP address from which requests came.
reply_to_via=no
# user | uid - uid to be used by the server. 99 = nobody.
#uid="nobody"
# group | gid - gid to be used by the server. 99 = nobody.
#gid="nobody"
#mhomed -- enable calculation of outboud interface; useful on
# multihomed servers.
#mhomed=0
# ------------------ module loading ----------------------------------
# Uncomment this if you want to use SQL database
loadmodule "/usr/local/lib/ser/modules/mysql.so"
loadmodule "/usr/local/lib/ser/modules/sl.so"
loadmodule "/usr/local/lib/ser/modules/tm.so"
loadmodule "/usr/local/lib/ser/modules/rr.so"
loadmodule "/usr/local/lib/ser/modules/maxfwd.so"
loadmodule "/usr/local/lib/ser/modules/usrloc.so"
loadmodule "/usr/local/lib/ser/modules/registrar.so"
loadmodule "/usr/local/lib/ser/modules/textops.so"
# Uncomment this if you want digest authentication
# mysql.so must be loaded !
#loadmodule "/usr/local/lib/ser/modules/auth.so"
#loadmodule "/usr/local/lib/ser/modules/auth_db.so"
loadmodule "/usr/local/lib/ser/modules/nathelper.so"
# ----------------- setting module-specific parameters ---------------
# -- usrloc params --
#modparam("usrloc", "db_mode", 0)
# Uncomment this if you want to use SQL database
# for persistent storage and comment the previous line
modparam("usrloc", "db_mode", 2)
# -- auth params --
# Uncomment if you are using auth module
#
#modparam("auth_db", "calculate_ha1", yes)
#
# If you set "calculate_ha1" parameter to yes (which true in this config),
# uncomment also the following parameter)
#
#modparam("auth_db", "password_column", "password")
# -- rr params --
# add value to ;lr param to make some broken UAs happy
modparam("rr", "enable_full_lr", 1)
# -- nathelper params --
modparam("registrar", "nat_flag", 6)
modparam("nathelper", "natping_interval", 30) # Ping interval 30 seconds
modparam("nathelper", "ping_nated_only", 1) # Ping only clients behind
NAT
# ------------------------- request routing logic -------------------
# main routing logic
route{
# initial sanity checks -- messages with
# max_forwards==0, or excessively long requests
if (!mf_process_maxfwd_header("10")) {
sl_send_reply("483","Too Many Hops");
break;
};
if ( msg:len > max_len ) {
sl_send_reply("513", "Message too big");
break;
};
# !! Nathelper
# Special handling for NATed clients; first, NAT test is
# executed: it looks for via!=received and RFC1918 addresses
# in Contact (may fail if line-folding is used); also,
# the received test should, if completed, check all vias
# for presence of received
if (nat_uac_test("3")) {
# Allow RR-ed requests, as there may indicate that
# a NAT-enabled proxy takes care of it; unless it is
# a REGISTER
if (method == "REGISTER" || ! search("^Record-Route:")) {
log("LOG: Someone trying to register from private
IP, rewriting\n");
fix_nated_contact(); # Rewrite contact with source
IP of signalling
if (method == "INVITE") {
fix_nated_sdp("1"); # Add direction=active
to SDP
};
force_rport(); # Add rport parameter to topmost Via
setflag(6); # Mark as NATed
};
};
# we record-route all messages -- to make sure that
# subsequent messages will go through our proxy; that's
# particularly good if upstream and downstream entities
# use different transport protocol
if (!method=="REGISTER") record_route();
# subsequent mesages within a dialog should take the
# path determined by record-routing
if (loose_route()) {
# mark routing logic in request
append_hf("P-hint: rr-enforced\r\n");
route(1);
break;
};
if (!uri==myself) {
# mark routing logic in request
append_hf("P-hint: outbound\r\n");
route(1);
break;
};
if (uri==myself) {
if (method=="INVITE") {
record_route();
if (isflagset(6)) {
force_rtp_proxy();
};
};
if (method=="REGISTER") {
save("location");
break;
};
lookup("aliases");
if (!uri==myself) {
append_hf("P-hint: outbound alias\r\n");
route(1);
break;
};
# native SIP destinations are handled using our USRLOCDB
if (!lookup("location")) {
sl_send_reply("404", "Not Found");
break;
};
};
append_hf("P-hint: usrloc applied\r\n");
route(1);
}
route[1] {
if (uri=~"[@:](192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)" &&
!search("^Route:")){
sl_send_reply("479", "We don't forward to private IP
addresses");
break;
};
if (isflagset(6)) {
force_rtp_proxy();
t_on_reply("1");
append_hf("P-Behind-NAT: Yes\r\n");
};
# send it out now; use stateful forwarding as it works reliably
# even for UDP2TCP
if (!t_relay()) {
sl_reply_error();
break;
};
}
onreply_route[1] {
# NATed transaction ?
if (status =~ "(183)|2[0-9][0-9]") {
fix_nated_contact();
force_rtp_proxy();
# otherwise, is it a transaction behind a NAT and we did not
# know at time or request processing ? (RFC1918 contacts)
} else if (nat_uac_test("1")) {
fix_nated_contact();
};
}
================================
-----Original Message-----
From: Bruno Lopes F. Cabral [mailto:bruno at openline.com.br]
Sent: Monday, November 15, 2004 2:18 PM
To: S Shah
Subject: Re: [Serusers] xlite voice session
Hi
get rtpproxy from CVS and set it up and it will work.
I'm doing the same way you are right now
a couple of days ago I post a message on the list
with the CVS command to download rtpproxy and the
URL of SER config to use it with nathelper
Hope this helps
!3runo
S Shah wrote:
> The remote computer does not have a public ip address. That computer is
> behind a netgear router. The router itself has the public ip address. My
> computer is on a lan as well. I'm behind linksys router. This router has a
> separate public ip address. My SER server is located in a separate
location
> from the two computers. The SER server has a public ip address.
>
> I've configured my ser.cfg file to use nathelper but I'm not using
> mediaproxy or rtpproxy. I agree that the RTP packets are getting blocked
> somewhere along the way. I'm guessing I can rectify the problem by using a
> mediaproxy or a rtpproxy. I'm still new to SER and sip so I'm not sure how
> to install and setup the mediaproxy and the rtpproxy.
>
> Thanks for your response Bruno.
More information about the sr-users
mailing list