Thanks Javarockx
That fixed the error and yes I had it running already
Thank you
_____
From: Java Rockx [mailto:javarockx@gmail.com]
Sent: Monday, 11 April 2005 9:50 AM
To: Mr Greg Plater
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] SER issue on startup
Greg,
Could you have multiple instances of ser running? Also, perhaps you can just
add this to the top of your ser.cfg:
listen=192.168.1.4
port=5060
Regards,
Paul
On Apr 10, 2005 7:16 PM, Mr Greg Plater <gplater(a)da-bratz.com> wrote:
I seen to have mis configured my ser.cfg file in some way. Can anyone tell
me what I have done wrong
[root@altcall2 ser]# /usr/local/sbin/ser -D -E
0(1832) WARNING: fix_socket_list: could not rev. resolve 1.1.1.1
0(1832) WARNING: fix_socket_list: could not rev. resolve 1.1.1.1
Listening on
udp: 127.0.0.1 [127.0.0.1]:5060
udp: 1.1.1.1 [1.1.1.1]:5060
udp: 192.168.1.4 [192.168.1.4]:5060
tcp: 127.0.0.1 [127.0.0.1]:5060
tcp: 1.1.1.1 [1.1.1.1]:5060
tcp: 192.168.1.4 [192.168.1.4]:5060
Aliases:
tcp: altcall2:5060
tcp: altcall2.altcall.com:5060
tcp: localhost:5060
udp: altcall2:5060
udp: altcall2.altcall.com:5060
udp: localhost:5060
stateless - initializing
[root@altcall2 ser]# 0(0) Maxfwd module- initializing
textops - initializing
0(0) ERROR: tcp_init: bind(7, 0x8132bfc, 16) on 127.0.0.1: Address already
in use
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
Hi everyone:
I'm having problems with serweb when I'm trying to login, I mean, when I type http://localhost/serweb/html/user_interface/index.php the screen apears, but when I introduce a user name and a password and press login the same login form screen appears.
Could anyone tell me what I'm doing wrong?
Thanks in advance
Edgar Vidal
Edgar Vidal
SAS Institute México, S.A. de C.V.
Edgar.Vidal(a)sas.com
Tel. (52) 55 5000 3814
SAS ... The Power to Know
I seen to have mis configured my ser.cfg file in some way. Can anyone tell
me what I have done wrong
[root@altcall2 ser]# /usr/local/sbin/ser -D -E
0(1832) WARNING: fix_socket_list: could not rev. resolve 1.1.1.1
0(1832) WARNING: fix_socket_list: could not rev. resolve 1.1.1.1
Listening on
udp: 127.0.0.1 [127.0.0.1]:5060
udp: 1.1.1.1 [1.1.1.1]:5060
udp: 192.168.1.4 [192.168.1.4]:5060
tcp: 127.0.0.1 [127.0.0.1]:5060
tcp: 1.1.1.1 [1.1.1.1]:5060
tcp: 192.168.1.4 [192.168.1.4]:5060
Aliases:
tcp: altcall2:5060
tcp: altcall2.altcall.com:5060
tcp: localhost:5060
udp: altcall2:5060
udp: altcall2.altcall.com:5060
udp: localhost:5060
stateless - initializing
[root@altcall2 ser]# 0(0) Maxfwd module- initializing
textops - initializing
0(0) ERROR: tcp_init: bind(7, 0x8132bfc, 16) on 127.0.0.1: Address already
in use
Below is what I currently have in my ser.cfg , What can I do to make it add
additional numbers infront?
I.e.
1./User dials 00 (ser knows to forwards to asterisk)
2./ Ser adds an additional extension 2202 to the 00 before sending to
asterisk (this is the pin asterisk requires to make the call)
3./ Asterisk receives 002202......
4./ Call proceeds.
So what I'm after is adding the additional 'hidden' number that people dont
see.
# send out 00 prefix to wholesale voip.brujula.net termination
if (uri=~"^sip:00[0-9].*@voip.fast.co.nz") {
if (!is_user_in("From", "ld")) {
sl_send_reply("403", "Payment required");
break;
};
setflag(1);
rewritehostport("asterisk.fast.co.nz:5060");
if (!t_relay()) {
sl_reply_error();
};
break;
};
I have the some problem of Sun Zongjun...
The function radius_authorize_sterman() do not send the msg to
freeradius.
I compiled SER with radiusclient-ng.
thank for help
g.ricca
CSINFO S.p.A.
INTERNET, VOCE E DATI
Via Malagoli, 12 - 56124 - Pisa
Tel.+39 50 782000
Fax +39 50 782782
Hi I was wondering if anyone could help with this configuration..
My office Users register with SERWEB and have an alias example : 8838212349
I have asterisk connected to my PSTN company and would like calls from SER
with say prefix 0 to be routed to asterisk for PSTN termination.
Currently I have Asterisk dialplans working for PSTN. I have Asterisk as a
user registered to SER but I can not seem to route the calls to Asterisk
>From SER .
All Services are on Public ip address's but can I use the example:
Asterisk = 192.168.1.5 with user name asterisk (2000) registered to SER
SER = 192.168.1.4 has users with Alias like 8838212349
Please help if you can
:-) Cheers
Greg
____________________________________________________________________________
_______________
#
# $Id: ser.cfg,v 1.27 2005/03/10 14:16:25 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)
#memlog=5 # memory debug log level
#log_facility=LOG_LOCAL0 # sets the facility used for logging (see
syslog(3))
/* Uncomment these lines to enter debugging mode
fork=no
log_stderror=yes
*/
check_via=no # (cmd. line: -v)
dns=no # (cmd. line: -r)
rev_dns=no # (cmd. line: -R)
port=5060
#children=4
fifo="/tmp/ser_fifo"
user=www
group=www
fifo_user=www # owner of the ser fifo
fifo_group=www
fifo_mode=0660 # fifo's permissions
#disable_core=yes #disables core dumping
#open_fd_limit=1024 # sets the open file descriptors limit
#mhomed=yes # usefull for multihomed hosts, small performance penalty
#disable_tcp=yes
tcp_accept_aliases=yes # accepts the tcp alias via option (see NEWS)
# ------------------ 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"
# ----------------- 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)
# ------------------------- 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;
};
# 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 messages withing 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 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("127.0.0.1", "subscriber")) {
www_challenge("127.0.0.1", "0");
break;
};
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 USRLOC DB
if (!lookup("location")) {
sl_send_reply("404", "Not Found");
break;
};
};
append_hf("P-hint: usrloc applied\r\n");
route(1);
}
route[1]
{
# send it out now; use stateful forwarding as it works reliably
# even for UDP2TCP
if (!t_relay()) {
sl_reply_error();
};
}
Ok, that makes a little more sense, thanks for clearing that up. However
what I'm noticing is that over a period of time the 4 "udp" procs lock
up, at random points from what I can tell. I can't seem to duplicate the
issue, by load testing or by load testing and waiting. One day our
production box "hung" 4 times. What's even more weird is this happens on
0.8.14, 0.9.0, and even latest cvs dev. To compensate I was raising the
child procs up to 100 until I found the problem, even with that many
procs still only 4 "udp" procs ever get generated. Also I disable TCP as
our infrastructure doesn't need it. Any suggestions? I don't want to
enable full debugging on production because I could never get debug to
run stable (duh?). Could this be a distro bug or some kind of lib
mismatch? I've read the manual many times, must be doing something
wrong. I love SER but getting to the point where we maybe forced to get
Asterisk to start proxying (gasp)..
Thanks, Matt
-----Original Message-----
From: Jan Janak [mailto:jan@iptel.org]
Sent: Saturday, April 09, 2005 3:26 AM
To: Matt Schulte
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] Child procs
The children are not all equal. Some of them serve requests coming from
UDP, some of them from TCP and some are auxiliary, like the timer
process or the fifo server.
You can see the purpose of each children using serctl ps command.
If most of the traffic being processed by your server comes over UDP
then only the UDP receivers will be running and the TCP receivers will
be idle, but you still need them to be able to receive TCP based
traffic.
Optimum number of processes depends on your hardware and the amount of
traffic being processed. For common setups 8 children should be OK.
Jan.
On 05-04 07:26, Matt Schulte wrote:
> Does anyone have any opinions on this? What I'm worried about is of
> course running out of procs and thus hanging SER, I believed this to
> have happened several times..
>
> Thanks..
>
> -----Original Message-----
> From: Matt Schulte
> Sent: Monday, April 04, 2005 8:45 AM
> To: serusers(a)lists.iptel.org
> Subject: [Serusers] Child procs
>
>
> Do increasing child procs actually do anything? When I do a 'ps axu' I
> only show 4 of the procs having CPU time, the rest having no cpu time
> at all. Any thoughts on this? Thanks, Matt
>
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
>
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi all,
I am pretty new to Ser and need help to restart the ser application using a
script run by the cron job, The command I am using to restart the ser
application in the script is "serctl stop" and "serctl start". When I try to
run this script by placing it in the cronjob it doesnot work. Although it
works when I run it manually. Can anyone help me how can I restart the SER
application using a script run in the cron job. I also defined the
SIP_DOMAIN parameter in the script itself but it did not work. The SER
version I have is 0.8.14
Thanks for your help in advance
Regards,
Prajyot Shirsolkar
Network Engineer,
BMX Inc.
315-797-1822
prajyot(a)bmx-inc.com
Hello,
Thanks for your reply
I don't find help on http://www.onsip.org/
I've ever load that config without this error message
!?
Look at my ser.cfg setflag is set to 3.
Harry
--- Java Rockx <javarockx(a)gmail.com> wrote:
> Harry,
>
> You can get a detailed line-by-line document on how
> to enable and configure
> MySQL with ser-0.9.x from http://www.onsip.org/
>
> Regards,
> Paul
>
> On Apr 9, 2005 7:29 PM, harry gaillac
> <gaillacharry(a)yahoo.fr> wrote:
> >
> > Hello,
> >
> > Ser don't start because of :
> > serveur1:/etc/ser# /etc/init.d/ser restart
> >
> > There are errors in the configuration file. Please
> fix
> > them first
> >
> > 0(2232) set_mod_param_regex: parameter <db_url>
> not
> > found in module <acc>
> > 0(2232) parse error (110,20-21): Can't set module
> > parameter
> > 0(2232) set_mod_param_regex: parameter
> > <db_missed_flag> not found in module <acc>
> > 0(2232) parse error (111,19-20): Can't set module
> > parameter
> > ERROR: bad config file (2 errors)
> >
> > my ser.cfg:
> >
> > 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"
> > loadmodule "/usr/lib/ser/modules/textops.so"
> > loadmodule "/usr/lib/ser/modules/domain.so"
> > loadmodule "/usr/lib/ser/modules/msilo.so"
> > loadmodule "/usr/lib/ser/modules/acc.so"
> >
> > # -- acc params --
> >
> > modparam("acc", "db_url",
> > "mysql://ser:heslo@localhost/ser")
> > modparam("acc", "db_missed_flag", 3)
> >
> > Harry
> >
> >
> >
> >
>
___________________________________________________________________________________________________
> > Le nouveau Yahoo! Messenger est arrivé ! Découvrez
> toutes les nouveautés
> > pour dialoguer instantanément avec vos amis. A
> télécharger gratuitement sur
> > http://fr.messenger.yahoo.com
> >
> > _______________________________________________
> > Serusers mailing list
> > serusers(a)lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers
> >
>
__________________________________________________________________
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails !
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
Hello,
If I start SER with "ser -d -d -d -d -d -d -d -D -E". I get something
like the following:
0(0) qm_free(0x8109b00, 0x8145548), called from script_cb.c:
destroy_script_cb(81)
0(0) qm_free: freeing frag. 0x8145530 alloc'ed from script_cb.c:
register_script_cb(53)
0(0) qm_free(0x8109b00, 0x8145850), called from script_cb.c:
destroy_script_cb(83)
0(0) qm_free: freeing frag. 0x8145838 alloc'ed from script_cb.c:
register_script_cb(53)
0(0) qm_free(0x4045b000, 0x4049153c), called from main.c:
cleanup(373)
0(0) qm_free: freeing frag. 0x40491524 alloc'ed from main.c:
main(1534)
0(13787) shm_mem_destroy
0(13787) destroying the shared memory lock
localhost:/opt/ser/sbin # pstree
....Does that explain anything? Again when I do pstree, I see 2*
[ser] instead of the usual 27 *[ser].
Kindest regards,
Aisling
>
>---- Original Message ----
>From: greger(a)teigre.com
>To: ashling.odriscoll(a)cit.ie, llanosserna(a)hotmail.com
>Subject: Re: [Serusers] Starting SER : PID file
>exists(/var/run/ser.pid)already running?
>Date: Fri, 8 Apr 2005 19:30:22 +0200
>
>>Try to start ser up in debug/no-fork mode!! You will see if it
>crashes.
>>g-)
>>
>>Aisling O'Driscoll wrote:
>>> Hello,
>>>
>>> When I removed the ser.pid file from /var/run and ran
>>> /opt/ser/sbin/serctl start, it said SER had started. Then when I
>look
>>> at pstree, I see 2 * [ser]. However usually when SER is working
>>> properly it says 27 * [ser]. When I check netstat -tunap, I dont
>see
>>> SER working.
>>>
>>> Any other ideas?
>>>
>>> ---- Original Message ----
>>> From: llanosserna(a)hotmail.com
>>> To: ashling.odriscoll(a)cit.ie
>>> Subject: RE: [Serusers] Starting SER : PID file exists
>>> (/var/run/ser.pid)already running?
>>> Date: Fri, 08 Apr 2005 13:53:25 +0200
>>>
>>>> <html><div style='background-color:'><DIV class=RTE></DIV>
>>>> <P>Make sure ser is not running with a </P>
>>>> <P>>ps -ef</P>
>>>> <P>I fit's not there, just remove the pid file</P>
>>>> <P>>rm /var/run/ser.pid</P>
>>>> <P>And then you should be able to start ser</P>
>>>> <P> </P>
>>>> <P> </P>
>>>> <P> </P>
>>>> <DIV class=RTE>>Hi, </DIV>
>>>> <DIV></DIV>>
>>>> <DIV></DIV>>I am wondering if anyone has ever come across this
>>>> error before?:
>>>> <DIV></DIV>>
>>>> <DIV></DIV>>Starting SER : PID file exists! (/var/run/ser.pid)
>>>> already running?
>>>> <DIV></DIV>>
>>>> <DIV></DIV>>I am using ser 0.9.0 and it worked like a charm
>the
>>>> first few times
>>>> <DIV></DIV>>that I stopped and started SER. There are no
>errors in
>>>> <DIV></DIV>>/var/log/messages. I also started SER as
>>>> /opt/ser/sbin/ser -c and it
>>>> <DIV></DIV>>showed that the config was ok and exited. However
>when
>>>> I check
>>>> <DIV></DIV>>pstree, I dont see SER listening.
>>>> <DIV></DIV>>
>>>> <DIV></DIV>>Could it perhaps be something got to do with the
>>>> database?. Example:
>>>> <DIV></DIV>>Should the version table in the SER database
>contain
>>>> "version" or
>>>> <DIV></DIV>>"table_version"? I have tried dropping and
>restarting
>>>> the database
>>>> <DIV></DIV>>i.e. /opt/ser/sbin/ser_mysql.sh drop, then
>>>> <DIV></DIV>>./opt/ser/sbin/ser_mysql.sh create.
>>>> <DIV></DIV>>
>>>> <DIV></DIV>>Any ideas would be appreciated.
>>>> <DIV></DIV>>Thanks,
>>>> <DIV></DIV>>Aisling.
>>>> <DIV></DIV>>
>>>> <DIV></DIV>>
>>>>
><DIV></DIV>>-------------------Legal Disclaimer--------
>>>> -------------------------------
>>>> <DIV></DIV>>
>>>> <DIV></DIV>>The above electronic mail transmission is
>confidential
>>>> and intended only for the person to whom it is addressed. Its
>>>> contents may be protected by legal and/or professional privilege.
>>>> Should it be received by you in error please contact the sender
>at
>>>> the above quoted email address. Any unauthorised form of
>reproduction
>>>> of this message is strictly prohibited. The Institute does not
>>>> guarantee the security of any information electronically
>transmitted
>>>> and is not liable if the information contained in this
>communication
>>>> is not a proper and complete record of the message as transmitted
>by
>>>> the sender nor for any delay in its receipt.
>>>> <DIV></DIV>>
>>>> <DIV></DIV>>_______________________________________________
>>>> <DIV></DIV>>Serusers mailing list
>>>> <DIV></DIV>>Serusers(a)iptel.org
>>>> <DIV></DIV>>http://mail.iptel.org/mailman/listinfo/serusers
>>>> <DIV></DIV></div></html>
>>>>
>>>>
>>>> -------------------Legal
>>>> Disclaimer---------------------------------------
>>>>
>>>> The above electronic mail transmission is confidential and
>intended
>>>> only for the person to whom it is addressed. Its contents may be
>>>> protected by legal and/or professional privilege. Should it be
>>>> received by you in error please contact the sender at the above
>>>> quoted email address. Any unauthorised form of reproduction of
>this
>>>> message is strictly prohibited. The Institute does not guarantee
>the
>>>> security of any information electronically transmitted and is not
>>>> liable if the information contained in this communication is not
>a
>>>> proper and complete record of the message as transmitted by the
>>>> sender nor for any delay in its receipt.
>>>>
>>>
>>>
>>>
>>> -------------------Legal
>>> Disclaimer---------------------------------------
>>>
>>> The above electronic mail transmission is confidential and
>intended
>>> only for the person to whom it is addressed. Its contents may be
>>> protected by legal and/or professional privilege. Should it be
>>> received by you in error please contact the sender at the above
>>> quoted email address. Any unauthorised form of reproduction of
>this
>>> message is strictly prohibited. The Institute does not guarantee
>the
>>> security of any information electronically transmitted and is not
>>> liable if the information contained in this communication is not a
>>> proper and complete record of the message as transmitted by the
>>> sender nor for any delay in its receipt.
>>>
>>> _______________________________________________
>>> Serusers mailing list
>>> Serusers(a)iptel.org
>>> http://mail.iptel.org/mailman/listinfo/serusers
>>
>>-------------------Legal
>Disclaimer---------------------------------------
>>
>>The above electronic mail transmission is confidential and intended
>only for the person to whom it is addressed. Its contents may be
>protected by legal and/or professional privilege. Should it be
>received by you in error please contact the sender at the above
>quoted email address. Any unauthorised form of reproduction of this
>message is strictly prohibited. The Institute does not guarantee the
>security of any information electronically transmitted and is not
>liable if the information contained in this communication is not a
>proper and complete record of the message as transmitted by the
>sender nor for any delay in its receipt.
-------------------Legal Disclaimer---------------------------------------
The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.