I lost my link to the only ser fifo tutorial I ever saw.I'd like to
write some scripts that talk to the fifo but I do not know what commands
are available. Does anyone have a tutorial?
Thanks,Steve
I want to support 302 type moves. The sip devices we had before supported
reinvites but the new linksys units send a 302 message telling me that the
user has temporarly moved. Is there a good example of the redirects modules
use in the cookbook example? My cfg file is based off that and I would like
to add this to a live working system with little interruption or suprises.
Thanks,
Shane
I see that there was some discussion back in March 2006
(http://www.openser.org/pipermail/users/2006-March/003339.html)
regarding this parameter, but nothing since. Daniel mentioned that
perhaps it might be put on the to-do list, but I see no mention of it
anywhere else. Was this implemented in 1.2?
I see that maddr is available using pseudo-var transformations as
{uri.maddr} in 1.2, but not mention of any automatic behavior if the
parameter exists.
I realize that I can work around it by using subst and subst_uri, but I
really shouldn't have to. A simple t_relay should send it on its merry
way to the value of maddr. My reading of both RFC3261 and 3263 seem to
imply that the existence of this parameter in the request URI mandates
forwarding the request to this address.
I see in the code (for 1.1.1, I haven't looked at 1.2 yet) that the
parameter is parsed, but then it appears (correct me if I'm wrong) as
though nothing further is done with it. Is there some relatively simple
way to modify the code to so that the maddr is used directly?
As you can probably tell, I have a gateway with which I have to
interoperate which uses this parameter extensively, hence my interest.
:)
Any advice (even if it's "use subst and subst_uri you whiner" ;) ) is
appreciated.
Thanks in advance,
- Brad
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
Hi
Does any one successfully deployed CDR Tools
with prepaid and post paid
iam looking mainly call disconnect when the balance of the user go negative
any sugestions
ram
Hello,
I am doing interop testing with Level3, and need to be able to rewrite
the To: field in requests to match their requirements. I can fake the
rewrites inside route[], but although the packets sent out look like
they use the new "To:", the header is never parsed again, so the
internal structures of SER still hold the former (incorrect) value.
When a request hit failure_route[] (for example when a CANCEL is sent
when an INVITE times out) the original, incorrect To: header is then
sent (and there's no way to modify the content of the CANCEL from
within failure_route[]).
Is there a standard way to alter the internally-stored value for To:
(and From:, since I'm asking)?
If not, could someone point me to the right place in the code to start
adding this kind of feature?
Thanks,
Stéphane Alnet
--
http://carrierclass.net/http://www.linkedin.com/in/stephalnet
This line?
modparam("auth_db", "password_column", "password")
If so, yes, we did try altering that line to reflect the password for the 'openser' user. Is that what you mean?--If not, can you explain?
Thanks for the help.
-Ben-
----- Original Message -----
From: "Ovidiu Sas" <sip.nslu(a)gmail.com>
To: "Ben Ferguson - backcountry.com" <bferguson(a)backcountry.com>
Cc: users(a)openser.org
Sent: Tuesday, February 20, 2007 6:36:50 PM (GMT-0700) US/Mountain
Subject: Re: [Users] Re: openSER on OpenBSD: cannot start openser
Hi Ben,
Have you changed the password inside the openser.cfg file?
Regards,
Ovidiu Sas
On 2/20/07, Ben Ferguson - backcountry.com <bferguson(a)backcountry.com> wrote:
> After further investigation, it looks as though this is actually caused by changing the default passwords for the openser and openserro users. We tried changing the passwords in openserctlrc to correspond with the mysql user password changes. We granted the rights accordingly in mysql as well. We also found /usr/local/lib/openser/openserctl/openserctl.sqlbase and /usr/local/sbin/openser_mysql.sh that referenced the passwords and we changed them accordingly there and still had no luck. We could not find any other files that seemed to reference the actual passwords. So we then removed the database and tried a fresh install and got the same result. So again the database was removed and this time we altered /usr/local/lib/openser/openserctl/openserctl.sqlbase and /usr/local/sbin/openser_mysql.sh to reflect the passwords we wanted to use, and ran openser_mysql.sh create. This resulted in the same error as before. So, we set all the files back to default with the default passwords, removed all mysql database info and again ran operser_mysql.sh create. Then ran openserctl start again:
>
> # openserctl start
> database engine 'MYSQL' loaded
> Control engine 'FIFO' loaded
>
> Starting OpenSER : \E[37;33mINFO: started (pid: 3947)
> #
>
> Sweet! We then stopped openser and went and changed the passwords again in mysql and in openserctlrc and got the same error as before. It is impossible to change the passwords for openser and openserro to something other than the default! Crazy! We do not want to run with the default passwords...
>
> Any ideas?
>
> We are using OpenBSD 4.0 i386, openSER-1.1.1-tls, mysql5.0.
>
> Thanks,
> Ben
>
>
> ----- Original Message -----
> From: "Ben Ferguson - backcountry.com" <bferguson(a)backcountry.com>
> To: users(a)openser.org
> Sent: Tuesday, February 20, 2007 2:04:15 PM (GMT-0700) US/Mountain
> Subject: openSER on OpenBSD: cannot start openser
>
>
>
> Hello all,
>
> I've just installed openSER on OpenBSD and I'm now trying to get openSER to start and am having trouble. I try openserctl start and here's what i get:
>
>
> # openserctl start
> database engine 'MYSQL' loaded
> Control engine 'FIFO' loaded
>
> Starting OpenSER :
> \E[37;31mERROR: PID file /var/run/openser.pid does not exist -- OpenSER start failed
> #
>
> After a bunch of reading it seems as if openserctl is now obsolete (???) and that you should use the init script. I can't find reference for anyone running it like this on OpenBSD. I have found openser.init file in /<src directory>/packaging/gentoo and /<src directory>/packaging/rpm, but i am not sure how to use them on OpenBSD (I'm rather new to OpenBSD... I'm used to the rpm style of things.)
>
> I've searched and searched but can't find any info... So. anybody out there using openSER on OpenBSD? Or anybody know howto (or whereto find the info to) set up the start script for openSER on OpenBSD?
>
> Any help is greatly appreciated!
>
> Thanks,
> Ben
>
> _______________________________________________
> Users mailing list
> Users(a)openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>
Hi
I am new to all openser related things. I managed to install it, combine
with postgres and do simple accounting, but now I am facing a slightly
problem. The situation looks like this:
I have two sip phones both on public IP and both registered to openser (on
public IP). I am able to ring between this two phones (so I guess that the
sip signalization works OK), but I can't hear any voice. For testing
purposes I disabled the firewall on openser so I am sure that all ports are
"free". My openser.cfg looks like this:
#------------------- global configuration parameters
------------------------
debug=3 # debug level (cmd line: -dddddddddd)
fork=yes # Set to no to enter debugging mode
log_stderror=no # (cmd line: -E) Set to yes to enter debugging mode
check_via=no # (cmd. line: -v)
dns=no # (cmd. line: -r)
rev_dns=no # (cmd. line: -R)
port=5060
children=4
fifo="/tmp/openser_fifo"
#
# 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 = "/build/buildd/openser-1.1.0
/debian/openser/etc/openser/tls/user/user-cert.pem"
#tls_private_key = "/build/buildd/openser-1.1.0
/debian/openser/etc/openser/tls/user/user-privkey.pem"
#tls_ca_list = "/build/buildd/openser-1.1.0
/debian/openser/etc/openser/tls/user/user-calist.pem"
# ------------------ module loading ----------------------------------
loadmodule "/usr/lib/openser/modules/postgres.so"
loadmodule "/usr/lib/openser/modules/sl.so"
loadmodule "/usr/lib/openser/modules/tm.so"
loadmodule "/usr/lib/openser/modules/rr.so"
loadmodule "/usr/lib/openser/modules/maxfwd.so"
loadmodule "/usr/lib/openser/modules/usrloc.so"
loadmodule "/usr/lib/openser/modules/registrar.so"
loadmodule "/usr/lib/openser/modules/textops.so"
loadmodule "/usr/lib/openser/modules/acc.so"
loadmodule "/usr/lib/openser/modules/dbtext.so"
#loadmodule "/usr/lib/openser/modules/mediaproxy.so"
# Uncomment this if you want digest authentication
# mysql.so must be loaded !
loadmodule "/usr/lib/openser/modules/auth.so"
loadmodule "/usr/lib/openser/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", no)
#
# If you set "calculate_ha1" parameter to yes (which true in this config),
# uncomment also the following parameter)
#
#modparam("auth_db", "password_column", "password")
modparam("auth_db", "password_column", "ha1")
# -- rr params --
# add value to ;lr param to make some broken UAs happy
modparam("rr", "enable_full_lr", 1)
#usrloc|auth_db|
modparam("usrloc|auth_db", "db_url", "
postgres://openser:openserrw@XXX.XXX.XXX.XXX:5432/openser")
modparam("acc", "db_url", "postgres://openser:openserrw@XXX.XXX.XXX.XXX
:5432/openser")
#modparam("acc", "db_url", "postgres://openser:openserrw@XXX.XXX.XXX.XXX
:5432/openser")
#modparam("acc", "failed_transaction_flag", 1)
#modparam("acc", "report_cancels", 1)
modparam("acc", "db_flag", 1)
modparam("acc", "log_level", 1)
#modparam("acc", "log_fmt", "mfs")
#modparam("acc", "log_flag", 1 )
#modparam("acc", "log_fmt", "miocfs")
#modparam("acc", "db_flag", 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");
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=="INVITE")
{
# mark the INVITEs for accounting
setflag(1);
# enforce record-routing so the BYEs will come through this
server
record_route();
};
#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
if(method=="BYE") {
setflag(1);
}
t_relay();
return;
#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("tls:domain1.net");
# exit;
#} else if(uri=~"@tls_domain2.net") {
# t_relay("tls:domain2.net");
# 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)
} else {
if (method=="REGISTER") {
#Uncomment this if you want to use digest authentication
if (!www_authorize("XXX.XXX.XXX.XXX", "subscriber")) {
www_challenge("XXX.XXX.XXX.XXX", "0");
exit;
} else {
save("location");
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 (uri=~"sip:003275566*") {
if (!lookup("location")) {
sl_send_reply("444", "Not Found");
exit;
}
append_hf("P-hint: usrloc applied\r\n");
} else {
rewritehost("YYY.YYY.YYY.YYY");
#t_relay();
};
};
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;
}
What could cause this silence?
I was wondering maybe mediaproxy or rtpproxy could help, but there is no nat
so I can find a reason why I should use them.
Could you check my conf file and point me into appropriate direction. Any
kind of help would be gladly expected.
Best wishes to all.
Andrew
Anyone can recommend a good CDR extraction module that would work with
old ser-0.8.14 ? I want it to parse all our calls that are sitting in
our old logs.
Thanks
Nick
Ok, I figured out how to unlock the config, using the new menu item called (doh!) "unlock config". One 7960 phone now a functioning SIP phone on the OpenSER. Last thing to figure out is why I cannot access it by browser.
Thanks again for the help.
Scott Yagel
PacketCall, Inc.
syagel(a)packetcall.net
>-----Original Message-----
>From: Stephen Varga [mailto:varga@zbzoom.net]
>Sent: Wednesday, February 21, 2007 11:38 AM
>To: syagel(a)packetcall.net
>Cc: users(a)openser.org
>Subject: Re: [Users] Cisco 7960 phones
>
>Scott,
>
>Put the attached files into your tftp server that the phones are pulling
>their configs and image from. You should also have the following image
>files in the same tftp server:
>
> P003-08-2-00.bin
> P0S3-08-2-00.loads
> P0S3-08-2-00.zip
> P003-08-2-00.sbn
> P0S3-08-2-00.sb2
>
>I have used these files to successfully upgrade phones.
>
>If you have SIPxxxxxxxxxxxx.cnf file created for the phones, make sure
>the image_version line is commented out.
>
>The biggest problem I have with this version is using that it reads the
>dialplan.xml file but it does not work; I am guessing there is a syntax
>change but can not been able to find SIP documentation related to the
>8.2 code on Cisco's website. I have been staying with the 7.5 version
>of the code because of this problem.
>
>I found watching which files are being requested by phone a big help in
>getting the loads to work properly
>
>Let me know what happens.
>
>Steve
>