28 Apr
2006
28 Apr
'06
2:37 p.m.
Thanks for the information.
I have both CVS and snapshot versions. Which one should I use really ?
You are welcome.
CVS version is still not documented (changed parameters of modules, new
module functions), should have some advantages like separated XCAP
module, some performance improvements (using undocumented parameters
;-)), some little bugs are corrected and some features are added
(details in ChangeLog files in module directories).
The snapshot should have documented all needed module parameters and
functions, was tested for all presence functions.
You can choose, but I recommend to use presence snapshot.
Both versions do not have xcap as module. So this
config is rejected:
modparam("xcap", "xcap_root",
"http://xcap-server.somewhere.com/xcap")
CVS version has XCAP module, really. (run "cvs update -d" needed?)
There should be directory modules/xcap in source tree. For compiling it
you have to add it to include_modules:
make install include_modules="dialog pa rls presence_b2b xcap mysql xmlrpc"
You need to call loadmodule in config file (like other modules). I
recommend to have this before loading other presence modules:
loadmodule "/usr/lib/ser/modules/xcap.so"
Vaclav
How can I do that ?
Thanks,
ilker
-----Original Message-----
From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
Sent: Friday, April 28, 2006 1:53 PM
To: ?lker Aktuna (Koç.net)
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] IM and presence problems
I found the issue with storing message. It was a
database issue.
I had used the example full configuration from presence handbook; but I didn't have
the database msilo created.
I think you should add these to the presence handbook (requirements
for modules in the example config)
Good idea! Thanks.
Now I have a problem with presence. It's not working.
Everytime I run the client, I receive the same popup saying that other client is
requesting permission to see the presence.
But even if I press "allow" each time, the other user can't see that
I'm online.
This will be problem with XCAP server. Do you have one?
If not set "auth" param of PA module to "none":
modparam("pa", "auth", "none")
If yes, take care that XCAP root given to client must be the same as XCAP root given to
XCAP module (CVS version only! presence snapshot has this as parameter to PA module):
modparam("xcap", "xcap_root",
"http://xcap-server.somewhere.com/xcap")
There is a possibility of changing the XCAP root during message processing using function
set_xcap_root (CVS version only!):
set_xcap_root("http://...");
There can be another problem - your clients might use other filename with presence rules
on XCAP server than default "presence-rules.xml". This can be changed using PA
module parameter "pres_rules_file" (CVS version
only!):
modparam("pa", "pres_rules_file",
"pres-rules.xml")
Could it be that I need to create other database or tables for presence ?
Btw, I sometimes get the following error after some PUBLISH messages:
"Warning: run_failure_handlers: no UAC support (0, 256)"
This might be (I'm not sure, you have to watch network traffic what happens
there) due to that sent notification to watcher was rejected with a 4xx response...
Vaclav
Apr 28 13:21:33 sesapp
/root/sexr/sbin/ser[26607]: MSILO: publish
offline messages for sip:200000900568888887@sip.test.net dumped Apr 28
13:21:37 sesapp /root/sexr/sbin/ser[26609]: SIP to XX: PUBLISH from:
sip:200000900568888887@sip.test.net to:
sip:200000900568888887@sip.test.net
Apr 28 13:21:40 sesapp /root/sexr/sbin/ser[26622]: Warning:
run_failure_handlers: no UAC support (0, 256) Apr 28 13:21:41 sesapp
/root/sexr/sbin/ser[26611]: SIP to XX: PUBLISH from:
sip:200000900568888887@sip.test.net to:
sip:200000900568888887@sip.test.net
Apr 28 13:21:41 sesapp /root/sexr/sbin/ser[26611]: MSILO: publish
offline messages for sip:200000900568888887@sip.test.net dumped
Thanks,
ilker
-----Original Message-----
From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
Sent: Friday, April 28, 2006 11:24 AM
To: ?lker Aktuna (Koç.net)
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] IM and presence problems
Hi.
<http://387555.sigclick.mailinfo.com/sigclick/0A090505/04064D02/0F024E02/19120131.jpg>
_____________________________________________________________________________________________________________________________________________
Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta
mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli
dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz
ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi
bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji
viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta
mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini
garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez.
This message is intended solely for the use of the individual or entity to whom it is
addressed , and may contain confidential information. If you are not the intended
recipient of this message or you receive this mail in error, you should refrain from
making any use of the contents and from opening any attachment. In that case, please
notify the sender immediately and return the message to the sender, then, delete and
destroy all copies. This e-mail message, can not be copied, published or sold for any
reason. This e-mail message has been swept by anti-virus systems for the presence of
computer viruses. In doing so, however, sender cannot warrant that virus or other forms
of data corruption may not be present and do not take any responsibility in any
occurrence.
_____________________________________________________________________________________________________________________________________________
/root/sexr/sbin/ser[25819]: Delivering MESSAGE
using usrloc
/root/sexr/sbin/ser[25817]: MSILO: MESSAGE forward failed - storing
it
/root/sexr/sbin/ser[25817]: ERROR: warning_builder: buffer size
exceeded
/root/sexr/sbin/ser[25817]: WARNING: warning skipped -- too big
There are 2 errors:
1- message forward fails - how can I understand why ?
May be, that destination user is not registered or something like that.
You can catch network traffic and look into it, where could be problem.
2- when storing with MSILO buffer size exceeds -
why ? And how can I fix it ?
I think, that this is not when storing MESSAGE content, but when sending reply. SER tries
to add Warning header inside it and generated text is too long. This could be probably
ignored.
You can look into database, if the message was stored.
Vaclav
I really need help on these issues. Please don't ignore my question...
Thanks,
ilker
<http://387555.sigclick.mailinfo.com/sigclick/06090304/030C4A02/030148
03/15141696.jpg>
______________________________________________________________________
______________________________________________________________________
_ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor
olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde
kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya
hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji,
hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi
satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan
taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol
ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan
dogacak hicbir sorumlulugu kabul etmez.
This message is intended solely for the use of the individual or entity to whom it is
addressed , and may contain confidential information. If you are not the intended
recipient of this message or you receive this mail in error, you should refrain from
making any use of the contents and from opening any attachment. In that case, please
notify the sender immediately and return the message to the sender, then, delete and
destroy all copies. This e-mail message, can not be copied, published or sold for any
reason. This e-mail message has been swept by anti-virus systems for the presence of
computer viruses. In doing so, however, sender cannot warrant that virus or other forms
of data corruption may not be present and do not take any responsibility in any
occurrence.
______________________________________________________________________
______________________________________________________________________
_