Hi Nhadie.
I'm using the autoprovisioning system with PAP2 and Sipura. I don't
know if the other phones have this feature. I also know that SJPhone can
have this feaure too.
Regards,
Ricardo Martinez.-
> -----Mensaje original-----
> De: Nhadie [mailto:nhadie@cbcpworld.com]
> Enviado el: Jueves, 08 de Septiembre de 2005 10:43
> Para: serusers(a)lists.iptel.org
> Asunto: [Serusers] auto configuration
>
>
> Hi List!
>
> Would just like to ask how can I automatically download a
> configuration for
> a SIP phone. I mean , let's say I have a client that bought
> the phone, once
> he plugged it in on the internet it will download a
> configuration file, that
> has it's username, password, sip proxy etc. I use
> Grandstream, PAP2, Sipura,
> x-lite x-pro and eyebeam. Is that possible?
>
> Thank You
>
> Regards,
> Nhadie
>
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
HI, I'm using Debian Linux(while I have no idea how to check its version), and running SER on my PC.
I installed MySQL 4.1.14 and SER 0.9.4, chmoded the /tmp directory to 777, and the MySQL server runs well.
But when I start SER, it does not run and leaves some error message in syslog like this:
--------------------------------------------------------------------------------------------
Oct 10 14:31:03 Serverhost /usr/sbin/ser[6525]: Maxfwd module- initializing
Oct 10 14:31:03 Serverhost /usr/sbin/ser[6525]: new_connection(): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Oct 10 14:31:03 Serverhost /usr/sbin/ser[6525]: db_init(): Could not create a connection
Oct 10 14:31:03 Serverhost /usr/sbin/ser[6525]: ERROR: auth_db_ver: unable to open database connection
Oct 10 14:31:03 Serverhost /usr/sbin/ser[6525]: auth_db:str_fixup(): Error while querying table version
Oct 10 14:31:03 Serverhost /usr/sbin/ser[6525]: ERROR: fix_expr : fix_actions error
--------------------------------------------------------------------------------------------
The file /var/run/mysqld/mysqld.sock doest not exist, but the MySQL still runs well. I also don't know if it is correct.
Does anyone know how to resolve this? Thank you!
ser.cfg, "gulab.twbbs.org" is my domain.
--------------------------------------------------------------------------------------------
#
# $Id: ser.cfg,v 1.25.2.1 2005/02/18 14:30:44 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)
/* 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"
# ------------------ 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"
loadmodule "/usr/lib/ser/modules/textops.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 --
# 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 >= 2048 ) {
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=~"gulab.twbbs.org") {
if (method=="REGISTER") {
# Uncomment this if you want to use digest authentication
if (!www_authorize("gulab.twbbs.org", "subscriber")) {
www_challenge("gulab.twbbs.org", "0");
break;
};
save("location");
break;
};
lookup("aliases");
if (!uri==myself) {
append_hf("P-hint: outbound alias\r\n");
route(1);
break;
};
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();
};
}
--------------------------------------------------------------------------------------------
my.cnf
--------------------------------------------------------------------------------------------
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "/var/lib/mysql/my.cnf" to set server-specific options or
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
# Here is entries for some specific programs
# The following values assume you have at least 32M ram
# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0
[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
language = /usr/share/mysql/english
skip-external-locking
#
# For compatibility to other Debian packages that still use
# libmysqlclient10 and libmysqlclient12.
old_passwords = 1
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1
#
# * Fine Tuning
#
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 128K
#
# * Query Cache Configuration
#
query_cache_limit = 1048576
query_cache_size = 16777216
query_cache_type = 1
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log = /var/log/mysql.log
#log = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement :)
#
# Here you can see queries with especially long duration
#log-slow-queries = /var/log/mysql/mysql-slow.log
#
# The following can be used as easy to replay backup logs or for replication.
#server-id = 1
log-bin = /var/log/mysql/mysql-bin.log
# See /etc/mysql/debian-log-rotate.conf for the number of files kept.
max_binlog_size = 104857600
#binlog-do-db = include_database_name
#binlog-ignore-db = include_database_name
#
# * BerkeleyDB
#
# According to an MySQL employee the use of BerkeleyDB is now discouraged
# and support for it will probably cease in the next versions.
skip-bdb
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# If you want to enable SSL support (recommended) read the manual or my
# HOWTO in /usr/share/doc/mysql-server/SSL-MINI-HOWTO.txt.gz
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
[mysql]
#no-auto-rehash # faster start of mysql but no tab completition
[isamchk]
key_buffer = 16M
#
# * NDB Cluster
#
# See /usr/share/doc/mysql-server-*/README.Debian for more information.
#
# The following configuration is read by the ndbd storage daemons,
# not from the ndb_mgmd management daemon.
#
# [MYSQL_CLUSTER]
# ndb-connectstring=127.0.0.1
--------------------------------------------------------------------------------------------
Hi,
I have been testing 'DNS SRV', backup server and t_replicate with
two 'ser'servers, BT101(firmware:1.0.7.11), and two GXP2000s(1.0.1.9).
The t_replicate works fine between sip1(main) and sip2(backup) servers.
Then, I stopped 'ser' on sip1 server, three UAs sent REGISTERs not to
sip1 but to sip2. I tested make calls between three UAs, sip2 took care
of sip calls, worked fine.
After that, I restarted 'ser' on sip1. But the three UAs still send
REGISTER to sip2, eventhough sip1 came back and became alive.
I set up 5 minutes intervals for these theree UAs for REGISTER.
So, I stopped 'ser' on sip2 for 10-15 minutes, three UAs sent REGISTERs
to sip1 again and tryed to 't_replicate' to sip2, these were failed
as 'destination unreachable'.
Then I restarted 'ser' on sip2 again. After REGISTERed on sip1, t_replicate
send REGISTERs from sip1 to sip2. Now, everything works fine.
Is this server side opration normal? Or these UAs are still bad boys?
Regards,
Zen
Hello everybody,
the new stable release is scheduled for next Friday, October 28.
It will be versioned *1.0.0* instead of 0.10.0 since mandatory
requirements of RFC are in place (the last major one, TLS is now in the
trunk) and a lot of new features have been introduced.
The release was postponed several time to allow more time for testing.
There is no known bug at this moment that is not going to be fixed
before release (the last one, reported by Klaus causing memory leak for
CANCEL transactions in failure routes has been localized and expect to
have it fixed tomorrow on CVS).
Until Friday, remaining docs should be updated and relevant documents
(changelog, new features, deprecated stuff) have to be written. We have
to ask people willing to generate packages for different architecture to
give some help since we do not have access to all OS distributions. We
can provide guidelines for those that need them.
If you are aware of some things that are missing for this release,
please report them to devel(a)openser.org
Cheers,
Daniel
Hi,
I want to use openser as proxy/registrar with Asterisk. Users will exist
both in openser's subscriber database and in asterisk's sip friends.
I have this kind of working, but have a few questions.
Currently openser authenticates users fine, and will route to * for pstn
and asterisk will accept the call if I have openser set up in * sip.conf
as a proxy.
I would rather, however, that the user gets authenticated as themselves
on asterisk, rather than the call happening as the proxy user. without
openser set up in asterisk, I get continual 407 Proxy Authentication
required.
Additionally, it appears that the call is still routing through openser,
rather than being directly between the client and asterisk.
Questions:
1. How can I set it up so that when a call gets sent to * that
authentication takes place directly between asterisk and the client
2. How should I be sending the call from openser so that the rest of the
call is directly between asterisk and the client?
Any working configs would be welcome - these seem to be hard to come by.
Thanks.
--
-Barry Flanagan
I have in my name server the lines:
trace-intl.net:
_sip._udp.trace-intl.net. IN SRV 20 0 5062
dns.trace-int.net.
trace-intl.net-internal:
_sip._udp IN SRV 20 0 5062 voip
but on the same machine another domain runs with the same lines for port
5060
My intention was to use trace-intl.net for Openser on 5062, while
Asterisk rmains on 5060.
It seems, that this lines convert all tries to connect at 5062 to
connect to 5060. Could that be?
I have now disabled the lines ( _sip._udp ....) for Asterisk, but still
receive the error:
Oct 25 08:17:36 viop2 /usr/local/sbin/openser[9142]: Maxfwd module-
initializing
Oct 25 08:17:36 viop2 /usr/local/sbin/openser[9142]: ERROR: udp_init:
bind(5, 0x622a04, 16) on 127.0.0.1: Address already in use
How can I solve that?
bye
Ronald Wiplinger
Hi,
I like to use SER for distribute calls on multiple PSTN gateways. In a
first step I just have two gateways and need SER to do some load
balancing. AFAIK previous SER versions came with a load balancing
module. What are the current options to do this (beside some kind of
suffix routing)?
Regards,
Stefan
Wondering what the school of thought it about the number the children that
should be specified given a statefull configuration with approx 300 users
with expiration of 60 sec and nat_ping of 30sec and
modparam("usrloc|domain", "db_mode", 1) with postgres and any other related
tweaks.
Thanks
