sr-users

sr-users@lists.kamailio.org

13 participants
37464 discussions

[Users] Number of children per interface
by Andreas Granig 26 May '06

26 May '06

Hi, I want OpenSER to listen on udp:localhost:5060 for local health checks, but I only need one process running on this interface (opposed to, say, 12 processes on the public interface). So is there a way to selectively define the number of children per interface? Thanks, Andy

2 1

RE: [Users] 2 Openser Instances
by Sam Lee 26 May '06

26 May '06

I tried the cacheless mode, it didn't work for me. I'm just wondering , how did those people out there do their OUTBOUND proxy ? Can anyone give me some hint ? Regards, Sam -----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Friday, May 26, 2006 4:57 PM To: Sam Lee Cc: users(a)openser.org Subject: Re: [Users] 2 Openser Instances Sam Lee wrote: > Hi Klaus, > > Thanks for the quick reply. My purpose is one of the instance being a > normal Openser, the other with a FORCE RTPproxy. This is so that if > they have a symmetric NAT going on in their network, they can make use > of this rtpproxy as an outbound proxy but still able to call those > register with the normal openser. > > Care to explain what is cacheless userloc mode ? How do I set it ? http://openser.org/docs/modules/devel/usrloc.html#AEN252 it's mode 3 (only available in CVS head) > > Because of the normal and force RTPproxy , these 2 instances has > different routing patterns, and they are handled differently. I still would use only one proxy and apply NAT traversal only for clients which use the "NAT traversal" port on your openser. The idea is: ... if ( dst_port = 6060) { # needs NAT traversal if (is_method("REGISTER")) { setflag(9); # this is the natflag specified in userloc module # http://openser.org/docs/modules/1.0.x/registrar.html#AEN103 fix_nated_register(); } else { # do all the NAT traversal, activate RTP proxy } } # now do the normal call and REGISTER handling ... ... lookup("location"); if(isflagset(9)) { ...#force rtp proxy } .... regards klaus > > Any ideas ? > > Regards, > Sam > > -----Original Message----- > From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > Sent: Friday, May 26, 2006 4:28 PM > To: Sam Lee > Cc: users(a)openser.org > Subject: Re: [Users] 2 Openser Instances > > 1. You can run several instances of openser on the same PC, but what > is your purpose? > > 2. If 2 openser proxies share the same userloc database, you have to > use the cacheless userloc mode > > 3. If you just want to listen on several ports, use a single proxy > with multiple listen directives > > listen=udp:1.2.3.4:5060 > listen=udp:1.2.3.4:6060 > listen=udp:1.2.3.4:7060 > > regards > klaus > > > Sam Lee wrote: >> Have anyone tried running 2 separate instances on OpenSER (running on >> different ports) ? >> Both these instances are doing almost exactly the same thing, they >> take in REGISTER and save them into the locations database. They all >> do all the other processing like INVITE. >> >> Will this causes a problem in MYSQL ? I'm asking this because i got a >> very strange problem. I register 1 UA to each instances. When i did a >> ul show , it always only have either the UA from instance A or UA >> from > >> instance B . Note, these 2 UA have different numbers. Why can't it >> just save both into the MYSQL DB ? >> >> I would be glad to clarify any doubts. Please assist as far as you > can. >> Thanks! >> >> Regards, >> Sam >> >> >> --------------------------------------------------------------------- >> - >> -- >> >> _______________________________________________ >> Users mailing list >> Users(a)openser.org >> http://openser.org/cgi-bin/mailman/listinfo/users >

2 1

[Users] LCR - scheme column
by Andrew And 26 May '06

26 May '06

In LCR, Is there something special the column scheme? I am having problem with this.

2 1

[Users] no authorize with ATA and phones
by Jens Carl 26 May '06

26 May '06

Hello list, i have following code in my openser configuration to prevent that everybody can make calls to PSTN: process INVITE messages -- snip if( !allow_trusted() ) { if( !proxy_authorize( "myrealm", "subscriber" ) ) { proxy_challenge( "realm", "1" ); return; } else if ( !check_from() ) { sl_send_reply( "403", "Use From=ID" ); return; }; consume_credentials(); }; -- snap This works fine with snom200, snom360 and some other phones/ATA. It isn't working with Linksys IPPhone SPA941, snom100 and the ATA Linksys SPA 2001. All these three devices aren't sending the credentials after they are challenge to send them. I know this because the new INVITE message have no digest information in it, the call isn't be placed and the following error message from the logs of OpenSER: /sbin/openser[3323]: find_credentials(): Error while parsing headers I have also tried that the second parameter of proxy_challenge are 0 (zero) but that didn't helped. Have anybody a clue where I can change this behaviour of the three devices? Have I change some settings, etc of the phones/ATA? Or maybe I have to change my code for the OpenSER? But I will avoid this because I don't want to be an open relay. Thanks in advance Jens

2 1

[Serusers] Registering users
by ravi reddy 26 May '06

26 May '06

hi all this is for one soft phone is doing like this ,,, i cannot register to my SER server U 81.21.34.34:212 -> 81.21.33.35:5060 REGISTER sip:81.21.33.35 SIP/2.0..Via: SIP/2.0/UDP 192.168.0.135:5060 ;rport;branch=z9hG4bK0DA1C9E2C22F46F5805CA80FA91EA5 67..From: 32331002 <sip:32331002@81.21.33.35>;tag=3696527705..To: 32331002 <sip:32331002@81.21.33.35>..Contact: "3233100 2" <sip:32331002@192.168.0.135:5060>..Call-ID: 7256439978B84537903A09F726B93509@81.21.33.35..CSeq: 55065 REGISTER..Expir es: 1800..Max-Forwards: 70..User-Agent: X-Lite release 1105x..Content-Length: 0.... # U 81.21.33.35:5060 -> 81.21.34.34:212 SIP/2.0 100 Trying..Via: SIP/2.0/UDP 192.168.0.135:5060 ;rport=212;branch=z9hG4bK0DA1C9E2C22F46F5805CA80FA91EA567;receive d=81.21.34.34..From: 32331002 <sip:32331002@81.21.33.35>;tag=3696527705..To: 32331002 <sip:32331002@81.21.33.35>..Call-I D: 7256439978B84537903A09F726B93509@81.21.33.35..CSeq: 55065 REGISTER..Server: Sip EXpress router (0.9.6 (i386/linux)).. Content-Length: 0..Warning: 392 81.21.33.35:5060 "Noisy feedback tells: pid=3630 req_src_ip=81.21.34.34 req_src_port=21 2 in_uri=sip:81.21.33.35 out_uri=sip:81.21.33.35 via_cnt==1".... # U 81.21.33.35:5060 -> 81.21.34.34:212 SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP 192.168.0.135:5060 ;rport=212;branch=z9hG4bK0DA1C9E2C22F46F5805CA80FA91EA567;r eceived=81.21.34.34..From: 32331002 <sip:32331002@81.21.33.35>;tag=3696527705..To: 32331002 <sip:32331002@81.21.33.35>;t ag=74961b5b71b6ddce908b9155b956083f.043b..Call-ID: 7256439978B84537903A09F726B93509@81.21.33.35..CSeq: 55065 REGISTER..W WW-Authenticate: Digest realm="81.21.33.35", nonce="4476df0f829037115d339a515fbb4cd42dc01881"..Server: Sip EXpress route r (0.9.6 (i386/linux))..Content-Length: 0..Warning: 392 81.21.33.35:5060"Noisy feedback tells: pid=3630 req_src_ip=81. 21.34.34 req_src_port=212 in_uri=sip:81.21.33.35 out_uri=sip:81.21.33.35via_cnt==1".... # And this for another soft phone which i register U 81.21.34.34:5060 -> 81.21.33.35:5060 REGISTER sip:81.21.33.35 SIP/2.0..Via: SIP/2.0/UDP 192.168.0.76;branch=z9hG4bKbc56000086c00000..From: "ravi" <sip:323310 01(a)81.21.33.35>;tag=c33700001dbcffff..To: <sip:32331001@81.21.33.35>..Contact: <sip:32331001@192.168.0.76>..Authorizatio n: Digest username="32331001", realm="81.21.33.35", algorithm=MD5, uri="sip:81.21.33.35", nonce="4476e07f5709732e89167b7 e64ed8ffb36b9626a", response="b2bf125d721aa70e7813d65f6a5da879"..Call-ID: 943300002fe50000@192.168.0.76..CSeq: 101 REGIS TER..Expires: 360000..User-Agent: Grandstream HT496 1.0.2.16..Max-Forwards: 70..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFE R,OPTIONS,INFO,SUBSCRIBE..Content-Length: 0.... # U 81.21.33.35:5060 -> 81.21.34.34:5060 SIP/2.0 100 Trying..Via: SIP/2.0/UDP 192.168.0.76 ;branch=z9hG4bKbc56000086c00000;received=81.21.34.34..From: "ravi" <sip :32331001@81.21.33.35>;tag=c33700001dbcffff..To: <sip:32331001@81.21.33.35>..Call-ID: 943300002fe50000@192.168.0.76..CSe q: 101 REGISTER..Server: Sip EXpress router (0.9.6(i386/linux))..Content-Length: 0..Warning: 392 81.21.33.35:5060 "Nois y feedback tells: pid=3630 req_src_ip=81.21.34.34 req_src_port=5060 in_uri=sip:81.21.33.35 out_uri=sip:81.21.33.35 via_ cnt==1".... # U 81.21.33.35:5060 -> 81.21.34.34:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.0.76 ;branch=z9hG4bKbc56000086c00000;rport=5060;received=81.21.34.34..From: "rav i" <sip:32331001@81.21.33.35>;tag=c33700001dbcffff..To: < sip:32331001@81.21.33.35>;tag=74961b5b71b6ddce908b9155b956083f. 740d..Call-ID: 943300002fe50000@192.168.0.76..CSeq: 101 REGISTER..Contact: <sip:32331001@192.168.0.76>;expires=360000;re ceived="sip:81.21.34.34:5060"..Server: Sip EXpress router (0.9.6(i386/linux))..Content-Length: 0..Warning: 392 81.21.33 .35:5060 "Noisy feedback tells: pid=3630 req_src_ip=81.21.34.34req_src_port=5060 in_uri=sip: 81.21.33.35 out_uri=sip:81 .21.33.35 via_cnt==1".... # U 81.21.34.34:5060 -> 81.21.33.35:5060 SUBSCRIBE sip:32331001@81.21.33.35 SIP/2.0..Via: SIP/2.0/UDP 192.168.0.76;branch=z9hG4bKc94cffff37bbffff..From: "ravi" < sip:32331001@81.21.33.35>;tag=0c61000042370000..To: < sip:32331001@81.21.33.35>..Contact: <sip:32331001@192.168.0.76>..Ca ll-ID: 01a5000043e20000@192.168.0.76..CSeq: 58060 SUBSCRIBE..User-Agent: Grandstream HT496 1.0.2.16..Max-Forwards: 70..A llow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Event: message-summary..Expires: 360000..Accept: applic ation/simple-message-summary..Content-Length: 0.... # U 81.21.33.35:5060 -> 81.21.34.34:5060 SUBSCRIBE sip:32331001@192.168.0.76 SIP/2.0..Record-Route: <sip: 81.21.33.35;ftag=0c61000042370000;lr=on>..Via: SIP/2.0/U DP 81.21.33.35;branch=z9hG4bKb62c.88852837.0..Via: SIP/2.0/UDP 192.168.0.76;received=81.21.34.34;branch=z9hG4bKc94cffff3 7bbffff..From: "ravi" <sip:32331001@81.21.33.35>;tag=0c61000042370000..To: <sip:32331001@81.21.33.35>..Contact: <sip:323 31001(a)192.168.0.76>..Call-ID: 01a5000043e20000@192.168.0.76..CSeq: 58060 SUBSCRIBE..User-Agent: Grandstream HT496 1.0.2. 16..Max-Forwards: 16..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Event: message-summary..Expires: 360000..Accept: application/simple-message-summary..Content-Length: 0.... # U 81.21.34.34:5060 -> 81.21.33.35:5060 SIP/2.0 202 Accepted..Via: SIP/2.0/UDP 81.21.33.35;branch= z9hG4bKb62c.88852837.0..Via: SIP/2.0/UDP 192.168.0.76;received =81.21.34.34;branch=z9hG4bKc94cffff37bbffff..Record-Route: <sip: 81.21.33.35;ftag=0c61000042370000;lr=on>..From: "ravi" < sip:32331001@81.21.33.35>;tag=0c61000042370000..To: < sip:32331001@81.21.33.35>;tag=58b60000e93cffff..Call-ID: 01a5000043 e20000@192.168.0.76..CSeq: 58060 SUBSCRIBE..User-Agent: Grandstream HT496 1.0.2.16..Contact: <sip:32331001@192.168.0.76> ..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Supported: replaces..Content-Length: 0.... # U 81.21.33.35:5060 -> 81.21.34.34:5060 SIP/2.0 202 Accepted..Via: SIP/2.0/UDP 192.168.0.76;received=81.21.34.34;branch=z9hG4bKc94cffff37bbffff..Record-Route: < sip:81.21.33.35;ftag=0c61000042370000;lr=on>..From: "ravi" < sip:32331001@81.21.33.35>;tag=0c61000042370000..To: <sip:323 31001(a)81.21.33.35>;tag=58b60000e93cffff..Call-ID: 01a5000043e20000@192.168.0.76..CSeq: 58060 SUBSCRIBE..User-Agent: Gran dstream HT496 1.0.2.16..Contact: <sip:32331001@81.21.34.34:5060>..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO ,SUBSCRIBE..Supported: replaces..Content-Length: 0.... i did the same in both cases but what happend to that one is registering and another is not registering please help me how to cross this registering users problem :-( Thanks in advance regards Ravi.

1 0

[Users] rtpproxy issue
by krishnamurthy kandi 26 May '06

26 May '06

Hi, I am getting the problem with rtp proxy in the case of call forking from ser. After forking, one callee sends 183 session progress (early media),with this rtpsession is established in rtp proxy. Then other callee accept the call, starts sending media, in this case after calling recvfrom function ,raddr structure is not containing exact destination and port, it containts previous packet IP ,current packet port at comparing session IP and remote IPs, once IP is updated, canupdate flag is disabled, then for further invalid IP comparisons , it wont update the remote IP. Thats why rtp is not getting relayed to user agents. Why raddr variable is not containing correct IP and port, why it is showing corrupted information. For my convention I am not checking canupdate flag, now it is disabled, then it is working now.Any suggitions. Thanks, kkmurthy --------------------------------- New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.

2 1

[Users] Multi UAC authorisations with AVPops or other method - any working example ?
by G.Jacobsen 26 May '06

26 May '06

Gentlemen, I would be most grateful, if someone could provide an example on how to use the new AVPops funktions (cvs head) to accompish multiple UAC registrations with authorisations uac_auth(); with external SIP providers. Any shortcut on how to accomplish this (avoiding AVPops) or related examples would also be greatly appreciated. TIA for your help. Gerry

2 1

[Users] uac_redirect and branches
by Andreas Granig 26 May '06

26 May '06

Hi, I'm currently playing around with uac_redirect to also handle UAC-triggered call forwards (301/302). My server-side CF-handling works in that way that I rewrite the R-URI in failure-routes and call my normal routes to manipulate the new R-URI and then append_branch() before t_relay(). Now with get_redirects() the new R-URIs are already appended as branches, so how may I manipulate the URIs then? Is there a way to get the R-URI of a branch back into the "normal" R-URI where I can use $rU and $rd and so on? Or how may I handle that then? Setting a branch-route and t_relay() and then manipulate my URI doesn't seem to be the way to go, because there's quite a lot of R-URI processing going on in my config before an INVITE leaves the server. Thanks, Andy

2 1

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

26 May '06

Actually I have tried and found TABLE_VERSION in the sources but I don't know what it should be. I have both old sources and the new sources in 2 different directories. How can I check the difference between 2 usrloc modules ? Using diff ? Regards, ilker -----Original Message----- From: samuel [mailto:samu60@gmail.com] Sent: Friday, May 26, 2006 12:51 PM To: İlker Aktuna (Koç.net) Cc: Vaclav Kubart; serusers(a)iptel.org Subject: Re: PA error sending notifies You have to look for DB_VERSION or something similar in usrloc module and check wether this value corresponds to the one appearing in the version table corresponding to the usrloc module. If they are different, you have to modify the version table to match the usrloc requirements...as Vaclav said maybe somebody forget to update it in the module or in the database.. Great news about the NOTIFY!!!! Let's see if I can ceck it in the coming weeks.... samuel. 2006/5/26, İlker Aktuna (Koç. net ) <ilkera(a)koc.net>: > > > > > Hi, > > Thanks for your reply; but I've already tried dropping and creating > with the mysql scripts that are supplied. > Unfortunately they are not creating suitable database version for usrloc. > Have you tried using usrloc with db support ? > > Btw, with the latest CVS sources presence is working fine. I have no > problem with sending notifications. > I just have the problem with usrloc db support now. And thus I need > the db structure for new CVS version. > > Thanks, > ilker > > -----Original Message----- > From: samuel [mailto:samu60@gmail.com] > Sent: Friday, May 26, 2006 12:17 PM > To: İlker Aktuna (Koç.net) > Cc: Vaclav Kubart; serusers(a)iptel.org > Subject: Re: PA error sending notifies > > The HEAD CVS version has a completely different database structure > than the stable version. You have to drop the older version and use > the new one. Next is a SIMPLIFICATION of a possible way to drop the > old structure and create the new one: > > The simple way to do it is with the script ser_mysql.sh, which uses > my_create.sql and my_drop.sql so be sure you've got the three scripts > in /usr/local/sbin. When you type form the shell: > > #ser_mysql.sh > > you'll see which are the possible options, being the most relevant > drop and create > > typing > > #ser_mysql.sh drop > > and later > > #ser_mysql.sh create > > > You'll have in the local machine the SER database. > > > Hope it helps, > > Samuel > > 2006/5/26, İlker Aktuna (Koç. net ) <ilkera(a)koc.net>: > > > > > > > > > > Hi vaclav, > > > > How can I get help for the usrloc db problem ? > > I don't know the necessary db structure for usrloc. Does it need a > > table named usrloc ? > > Please point me to the correct address for help on the db structure. > > > > Btw, I'm downloading the new cvs sources now and I'll try it. I hope > > the sending notifies problem is solved for my case too. > > > > Thanks, > > ilker > > > > -----Original Message----- > > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] > > Sent: Friday, May 26, 2006 8:18 AM > > To: İlker Aktuna (Koç.net) > > Cc: serusers(a)iptel.org; samuel > > Subject: Re: PA error sending notifies > > > > It was something forgotten in modules/tm/ut.h, now it is corrected on CVS. > > > > I have no such DB error, but I'm not using usrloc/registrar with DB. > > May be that somebody increments the version number in code and > > forgot increment the table version number in DB initialization or > > something like that. > > > > Vaclav > > > > On Thu, May 25, 2006 at 04:35:26PM +0300, ?lker Aktuna (Koç.net) wrote: > > > Great :) > > > That's good nes for me, because I couldn't make you believe that > > > there was a serious problem :) Now how shall we proceed ? > > > > > > Btw, you'll also have the following error in latest CVS, can you check ? > > > > > > May 25 16:44:57 sesapp /root/ser/sbin/ser[3173]: register_udomain(): > > > Invalid table version (use ser_mysql.sh reinstall) May 25 16:44:57 > > > sesapp /root/ser/sbin/ser[3173]: register_udomain(): Invalid table > > > version (use ser_mysql.sh reinstall) > > > > > > Regards, > > > ilker > > > > > > -----Original Message----- > > > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] > > > Sent: Thursday, May 25, 2006 4:26 PM > > > To: ?lker Aktuna (Koç.net) > > > Cc: serusers(a)iptel.org; samuel > > > Subject: Re: PA error sending notifies > > > > > > I updated to latest CVS sources and I have the same problem now! > > > [Can't send watcherinfo notification (-7)] > > > > > > Vaclav > > > > > > On Wed, May 24, 2006 at 10:45:42AM +0300, ?lker Aktuna (Koç.net) wrote: > > > > Hi Vaclav, > > > > > > > > I want to install and run Ser on an identical linux setup with > > > > you to overcome the notification sending issue (thus presence) > > > > That's why I > > need the library versions that you use. > > > > Also I need to know which version of Debian Sarge you are using. > > > > And your ser snapshot version. > > > > > > > > Can you supply me these information please ? > > > > > > > > Thanks, > > > > ilker > > > > > > > > > > > > ________________________________ > > > > > > > > From: ?lker Aktuna (Koç.net) > > > > Sent: Tuesday, May 23, 2006 5:44 PM > > > > To: 'samuel' > > > > Cc: Vaclav Kubart; serusers(a)iptel.org > > > > Subject: RE: PA error sending notifies > > > > > > > > > > > > > > > > So you are not able to use presence but other traffic (IM, voice > > > > etc.) > > is fine ? > > > > Do you know the xml parser library that your system has installed ? > > > > Vaclav, which library version do you use ? > > > > > > > > Thanks, > > > > ilker > > > > > > > > -----Original Message----- > > > > From: samuel [mailto:samu60@gmail.com] > > > > Sent: Tuesday, May 23, 2006 5:05 PM > > > > To: ?lker Aktuna (Koç.net) > > > > Cc: Vaclav Kubart; serusers(a)iptel.org > > > > Subject: Re: PA error sending notifies > > > > > > > > Unfortunately I had no more time to look into it, so I have no > > > > more > > progress..I just saw that the contact header was not properly parsed > > and there were problems when selecting the local socket where to > > send the notifies from...I hope in the following weeks I find some > > more time to spend on it. > > > > > > > > Samuel. > > > > > > > > > > > > 2006/5/23, ?lker Aktuna (Koç. net ) <ilkera(a)koc.net>: > > > > > > > > > > > > > > > > > > > > > > > > > Hi Samuel, > > > > > > > > > > Did you solve the issue where sending notifies would fail with > > > > > error code -7 ? > > > > > > > > > > "Can't send watcherinfo notification (-7)" > > > > > > > > > > If you solved it can you tell me how ? > > > > > > > > > > I believe the problem is occuring while creating the headers. > > > > > Because in "notify.c" I see that -7 is returned only while > > > > > creating > > headers. > > > > > > > > > > Regards, > > > > > ilker > > > > > > > > > > > > > > > > > <http://387555.sigclick.mailinfo.com/sigclick/00090307/01044D0C/02024800/431…> _____________________________________________________________________________________________________________________________________________ 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] RE: PA error sending notifies
by İlker Aktuna (Koç.net) 26 May '06

26 May '06

Hi, Thanks for your reply; but I've already tried dropping and creating with the mysql scripts that are supplied. Unfortunately they are not creating suitable database version for usrloc. Have you tried using usrloc with db support ? Btw, with the latest CVS sources presence is working fine. I have no problem with sending notifications. I just have the problem with usrloc db support now. And thus I need the db structure for new CVS version. Thanks, ilker -----Original Message----- From: samuel [mailto:samu60@gmail.com] Sent: Friday, May 26, 2006 12:17 PM To: İlker Aktuna (Koç.net) Cc: Vaclav Kubart; serusers(a)iptel.org Subject: Re: PA error sending notifies The HEAD CVS version has a completely different database structure than the stable version. You have to drop the older version and use the new one. Next is a SIMPLIFICATION of a possible way to drop the old structure and create the new one: The simple way to do it is with the script ser_mysql.sh, which uses my_create.sql and my_drop.sql so be sure you've got the three scripts in /usr/local/sbin. When you type form the shell: #ser_mysql.sh you'll see which are the possible options, being the most relevant drop and create typing #ser_mysql.sh drop and later #ser_mysql.sh create You'll have in the local machine the SER database. Hope it helps, Samuel 2006/5/26, İlker Aktuna (Koç. net ) <ilkera(a)koc.net>: > > > > > Hi vaclav, > > How can I get help for the usrloc db problem ? > I don't know the necessary db structure for usrloc. Does it need a > table named usrloc ? > Please point me to the correct address for help on the db structure. > > Btw, I'm downloading the new cvs sources now and I'll try it. I hope > the sending notifies problem is solved for my case too. > > Thanks, > ilker > > -----Original Message----- > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] > Sent: Friday, May 26, 2006 8:18 AM > To: İlker Aktuna (Koç.net) > Cc: serusers(a)iptel.org; samuel > Subject: Re: PA error sending notifies > > It was something forgotten in modules/tm/ut.h, now it is corrected on CVS. > > I have no such DB error, but I'm not using usrloc/registrar with DB. > May be that somebody increments the version number in code and forgot > increment the table version number in DB initialization or something > like that. > > Vaclav > > On Thu, May 25, 2006 at 04:35:26PM +0300, ?lker Aktuna (Koç.net) wrote: > > Great :) > > That's good nes for me, because I couldn't make you believe that > > there was a serious problem :) Now how shall we proceed ? > > > > Btw, you'll also have the following error in latest CVS, can you check ? > > > > May 25 16:44:57 sesapp /root/ser/sbin/ser[3173]: register_udomain(): > > Invalid table version (use ser_mysql.sh reinstall) May 25 16:44:57 > > sesapp /root/ser/sbin/ser[3173]: register_udomain(): Invalid table > > version (use ser_mysql.sh reinstall) > > > > Regards, > > ilker > > > > -----Original Message----- > > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] > > Sent: Thursday, May 25, 2006 4:26 PM > > To: ?lker Aktuna (Koç.net) > > Cc: serusers(a)iptel.org; samuel > > Subject: Re: PA error sending notifies > > > > I updated to latest CVS sources and I have the same problem now! > > [Can't send watcherinfo notification (-7)] > > > > Vaclav > > > > On Wed, May 24, 2006 at 10:45:42AM +0300, ?lker Aktuna (Koç.net) wrote: > > > Hi Vaclav, > > > > > > I want to install and run Ser on an identical linux setup with you > > > to overcome the notification sending issue (thus presence) That's > > > why I > need the library versions that you use. > > > Also I need to know which version of Debian Sarge you are using. > > > And your ser snapshot version. > > > > > > Can you supply me these information please ? > > > > > > Thanks, > > > ilker > > > > > > > > > ________________________________ > > > > > > From: ?lker Aktuna (Koç.net) > > > Sent: Tuesday, May 23, 2006 5:44 PM > > > To: 'samuel' > > > Cc: Vaclav Kubart; serusers(a)iptel.org > > > Subject: RE: PA error sending notifies > > > > > > > > > > > > So you are not able to use presence but other traffic (IM, voice > > > etc.) > is fine ? > > > Do you know the xml parser library that your system has installed ? > > > Vaclav, which library version do you use ? > > > > > > Thanks, > > > ilker > > > > > > -----Original Message----- > > > From: samuel [mailto:samu60@gmail.com] > > > Sent: Tuesday, May 23, 2006 5:05 PM > > > To: ?lker Aktuna (Koç.net) > > > Cc: Vaclav Kubart; serusers(a)iptel.org > > > Subject: Re: PA error sending notifies > > > > > > Unfortunately I had no more time to look into it, so I have no > > > more > progress..I just saw that the contact header was not properly parsed > and there were problems when selecting the local socket where to send > the notifies from...I hope in the following weeks I find some more > time to spend on it. > > > > > > Samuel. > > > > > > > > > 2006/5/23, ?lker Aktuna (Koç. net ) <ilkera(a)koc.net>: > > > > > > > > > > > > > > > > > > > > Hi Samuel, > > > > > > > > Did you solve the issue where sending notifies would fail with > > > > error code -7 ? > > > > > > > > "Can't send watcherinfo notification (-7)" > > > > > > > > If you solved it can you tell me how ? > > > > > > > > I believe the problem is occuring while creating the headers. > > > > Because in "notify.c" I see that -7 is returned only while > > > > creating > headers. > > > > > > > > Regards, > > > > ilker > > > > > > > > > > > > > > > <http://387555.sigclick.mailinfo.com/sigclick/010C0605/07044406/0B044D > > 02/12410218.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. > > > ______________________________________________________________________ > > > ______________________________________________________________________ > > _ > > > > > > ______________________________________________________________________ > ______________________________________________________________________ > _ 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. > ______________________________________________________________________ > ______________________________________________________________________ > _ > <http://387555.sigclick.mailinfo.com/sigclick/030B0504/07064D0A/01014E03/203…> _____________________________________________________________________________________________________________________________________________ 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

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