sr-users

sr-users@lists.kamailio.org

36 participants
37545 discussions

RE: [Serusers] PA error sending notifies
by İlker Aktuna (Koç.net) 16 May '06

16 May '06

Hi again, Forgive me as I don't understand as much as you about Ser configuration. I still have questions: Should I change the configuration as you described ( authorize_message("im-rules.xml") ) ? I am using Eyebeam client; would that make a change for me ? After those changes did you succeed in receiving the Xcap authorization message/notification ? What else should I change ? Should I use im-rules.xml ? Should I change something in Eyebeam client for using this file ? You said you had merged two configs and now you don't get the same problem. How did you merge the configs ? An example configuration would be very helpful to me, if you solved the issue. Thanks, ilker -----Original Message----- From: samuel [mailto:samu60@gmail.com] Sent: Tuesday, May 16, 2006 10:53 AM To: İlker Aktuna (Koç.net) Cc: Vaclav Kubart; serusers(a)lists.iptel.org Subject: Re: [Serusers] PA error sending notifies If you are using XCAP authentication for MESSAGEs, there's a function called authorize_message that needs to have as parameter the file name of the IM ruleset. For user sam, in xcap-root/im-rules/users/sam/im-rules.xml there are the rules for this function. The XML file is similar to the presence-rules but has important differences (correct me if I'm wrong, Vaclav!!!): *it only has a blacklist parameter (no whitelist!!) *the namespace is different (so be carefull in copy&paste from the presence-rules!!!) and, as Vaclav poitned out "proprietary" from iptel. About the structure I have: x86 debian testing. Libraries versions I don't know exactly but the ones in the testing repository EXCEPT a library which I had to get for serweb from the stable version...but it's not affecting SER part. Samuel. 2006/5/16, İlker Aktuna (Koç. net ) <ilkera(a)koc.net>: > > > > > Hi, > > What did you mean by following: > > >Instead of > >> > >> if (authorize_message("http://localhost/xcap")) { > > > >there should be > > > >if (authorize_message("im-rules.xml")){ > > Btw, did you receive my email with following questions : > > >> I have the same problem with notification and other presence > >> messages > with you. > >> Can you tell me which Linux distribution you are using Ser on ? > >> Also please include version numbers for libraries that are required > >> by > Ser. > >> > >> I am trying to find similarities between yours and my ser server. > > Regards, > ilker > > -----Original Message----- > From: serusers-bounces(a)lists.iptel.org > [mailto:serusers-bounces@lists.iptel.org] On Behalf Of samuel > Sent: Monday, May 15, 2006 7:13 PM > To: Vaclav Kubart > Cc: serusers(a)lists.iptel.org > Subject: Re: [Serusers] PA error sending notifies > > Let's see if I can finish the e-mail before gmail decides it's > enough...:P > > 006/5/15, samuel <samu60(a)gmail.com>: > > Following with the handbook... > > > > > the authorize message in the sample confgi files has as parameter > > the xcap root while it should have the xml file containing the auth.rules. > > > Instead of > > > > > if (authorize_message("http://localhost/xcap")) { > > there should be > > if (authorize_message("im-rules.xml")){ > > > > > > > > > 2006/5/15, samuel <samu60(a)gmail.com>: > > > First of all, I have to thank you for the time you spent writing > > > the handbook, it's really really helpfull....I wish all SER > > > related parts had this docs.. > > > > > > I'll try to get familiar with the code of the notifications and > > > I'll try to find something....which I don't thing so :P. I'll also > > > merge the two functionalities (proxy + presence) in a unique > > > config file to see if it works. > > > I hope I can provide more info these following days. > > > > > > About the missing things in the presence handbook, probably the > > > most important is the new xcap module because in the sample config > > > files it's missing. > > > Another thing is that in the XCAP structure description, the > > > im-rules directory is missing, which might lead to > > > misunderstandings. I downloaded the structure from the iptel's ftp > > > and inside the im-rules there were several files corresponding to > > > presence-rules which should be either removed or updated with the > > > im-rules namespaces and removing the whitelist. > > > > > > Thanks, > > > > > > Samuel. > > > <http://387555.sigclick.mailinfo.com/sigclick/03090007/07044D07/02024B00/101…> _____________________________________________________________________________________________________________________________________________ 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. _____________________________________________________________________________________________________________________________________________

2 1

[Serusers] Which IM client
by Suraj Kumar 16 May '06

16 May '06

Hi, a) Can any one suggest a free IM client that I can use to test SIP+SIMPLE using the ser + presence ? I tried with windows messenger 5.1, but it does not seems to be working with the ser + presence server configuration that I used the latest snap shot (ser-0.10.99-dev35-pa-4.1_src.tar.gz). b) Also, can any one suggest a working sample config for presence (without using the database)? Any suggestions on this is highly appreciated. Regards, Suraj

2 1

[Serusers] serweb CTD and message
by Andrey Kouprianov 16 May '06

16 May '06

Hello again, I've sent this message already, but no reply yet. Anyway, Im still facing the problem with CTD and IM in serweb. All the time it would say "503 Service Unavailable". /var/log/messages shows May 15 14:43:14 sip /usr/local/sbin/ser[79174]: ERROR: udp_send: sendto(sock,0x284c0800,452,0,0x284bf208,16): Host is down(64) May 15 14:43:14 sip /usr/local/sbin/ser[79174]: msg_send: ERROR: udp_send failed May 15 14:43:14 sip /usr/local/sbin/ser[79174]: Warning: run_failure_handlers: no UAC support (0, 256) What host is down?? /var/log/serweb shows May 12 22:02:26 serweb [debug] Html form was not assigned to APU apu_aliases3. Useing default. May 12 22:02:26 serweb [debug] Html form was not assigned to APU apu_acl4. Useing default. May 12 22:02:30 serweb [debug] Html form was not assigned to APU apu_aliases3. Useing default. May 12 22:02:30 serweb [debug] Html form was not assigned to APU apu_acl4. Useing default. May 12 22:04:00 serweb [debug] Html form was not assigned to APU apu_aliases3. Useing default. May 12 22:04:00 serweb [debug] Html form was not assigned to APU apu_acl4. Useing default. Is that a problem? Please, can anyone tell me what happened?? Regards, Andrey.

1 1

[Users] Active Passive role supported in UAs
by Ladislav Andel 16 May '06

16 May '06

Hello everybody, I'm sorry for this off topic. I'm trying to make a list of UAs which supports active, passive role. (Regarding connection oriented media or so) These UAs can be gateways, hardphones, softphones, B2BUAs etc. I would appreciate any contribution to my list and thank you, Ladislav

1 1

[Serusers] "old" sems code ...
by Cesc 16 May '06

16 May '06

Hi, what is the status of the old sems code? what is going to happen with it? How much is taken from the "old" code to the "new" code? Regards, Cesc

2 1

[Serusers] How to add and use uri
by İlker Aktuna (Koç.net) 16 May '06

16 May '06

Hi, I add an extra uri to a user with ser_uri command: ./ser_uri add 200000900568888885 0202(a)sip.test.net When 200000900568888885 registers to ser I can call him by dialing 200000900568888885(a)sip.test.net Then I dial 0202(a)sip.test.net from my sip client but it fails at the lookup("location") . What should I add to the configuration to lookup the uris to find the location of the user ? Thanks, ilker <http://387555.sigclick.mailinfo.com/sigclick/02090704/06074807/03044C03/111…> _____________________________________________________________________________________________________________________________________________ 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. _____________________________________________________________________________________________________________________________________________

1 0

RE: [Serusers] PA error sending notifies
by İlker Aktuna (Koç.net) 16 May '06

16 May '06

Hi Vaclav, Do you still need me to send you ngrep output and ser log ? Or else, did you find out where the problem is, from Samuel's information ? If you can find the problem and suggest some fixes, I'd be glad to test it on my system. Please let me know... Thanks, ilker -----Original Message----- From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Vaclav Kubart Sent: Tuesday, May 16, 2006 11:13 AM To: samuel Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] PA error sending notifies Interesting results. Go ahead... :-) Two rulesets are due to their separation in XCAP/authorization related drafts, but you are right, in one file it could be better so I will modify the parser to accept more rulesets in one file... Vaclav On Tue, May 16, 2006 at 09:44:56AM +0200, samuel wrote: > Inline... > > 2006/5/16, Vaclav Kubart <vaclav.kubart(a)iptel.org>: > >> First of all, I have to thank you for the time you spent writing > >> the handbook, it's really really helpfull....I wish all SER related > >> parts had this docs.. > > > >Thanks. :-) It is nice to hear something like that. > > > >> > >> I'll try to get familiar with the code of the notifications and > >> I'll try to find something....which I don't thing so :P. I'll also > >> merge the two functionalities (proxy + presence) in a unique config > >> file to see if it works. > >> I hope I can provide more info these following days. > > > >Thanks. > > > > I've merged the configs without much success...I still have the > problem of sending the NOTIFY but in another function: > > May 15 20:39:07 localhost /usr/local/sbin/ser[19354]: ERROR: uri2sock: > no corresponding socket for af 2 > May 15 20:39:07 localhost /usr/local/sbin/ser[19354]: ERROR: > euac_funcs.c:219: BUG: can't send SUBSCRIBE without contact > > Internally, though I thing everything goes to the same point, when > trying to set the dest_info structure in tm/ut.h, there's some problem > (which I have no clue yet why) when selecting the socket and I think > that the condition that always raise the errors when sending notifies > is: > > dst->send_sock==0 > > This is just the first impression I have...let's see if I can find > something more usefull today or I'll run out of time :( > > There's the "CVS log" > 2006-04-13 added uri2dst(), simplified uri2sock() (andrei) So we can > ask Andrei wether something has changed this last 2 months that can > affect sending the requests from the uac-presence connection. > > > > > > >> > >> About the missing things in the presence handbook, probably the > >> most important is the new xcap module because in the sample config > >> files it's missing. > > > >You are right, but in the "compiled" version of presence handbook > >(published on iptel's ftp) is described current presence snapshot > >which doesn't have xcap module. > > > >In the source version of the handbook (in directory doc/presence of > >SER source tree) is the description still missing too, but will be > >added soon. :-) > > > >> Another thing is that in the XCAP structure description, the > >> im-rules directory is missing, which might lead to > >> misunderstandings. I downloaded the structure from the iptel's ftp > >> and inside the im-rules there were several files corresponding to > >> presence-rules which should be either removed or updated with the > >> im-rules namespaces and removing the whitelist. > > > >Thanks! I will correct it. > > > >By the way, "im-rules" are NOT standardized in any way - we (at > >iptel) only needed something like that, so it is there... > > I don't know wethere it's required to have two different rulesets but > if you have required it I just haven't faced yet the use case so I > guess it's the way to go... > > > > > Vaclav > > > >> > >> Thanks, > >> > >> Samuel. > >> > >> > >> > >> <http://387555.sigclick.mailinfo.com/sigclick/010A0607/04004D07/00064D00/122…> _____________________________________________________________________________________________________________________________________________ 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. _____________________________________________________________________________________________________________________________________________

1 0

[Serusers] CDRTool mailing list
by Cameron Beattie 16 May '06

16 May '06

Forgive the cross posting but I know there are some users on this list interested in CDRTool. A CDRTool-users mailing list has been created at coollist.com since there didn't appear to be a relevant mailing list in existence. To subscribe, visit http://www.coollist.com/subscribe.html and enter the list name CDRTool-users. The list is not sponsored by, affiliated with or endorsed by ag-projects, the authors of CDRTool. Regards Cameron

2 1

[Users] FYI: bug in radiusclient ng for 64b
by Daniel-Constantin Mierla 16 May '06

16 May '06

On 05/16/06 02:48, Maxim Sobolev wrote: > Hi, > > Reportedly there is an problem in radiusclient library with md5 hash > calculation on 64bit platforms (amd64, sparc64, etc), which results in > server rejecting requests even with proper secret configured on > client. I have applied a fix, but don't have access to any 64bit > hardware, therefore can't verify. > > Therefore, if anybody is having problems with radiusclient on 64bit > arch he is more than welcome to try update to the latest version from > cvs and let me know if it helps or not. Instructions on checking out > sources from berlios cvs are here: > https://developer.berlios.de/cvs/?group_id=1208. > > Thanks! > > -Maxim

1 0

[Serusers] Critical bug in radiusclient on 64bit platforms [testers needed]
by Maxim Sobolev 15 May '06

15 May '06

Hi, Reportedly there is an problem in radiusclient library with md5 hash calculation on 64bit platforms (amd64, sparc64, etc), which results in server rejecting requests even with proper secret configured on client. I have applied a fix, but don't have access to any 64bit hardware, therefore can't verify. Therefore, if anybody is having problems with radiusclient on 64bit arch he is more than welcome to try update to the latest version from cvs and let me know if it helps or not. Instructions on checking out sources from berlios cvs are here: https://developer.berlios.de/cvs/?group_id=1208. Thanks! -Maxim

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users