The voting on technical board members is now closed.
The votes have been counted:
Raphael Coeffic: 7 votes
Stefan Sayer: 8 votes
Jan Janak: 13 votes
Andrei Pelinescu-Onciul: 13 votes
N. (Arcdiv.com): 1 vote
Martin Hoffmann: 7 votes
Greger Viken Teigre: 14 votes
Hendrik Scholz: 5 votes
The confirmed members of the technical board for the term starting June
15, 2007 and ending May 31, 2009 are:
Jan Janak, Andrei Pelinescu-Onciul, Greger Viken Teigre, and Stefan Sayer.
We have a tie between Raphael Coeffic and Martin Hoffmann on 7 votes
each. We don't really have described the rules for how to handle a tie.
Any suggestions?
g-)
Hello,
I'm facing some error when trying to configure dynamic imap url in my ser.cfg
I've got stuck in avpops module.
below is my configuration:
avp_write("imap://$to:vmailuser@pcr.ac.id:143/INBOX", "$mailbox_url");
but when I saw the debug of SEMS, the P-Mailbox-URL just recognize the "$to" as string. How to manipulate the line to get the destination uri?
The other problem shown in the debugs are:
(4979) ERROR: Ivr-Python: ********** Ivr-Python exception report ****************
(4979) ERROR: Ivr-Python: <type 'exceptions.TypeError'> raised: descriptor '__init__' requires a 'exceptions.Exception' object but received a 'str'
(4979) ERROR: Ivr-Python: File '/usr/local/lib/sems/ivr/imap_mailbox/MailboxURL.py': line 9
(4979) ERROR: Ivr-Python: , line 33
(4979) ERROR: Ivr-Python: , line 27
(4979) ERROR: Ivr-Python: File './imap_mailbox/imap4ext.py': line 122
(4979) ERROR: Ivr-Python: File '/usr/local/lib/sems/ivr/mailbox.py': line 19
(4979) ERROR: Ivr-Python: ********** end of Ivr-Python exception report *********
I leave the following line like the original in MailboxURL.py
url = ""
user = ""
passwd = ""
host = ""
port = 0
path = ""
Please tell me what to configure to get the mailbox/mailbox_query run. Really hope the answer. Thanx before.
GBU
Regards,
Meidiana
---------------------------------
Building a website is a piece of cake.
Yahoo! Small Business gives you all the tools to get online.
Hi!
I have added xmpp module to my system and change my config file
operser.cfg and now I get an error that I can´t resolve, I don't
really know which is the problem.
If anyone can have a look at it, I would be very pleased.
Thanks a lot,
Izortze.
#:/usr/local/etc/openser# openser -f openser.cfg
0(25922) parse error (141,2-3): syntax error
0(25922) ERROR: cfg. parser: unexpected EOF in unclosed string
ERROR: bad config file (1 errors)
0(25922) INFO:mi_fifo:mi_destroy:memory for the child's mi_fifo_pid
was not allocated -> nothing to destroy
# $Id: openser.cfg 1676 2007-02-21 13:16:34Z bogdan_iancu $
#
# ----------- global configuration parameters ------------------------
debug=3 # debug level (cmd line: -dddddddddd)
fork=yes
#log_stderror=no # (cmd line: -E)
children=4
# Uncomment these lines to enter debugging mode
#fork=no
log_stderror=yes
#
check_via=no
rev_dns=no
dns=no
port=5060
#fifo='/tmp/openser_fifo'
# ------------------ module loading ----------------------------------
#set module path
mpath="/usr/local/lib/openser/modules/"
# Uncomment this if you want to use SQL database
loadmodule "mysql.so"
loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "maxfwd.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
loadmodule "textops.so"
loadmodule "mi_fifo.so"
loadmodule "xmpp.so"
# ----------------- setting module-specific parameters ---------------
# -- mi_fifo params --
modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")
# -- 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)
#-- xmpp module parameters --
modparam("xmpp","domain_separator","*")
modparam("xmpp","gateway_domain","sip-xmpp.openser.org")
modparam("xmpp","xmpp_domain","xmpp-sip.openser.org")
modparam("xmpp","xmpp_password","ormazabal")
modparam("xmpp","xmpp_host","xmpp.openser.org")
modparam("xmpp","backend","component")
#modparam("xmm","xmpp_port","5347")
# ------------------------- 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(uri=~"sip:.+@sip-xmpp\.openser\.org"){
#absorb retransmisions
if(!t_newtran()){
sl_reply_error();
return;
}
#handle IM
if(method == "MESSAGE"){
log("*** xmpp-handled MESSAGE message.\n");
if(xmpp_send_message()){
t_reply("200","Accepted");
}else {
t_reply("404","Not found);
}
return;
}
#unsupported type of SIP message
log("*** xmpp unhandled message type.\n");
t_reply("503", "Service unavailable");
return;
}
else {
# 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("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)
if (uri==myself) {
if (method=="REGISTER") {
# Uncomment this if you want to use
digest authentication
#if (!www_authorize
("openser.org", "subscriber")) {
# www_challenge
("openser.org", "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");
};
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;
}
It seems that I solved the problem by using record_route_preset("my.domain.net");
Now the message flow is correct.
I don't know why does it make a difference if I use the domain name (which will be resolved to public ip address) or the actual ip address. Every suggestion will be appreciated.
Best regards,
Maciej Kowalski
---- Wiadomość Oryginalna ----
Od: Maciek Kowalski <macius_13(a)o2.pl>
Do: users(a)openser.org
Data: 13 czerwca 2007 13:33
Temat: Re: Re: [Users] 200OK Contact header field.
> Thanks for a quick response.
> I'm sorry but I've messed up a little bit.
> I've got 2 asterisks and the one I've mentioned is on the same box as Openser.(Openser 192.168.1.2:5060, Asterisk 192.168.1.2:5065)
> Openser acually "record_route" the Invite but it puts there his private address (192.168.1.2). I presume that's why the user behind different NAT cannot reach it.
> I've tried record_route_preset(""); with public IP of NAT where openser is, and in that configuration, ACK reaches Openser but it loops and is not forwarded to 192.168.1.2:5065 (Asterisk).RURI in this ACK is "sth@192.168.1.2:5065", and Openser listens on port 5060 so I dont understand why it behaves this way.
>
> What do You suggest?
>
> Thanks in advance and sorry once more for this mess.I hope what I write is still clear.
>
> ---- Wiadomość Oryginalna ----
> Od: Klaus Darilion <klaus.mailinglists(a)pernau.at>
> Do: Maciek Kowalski <macius_13(a)o2.pl>
> Kopia do: users(a)openser.org
> Data: 13 czerwca 2007 13:11
> Temat: Re: [Users] 200OK Contact header field.
>
> > You are right. If record_route is used the ACK should be sent to openser
> > first. Thus, inspect the 200 ok received by the client if the record
> > route header present, and inspect the ACK sent from the client if a
> > Route header with the content of the record_route header is present.
> >
> > btw: which client do you use? There are dozens of buggy sip clients out
> > there.
> >
> > regards
> > klaus
> >
> > Maciek Kowalski wrote:
> > > Hello All,
> > >
> > > I have a problem with transactions rewrited to asterisk.
> > > In my configuration asterisk and openser are behind NAT on a Local Network.(Openser- 192.168.1.2, Asterisk 192.168.1.5)
> > > When a User who is behind different NAT(different LAN) sends an Invite which is then rewrited to Asterisk with (rewritehostport("192.168.1.5:5060");) everything works great till asterisk answers with 200OK. In this message the Contact header field is set to "192.168.1.5:5060". When user recieves this 200OK it sends ACK to IPaddress 192.168.1.5 (and since he is behind different NAT..the message goes nowhere).
> > > Since the Initial Invite in this transaction is "record_routed" by Openser I thought that the ACK should first go through Openser.
> > > Please corect me if Im wrong, and if possible, suggest some solution.
> > >
> > > Best Regards,
> > >
> > > Maciej Kowalski
> > >
> > > _______________________________________________
> > > 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
Hi,
For a basic call, when the UAS does not send a 200 within approx 4
seconds, the OpenSER has a timer fire and sends a 408 to the UAC and a
Cancel to the UAS. This only allows one ring on the terminating phone
before the call is dropped.. I'm attaching the log and Wireshark/snoop
capture file. I'll put the openser config file inline here. Please
advise:
#
# openser_vm.cfg
#
# ----------- global configuration parameters ------------------------
debug=3 # debug level (cmd line: -dddddddddd)
fork=yes
log_stderror=no # (cmd line: -E)
maxbuffer=1048576
check_via=no # (cmd. line: -v)
dns=no # (cmd. line: -r)
rev_dns=no # (cmd. line: -R)
#reply_to_via=1
children=32
log_facility=LOG_LOCAL5
dns_use_search_list=no
dns_servers_no=1
user="sipproxy"
group="sipproxy"
# Local IP address/port pairs to listen to
# Set the following IP addresses to the value of the local e1000g0 interface
listen=udp:65.185.233.55:5061
listen=udp:65.185.233.55:5062
# Alias IP address/port pair values will be in the Req URI when the
# OpenSER is being load balanced with a BIG IP server
# Set the IP address to the value of the associated blade
# of the BIG IP that is load balancing for the SIP Proxy server.
alias=65.185.233.104:5061
alias=65.185.233.104:5062
# LOAD OpenSER MODULES
mpath="/sw/lib/openser/modules/"
loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "maxfwd.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
loadmodule "textops.so"
loadmodule "acc.so"
loadmodule "mi_fifo.so"
loadmodule "enum.so"
loadmodule "perl.so"
loadmodule "xlog.so"
# ----------------- setting module-specific parameters ---------------
# -- usrloc params --
modparam("usrloc", "db_mode", 0)
# -- rr params --
# add value to ;lr param to make some broken UAs happy
modparam("rr", "enable_full_lr", 1)
# ------------------------- request routing logic -------------------
modparam("acc", "log_level", 2)
modparam("acc", "log_flag", 1)
modparam("acc","report_cancels", 1)
modparam("acc","failed_transaction_flag", 1)
modparam("acc","log_extra", "req_uri=$rU")
modparam("tm", "fr_timer", 2)
modparam("tm","fr_inv_timer",4)
modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")
modparam("perl", "filename",
"/sw/lib/openser/perl/openser_twc_sip_proxy_3.0.pl")
# 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) {
route(1);
};
if (method=="OPTIONS") {
sl_send_reply("200", "OK");
exit;
}
##############################################################
# TWC: dst_port 5062 indicates Message Waiting Indicator
##############################################################
if (dst_port==5062 && method=="NOTIFY") {
xlog("L_DBG", "TWC: received incoming message:\n <$mb>\n");
perl_exec("twc_proc_vm_mwi");
if ($rc==-1) {
log("TWC: COULD NOT PARSE THE MWI TRIGGER");
sl_send_reply("400", "Bad Request");
exit;
}
# The enum_query() call will form an ENUM (NAPTR DNS) request from
# the user part of the Req URI and the passed MWI server and send
# it to the ENUM server defined in resolv.conf.
enum_query("mwi.ex.e164.rr.com");
if ($rc==1) {
log("MWI ENUM QUERY SUCCEEDED");
setflag(1);
route(1);
} else {
log("MWI ENUM QUERY FAILED");
sl_send_reply("404", "Not Found");
exit;
}
}
##############################################################
# TWC: dst_port 5061 indicates VM Outbound dial trigger
##############################################################
if (dst_port==5061 && method=="INVITE") {
xlog("L_DBG", "TWC: received incoming message:\n <$mb>\n");
perl_exec("twc_proc_vm_outdial");
if ($rc==-1) {
log("TWC: COULD NOT PARSE THE VM OUTDIAL TRIGGER");
sl_send_reply("400", "Bad Request");
exit;
}
# The enum_query() call will form an ENUM (NAPTR DNS) request from
# the user part of the Req URI and the passed VMO server and send
# it to the ENUM server defined in resolv.conf.
enum_query("vmo.ex.e164.rr.com");
if ($rc==1) {
log("VMO ENUM QUERY SUCCEEDED");
setflag(1);
# Use pseudo vars to set REQ URI User to the original
Req URI User
$rU = $oU;
route(1);
} else {
log("ENUM QUERY FAILED");
sl_send_reply("404", "Not Found");
exit;
}
}
}
#####################################################
# Default Message Handler
#####################################################
route[1] {
# Send it out now; use stateful forwarding as it works reliably
# even for UDP2TCP
if (!t_relay()) {
sl_reply_error();
};
exit;
}
Hi to All,
I've successfull installed ser with mysql support on my RedHat Server.
When I try to start ser I've the follow error message:
0(0) new_connection(): Client does not support authentication protocol
requested by server; consider upgrading MySQL client*
I have follow the suggestion posted in the list, as:
> *root at ubuntu:/usr/local/sbin # 0(0) new_connection(): Client does not
> support authentication protocol requested by server; consider upgrading
> MySQL client*
>
http://dev.mysql.com/doc/refman/5.0/en/old-client.html
But error remains. Any suggestions about??
ps Yes, on my slackware test pc, following that no problems was found!!
-
********************************
* (o< ing. Patria Flavio
* //\ phone 0823451358
* V_/_ mobile 3407873357
*
********************************
Hi Julia,
Please send output generated by
enroll.sh osptestserver.transnexus.com
Regards,
Dmitry
> hi,
> has somebody tried to enroll ser osp module with a peering server? I use
> this howto
>
(http://sourceforge.net/docman/display_doc.php?docid=43221&group_id=187299)
but
> I cannot find the three required crypto files (localcert.pem,
pkey.pem and
> cacert_#.pem). I hope somebody can help me! I use ser in version 0.9.6.
> Kind regards,
> Julia
