Hi all,
Openser works pretty well as Presence Server, but on this development stage (version 1.2.x) the communication with XCAP Server is done via mysql (xcap_xml table). The integration with XCAP-Lite works this way and works Ok.
However, SER has a library with XCAP-Client interface and we have started an integration of that library on the presence module of Openser. With this standard approach becomes possible the integration of the Openser Presence Server with, not only the XCAP-Lite, but also with others XCAP Servers, e.g., OpenXDM (https://openxdm.dev.java.net/).
To have this integration accomplish get into the following steps:
Libxcap Instalation:
tar xvzf ser-2.0.0+cvs20070315_src.tar.gz
cd ser-2.0.0+cvs20070315/lib/cds/
make install
cd ../xcap/
make install
export LD_LIBRARY_PATH=/usr/local/lib ( execute before starting openser)
Run the attached patch:
cd openser-1.2.x (openser's root)
cp ../xcap_interface.diff . (Copy the patch to openser's root)
patch -p1 <xcap_interface.diff (apply the patch )
Compile Openser, or if it is already compilied, just compile and install the presence module:
make modules=modules/presence modules
cp modules/presence/presence.so /usr/local/lib/openser/modules/
Add the XCAP configuration parameters on the Openser configuration file (openser.cfg):
"...
modparam("presence", "xcap_server", "http://x.x.x.x")
modparam("presence", "xcap_root", "xcap-root")
modparam("presence", "xcap_app_usage", "org.openmobilealliance.pres-rules")
modparam("presence", "xcap_document_name", "presrules")
modparam("presence", "xcap_auth_username", "openser")
modparam("presence", "xcap_auth_password", "openserrw")
..."
The integration was done with the following versions:
openser-1.2.x-svn-20070517-221101.tgz (http://www.openser.org/downloads/snapshots/openser-1.2.x/)
ser-2.0.0+cvs20070315_src.tar.gz (http://ftp.iptel.org/pub/ser/daily-snapshots/testing/)
With this modification, when the Presence Servers need to consult a client's pres-rules it can do a XCAP Get instead of a MySql Query.
This approach is closer to the OMA Presence SIMPLE + OMA XDM standards.
Try it, test it and give us some feedback about it. If you have difficulties on the installation or configuration please contact us.
Best Regards,
Toni
Hey everyone,
After quite a bit of google digging I've came across Dimitry's mail that
cleared up
some things that weren't so obvious in the documentation of the ACC module.
He gave the example of using the following code:
modparam("acc", "radius_extra",
"Sip-UA=$hdr(User-Agent);Sip-Via=$hdr(Via[*]); Sip-SDP=$rb")
Which in his case makes use of the Sip-UA, Sip-Via and Sip-SDP attributes
but in the dictionary.sip file
provided with openser/radiusclient-ng these attribute aren't present, there
are other sets of attributes
but not these... And so, I tried adding myself some custom attributes to
both dictionary files,
the one on the freeradius server and the other on openser's radiusclient-ng
server and tried for example this:
ATTRIBUTE Sip-Src-IP 900 string
ATTRIBUTE Sip-Src-Port 901 string
ATTRIBUTE Sip-Hdr-Contact 902 string
ATTRIBUTE Sip-Hdr-UA 903 string
ATTRIBUTE Sip-Hdr-From 904 string
ATTRIBUTE Sip-Hdr-Media 905 string
And then I put in openser's cfg:
modparam("acc", "radius_extra", "Sip-Src-IP=$si")
But it doesn't work, the accounting record on the freeradius server doesn't
show the Sip-Src-IP attribute.
If I change the modparam to use Sip-User-Realm which is defined in the
original dictionary.sip on both
servers then THAT IS added to the accounting record... my question is why?
And the second question, is there a more extensive dictionary.sip file?
How is it possible to add my own custom attributes as well?
Thanks,
Liri.
> -----Original Message-----
> From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at]
> Sent: Monday, June 25, 2007 9:28 AM
> To: Papadopoulos Georgios
> Cc: Bogdan-Andrei Iancu; users(a)openser.org
> Subject: Re: [OpenSER-Users] RE: [Users] out of memory - please help
>
>
>
> Papadopoulos Georgios wrote:
> > Why did this only appear on the first receiver child? I
> would expect
> > that all children receive an equal amount of traffic so they should
> > all run out of memory more or less at the same time. Except
> if when a
> > message is received, Openser finds the first available
> child and does
> > this by trying child 1,2,3... Is this the case?
>
> The distribution between the UDP listener threads is not done
> by openser but by the OS. openser will open port 5060 and
> then fork the process "children=..." times. Then, all
> processes will read from the same port.
>
Then how do you explain that only the first child ran out of memory?
Disclaimer
The information in this e-mail and any attachments is confidential. It is intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, or person responsible for delivering this information to the intended recipient, please notify the sender immediately. Unless you are the intended recipient or his/her representative you are not authorized to, and must not, read, copy, distribute, use or retain this message or any part of it. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
Here it is.. We are trying to keep the prefix, in a header or a avp or
something..
So we want to use the prefix to log a certain gw used..
Usually calls come from A to SER to other Term boxes.
The problem is once I load_gw() then I cannot use the values.
EX: on invite I do some checking , then load_gw..
If gw is box X.. then we add a prefix 2312 lets say.
Upon reply I cannot get that value back even in $ruri
Although I can set anything in the invite before leaving .
Also tried add_rr_param but no go..
Any ideas ?
Basically on :
onreply_route[1] {
if(is_method("INVITE") && ($rs==183) ) {
# DO STUFF
I need to access the gateway it used from here..
}
}
Hi,
How can configure pa module in such a way that it will look for the particular user presence document in the "...pres-rules/users/user/.." instead of
"../pres-rules/users/user@domain/..".
Cheers tomasz
On 6/25/07, ram <talk2ram(a)gmail.com> wrote:
>
> Google for more information to learn
>
> any way for your disctionary
>
> Post Dialing Delay PDD
>
If the reqeust is Delay.. then can u do , redialing by using the avp
modules. This is take place on failover case...
Automatic Speech Recognition *ASR*
>
This ASR , openSER can't do ASR , u need to forward this to Asterisk or PBX
servers...
On 6/25/07, raviprakash sunkara <sunkara.raviprakash.feb14(a)gmail.com> wrote:
> >
> >
> >
> > On 6/25/07, ram <talk2ram(a)gmail.com > wrote:
> > >
> > > Hi
> > >
> > > iam using openser with mysql accounting
> > >
> > > can some one assist me how to calculate ASR and PDD
> > >
> >
> > can abbreviate the ASR and PDD .
> >
> >
> > for the calls
> > >
> > > recomend some documentation to read would be great
> > >
> > > ram
> > >
> > > _______________________________________________
> > > Users mailing list
> > > Users(a)openser.org
> > > http://openser.org/cgi-bin/mailman/listinfo/users
> > >
> > >
> >
> >
> > --
> > Thanks &Regards
> > Ravi Prakash Sunkara
>
>
>
--
Thanks &Regards
Ravi Prakash Sunkara
Hello all I have set up ser and I am able to use the sample config to get
ser running within my NAT. Now I am trying to get external users to connect
to my ser which is behind a nat device.
Whenever I use the sample config I can make calls inside my netkwork.
whenever I use the nat config that I have below. I cannot even get my local
devices to speak to each other. Can someone help here.
Whenever I start ser with this config this is what ther system does.
ser dead but subsys locked
<serusers(a)lists.iptel.org>
This is the config that I am using
# ----------- 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"
# !! Nathelper
loadmodule "/usr/lib/ser/modules/nathelper.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)
# !! Nathelper
modparam("registrar", "nat_flag", 6)
modparam("nathelper", "natping_interval", 30) # Ping interval 30 s
modparam("nathelper", "ping_nated_only", 1) # Ping only clients behind NAT
# ------------------------- 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 >= max_len ) {
sl_send_reply("513", "Message too big");
break;
};
# !! Nathelper
# Special handling for NATed clients; first, NAT test is
# executed: it looks for via!=received and RFC1918 addresses
# in Contact (may fail if line-folding is used); also,
# the received test should, if completed, should check all
# vias for rpesence of received
if (nat_uac_test("3")) {
# Allow RR-ed requests, as these may indicate that
# a NAT-enabled proxy takes care of it; unless it is
# a REGISTER
if (method == "REGISTER" || ! search("^Record-Route:")) {
log("LOG: Someone trying to register from private IP,
rewriting\n");
# This will work only for user agents that support
symmetric
# communication. We tested quite many of them and
majority is
# smart enough to be symmetric. In some phones it takes
a configuration
# option. With Cisco 7960, it is called NAT_Enable=Yes,
with kphone it is
# called "symmetric media" and "symmetric signalling".
fix_nated_contact(); # Rewrite contact with source IP of
signalling
if (method == "INVITE") {
fix_nated_sdp("1"); # Add direction=active to SDP
};
force_rport(); # Add rport parameter to topmost Via
setflag(6); # Mark as NATed
};
};
# 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==myself) {
if (method=="REGISTER") {
# Uncomment this if you want to use digest authentication
# if (!www_authorize("iptel.org", "subscriber")) {
# www_challenge("iptel.org", "0");
# break;
# };
save("location");
break;
};
lookup("aliases");
if (!uri==myself) {
append_hf("P-hint: outbound alias\r\n");
route(1);
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]
{
# !! Nathelper
if (uri=~"[@:](192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)" &&
!search("^Route:")){
sl_send_reply("479", "We don't forward to private IP
addresses");
break;
};
# if client or server know to be behind a NAT, enable relay
if (isflagset(6)) {
force_rtp_proxy();
};
# NAT processing of replies; apply to all transactions (for example,
# re-INVITEs from public to private UA are hard to identify as
# NATed at the moment of request processing); look at replies
t_on_reply("1");
# send it out now; use stateful forwarding as it works reliably
# even for UDP2TCP
if (!t_relay()) {
sl_reply_error();
};
}
# !! Nathelper
onreply_route[1] {
# NATed transaction ?
if (isflagset(6) && status =~ "(183)|2[0-9][0-9]") {
fix_nated_contact();
force_rtp_proxy();
# otherwise, is it a transaction behind a NAT and we did not
# know at time of request processing ? (RFC1918 contacts)
} else if (nat_uac_test("1")) {
fix_nated_contact();
};
}