Hi padmaja,
I guess there should have been a standalone directory called openser1.0.1 after you untar the .tar.gz file using tar -xzvf. In that directory itself there is file called Makefile in which the mysql module is excluded by default.
Did you also check the logs in /var/log/messages about what is the error. Those messages are helpful to debug.
You dont always need to go to sbin to start openser, there is a command called openserctl start to start it.
I have a suggestion for you. Please visit onsip.org and register on that site. They have very good getting started documents which will help you.
You can then structure your openser.cfg the way you want.
w/regards,
Jayesh.
Hi Jayesh,
Thank you so much for the reply. I have downloaded the version openser-1.0.1 from cvs. I thought that is a stable release and no changes are going to be made to it. Do i have to again revert to the tar.gx version? Also please look at what happened when i previously installed the .tar.gz version of openser before doing the cvs
1. downloaded openser-1.0.1-linux_i386.tar.gz version as root.
2. It is now under / (the root directory). after that i did unzip and untar on that.
3. the file and modules are loaded into the subdirectories of the /usr directory.I could not anywhere find a standalone directory called openser-1.0.1 with the directory sip-server in it. also there is no makefile here.... (All these i see when i download it thru CVS in the /usr/local/src directory.)
4. I tried to see through the list for the module mysql.so but i could not find it....and so for uri_db module also. these modules are present when i install openser thru cvs
5. i did not do any make on it. I thought it is precompiled version and will automatically get installed when i do the untar and unzip. please correct me if the tar version also has to go thru make
6. i ran openser through /usr/local/sbin/openser start. and it ran successfully... it showd the tcp and udp ports on which it is running..i could register my sip UA without authentication.
7. then i wanted to set it up for mysql support. i edited the config file and uncommented the necessary modules and tried to create the openser databse in mysql. here it failed stating ha1 calculation failed.. also it states there is no mysql.so module which is true.
Please let me know if I have made any mistakes in the installation process.... I am new to openser.. now if i want to revert to .tar.gz version, will all the openser modules and config files from the cvs be replaced by the tar.gz version? or will there be duplicate entries left?
Thanks again
Regards,
Padmaja
----- Original Message -----
From: Jayesh Nambiar
To: users(a)openser.org
Cc: padmaja.rv(a)vodcalabs.com
Sent: Wednesday, May 31, 2006 12:08 PM
Subject: [Users] Re: how to run openser through monit daemon?
Hi padmaja,
Running openser from cvs would not solve your problem. Openser from cvs is the development version which will be released after final testing is done.
To be safe, its better if you use .tar.gz file to install. For enabling mysql, go to the openser directory and you'll find a makefile. In the makefile there is a line exclude_modules?= somewhere around line no.49. From there just remove mysql and recompile it again.
You can start openser using openserctl start from the command line.
To check for some errors you can set debug=9 in the openser.cfg file.
Normally the logs are stored into /var/log/messages. You can check for errors in this file.
Hi!
there is something I need to mention here with respect to openser not
working.....
Initially I had openser installed from .tar.gz and i could run it from
/usr/local/sbin/openser. It worked fine that way without any authentication.
I could see local registration of my sip UAs with the openser being
successful. then i set up mysql. It too started successfulyy thru webmin.
next I tried to create the openser database in mysql from
/usr/sbin/openser_mysql.sh create. It prompted me for the root password of
mysql, the domain name and then failed stating that the Ha1 calculation
failed. also when i tried to modify the openser.cfg file to support mysql
database i found that there is no mysql.so module in the
/usr/local/lib/openser/modules/ path.
Because of the above problems, I tried installing openser from CVS and here
all the modules and configuration files are present in the respective
locations as mentioned in the web link for installing openser. I could even
create the openser database structures in mysql. i tried uncommenting the
needed modules for database suppport. now when i try to run openser thru
monit, there is absolutely no response and openser does not look like
running............
I am a newbie at openser......please help me which way i should run
openser.....
thanks and regards,
Padmaja
---------------------------------
Yahoo! India Answers: Share what you know. Learn something new Click here
Send free SMS to your Friends on Mobile from your Yahoo! Messenger Download now
Hello,
I'm asking how to configure a server mail with SER.
I would test sending mail over SER between two MSN clients but thid doen't
wok!
Thanks in advance!
Cheers,
Rekik Refka
I have prefix e.164 that I need to change by domainame, but I have problem
with DNS.
When I have prefix "19991" I need to change URI by "@domainname.br". Is the
regexp "!^.*$sip:.+$!@domainname.br" correct?
$ORIGIN 1.9.9.9.1.e164.arpa.
IN NAPTR 1 10 "E2U+sip" "!^.*$sip:.+$!@domainname.br".
Hi Everybody,
I had arrived a small problem , when i making the call from softphones....
It logined and when dialing to some other softphone , its show me as " CALL
NOT aPPROVED "
what this means,
please solve problem....
and my openser.cfg file
--------------------------
#
# $Id: openser.cfg,v 1.5 2005/10/28 19:45:33 bogdan_iancu Exp $
#
# simple quick-start config script
#
# ----------- global configuration parameters ------------------------
debug=4 # debug level (cmd line: -dddddddddd)
fork=no
log_stderror=yes # (cmd line: -E)
/* Uncomment these lines to enter debugging mode
fork=no
log_stderror=yes
*/
server_signature=yes
unix_sock="/tmp/openser.sock"
#user="openser"
#group="openser"
listen=192.168.2.55
check_via=0 # (cmd. line: -v)
dns=no # (cmd. line: -r)
rev_dns=no # (cmd. line: -R)
port=5060
children=3
alias=192.168.2.55
fifo="/tmp/openser_fifo"
fifo_db_url="mysql://openser:openserrw@localhost/openser"
fifo_mode=0666
#fifo_dir="/tmp/"
#fifo_modesock_modefile_mode=0660
#
# uncomment the following lines for TLS support
#disable_tls = 0
#listen = tls:your_IP:5061
#tls_verify = 1
#tls_require_certificate = 0
#tls_method = TLSv1
#tls_certificate = "/usr/local/etc/openser/tls/user/user-cert.pem"
#tls_private_key = "/usr/local/etc/openser/tls/user/user-privkey.pem"
#tls_ca_list = "/usr/local/etc/openser/tls/user/user-calist.pem"
# ------------------ module loading ----------------------------------
# Uncomment this if you want to use SQL database
loadmodule "/usr/local/lib/openser/modules/mysql.so"
loadmodule "/usr/local/lib/openser/modules/sl.so"
loadmodule "/usr/local/lib/openser/modules/tm.so"
loadmodule "/usr/local/lib/openser/modules/rr.so"
loadmodule "/usr/local/lib/openser/modules/maxfwd.so"
loadmodule "/usr/local/lib/openser/modules/usrloc.so"
loadmodule "/usr/local/lib/openser/modules/registrar.so"
loadmodule "/usr/local/lib/openser/modules/textops.so"
# Uncomment this if you want digest authentication
# mysql.so must be loaded !
loadmodule "/usr/local/lib/openser/modules/auth.so"
loadmodule "/usr/local/lib/openser/modules/auth_db.so"
loadmodule "/usr/local/lib/openser/modules/acc.so"
# ----------------- setting module-specific parameters ---------------
# -- usrloc params --
#modparam("usrloc", "db_mode", 1)
# 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)
modparam("usrloc","db_url","mysql://openser:openserrw@localhost/openser")
#modparam("auth","db_url","mysql://openser:openserrw@localhost/openser")
modparam("auth_db","db_url","mysql://openser:openserrw@localhost/openser")
modparam("auth","secret","")
modparam("acc","log_flag",1)
modparam("acc","log_level",1)
modparam("acc","radius_config","/usr/local/etc/radiusclient-ng/radiusclient.conf")
# ------------------------- 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");
exit;
};
if (msg:len >= 2048 ) {
sl_send_reply("513", "Message too big");
exit;
};
# 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);
};
if (!uri==myself) {
# mark routing logic in request
append_hf("P-hint: outbound\r\n");
# if you have some interdomain connections via TLS
#if(uri=~"@tls_domain1.net") {
# t_relay_to_tls("IP_domain1","port_domain1");
# exit;
#} else if(uri=~"@tls_domain2.net") {
# t_relay_to_tls("IP_domain2","port_domain2");
# exit;
#}
route(1);
};
# 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("192.168.2.55", "subscriber")) {
www_challenge("192.168.2.55", "0");
exit;
};
save("location");
setflag(1);
if(method=="INVITE")
{
record_route();
};
exit;
};
lookup("aliases");
if (!uri==myself) {
append_hf("P-hint: outbound alias\r\n");
route(1);
};
# native SIP destinations are handled using our USRLOC DB
if (!lookup("location")) {
sl_send_reply("404", "Not Found");
exit;
};
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();
};
exit;
}
Bye
--
Thanks and Regards with cheers
Sunkara Ravi Prakash (Voip Developer)
Hyperion Technology
www.hyperion-tech.com
<b>
Hi Vaclav,
On which file does Ser look for when authorizing messages ?
According to that maybe I can link privacy-lists file to im-rules file (which Ser looks for)
Would that work ?
Usrloc problem is very important for me. Please tell me anything I can do to find out the problem (if there is anything that I can do)
Thanks,
ilker
-----Original Message-----
From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
Sent: Wednesday, May 31, 2006 9:29 AM
To: İlker Aktuna (Koç.net)
Cc: samuel; serusers(a)iptel.org
Subject: Re: Authorizing IM requests
Hi,
yes I did, but I had forgotten...
You can NOT use EyeBeam to work with message authorization - it will NEVER set the rules which are needed by SER. You can do this only manually on XCAP server.
I try to look on the userloc problem, but don't know when.
Vaclav
On Tue, May 30, 2006 at 05:29:27PM +0300, ?lker Aktuna (Koç.net) wrote:
> Hi Vaclav,
>
> Did you receive my following email ?
>
> Btw, I still couldn't find the neccessary db structure for using
> usrloc with db support. Can you point me to the right person who knows
> the required db structure ?
>
> Thanks,
> ilker
>
> ________________________________
>
> From: ?lker Aktuna (Koç.net)
> Sent: Monday, May 29, 2006 12:52 PM
> To: 'Vaclav Kubart'
> Cc: samuel; serusers(a)iptel.org
> Subject: RE: Authorizing IM requests
>
>
>
>
> Well, then what can I use in the following line to authorize IM messages ?
>
> if (authorize_message("https://sip.koc.net/xcap")) {
>
> Eyebeam updates file /xcap/privacy-lists/user/privacy-lists.xml when I change the "privacy" configuration on Eyebeam client.
>
> Thanks,
> ilker
>
> -----Original Message-----
> From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
> Sent: Friday, May 26, 2006 4:48 PM
> To: ?lker Aktuna (Koç.net)
> Cc: samuel; serusers(a)iptel.org
> Subject: Re: Authorizing IM requests
>
> Yes, I meant, that this will not work together.
>
> I don't know. Privacy-lists are something eyeBeam's internal or something standardized?
>
> Im-rules are SER internal.
>
> Vaclav
>
> On Fri, May 26, 2006 at 04:43:35PM +0300, ?lker Aktuna (Koç.net) wrote:
> > Do you mean it won't work with privacy-lists ?
> > What can I try ?
> >
> > Thanks,
> > ilker
> >
> > -----Original Message-----
> > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
> > Sent: Friday, May 26, 2006 4:40 PM
> > To: ?lker Aktuna (Koç.net)
> > Cc: samuel; serusers(a)iptel.org
> > Subject: Re: Authorizing IM requests
> >
> > EyeBeam won't use im-rules and SER won't use with privacy-lists. It something else.
> >
> > Vaclav
> >
> > On Fri, May 26, 2006 at 02:24:42PM +0300, ?lker Aktuna (Koç.net) wrote:
> > > Hi Samuel,
> > >
> > > Now that presence is working I'm checking xcap possibilities.
> > > I see that IM xcap authorization is not working.
> > >
> > > I don't know what to use in:
> > > >if (authorize_message("im-rules.xml")){
> > >
> > > My client (Eyebeam) does not use im-rules.xml , but it uses
> > > privacy-lists.xml and that file is in privacy-lists folder. How
> > > should I change the configuration line to use this file ?
> > >
> > > Regards,
> > > ilker
> > >
> > > -----Original Message-----
> > > From: samuel [mailto:samu60@gmail.com]
> > > Sent: Tuesday, May 16, 2006 5:26 PM
> > > To: Vaclav Kubart
> > > Cc: ?lker Aktuna (Koç.net); serusers(a)iptel.org
> > > Subject: Re: [Serusers] PA error sending notifies
> > >
> > > 2006/5/16, Vaclav Kubart <vaclav.kubart(a)iptel.org>:
> > > > reply inline...
> > > > > If you are using XCAP authentication for MESSAGEs, there's a
> > > > > function called authorize_message that needs to have as
> > > > > parameter the file name of the IM ruleset.
> > > > > For user sam, in xcap-root/im-rules/users/sam/im-rules.xml
> > > > > there are the rules for this function. The XML file is similar
> > > > > to the presence-rules but has important differences (correct
> > > > > me if I'm wrong,
> > > > > Vaclav!!!):
> > > > > *it only has a blacklist parameter (no whitelist!!)
> > > >
> > > > It doesn't depend on name of the rule (blacklist/whitelist/...)
> > > > it depends on the action (block, ...). You can have as many
> > > > rules as you want, but to explicitly enable something
> > > > (whitelist) is needless because MESSSAGEs are allowed by default
> > > > (at the end of the presence handbook I tried to describe
> > > > im-rules the same way as presence-rules are described in their draft).
> > > >
> > > > > *the namespace is different (so be carefull in copy&paste from
> > > > > the
> > > > > presence-rules!!!) and, as Vaclav poitned out "proprietary"
> > > > > from iptel.
> > > >
> > > > And the action element name differs: <im-handling> is used
> > > > instead of <sub-handling>.
> > > >
> > >
> > > Uops...I haven't noticed :P thanks!
> > >
> > > > Vaclav
> > > >
> > > > >
> > > > > About the structure I have: x86 debian testing. Libraries
> > > > > versions I don't know exactly but the ones in the testing
> > > > > repository EXCEPT a library which I had to get for serweb from
> > > > > the stable version...but it's not affecting SER part.
> > > > >
> > > > > Samuel.
> > > > > 2006/5/16, ?lker Aktuna (Koç. net ) <ilkera(a)koc.net>:
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >Hi,
> > > > > >
> > > > > >What did you mean by following:
> > > > > >
> > > > > >>Instead of
> > > > > >>>
> > > > > >>> if (authorize_message("http://localhost/xcap")) {
> > > > > >>
> > > > > >>there should be
> > > > > >>
> > > > > >>if (authorize_message("im-rules.xml")){
> > > > > >
> > > > > >Btw, did you receive my email with following questions :
> > > > > >
> > > > > >>> I have the same problem with notification and other
> > > > > >>> presence messages
> > > > > >with you.
> > > > > >>> Can you tell me which Linux distribution you are using Ser on ?
> > > > > >>> Also please include version numbers for libraries that are
> > > > > >>> required by
> > > > > >Ser.
> > > > > >>>
> > > > > >>> I am trying to find similarities between yours and my ser server.
> > > > > >
> > > > > >Regards,
> > > > > >ilker
> > > > > >
<http://387555.sigclick.mailinfo.com/sigclick/06090304/030C4A09/02014803/151…>
_____________________________________________________________________________________________________________________________________________
Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez.
This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence.
_____________________________________________________________________________________________________________________________________________
I am still digging in this cseq uac problem which I need desperately to solve.
The problem is that the uac_auth function can create credentials for the downstream proxy after being challenged with a 401 or 407 message - but the downstream proxy (UAS) refuses this proxy_auth message since openser does not increase the cseq number. Increasing the cseq number only downstream wouldnt solve the problem since any replies of the downstream proxy back to the originating UAC would have cseq numbers which are out of sync.
I propose: In order to keep the cseq numbers in sync upstream and downstream one must generate challenges and proxy-auth responses on both legs of the route - and not only respond downstream as currently.
So whenever openser receives from the downstream proxy a challenge it must forward this challenge the originating UAC (if necessary modify the message in such a way that the UAC is guaranteed to respond). This upstream challenge causes the originating UAC to increase the cseq. Naturally openser must also increase the cseq number downstream when generating its own proxy_auth repsonse to the downstream proxy. Whatever credentials UAC produces are discarted by openser.
The scheme:
1. UAC issues invite which is routed by OS to the downstream proxy (UAS) - as usual.
2. UAS issues challenge 401 or 407 - as usual
3. OS captures challenge on_failure route - as envisaged by UAC module
4. this is new:
a) OS relays the challenge upstream to UAC (would it be necessary to modify it before doing so ?)
b) OS constructs with uac_auth function correct proxy_auth credentials for UAS, increases the cseq with some text manipulation function and replies to UAS.
5. UAC responds with (wrong) proxy_auth credentials via OS to UAS
6. OS discards the credential message it received from the UAC - to avoid that the message reaches UAS.
7. Invite successful or failure : UAS responds with further messages which are routed to UAC.
Can this scheme work - or am I overlooking something here ?
TIA
Gerry
Hi all!
can any one tell me what is the best method to run openser out of
all the methods mentioned in the link below?
http://openser.org/install.php
Thank you,
Regards,
Padmaja
----- Original Message -----
From: <users-request(a)openser.org>
To: <users(a)openser.org>
Sent: Wednesday, May 31, 2006 12:09 PM
Subject: Users Digest, Vol 12, Issue 83
> Send Users mailing list submissions to
> users(a)openser.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://openser.org/cgi-bin/mailman/listinfo/users
> or, via email, send a message with subject or body 'help' to
> users-request(a)openser.org
>
> You can reach the person managing the list at
> users-owner(a)openser.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Users digest..."
>
>
> Today's Topics:
>
> 1. Can this work?: re. uac_auth cseq problem (G.Jacobsen)
> 2. Call Hunting: use Avpop or LCR module ? (Rafael J. Risco G.V.)
> 3. Re: Call Hunting: use Avpop or LCR module ?
> (Daniel-Constantin Mierla)
> 4. multiple domain best practices? (Mark Kent)
> 5. Re: dispatcher module and rewritehost vs forward (Script Head)
> 6. Dialog Module & MySQL (Martin Klisch)
> 7. OpenSER and Redundancy (Martin Klisch)
> 8. Re: how to run openser through monit daemon? (Jayesh Nambiar)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 30 May 2006 17:19:05 +0300
> From: "G.Jacobsen" <g_jacobsen(a)yahoo.co.uk>
> Subject: [Users] Can this work?: re. uac_auth cseq problem
> To: <users(a)openser.org>
> Message-ID: <06ef01c683f8$3d8da960$6501a8c0@winmach1>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I am still digging in this cseq uac problem which I need desperately to
> solve.
>
> The problem is that the uac_auth function can create credentials for the
> downstream proxy after being challenged with a 401 or 407 message - but
> the downstream proxy (UAS) refuses this proxy_auth message since openser
> does not increase the cseq number. Increasing the cseq number only
> downstream wouldnt solve the problem since any replies of the downstream
> proxy back to the originating UAC would have cseq numbers which are out of
> sync.
>
> I propose: In order to keep the cseq numbers in sync upstream and
> downstream one must generate challenges and proxy-auth responses on both
> legs of the route - and not only respond downstream as currently.
>
> So whenever openser receives from the downstream proxy a challenge it must
> forward this challenge the originating UAC (if necessary modify the
> message in such a way that the UAC is guaranteed to respond). This
> upstream challenge causes the originating UAC to increase the cseq.
> Naturally openser must also increase the cseq number downstream when
> generating its own proxy_auth repsonse to the downstream proxy. Whatever
> credentials UAC produces are discarted by openser.
>
> The scheme:
>
> 1. UAC issues invite which is routed by OS to the downstream proxy (UAS) -
> as usual.
> 2. UAS issues challenge 401 or 407 - as usual
> 3. OS captures challenge on_failure route - as envisaged by UAC module
> 4. this is new:
> a) OS relays the challenge upstream to UAC (would it be necessary to
> modify it before doing so ?)
> b) OS constructs with uac_auth function correct proxy_auth credentials for
> UAS, increases the cseq with some text manipulation function and replies
> to UAS.
> 5. UAC responds with (wrong) proxy_auth credentials via OS to UAS
> 6. OS discards the credential message it received from the UAC - to avoid
> that the message reaches UAS.
> 7. Invite successful or failure : UAS responds with further messages which
> are routed to UAC.
>
> Can this scheme work - or am I overlooking something here ?
>
> TIA
>
> Gerry
>
Hello,
I am deploying OpenSER to distribute calls for a number of Asterisk boxes. I
believe there are some people on this list to have a similar setup. I'd like
to know what kind of hardware do you guys run OpenSER on and how many calls
per second can you set up with your specs. I am looking to set up about
30-40 calls per second so I was wondering what kind of hardware I'd need.
ScriptHead
I have the following in my config, which works...
now if I comment forward and comment out rewritehost I get errors. Am I not
using the correct syntax?
route[5] {
# -----------------------------------------------------------------
# PSTN Handler
# -----------------------------------------------------------------
t_on_reply("1");
# do load balancing
ds_select_dst("1","4");
sl_send_reply("100","Trying");
#rewritehost(uri:host);
forward(uri:host,uri:port);
route(4);
route(1);
}
