At this time using DB is not very important for us.
I just
need a working configuration.
I don't know why it doesn't work even if I do
everything as described in the book.
I am desperately seeking
help...
Thanks for everything you do...
ilker
-----Original
Message-----
From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
Sent:
Thursday, May 11, 2006 11:45 AM
To: İlker Aktuna (Koç.net)
Cc: Miguel
Freitas; serusers@lists.iptel.org
Subject: Re: [Serusers] SER and XCAP
Server
Hi Ilker,
this will not help you - in your case is a problem
with routing, but I don't know what.
You don't need "db_mode" or "use_db"
parameters set if you don't want to use database as backup. It is useful if you
want it for "failover" (to restore existing subscriptions on SER
startup).
Vaclav
On
Thu, May 11, 2006 at 11:37:50AM +0300, ?lker Aktuna (Koç.net) wrote:
>
Hi,
>
> Would that correction be a solution to my case ?
> If
so, which version should I try (CVS or snapshot) ?
> And what
configuration is correct ?
>
> Thanks,
> ilker
>
>
-----Original Message-----
> From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@iptel.org]
>
On Behalf Of Vaclav Kubart
> Sent: Thursday, May 11, 2006 11:33 AM
>
To: Miguel Freitas
> Cc: serusers@lists.iptel.org
> Subject: Re:
[Serusers] SER and XCAP Server
>
> I have corrected it on CVS and
added new snapshot version 4.1 with this correction on ftp.iptel.org. It is not
tested like normal snapshot, but it seems to be working for the first
look.
>
> The settings
> modparam("rls",
"db_mode", 1)
> says that only resource list subscriptions (subscriptions
to resource lists NOT subscriptions to standalone users) will be stored into
database. If you want to store subscriptions to standalone users and published
information you have to set
> modparam("pa", "use_db",
1)
>
> [more information about module parameters you can read in
presence
> handbook in description of PA and RLS
module]
>
>
Vaclav
>
> On Wed, May 10, 2006 at 06:13:06PM +0100, Miguel Freitas
wrote:
> > just glad of being useful
> >
> > Thanks
for your feedback!
> >
> > One last question: subscriptions
are stored on the SER DB?
> > I have <modparam("rls", "db_mode",
1)> on the config file
> >
> > Miguel
> >
>
>
> > On 5/10/06, Vaclav Kubart <vaclav.kubart@iptel.org>
wrote:
> > >
> > >>
> > >>
>
> >> I was missing line
> > >>
lookup_user("To");
> > >
> > >It was missing in the
presence handbook too - it will be corrected
> > >in next
version.
> > >
> > >>
> > >> Shouldn't
the resource list of subscriptions be stored on the SER DB?
> >
>> Because I'm getting that Waning all the time and I can't find
any
> > >> entry related with subscriptions (table
rls_subscription, ...)
> > >
> > >No DB is not problem
there. I will correct it in CVS - this warning
> > >will not be
displayed if parameter will be "0".
> >
> >
>
>
> >
> > >I have captured SIP and HTTP packets with
Ethereal, sending file..
> > >> (It doesn't include packets
changed between SER and apache
> > >> because they
> >
>are
> > >> on the same machine and I don't have access to it
right now) SER
> > >> and apache on 193.136.93.140 SIP domain =
itav140.av.it.pt
> > >> eyeBeam <sip:4004@193.136.93.252>
and <sip:4002@193.136.92.68 >
> > >> After register, client
<sip:4002@193.136.92.68
> > >>
<sip:4002@193.136.92.68>> changes his status to Away (packet
53)
> > >> <sip:4004> receives the new presence status of
<sip:4002> (packet
> > >> 55 and
> >
>75)
> > >> But when <sip:4002> renew his PUBLISH
(packet 79) he doesn't
> > >> include a message body with his
presence state.
> > >> So, the subsequent NOTIFY received by
<sip:4004> (packet 85)
> > >> doesn't
> >
>include
> > >> the presence status Away any more, even thou
<sip:4002> hasn't
> > >> changed
> >
>his
> > >> status.
> > >> After that, the
client <sip:4004> shows <sip:4002> as Available,
> >
>> when he
> > >is
> > >> Away.
> >
>
> > >Bingo! You have found a bug in SER - thanks! I have read
it in RFC
> > >now, and in the case of empty body needs the state be
refreshed,
> > >not cleared as was done. I will correct it
soon.
> > >
> >
> Vaclav
> > >
>
> >
>
>
_______________________________________________
> Serusers mailing
list
> serusers@lists.iptel.org
> http://mail.iptel.org/mailman/listinfo/serusers
>
>
>
>
>
>
<http://387555.sigclick.mailinfo.com/sigclick/000C0601/04034E04/05044D
>
06/13414162.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.
>
______________________________________________________________________
>
______________________________________________________________________
>
_