Hi
I need to see the ser.cfg, or to make life easier use one from onsip.org, which is a good little get started guide, and will connect to pstn, u just pretty much cut and paste the config make a few changes and away you go
iqbal
Colin Jordan wrote:
I do not too much about this, can please let me know where and in what part of the ser.cfg it will be?
-----Original Message----- From: Iqbal [mailto:iqbal@gigo.co.uk] Sent: Friday, September 16, 2005 12:07 PM To: cjordan@econetwireless.com; olivier.taylor@gmail.com Cc: serusers@lists.iptel.org Subject: RE: [Serusers] Handoff to PSTN
where u route your INVITE
Iqbal
On 9/16/2005, "Colin Jordan" cjordan@econetwireless.com wrote:
Where should I insert it in the code below?
# attempt handoff to PSTN
if (uri=~“^sip:9[0-9]*@mydomain.com”) {
log(“Forwarding to PSTN\n”);
t_relay_to( “192.168.0.2”, “5060”);
break;
};
From: Olivier Taylor [mailto:olivier.taylor@gmail.com] Sent: Thursday, September 15, 2005 4:00 PM To: 'Colin Jordan' Cc: serusers@lists.iptel.org Subject: RE : [Serusers] Handoff to PSTN
prefix("666")
-----Message d'origine----- De : serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] De la part de Colin Jordan Envoyé : jeudi 15 septembre 2005 15:19 À : 'Olivier Taylor' Cc : serusers@lists.iptel.org Objet : RE: [Serusers] Handoff to PSTN
The PSTN has given me a prefix of 666# to dial before the number, where can I insert this so that it will allow me to make a call?
From: Olivier Taylor [mailto:olivier.taylor@gmail.com] Sent: Thursday, September 15, 2005 2:58 PM To: 'Colin Jordan' Cc: serusers@lists.iptel.org Subject: RE : [Serusers] Handoff to PSTN
module tm
-----Message d'origine----- De : Colin Jordan [mailto:cjordan@econetwireless.com] Envoyé : jeudi 15 septembre 2005 14:55 À : 'Olivier Taylor' Cc : serusers@lists.iptel.org Objet : RE: [Serusers] Handoff to PSTN
t_relay_to( “192.168.0.2”, “5060”);
From: Olivier Taylor [mailto:olivier.taylor@gmail.com] Sent: Thursday, September 15, 2005 2:50 PM To: 'Colin Jordan' Cc: serusers@lists.iptel.org Subject: RE : [Serusers] Handoff to PSTN
what's on the line 143???
-----Message d'origine----- De : Colin Jordan [mailto:cjordan@econetwireless.com] Envoyé : jeudi 15 septembre 2005 14:46 À : 'Olivier Taylor' Cc : serusers@lists.iptel.org Objet : RE: [Serusers] Handoff to PSTN
The line 143 points to the script below. What modules will it be looking for?
From: Olivier Taylor [mailto:olivier.taylor@gmail.com] Sent: Thursday, September 15, 2005 2:33 PM To: 'Colin Jordan' Cc: serusers@lists.iptel.org Subject: RE : [Serusers] Handoff to PSTN
please reply to all
u have a module not loaded, the one involved on line 143
Olivier
-----Message d'origine----- De : Colin Jordan [mailto:cjordan@econetwireless.com] Envoyé : jeudi 15 septembre 2005 14:28 À : 'Olivier Taylor' Objet : RE: [Serusers] Handoff to PSTN
It gives me the following message:
Parse error (143,40-41): unknown command missing loadmodule?
From: Olivier Taylor [mailto:olivier.taylor@gmail.com] Sent: Thursday, September 15, 2005 1:21 PM To: 'Colin Jordan'; serusers-request@lists.iptel.org Cc: serusers@lists.iptel.org Subject: RE : [Serusers] Handoff to PSTN
just have a look at /var/log/messages u will find the line number where
the
error occurs
Olivier
-----Message d'origine----- De : serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] De la part de Colin Jordan Envoyé : jeudi 15 septembre 2005 12:33 À : serusers-request@lists.iptel.org Cc : serusers@lists.iptel.org Objet : [Serusers] Handoff to PSTN
I am not able to restart ser if I put he code below in the ser.cfg to handoff calls to PSTN.
# attempt handoff to PSTN
if (uri=~“^sip:9[0-9]*@mydomain.com”) {
log(“Forwarding to PSTN\n”);
t_relay_to( “192.168.0.2”, “5060”);
break;
};
Please help!!!!
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.
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.
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.
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.
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.
.
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.115.87","5060"); t_relay_to_tcp("217.15.115.87","5060"); break; };
}
_____________________________________________________________________
-----Original Message----- From: Iqbal [mailto:iqbal@gigo.co.uk] Sent: Friday, September 16, 2005 1:16 PM To: Colin Jordan Cc: olivier.taylor@gmail.com; serusers@lists.iptel.org Subject: Re: [Serusers] Handoff to PSTN
Hi
I need to see the ser.cfg, or to make life easier use one from onsip.org, which is a good little get started guide, and will connect to pstn, u just pretty much cut and paste the config make a few changes and away you go
iqbal
Colin Jordan wrote:
I do not too much about this, can please let me know where and in what part of the ser.cfg it will be?
-----Original Message----- From: Iqbal [mailto:iqbal@gigo.co.uk] Sent: Friday, September 16, 2005 12:07 PM To: cjordan@econetwireless.com; olivier.taylor@gmail.com Cc: serusers@lists.iptel.org Subject: RE: [Serusers] Handoff to PSTN
where u route your INVITE
Iqbal
On 9/16/2005, "Colin Jordan" cjordan@econetwireless.com wrote:
Where should I insert it in the code below?
# attempt handoff to PSTN
if (uri=~^sip:9[0-9]*@mydomain.com) {
log(Forwarding to PSTN\n);
t_relay_to( 192.168.0.2, 5060);
break;
};
From: Olivier Taylor [mailto:olivier.taylor@gmail.com] Sent: Thursday, September 15, 2005 4:00 PM To: 'Colin Jordan' Cc: serusers@lists.iptel.org Subject: RE : [Serusers] Handoff to PSTN
prefix("666")
-----Message d'origine----- De : serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] De la part de Colin Jordan Envoyé : jeudi 15 septembre 2005 15:19 À : 'Olivier Taylor' Cc : serusers@lists.iptel.org Objet : RE: [Serusers] Handoff to PSTN
The PSTN has given me a prefix of 666# to dial before the number, where
can
I insert this so that it will allow me to make a call?
From: Olivier Taylor [mailto:olivier.taylor@gmail.com] Sent: Thursday, September 15, 2005 2:58 PM To: 'Colin Jordan' Cc: serusers@lists.iptel.org Subject: RE : [Serusers] Handoff to PSTN
module tm
-----Message d'origine----- De : Colin Jordan [mailto:cjordan@econetwireless.com] Envoyé : jeudi 15 septembre 2005 14:55 À : 'Olivier Taylor' Cc : serusers@lists.iptel.org Objet : RE: [Serusers] Handoff to PSTN
t_relay_to( 192.168.0.2, 5060);
From: Olivier Taylor [mailto:olivier.taylor@gmail.com] Sent: Thursday, September 15, 2005 2:50 PM To: 'Colin Jordan' Cc: serusers@lists.iptel.org Subject: RE : [Serusers] Handoff to PSTN
what's on the line 143???
-----Message d'origine----- De : Colin Jordan [mailto:cjordan@econetwireless.com] Envoyé : jeudi 15 septembre 2005 14:46 À : 'Olivier Taylor' Cc : serusers@lists.iptel.org Objet : RE: [Serusers] Handoff to PSTN
The line 143 points to the script below. What modules will it be looking for?
From: Olivier Taylor [mailto:olivier.taylor@gmail.com] Sent: Thursday, September 15, 2005 2:33 PM To: 'Colin Jordan' Cc: serusers@lists.iptel.org Subject: RE : [Serusers] Handoff to PSTN
please reply to all
u have a module not loaded, the one involved on line 143
Olivier
-----Message d'origine----- De : Colin Jordan [mailto:cjordan@econetwireless.com] Envoyé : jeudi 15 septembre 2005 14:28 À : 'Olivier Taylor' Objet : RE: [Serusers] Handoff to PSTN
It gives me the following message:
Parse error (143,40-41): unknown command missing loadmodule?
From: Olivier Taylor [mailto:olivier.taylor@gmail.com] Sent: Thursday, September 15, 2005 1:21 PM To: 'Colin Jordan'; serusers-request@lists.iptel.org Cc: serusers@lists.iptel.org Subject: RE : [Serusers] Handoff to PSTN
just have a look at /var/log/messages u will find the line number where
the
error occurs
Olivier
-----Message d'origine----- De : serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] De la part de Colin Jordan Envoyé : jeudi 15 septembre 2005 12:33 À : serusers-request@lists.iptel.org Cc : serusers@lists.iptel.org Objet : [Serusers] Handoff to PSTN
I am not able to restart ser if I put he code below in the ser.cfg to handoff calls to PSTN.
# attempt handoff to PSTN
if (uri=~^sip:9[0-9]*@mydomain.com) {
log(Forwarding to PSTN\n);
t_relay_to( 192.168.0.2, 5060);
break;
};
Please help!!!!
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.
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.
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.
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.
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.
.
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.
-
Colin Jordan -
Iqbal