[Serusers] IM and presence problems

Vaclav Kubart vaclav.kubart at iptel.org
Tue May 2 09:09:18 CEST 2006


Hi,
as I can see from the dump - MESSAGEs go through without problems,
right?
Try to increase debug level in config file, might be, you will see more.
I don't see any problems... :-(

	Vaclav

On Fri, Apr 28, 2006 at 03:32:24PM +0300, ?lker Aktuna (Koç.net) wrote:
> Hi Vaclav,
> 
> I've installed ngrep and sending you ngrep output.
> 
> "t_uac: no socket found" error is occuring in nearly all of the events.
> Should I use unixsock module ? If yes, what are the needed parameters ?
> Currently fifo module is loaded. Should I use it also ?
> 
> For problem 2 ; you are right. I am using Eyebeam. Then I'll ignore this error.
> 
> Thanks for your help.
> 
> ilker
> 
> -----Original Message-----
> From: Vaclav Kubart [mailto:vaclav.kubart at iptel.org]
> Sent: Friday, April 28, 2006 3:08 PM
> To: ?lker Aktuna (Koç.net)
> Cc: serusers at lists.iptel.org
> Subject: Re: [Serusers] IM and presence problems
> 
> Hi Ilker :-)
> 
> > Hi again,
> >
> > Really your information is helping me very much.
> > I re-compiled the CVS version with xcap module. And added parameters you suggested.
> >
> > Now, I registered one client and I see 3 errors :
> > 1- after a REGISTER message I see the following line 2 times:
> > t_uac: no socket found
> 
> I need to see the message flow - try to catch something with ngrep.
> (ngrep -W byline port 5060 -d any)
> 
> >
> > 2- after a SUBSCRIBE message (after register) I see the following errors:
> > check_message(): Unsupported event package
> > ERROR: subscribe.c:860: Error while checking message
> > ERROR: subscribe.c:948: handle_subscription about to send_reply and
> > return -2
> 
> This means, that a SUBSCRIBE to unsupported events arrives - this is probably not problem (for example eyeBeam tries to subscribe to something like "xcap change", I'm not sure now). This is not needed for presence handling.
> 
> >
> > 3- after another SUBSCRIBE message I see the following lines:
> > t_uac: no socket found
> > ERROR: notify.c:398: Can't send watcherinfo notification (-7)
> > send_winfo_notify returned -7
> >
> 
> I think, it could be problem with contact in "presence.winfo"
> subscription. I need to see message flows between client and SER.
> (Watcherinfo - more precisely presence.winfo event package
> - is used for watching to "who is watching a user" - see RFC 3857).
> 
>         Vaclav
> 
> > What is watcherinfo and why doesn't it work with the config ?
> >
> > Thanks,
> > ilker
> >
> 
> 
> 
> 
>  <http://387555.sigclick.mailinfo.com/sigclick/06090104/04064505/03044A03/65161139.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.
> _____________________________________________________________________________________________________________________________________________





More information about the sr-users mailing list