messa(a)innsof.com wrote:
> Hi Klaus
>
> this command does not work for me!
> but, my openser works with those errors!
You have to install the "ngrep" application. E.g. "apt-get install
ngrep" if you are using debian based distros.
klaus
>
> bests regards!
> Serge
>
>
>
>
>>looks like a bad formated SIP message.
>>
>>Post the SIP signaling dump (ngrep -t -W byline port 5060)
>>
>>klaus
>>
>>messa(a)innsof.com wrote:
>>
>>>Hi all
>>>
>>> When imake calls, signalisation goes well but, when, i hang up my
>>>client, i have no voice in any client!
>>>And my openser server display methese errors:
>>>
>>>0(4335) lookup(): Error while extracting address of record
>>> 0(4335) ERROR: parse_uri: uri too short: <sip:> (4)
>>> 0(4335) ERROR: parse_sip_msg_uri: bad uri <sip:>
>>> 0(4335) WARNING: do_action:error in expression
>>> 0(4335) ERROR: parse_uri: uri too short: <sip:> (4)
>>> 0(4335) extract_aor(): Error while parsing Address of Record
>>> 0(4335) lookup(): Error while extracting address of record
>>> 0(4335) Warning: sl_send_reply: I won't send a reply for ACK!!
>>> 0(4335) force_rtp_proxy2: incorrect port in reply from rtp proxy
>>> 0(4335) force_rtp_proxy2: incorrect port in reply from rtp proxy
>>> 0(4335) force_rtp_proxy2: incorrect port in reply from rtp proxy
>>> 0(4335) force_rtp_proxy2: incorrect port in reply from rtp proxy
>>> 0(4335) force_rtp_proxy2: incorrect port in reply from rtp proxy
>>> 0(4335) force_rtp_proxy2: incorrect port in reply from rtp proxy
>>> 0(4335) ERROR: parse_uri: uri too short: <sip:> (4)
>>> 0(4335) ERROR: parse_sip_msg_uri: bad uri <sip:>
>>> 0(4335) loose_route: Error while parsing Request URI
>>> 0(4335) ERROR: parse_uri: uri too short: <sip:> (4)
>>> 0(4335) ERROR: parse_sip_msg_uri: bad uri <sip:>
>>> 0(4335) WARNING: do_action:error in expression
>>> 0(4335) ERROR: parse_uri: uri too short: <sip:> (4)
>>> 0(4335) extract_aor(): Error while parsing Address of Record
>>> 0(4335) lookup(): Error while extracting address of record
>>> 0(4335) ERROR: parse_uri: uri too short: <sip:> (4)
>>> 0(4335) ERROR: parse_sip_msg_uri: bad uri <sip:>
>>> 0(4335) WARNING: do_action:error in expression
>>> 0(4335) ERROR: parse_uri: uri too short: <sip:> (4)
>>> 0(4335) extract_aor(): Error while parsing Address of Record
>>> 0(4335) lookup(): Error while extracting address of record
>>> 0(4335) force_rtp_proxy2: incorrect port in reply from rtp proxy
>>> 0(4335) force_rtp_proxy2: incorrect port in reply from rtp proxy
>>>
>>>How can i fix those errors?
>>> Thanks for help
>>> Serge
>>>
>>>
>>>_______________________________________________
>>>Users mailing list
>>>Users(a)openser.org
>>>http://openser.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>
>>
>
>
>
Can Anyone tell me is it possible to route calls based on from_uri with the LCR Module??
I see the from_uri field but I have tried using %(a)192.168.1.1 & 192.168.1.1
I replaced 192 address with an actual IP of another SER box that is Trusted. No matter
what I put in there it still routes to the % only group. Even when I dial the prefix related
to that entry.
Eric
hi everyone,
I was just trying to transfer the call to another user. All users are registered at the same openser server. Now when I receive a call, is it not possible to transfer the call to another IP user.
I thought REFER mehtod does this, but i think I am wrong. Is this possible, can somebody pls clear my understanding regarding this concept.
thanks in advance!!
jayesh
---------------------------------
Enjoy this Diwali with Y! India Click here
I'm new to SER and was wondering how are people offering music on
hold with it. Is it possible? Is the solution simply to send the call
to Asterisk? What about SEMS? Does it offer music on hold?
Thanks,
Waldo
Thanks for the info! :-) If I do not succeed in getting around this
hairpinning issue, I'll have to replace my Netgear gateway with one of
these.
On Mon, 2005-12-05 at 12:29 -0500, sip wrote:
> On Mon, 05 Dec 2005 11:59:18 +0200, Jan Henkins wrote
> > Hello all,
> >
> > On Sun, 2005-12-04 at 18:13 -0500, sip wrote:
> >
> > > If the gateway has no issues with hairpinning, then yes, it's quite possible.
> > > I use a Linksys gateway at home and a slightly older, pre-sip-proxy version
> > > of Astaro linux firewall at work, and we have multiple UAs behind each in the
> > > NAT space of our firewall. They can call each other. They can all outside. All
> > > based off registrations with a SER server on the outside of the network.
> >
> > Could you perhaps tell me the model number of your Linksys gateway?
> >
>
> I'm using a Linksys WRT54G (not sure which series). It's got the latest
> Linksys firmware on it (if that makes any difference).
>
> N.
--
Regards,
Jan Henkins
I become crazy to realize a serial forking.
I try to use load_contacts() and next_contscts().
This is my openser.cfg nd my location table:
In teory when I call 309(a)192.168.9.98 the location with the q value
equal to 0.80 it is the first but it is processed only the location
309(a)192.168.9.131.
Help!!!
#
# $Id: openser.cfg,v 1.5 2005/10/28 19:45:33 bogdan_iancu Exp $
#
# simple quick-start config script
#
# ----------- global configuration parameters ------------------------
debug=3 # debug level (cmd line: -dddddddddd)
fork=yes
log_stderror=yes # (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: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"
loadmodule "/usr/local/lib/openser/modules/avpops.so"
loadmodule "/usr/local/lib/openser/modules/xlog.so"
loadmodule "/usr/local/lib/openser/modules/lcr.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("registrar", "append_branches", 1)
#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)
modparam("usrloc","db_url","mysql://openser:heslo@127.0.0.1/openser")
modparam("auth_db","db_url","mysql://openser:heslo@127.0.0.1/openser")
modparam("lcr","db_url","mysql://openser:heslo@127.0.0.1/openser")
modparam("avpops","avp_url","mysql://openser:heslo@127.0.0.1/openser")
modparam("avpops","avp_table","usr_preferences")
modparam("tm", "fr_timer", 8)
modparam("tm", "fr_inv_timer", 10)
modparam("tm", "wt_timer", 5)
#modparam("avpops","avp_aliases","fwdbusy=i:665")
# ------------------------- 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;
};
if (method =="INVITE" && uri =~"^sip:0[0-9]*@*"){
log(1, "Check 1 Start PSTN Call\n");
rewritehostport("192.168.9.97:5061");
t_relay();
exit;
}
if (method == "CANCEL"){
t_relay();
}
if (method =="BYE"){
t_relay();
}
# 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("create-net.it", "subscriber")) {
www_challenge("create-net.it", "0");
exit;
};
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 (!lookup("location")) {
sl_send_reply("404", "Not Found");
exit;
};
append_hf("P-hint: usrloc applied\r\n");
};
if(load_contacts()){
xlog("L_ERR","LOAD CONTACTS!\n");
}
xlog("L_ERR","CONTACT <$ru> !\n");
t_on_failure("1");
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;
}
failure_route[1] {
if (next_contacts()) {
xlog("L_ERR","NEXT CONTACT <$ru> !\n");
append_branch();
t_relay();
}
else {
xlog("L_ERR","ERROR!\n");
}
}
This is my location table
============================================================
username | domain | contact | q
400 | | sip:400@192.168.9.193 | 1.00
308 | | sip:308@192.168.9.181:5060 | 1.00
309 | | sip:309@192.168.9.131;transport=udp | 1.00
309 | | sip:400@192.168.9.97 | 0.80
--
=======================================
Matteo Piazza, Junior Researcher
CREATE-NET
Via Solteri, 38 - 38100 Trento - Italy
email: matteo.piazza(a)create-net.it
Tel: +39-0461-408400ext:308
www.create-net.it
=======================================
Yesterday I upgraded the version of the operating system of our sip
server from OpenBSD amd64 3.7 to 3.8.
Now I noticed that domain name lookups seems to don't work anymore and
the INVITES are replyed with 478.
Here is an example of the logs:
Dec 5 13:11:03 eowyn OpenSER[15740]: ERROR: mk_proxy: could not resolve
hostname: "voip.eutelia.it"
Dec 5 13:11:03 eowyn OpenSER[15740]: ERROR: uri2proxy: bad host name in
URI <sip:800900800@voip.eutelia.it:5060;user=phone>
Dec 5 13:11:03 eowyn OpenSER[15740]: ERROR:tm:t_forward_nonack: failure
to add branches
Obviously "voip.eutelia.it" is resolved by dig on the same machine.
Anybody had the same problem?
Thanks.
--
___________________________________________________
__
|- giannici(a)neomedia.it
|ederico Giannici http://www.neomedia.it
___________________________________________________
Hi again
That's the way SER send the information to the RADIUS server, using Digest
attributes.
Regarding to the "not readable outputs" i don't know why that happen to you,
in my case i use RADIATOR and i can read the Digest attributes without any
problem. What RADIUS server are you using?
Ricardo.-
-----Mensaje original-----
De: Sait Karalar [mailto:saitkaralar@gmail.com]
Enviado el: Lunes, 05 de Diciembre de 2005 11:06
Para: Ricardo Martinez
Asunto: Re: [Serusers] SER + Radius
Hi,
I read that tutorial, but when I send REGISTER request to the radius,
I got some un-readable chars only.
I expect SIP-Auth-Name or SER-Auth-Name, got instead
Digest-Auth-Name etc... Digest-XXXX 's. and values are really not readable
outputs. just some chars.
so, I send this mail to get more information.
:)
thanks.
On 12/5/05, Ricardo Martinez < rmartinez(a)redvoiss.net
<mailto:rmartinez@redvoiss.net> > wrote:
Hello
There is a RADIUS HOW TO somwhere in the website www.iptel.org
<http://www.iptel.org/> , you can authenticate SIP users via RADIUS, and do
accounting also.
About managing routes, maybe you can try LCR module, but it works only
through a mysql local database, perhaps you can try do somethign with the
AVP_RADIUS module...
Good Luck
Ricardo.-
-----Mensaje original-----
De: Sait Karalar [mailto: <mailto:saitkaralar@gmail.com>
saitkaralar(a)gmail.com]
Enviado el: Sábado, 03 de Diciembre de 2005 8:59
Para: serusers(a)lists.iptel.org <mailto:serusers@lists.iptel.org>
Asunto: [Serusers] SER + Radius
Hi list,
I am so new to list SER.
I just tried to
I want to authenticate SIP users via RADIUS and want accounting with radius.
also if possible, ask route to radius also.
but I did not manage it ;(
any simple sample? I read documents etc. no good sample found.
--
gMail : google mail
Try it! It is the best
http://www.gmail.com <http://www.gmail.com/>
--
gMail : google mail
Try it! It is the best
http://www.gmail.com <http://www.gmail.com>
