1. Make sure openser receives the message
2. Follow how the message is routed in openser.cfg
3. Watch for error message
Thus, put xlog statements into your openser.cfg and watch them in syslog.
regards
klaus
Russ Daigle wrote:
Yes, it is listening on TCP. Fair question, though.
I know it is
listening on TCP because INVITES that I send to openSER via TCP it
actually responds properly. (Well, mostly responds properly.... there
is another email I sent about that problem.) Also, my TCP socket gets
established and II successfully send the REGISTER..... then the
connection is torn down by OpenSER with no response.
Below is the config. (No where does it specify TCP, but it also doesn't
turn it off.)
sip:~/bin/tools/openser/openser-1.1.0-tls russdaigle$ cat
/usr/local/etc/openser/openser.cfg
#
# $Id: openser.cfg,v 1.6 2006/02/15 18:23:46 bogdan_iancu Exp $
#
# simple quick-start config script
#
# ----------- global configuration parameters ------------------------
debug=9 #3 # debug level (cmd line: -dddddddddd)
/* for non debugging mode */
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/openser_fifo"
#
# uncomment the following lines for TLS support
#disable_tls = 0
#listen = tls:10.10.1.234: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"
# ----------------- 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 -------------------
On Nov 10, 2006, at 1:46 AM, Christophe Irles wrote:
Hi,
Are you sure OpenSER is listening on TCP port ? Can you provide your
openser
configuration file ?
I'm using openser 1.1.0 with both TCP and UDP and all works fine.
Christophe
-----Message d'origine-----
De : users-bounces(a)openser.org [mailto:users-bounces@openser.org] De
la part
de Russ Daigle
Envoyé : vendredi 10 novembre 2006 10:16
À : users(a)openser.org
Objet : [Users] Problems with TCP REGISTER, UDP REGISTER works fine
For some reason, I am having problems with having TCP REGISTER messages
being accepted by openser.
The following is a REGISTER I send to Open SER. It is never
responded to. Do you see anything wrong with it? It should be
registering port 5060 TCP.
00:19:42.157347 IP 10.10.2.6.50083 > 10.10.1.234.sip: tcp 345 REGISTER
sip:siptest2.com:5060 SIP/2.0^M
Via: SIP/2.0/TCP 10.10.2.6:50083;branch=z9hG4bK45^M
From: Alice <sip:alice@siptest2.com>;tag=fromhackblah^M
To: Alice <sip:alice@siptest2.com>^M
CSeq: 1 REGISTER^M
Call-ID: DNYEXXLURKQELGQLDAJXJADPKUJVSHKUZSFPYXDGQ(a)musecurity.com^M
Contact: <sip:alice@10.10.2.6>;expires=900;transport=TCP^M
Max-Forwards: 70^M
^M
When I send a similar UDP register, it works fine!
REGISTER sip:siptest2.com:5060 SIP/2.0^M
Via: SIP/2.0/UDP 10.10.2.6:5070;branch=z9hG4bK8149125^M
From: Alice <sip:alice@siptest2.com>;tag=fromhackblah^M
To: Alice <sip:alice@siptest2.com>^M
CSeq: 1 REGISTER^M
Call-ID:
PFZEHCUVOJRSHOXXOQNYONBOFKDGWUKNEWRYDJFSCTBCDJQLLNQPJUN(a)musecurity.com
Contact: <sip:alice@10.10.2.6:5070>;expires=900;transport=UDP^M
Max-Forwards: 70^M
^M
00:19:39.364079 IP 10.10.1.234.sip > 10.10.2.6.5070: UDP, length 593
SIP/2.0
200 OK^M
Via: SIP/2.0/UDP 10.10.2.6:5070;branch=z9hG4bK8149125^M
From: Alice <sip:alice@siptest2.com>;tag=fromhackblah^M
To: Alice
<sip:alice@siptest2.com>;tag=329cfeaa6ded039da25ff8cbb8668bd2.c3bf^M
CSeq: 1 REGISTER^M
Call-ID:
PFZEHCUVOJRSHOXXOQNYONBOFKDGWUKNEWRYDJFSCTBCDJQLLNQPJUN(a)musecurity.com
Contact: <sip:alice@10.10.2.6:5070>;expires=900^M
Server: OpenSer (1.1.0-notls (i386/darwin))^M
Content-Length: 0^M
Warning: 392 10.10.1.234:5060 "Noisy feedback tells: pid=11956
req_src_ip=10.10
.2.6 req_src_port=5070 in_uri=sip:siptest2.com:5060
out_uri=sip:siptest2.com:506
0 via_cnt==1"^M
^M
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users