sr-users May 2006

sr-users@lists.kamailio.org

195 participants
502 discussions

by roger leszczynski

Anyone here use ser + b2bua for billing reasons? if so can you provide the config files? ..... i want to be able to capture cdrs even if i restart ser.

18 years

[Users] Re: ACK is sent before the re-INVITE to OpenSER

by Gene Willingham

I thought I was experiencing the same issue. But after looking at it closely, I discovered the ACK is not being sent. I am not an expert with OpenSER and may not be using the correct terminology, but I will try to explain what I see happening. I am using Openser as a gateway to our provider. We send invites from asterisk to openser and we forward the invite to the provider. We are using rewritehost followed by t_relay to route the requests. When we receive the 200 ok back from the provider we relay the message back to asterisk. Asterisk responds with an ACK followed by the reinvites. The issue we are seeing is the ack is not relayed at all, only the reinvites get relayed. We then added the following to the top of openser.cfg: # --------------------------------------------- # Asterisk reinvite issue relay ACK immediately # --------------------------------------------- if (method=="ACK") { forward(uri:host, uri:port); route(1); }; Now the ACK is being handled correctly. We are clearly missing something. I suspect the same thing is happening on inbound calls with the relaying of 200 ok messages. Gene ------------------------------ Message: 6 Date: Wed, 10 May 2006 10:54:52 +0200 From: Klaus Darilion <klaus.mailinglists(a)pernau.at> Subject: Re: [Users] ACK is sent before the re-INVITE to OpenSER, but the proxy relays the re-INVITE first (call flow in the body). To: Bogdan-Andrei Iancu <bogdan(a)voice-system.ro> Cc: users(a)openser.org Message-ID: <4461AA5C.7090403(a)pernau.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed IMO the receiving client should be tolerant and accept the reINVITe although the ACK is missing/delayed, as the reINVITE is an implict ACK. regards klaus Bogdan-Andrei Iancu wrote: > Hi Alexandre, > > if I'm not wrong ,this topic was previously discussed on the mailing > list. The idea is that openser cannot guarantee that messages will be > sent in same order as received. And this because of parallel > multi-process execution. > > the idea is that the CC1 shouldn;t send a re-INVITE so fast and also the > GW should wait a little bit to see if ACK is delayed or not. > > if you are running in full debug, the logs will might help you to see > how the ACK and INVITE gets swapped during processing. > > regards, > bogdan > <<snip>>

18 years, 1 month

[Users] Mixing uri_db and auth_db

by Edgar Barbosa

Hi all, I'm having a weird behaviour when mixing auth_db and uri_db. With the following openser.cfg, the xlog("L_INFO", "TEST\n") is never executed... seems that openser just hangs up... If I remove the uri_db it works... If I remove the auth_db it works too... The problem seems to happen when I mix both... Any idea of what may be wrong? I'm using the latest version (openser 1.0.1). Thanks debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=yes reply_to_via=no check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=4 fifo="/tmp/ser_fifo" loadmodule "/usr/lib/openser/modules/mysql.so" loadmodule "/usr/lib/openser/modules/sl.so" loadmodule "/usr/lib/openser/modules/auth.so" loadmodule "/usr/lib/openser/modules/auth_db.so" loadmodule "/usr/lib/openser/modules/uri_db.so" loadmodule "/usr/lib/openser/modules/xlog.so" modparam("uri_db", "db_url", "mysql://root@192.168.1.104/openser") modparam("auth_db", "db_url", "mysql://root@192.168.1.104/openser") route { xlog("L_INFO", "TEST\n"); }

18 years, 1 month

[Users] Call Hunting: use Avpop or LCR module ?

by Rafael J. Risco G.V.

hi I would like to read some opinions to know which method its better to implement Call Hunting, using serial forking with 'avpops' or 'lcr' module 'load_contacts()/next_contact()' functions, does someone has an example of any of these methods? rafael

18 years, 1 month

RE: [Serusers] PA error sending notifies

by İlker Aktuna (Koç.net)

Hi Samuel, Did you manage to get message rules from im-rules file ? Do you know which path does SER check if you write the authorize_message command as in below ? if (authorize_message("im-rules.xml")){ If you managed to make it work, which client do you use for this ? Did you make any change in the source ? 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)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)iptel.org > [mailto:serusers-bounces@iptel.org] On Behalf Of samuel > Sent: Monday, May 15, 2006 7:13 PM > To: Vaclav Kubart > Cc: serusers(a)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. > > > > > > > > > > > > > > > 2006/5/15, Vaclav Kubart <vaclav.kubart(a)iptel.org>: > > > > Hi, > > > > this problem I'm trying to solve with Ilker Aktuna. I try to > > > > simulate it on my machine and let you know. Or if you solve it, > > > > please > let me know. > > > > :-) > > > > > > > > Please, could you tell me, what things you were missing in > > > > presence handbook? I'm trying to do it as useful as possible and > > > > whatever ideas are welcome... > > > > > > > > Vaclav > > > > > > > > On Mon, May 15, 2006 at 01:38:02PM +0200, samuel wrote: > > > > > Hi all, > > > > > > > > > > I recently had a few hours and start installing the presence > > > > > staff and I have to say that I have it amost workign thanks to > > > > > the presence handbook, the mailing list and, obviously, a > > > > > little bit of code review..:P > > > > > > > > > > I have two SER instances, the "proxy" and the "presence server" > > > > > (both with last CVS code) co-located in the same host and I > > > > > have an issue when the "presence server" tries to send the > > > > > NOTIFY requests. Below there's an attched log showing the > > > > > problem (on IP a.b.c.d I've got the two instances): > > > > > > > > > > 3(30682) DEBUG notify.c:378: sending winfo notify > > > > > 3(30682) DEBUG notify.c:383: winfo document created > > > > > 3(30682) DEBUG notify.c:391: creating headers > > > > > 3(30682) DEBUG notify.c:398: headers created > > > > > 3(30682) DEBUG:tm:t_uac: > > > > > > next_hop=<sip:a.b.c.d;transport=tcp;ftag=c77b3f33;lr=on> > > > > > 3(30682) t_uac: no socket found > > > > > 3(30682) DEBUG notify.c:402: request sent with result -7 > > > > > 3(30682) ERROR: notify.c:404: Can't send watcherinfo > > > > > notification (-7) > > > > > > > > > > This problem appears in other places, not only in the > > > > > notifications for winfo so probably there's somthing in the > > > > > selection of the outgoing socket directing to the local IP. > > > > > > > > > > >From the proxy part I just ust t_forward_nonack for the "SIMPLE" > > > > > messages with record route....maybe adding the port in the > > > > > record route should help? > > > > > <http://387555.sigclick.mailinfo.com/sigclick/010A000C/0406440E/05054B0B/622…> _____________________________________________________________________________________________________________________________________________ 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. _____________________________________________________________________________________________________________________________________________

18 years, 1 month

RE: [Users] /etc/init.d doesn't work

by Ty Manthey

I've tried it, but it doesn't seem to work. I get this error message: Starting openser: openser/etc/init.d/openser: line 63: start-stop-daemon: command not found My scripting sucks, because I can't see what's wrong with it... Ty Manthey -----Original Message----- From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] Sent: Friday, May 19, 2006 9:37 To: Ty Manthey Cc: users(a)openser.org Subject: Re: [Users] /etc/init.d doesn't work Hello, On 05/19/06 01:32, Ty Manthey wrote: > I just did a removal of 0.9.5 and installed 1.0.1 for RH from RPM. My > problem is that the /etc/init.d doesn't work. > I get errors for lines 63, 69, 105 : -start-stop-daemon command not found. > This is a debian command? Should this also work for RH? > Docs also say sample /etc/init.d config file should be at > /usr/local/src/openser-1.0.1/sip-server/etc/openser.init ,but /usr/local/src > is empty. whereis openser only returns a config file and a folder with > modules. > I searched the internet but can't find a posting of a working script, just > references to the script. > that is an issue in the rpm package. Somehow I used the wrong init.d script when building it. Please use the following script to replace the existing one: http://openser.cvs.sourceforge.net/openser/sip-server/packaging/rpm/openser. init?view=markup Cheers, Daniel > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users > >

18 years, 1 month

[Users] sending mail in SER

by rekik refka

Hello, I'm asking how to configure a server mail with SER. I would test sending mail over SER between two MSN clients but this doesn't wok! Thanks in advance! Cheers, Rekik Refka

18 years, 1 month

[Serusers] serctl domain module

by Mindaugas Kuprys

I have problems with serctl domain add (show) functions. Script inserts domain into mysql table, but I'm getting the following errors: 500 command 'domain_dump' not available 500 command 'domain_reload' not available Do you have solution for that? Regards, Mindaugas

18 years, 1 month

[Serusers] Ser: still no voice outside my LAN with ser and rtpProxy

by Americania .it

Hi, I've tried a lot of examples and config. files but still I can't hear any voice when a call is enstablished between users (Nat) outside the Lan where ser in installed (local pc IP 10.0.0.133; LAn router Public IP 80.105.2.110). Tried also from one user outside behind Nat and one in my Lan . I've enclosed trace.log with this case. I've forwarded every ports I think that are needed to 10.0.0.133 (ports 5060 ; udp from 5060 - 5070; 35000 to 35020 ). I've recompiled rtpproxy to use the range of ports 35000-35020. I've also tried the config file from onsip.org for rtpproxy and the one for mediaproxy (with mediaproxy instead of rtpproxy). Whit that config file I've also problems enstablishing the call from outside to inside the Lan. With the ser.cfg that is attached here I can enstablish tha call but no voice (but I can see that 3cx Phone reports packets to be transmitted from both the clients but no packets are received on them). Can someone help me? Thanks ser.cfg : # $Id: ser.cfg,v 1.25.2.1 2005/02/18 14:30:44 andrei Exp $ # # simple quick-start config script # # ----------- global configuration parameters ------------------------ debug=4 # debug level (cmd line: -dddddddddd) /* Uncomment these lines to enter debugging mode */ fork=no log_stderror=yes listen=10.0.0.133 alias=80.105.2.110 check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=4 fifo="/tmp/ser_fifo" fifo_db_url="mysql://ser:heslo@localhost/ser" # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database loadmodule "/usr/lib/ser/modules/mysql.so" loadmodule "/usr/lib/ser/modules/sl.so" loadmodule "/usr/lib/ser/modules/tm.so" loadmodule "/usr/lib/ser/modules/rr.so" loadmodule "/usr/lib/ser/modules/maxfwd.so" loadmodule "/usr/lib/ser/modules/usrloc.so" loadmodule "/usr/lib/ser/modules/registrar.so" #loadmodule "/usr/lib/ser/modules/group.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! loadmodule "/usr/lib/ser/modules/auth.so" loadmodule "/usr/lib/ser/modules/auth_db.so" loadmodule "/usr/lib/ser/modules/uri.so" loadmodule "/usr/lib/ser/modules/uri_db.so" loadmodule "/usr/lib/ser/modules/nathelper.so" loadmodule "/usr/lib/ser/modules/textops.so" # ----------------- setting module-specific parameters --------------- modparam("usrloc", "db_mode", 2) modparam("auth_db|uri_db|usrloc", "db_url","mysql://ser:heslo@localhost/ser") modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "password_column", "password") # !! Nathelper modparam("nathelper", "natping_interval", 30) # Ping interval 30 s modparam("nathelper", "ping_nated_only", 1) # Ping only clients behind NAT modparam("registrar", "nat_flag", 6) # -- rr params -- modparam("rr", "enable_full_lr", 1) # ------------------------- request routing logic ------------------- # main routing logic route{ # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); break; }; # !! Nathelper # Special handling for NATed clients; first, NAT test is # executed: it looks for via!=received and RFC1918 addresses # in Contact (may fail if line-folding is used); also, # the received test should, if completed, should check all # vias for rpesence of received if (nat_uac_test("3")) { # Allow RR-ed requests, as these may indicate that # a NAT-enabled proxy takes care of it; unless it is # a REGISTER if (method == "REGISTER" || ! search("^Record-Route:")) { log("LOG: Someone trying to register from private IP, rewriting\n"); # This will work only for user agents that support symmetric # communication. We tested quite many of them and majority is # smart enough to be symmetric. In some phones it takes a configuration # option. With Cisco 7960, it is called NAT_Enable=Yes, with kphone it is # called "symmetric media" and "symmetric signalling". fix_nated_contact(); # Rewrite contact with source IP of signalling if (method == "INVITE") { fix_nated_sdp("1"); # Add direction=active to SDP }; force_rport(); # Add rport parameter to topmost Via setflag(6); # Mark as NATed }; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); break; }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); route(1); break; }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) { if (method=="REGISTER") { # Uncomment this if you want to use digest authentication if (!www_authorize("80.105.2.110", "subscriber")) { www_challenge("80.105.2.110", "0"); break; }; save("location"); break; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); break; }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; append_hf("P-hint: usrloc applied\r\n"); route(1); } route[1] { # !! Nathelper # if (uri=~"[@:](192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)" && !search("^Route:")){ # sl_send_reply("479", "We don't forward to private IP addresses"); # break; # }; # if client or server know to be behind a NAT, enable relay if (isflagset(6)) { force_rtp_proxy(); }; # NAT processing of replies; apply to all transactions (for example, # re-INVITEs from public to private UA are hard to identify as # NATed at the moment of request processing); look at replies t_on_reply("1"); # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; } # !! Nathelper onreply_route[1] { # NATed transaction ? if (isflagset(6) && status =~ "(183)|2[0-9][0-9]") { fix_nated_contact(); force_rtp_proxy(); # otherwise, is it a transaction behind a NAT and we did not # know at time of request processing ? (RFC1918 contacts) } else if (nat_uac_test("1")) { fix_nated_contact(); }; }

18 years, 1 month

RE: [Serusers] Radius accounting howto

by İlker Aktuna (Koç.net)

I tried that configuration. I get no errors but also no radius packet is created/sent. after setting the flag by "setflag()" command , do I have to enter another command to send the accounting packet for that marked message ? Thanks, ilker ________________________________ From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of İlker Aktuna (Koç.net) Sent: Wednesday, May 31, 2006 5:26 PM To: sip; serusers(a)iptel.org Subject: RE: [Serusers] Radius accounting howto Thanks for that information. But, how does Ser know to send start or stop message to radius ? Thanks, ilker ________________________________ From: sip [mailto:sip@arcdiv.com] Sent: Wednesday, May 31, 2006 2:13 PM To: İlker Aktuna (Koç.net); serusers(a)iptel.org Subject: RE: [Serusers] Radius accounting howto These are essentially log flags. In order to log an INVITE or a BYE to the radius server (assuming your log_flag param was set to 1), you'd do something like: if((method=="INVITE" && !has_totag()) || method=="BYE") { setflag(1); }; I stick that BEFORE the loose_route section of my config, as if I don't, it doesn't seem to catch things correctly. I've yet to debug why. The reason I put the extra !has_totag() in there is for my accounting, so I don't end up logging reINVITES from the remote side. Basically, the parameter for log_flag determines which flag you set in order to log the packet to the radius server. N. [UTF-8?]On Wed, 31 May 2006 10:48:42 +0300, Ä°lker Aktuna $KoÃ§.net$ wrote > Hi, > > Thanks for your reply. I saw that in the source and changed according to them. But I still can't see any radius packets created/sent by Ser when a call is made. > What should I add to the configuration to send start/stop packets ? > > Regards, > ilker > > -----Original Message----- > From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of sip > Sent: Tuesday, May 30, 2006 8:28 PM > To: serusers(a)iptel.org > Subject: Re: [Serusers] Radius accounting howto > > Those params are valid for the old acc module compiled with radius support. > The acc_radius module I think uses log_flag and log_missed_flag (according to the source). > > N. > > On Tue, 30 May 2006 17:54:40 +0300, Ýlker Aktuna (Koç.net) wrote > > Hi everyone, > > > > I am trying to use acc_radius module with presence CVS sources. > > I compiled the radiusclient library and compiled ser with acc_radius module. > > > > Then I added following lines to the config: > > > > loadmodule "/root/ser/lib/ser/modules/acc_radius.so" > > modparam("acc_radius", "radius_config", > "/usr/local/etc/radiusclient-ng/radiusclient.conf") > > modparam("acc_radius", "service_type", 15) modparam("acc_radius", > > "radius_flag", 1) modparam("acc_radius", "radius_missed_flag", 3) > > modparam("acc_radius", "report_ack", 0) > > > > > > But when I try to start ser, it doesn't accept 2 parameters: > > modparam("acc_radius", "radius_flag", 1) modparam("acc_radius", > > "radius_missed_flag", 3) > > > > What should be the correct syntax for these parameters ? are they required ? > > > > And what else should I add to the configuration to send radius-start > > and > radius-stop messages to the radius server ? > > > > Thanks, > > ilker > > > > > > > > <http://387555.sigclick.mailinfo.com/sigclick/0B0A0607/040C4D0A/00034D00/282…> _____________________________________________________________________________________________________________________________________________ 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. _____________________________________________________________________________________________________________________________________________

18 years, 1 month

Jump to page:

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 May 2006