[Serusers] Handoff to PSTN with a set prefix

Colin Jordan cjordan at econetwireless.com
Tue Sep 20 09:40:34 CEST 2005


I need to set a fixed prefix of, 666#, to enable me to break out to the PSTN
that I am sending my traffic. Will you please help me with the needed
commands and where to place it? Please find below the ser.cfg file:

________________________________

#
# $Id: ser.cfg,v 1.21.2.1 2003/07/30 16:46:18 andrei Exp $
#
# simple quick-start config script
#

# ----------- global configuration parameters ------------------------

#debug=3         # debug level (cmd line: -dddddddddd)
#fork=yes
#log_stderror=no	# (cmd line: -E)

# new insterted statement
listen=66.8.91.200
listen=127.0.0.1

# hostname matching an allias will satify the condition uri-myself
alias=gaco.co.za
alias=66.8.91.200

/* Uncomment these lines to enter debugging mode
debug=7
fork=no
log_stderror=yes
*/

check_via=no	# (cmd. line: -v)
dns=no           # (cmd. line: -r)
rev_dns=no      # (cmd. line: -R)

# this was commented
port=5060
children=4

fifo="/tmp/ser_fifo"

# ------------------ module loading ----------------------------------

# Uncomment this if you want to use SQL database
loadmodule "/usr/lib/ser/modules/mysql.so"
loadmodule "/usr/lib/ser/modules/sl.so"
loadmodule "/usr/lib/ser/modules/tm.so"
loadmodule "/usr/lib/ser/modules/rr.so"
loadmodule "/usr/lib/ser/modules/maxfwd.so"
loadmodule "/usr/lib/ser/modules/usrloc.so"
loadmodule "/usr/lib/ser/modules/registrar.so"

# Uncomment this if you want digest authentication
# mysql.so must be loaded !
loadmodule "/usr/lib/ser/modules/auth.so"
loadmodule "/usr/lib/ser/modules/auth_db.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 --

# database location - NEW
#modparam("auth_db, "db_uri, "sql://ser:>heslo>@localhost/ser")

# 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)

# -------------------------  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 (len_gt( max_len )) {
		sl_send_reply("513", "Message too big");
		break;
	};

	# 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
	record_route();
	# loose-route processing
	if (loose_route()) {
		t_relay();
		break;
	};

	# if the request is for other domain use UsrLoc
	# (in case, it does not work, use the following command
	# with proper names and addresses in it)
	if (uri==myself) {

		if (method=="REGISTER") {

# Uncomment this if you want to use digest authentication
	if (!www_authorize("gaco.co.za", "subscriber")) {
	www_challenge("gaco.co.za", "0");
	break;
	};

			save("location");
			break;
		};

		# native SIP destinations are handled using our USRLOC DB
		if (!lookup("location")) {
			sl_send_reply("404", "Not Found");
			break;
		};
	};
	# forward to current uri now; use stateful forwarding; that
	# works reliably even if we forward from TCP to UDP
	if (!t_relay()) {
		sl_reply_error();

	};

	# attemt handoff to PSTN
	if (uri=~"^sip:9[0-9] *@gaco.co.za") {
	   log ("Forwarding to PSTN\n");
	   t_relay_to_udp("217.15.11.87","5060");
	   t_relay_to_tcp("217.15.11.87","5060");
	   break;
	   };

}

________________________________
DISCLAIMER: The information in this message is confidential and is legally
privileged. It is intended solely for the addressee. Access to this message by
anyone else is unauthorized.If receiving in error please accept our apologies
and notify the sender immediately. You must also delete the original
message from your machine. If you are not the intended recipient, any use,
disclosure, copying, distribution or action taken in reliance of it, is prohibited
and maybe
unlawful. 
 






More information about the sr-users mailing list