sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

[Users] SER not to mask the FROM field
by Mark Anthony C. Delfin 18 Nov '06

18 Nov '06

Hello Guys, I would like SER not to mask the FROM field when its sending a call to another sip proxy/gateway. What Im getting on the destination gateway is the IP of the SER. I wouldnt want SER to proxy/mask the original IP address of the UAC. Is this possible. Here is a sample callflow: UAC (192.168.10.10) >> SER (192.168.11.10) >> UAS (192.168.12.10) i would like the FROM on the UAS to look like 123456(a)192.168.10.10 and not 123456(a)192.168.11.10 which is the SER's IP. Please help. Thanks in advance.

3 2

Re: [Users] T.38 together with OpenSER+RTPProxy and OpenPBX not working
by Ovidiu Sas 18 Nov '06

18 Nov '06

Hi Bastien, If you see incoming and outgoing udptl traffic on both SIP-FAX devices, capture it and load the file on wireshark. Check the T.38 signaling and see where it is failing and why. As an example/reference, use a capture from a working case. Regards, Ovidiu Sas On 11/17/06, Bastian Schern <ml02(a)in-bln.de> wrote: > Hi Bogdan, > > I think it has nothing to do with a deadlock. I see the incoming and > outgoing UDPTL traffic on both SIP-FAX devices. > > Do you got a suggestion for me, what I could do to locate and resolve the > problem. > > Cheers > Bastian > > --On Donnerstag, 16. November 2006 14:12 +0200 Bogdan-Andrei Iancu > <bogdan(a)voice-system.ro> wrote: > > > Hi Bastin, > > > > probably there is kind of a RTP deadlock between the RTPproxy and > > OpenPBX - both are waiting for the other party to send the media before > > sending on its turn. > > > > try something like: > > if (nat_uac_test("8")) { > > force_rtp_proxy(); > > } else { > > force_rtp_proxy("r"); > > } > > > > refer to http://www.openser.org/docs/modules/1.2.x/nathelper.html for > > more details. > > > > regards, > > bogdan > > > > > > Bastian Schern wrote: > > > >> Hi everybody, > >> > >> I've got a question: Does anybody get T.38 working between OpenPBX and > >> OpenSER + RTPProxy? > >> > >> The following scenarios are working fine: > >> > >> 1: SIP-FAX1 (pub. IP) <-> OpenPBX <-> SIP-FAX2 (pub. IP) > >> 2: SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> SIP-FAX2 (pub. IP) > >> 3: SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> SIP-FAX2 (NAT) > >> 4: SIP-FAX1 (pub. IP) <-> OpenSER <-> OpenPBX <-> SIP-FAX2 (pub. IP) > >> > >> > >> But the following scenario is not working: > >> > >> SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> OpenPBX <-> SIP-FAX2 (pub. IP) > >> > >> > >> > >> It seems to be that the RTPproxy has a problem with the OpenPBX but no > >> Problem with SIP-FAX-ATAs. > >> > >> Does anybody have an idea what's going wrong??? > >> > >> > >> Cheers > >> Bastian > >> > >> _______________________________________________ > >> Users mailing list > >> Users(a)openser.org > >> http://openser.org/cgi-bin/mailman/listinfo/users > >> > > > > > > > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users >

1 0

[Users] T.38 together with OpenSER+RTPProxy and OpenPBX not working
by Bastian Schern 18 Nov '06

18 Nov '06

Hi everybody, I've got a question: Does anybody get T.38 working between OpenPBX and OpenSER + RTPProxy? The following scenarios are working fine: 1: SIP-FAX1 (pub. IP) <-> OpenPBX <-> SIP-FAX2 (pub. IP) 2: SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> SIP-FAX2 (pub. IP) 3: SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> SIP-FAX2 (NAT) 4: SIP-FAX1 (pub. IP) <-> OpenSER <-> OpenPBX <-> SIP-FAX2 (pub. IP) But the following scenario is not working: SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> OpenPBX <-> SIP-FAX2 (pub. IP) It seems to be that the RTPproxy has a problem with the OpenPBX but no Problem with SIP-FAX-ATAs. Does anybody have an idea what's going wrong??? Cheers Bastian

3 5

[Users] t_relay without 100 trying
by Klaus Darilion 17 Nov '06

17 Nov '06

Hi! Is it possible to deactivate the 100 Trying during t_relay? I want to use sl_send_reply("100","trying"), thus the implicit 100 trying during t_relay is not needed. regards klaus -- Klaus Darilion nic.at

5 8

[Serusers] ser ottendorf flags does not parsing strings
by samuel 17 Nov '06

17 Nov '06

I can not use "nat.uac" and "nat.uas" as registrar flags: 0(12872) str2s: ERROR: unexpected char N in NATuac 0(12872) set_mod_param_regex: 'registrar' matches module 'registrar' 0(12872) find_param_export: found <load_nat_flag> in module registrar [/usr/local/lib/ser/modules/registrar.so] 0(12872) set_mod_param_regex: found <load_nat_flag> in module registrar [/usr/local/lib/ser/modules/registrar.so] 0(12872) str2s: ERROR: unexpected char N in NATuas

4 13

[Users] OpenSer and Asterisk
by Marnus van Niekerk 17 Nov '06

17 Nov '06

3 4

RE: [Users] Radius extra: integer attribute type how to
by Pletli Antal 17 Nov '06

17 Nov '06

Bogdan, Thank you.I did it, but doesn't work. I will try to implement my own radius extra solution. Antal -----Original Message----- From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] Sent: Thursday, November 16, 2006 1:19 PM To: Pletli Antal Cc: users(a)openser.org Subject: Re: [Users] Radius extra: integer attribute type how to Hi Antal, If I'm not wrong, all extra accounting information is added as string (it's a limitation because of using several backend), so you may try configuring the attribute in the RADIUS dictionary as string and not integer. regards, bogdan Pletli Antal wrote: > Hello, > > I'm trying the radius-extra feature in openser cvs snapshot. > > In my openser.cfg I set up the following parameter: > > modparam("acc", "radius_extra", > "Acct-Session-Time=$avp(call_length)") > > modparam( "avpops", "avp_aliases", "start_timestamp=i:100") > modparam( "avpops", "avp_aliases", "end_timestamp=i:101") > modparam( "avpops", "avp_aliases", "call_length=i:102") > > (...) > > avp_op("$avp(end_timestamp)","sub/$avp(start_timestamp)"); > > avp_op("$avp(end_timestamp)/$avp(call_length)","sub/$avp(start_timesta > mp)"); > > > > I have experienced that when I sent an Accounting-Stop request to > radius server, it received the integer value as an string and it > decoded the value to the chr code of the "3" > > In the radius log: > > * Attr: 46 - Acct-Delay-Time len: 6 val: 51 > > In the openser.log: > > Nov 14 16:12:09 sip2 ./openser[727]: INFO:avpops:print_avp: > p=0x40623b88, flags=0x0000 > Nov 14 16:12:09 sip2 ./openser[727]: INFO: id=<102> > Nov 14 16:12:09 sip2 ./openser[727]: INFO: > val_int=<3> > > How can I set the corresponding integer attribute in the request? > > Thanks in advance, > > Antal > >----------------------------------------------------------------------- >- > >_______________________________________________ >Users mailing list >Users(a)openser.org >http://openser.org/cgi-bin/mailman/listinfo/users > >

1 0

[Users] Not Hung up Properly...................
by raviprakash sunkara 17 Nov '06

17 Nov '06

Hello Users.... For me The Hung up ( Bye Request not coming to SIP server ) not properly taking Take............... :P Below I metioned the Ngrepped messages.... Help me ........ 2006/11/14 03:01:04.129657 61.17.248.68:5831 -> 192.168.2.90:5060 INVITE sip:102@24.99.145.14 SIP/2.0..v: SIP/2.0/UDP 192.168.2.20:5060;rport;branch=z9hG4bK3F90EDDDCA6F4BD7A0B044CB585A28B9..f: siri <sip:101@24.99.145.1 4>;tag=3410236415..t: <sip:102@24.99.145.14>..m: <sip:101@192.168.2.20:5060>..i: CB3623BF-158D-4124-A1D6-877D2673BBD4@192.168.2.20..CSeq: 41383 INVITE.. Max-Forwards: 70..c: application/sdp..User-Agent: X-Lite release 1103m..l: 135....v=0..o=101 9577234 9577250 IN IP4 192.168.2.20..s=X-Lite..c=IN IP4 192 .168.2.20..t=0 0..m=audio 12222 RTP/AVP 0..a=rtpmap:0 pcmu/8000.. U 2006/11/14 03:01:04.130618 192.168.2.90:5060 -> 61.17.248.68:5831 SIP/2.0 407 Proxy Authentication Required..v: SIP/2.0/UDP 192.168.2.20:5060 ;rport=5831;branch=z9hG4bK3F90EDDDCA6F4BD7A0B044CB585A28B9;received= 61.17.248 .68..f: siri <sip:101@24.99.145.14>;tag=3410236415..t: < sip:102@24.99.145.14>;tag=952b5d87ce2effa04bc4206000ec51df.2411..i:CB3623BF-158D-4124-A1D6-877D 2673BBD4@192.168.2.20..CSeq: 41383 INVITE..Proxy-Authenticate: Digest realm="24.99.145.14", nonce="455978ece372d35484e2a5f0010e0766a823f3a6"..Server: Op enSer (1.1.0-notls (i386/linux))..Content-Length: 0..Warning: 392 192.168.2.90:5060 "Noisy feedback tells: pid=4701 req_src_ip=61.17.248.68req_src_por t=5831 in_uri=sip:102@24.99.145.14 out_uri=sip:102@24.99.145.14via_cnt==1".... U 2006/11/14 03:01:04.628174 61.17.248.68:5831 -> 192.168.2.90:5060 ACK sip:102@24.99.145.14 SIP/2.0..v: SIP/2.0/UDP 192.168.2.20:5060;rport;branch=z9hG4bK3F90EDDDCA6F4BD7A0B044CB585A28B9..f: siri <sip:101@24.99.145.14>; tag=3410236415..t: <sip:102@24.99.145.14>;tag= 952b5d87ce2effa04bc4206000ec51df.2411..m: <sip:101@192.168.2.20:5060>..i: CB3623BF-158D-4124-A1D6-877D2673 BBD4@192.168.2.20..CSeq: 41383 ACK..Max-Forwards: 70..l: 0.... U 2006/11/14 03:01:04.642913 61.17.248.68:5831 -> 192.168.2.90:5060 INVITE sip:102@24.99.145.14 SIP/2.0..v: SIP/2.0/UDP 192.168.2.20:5060;rport;branch=z9hG4bKB90C342E73C741EE87BEC21516FF0FF6..f: siri <sip:101@24.99.145.1 4>;tag=3410236415..t: <sip:102@24.99.145.14>..m: <sip:101@192.168.2.20:5060>..i: CB3623BF-158D-4124-A1D6-877D2673BBD4@192.168.2.20..CSeq: 41384 INVITE.. Proxy-Authorization: Digest username="101",realm="24.99.145.14 ",nonce="455978ece372d35484e2a5f0010e0766a823f3a6",response="3f35a6a54ac7c9695824c5443a9bf 512",uri="sip:102@24.99.145.14"..Max-Forwards: 70..c: application/sdp..User-Agent: X-Lite release 1103m..l: 135....v=0..o=101 9577234 9577250 IN IP4 192 .168.2.20..s=X-Lite..c=IN IP4 192.168.2.20..t=0 0..m=audio 12222 RTP/AVP 0..a=rtpmap:0 pcmu/8000.. U 2006/11/14 03:01:04.644799 192.168.2.90:5060 -> 61.17.248.68:5831 SIP/2.0 100 trying -- your call is important to us..v: SIP/2.0/UDP 192.168.2.20:5060 ;rport=5831;branch=z9hG4bKB90C342E73C741EE87BEC21516FF0FF6;received= 61.17.248.68..f: siri <sip:101@24.99.145.14>;tag=3410236415..t: < sip:102@24.99.145.14>..i: CB3623BF-158D-4124-A1D6-877D2673BBD4@192.168.2.20..CSeq: 4138 4 INVITE..Server: OpenSer (1.1.0-notls (i386/linux))..Content-Length: 0..Warning: 392 192.168.2.90:5060 "Noisy feedback tells: pid=4701 req_src_ip=61.1 7.248.68 req_src_port=5831 in_uri=sip:102@24.99.145.14 out_uri= sip:102@192.168.2.45:5060 via_cnt==1".... U 2006/11/14 03:01:04.645093 192.168.2.90:5060 -> 61.17.248.68:5060 INVITE sip:102@192.168.2.45:5060 SIP/2.0..Record-Route: <sip:192.168.2.90;lr=on;ftag=3410236415>..Via: SIP/2.0/UDP 192.168.2.90;branch=z9hG4bK535d.31f40 331.0..v: SIP/2.0/UDP 192.168.2.20:5060;received=61.17.248.68;rport=5831;branch=z9hG4bKB90C342E73C741EE87BEC21516FF0FF6..f: siri <sip:101@24.99.145.14>; tag=3410236415..t: <sip:102@24.99.145.14>..m: <sip:101@61.17.248.68:5831>..i: CB3623BF-158D-4124-A1D6-877D2673BBD4@192.168.2.20..CSeq: 41384 INVITE..Pro xy-Authorization: Digest username="101",realm="24.99.145.14 ",nonce="455978ece372d35484e2a5f0010e0766a823f3a6",response="3f35a6a54ac7c9695824c5443a9bf512 ",uri="sip:102@24.99.145.14"..Max-Forwards: 69..c: application/sdp..User-Agent: X-Lite release 1103m..Content-Length: 162....v=0..o=101 9577234 9577250 IN IP4 192.168.2.20..s=X-Lite..c=IN IP4 61.17.248.68..t=0 0..m=audio 12222 RTP/AVP 0..a=rtpmap:0 pcmu/8000..a=oldmediaip:192.168.2.20.. U 2006/11/14 03:01:05.223317 192.168.2.90:5060 -> 61.17.248.68:5060 INVITE sip:102@192.168.2.45:5060 SIP/2.0..Record-Route: <sip:192.168.2.90;lr=on;ftag=3410236415>..Via: SIP/2.0/UDP 192.168.2.90;branch=z9hG4bK535d.31f40 331.0..v: SIP/2.0/UDP 192.168.2.20:5060;received=61.17.248.68;rport=5831;branch=z9hG4bKB90C342E73C741EE87BEC21516FF0FF6..f: siri <sip:101@24.99.145.14>; tag=3410236415..t: <sip:102@24.99.145.14>..m: <sip:101@61.17.248.68:5831>..i: CB3623BF-158D-4124-A1D6-877D2673BBD4@192.168.2.20..CSeq: 41384 INVITE..Pro xy-Authorization: Digest username="101",realm="24.99.145.14 ",nonce="455978ece372d35484e2a5f0010e0766a823f3a6",response="3f35a6a54ac7c9695824c5443a9bf512 ",uri="sip:102@24.99.145.14"..Max-Forwards: 69..c: application/sdp..User-Agent: X-Lite release 1103m..Content-Length: 162....v=0..o=101 9577234 9577250 IN IP4 192.168.2.20..s=X-Lite..c=IN IP4 61.17.248.68..t=0 0..m=audio 12222 RTP/AVP 0..a=rtpmap:0 pcmu/8000..a=oldmediaip:192.168.2.20.. U 2006/11/14 03:01:05.674174 61.17.248.68:5060 -> 192.168.2.90:5060 SIP/2.0 100 Trying..v: SIP/2.0/UDP 192.168.2.90;branch= z9hG4bK535d.31f40331.0;received=24.99.145.14..v: SIP/2.0/UDP 192.168.2.20:5060;received=61.17.248 .68;rport=5831;branch=z9hG4bKB90C342E73C741EE87BEC21516FF0FF6..f: siri < sip:101@24.99.145.14>;tag=3410236415..t: <sip:102@24.99.145.14 >;tag=3539775680.. m: <sip:102@192.168.2.45:5060>..Record-Route: <sip:192.168.2.90;lr=on;ftag=3410236415>..i: CB3623BF-158D-4124-A1D6-877D2673BBD4@192.168.2.20..CSeq: 4138 4 INVITE..Server: X-Lite release 1103m..l: 0.... ----------------------------------------------------------- Now the starts Ring at both ends points .......... -------------------------------------------------- When the phone is pick up ............ it send the Reply only 200 Ack......... 2006/11/14 03:01:06.263035 192.168.2.90:5060 -> 61.17.248.68:5831 SIP/2.0 180 Ringing..v: SIP/2.0/UDP 192.168.2.20:5060;received= 61.17.248.68;rport=5831;branch=z9hG4bKB90C342E73C741EE87BEC21516FF0FF6..f: siri <sip:101@ 24.99.145.14>;tag=3410236415..t: <sip:102@24.99.145.14>;tag=3539775680..m: <sip:102@61.17.248.68:5060>..Record-Route: <sip:192.168.2.90 ;lr=on;ftag=34102 36415>..i: CB3623BF-158D-4124-A1D6-877D2673BBD4@192.168.2.20..CSeq: 41384 INVITE..Server: X-Lite release 1103m..l: 0.... U 2006/11/14 03:01:22.633879 61.17.248.68:5060 -> 192.168.2.90:5060 SIP/2.0 200 Ok..v: SIP/2.0/UDP 192.168.2.90;branch=z9hG4bK535d.31f40331.0 ;received=24.99.145.14..v: SIP/2.0/UDP 192.168.2.20:5060;received= 61.17.248.68; rport=5831;branch=z9hG4bKB90C342E73C741EE87BEC21516FF0FF6..f: siri < sip:101@24.99.145.14>;tag=3410236415..t: <sip:102@24.99.145.14>;tag=3539775680..m: < sip:102@192.168.2.45:5060>..Record-Route: <sip:192.168.2.90;lr=on;ftag=3410236415>..i: CB3623BF-158D-4124-A1D6-877D2673BBD4@192.168.2.20..CSeq: 41384 IN VITE..c: application/sdp..Server: X-Lite release 1103m..l: 135....v=0..o=102 6553093 6570062 IN IP4 192.168.2.45..s=X-Lite..c=IN IP4 192.168.2.45..t=0 0 ..m=audio 12222 RTP/AVP 0..a=rtpmap:0 pcmu/8000.. U 2006/11/14 03:01:22.634713 192.168.2.90:5060 -> 61.17.248.68:5831 SIP/2.0 200 Ok..v: SIP/2.0/UDP 192.168.2.20:5060;received=61.17.248.68;rport=5831;branch=z9hG4bKB90C342E73C741EE87BEC21516FF0FF6..f: siri <sip:101@24.99 .145.14>;tag=3410236415..t: <sip:102@24.99.145.14>;tag=3539775680..m: < sip:102@61.17.248.68:5060>..Record-Route: <sip:192.168.2.90 ;lr=on;ftag=3410236415 >..i: CB3623BF-158D-4124-A1D6-877D2673BBD4@192.168.2.20..CSeq: 41384 INVITE..c: application/sdp..Server: X-Lite release 1103m..l: 135....v=0..o=102 6553 093 6570062 IN IP4 192.168.2.45..s=X-Lite..c=IN IP4 192.168.2.45..t=00..m=audio 12222 RTP/AVP 0..a=rtpmap:0 pcmu/8000.. ---------------------------------- That this Time when the User agents are Hung up the Bye Request not coming to sip server at all........... Below logs are from x-lite after the Invite method processed SEND TIME: 6581140 SEND >> 24.99.145.14:5060 SIP/2.0 200 Ok v: SIP/2.0/UDP 192.168.2.90;branch=z9hG4bK535d.31f40331.0;received= 24.99.145.14 v: SIP/2.0/UDP 192.168.2.20:5060;received=61.17.248.68 ;rport=5831;branch=z9hG4bKB90C342E73C741EE87BEC21516FF0FF6 f: siri <sip:101@24.99.145.14>;tag=3410236415 t: <sip:102@24.99.145.14>;tag=3539775680 m: <sip:102@192.168.2.45:5060> Record-Route: <sip:192.168.2.90;lr=on;ftag=3410236415> i: CB3623BF-158D-4124-A1D6-877D2673BBD4(a)192.168.2.20 CSeq: 41384 INVITE c: application/sdp Server: X-Lite release 1103m l: 135 v=0 o=102 6553093 6570062 IN IP4 192.168.2.45 s=X-Lite c=IN IP4 192.168.2.45 t=0 0 m=audio 12222 RTP/AVP 0 a=rtpmap:0 pcmu/8000 SEND TIME: 6602609 SEND >> 192.168.2.90:5060 BYE sip:101@61.17.248.68:5831 SIP/2.0 v: SIP/2.0/UDP 192.168.2.45:5060 ;rport;branch=z9hG4bK827A50D7ABED4E0ABA350E5487A52AB9 f: <sip:102@24.99.145.14>;tag=3539775680 t: siri <sip:101@24.99.145.14>;tag=3410236415 m: <sip:102@192.168.2.45:5060> Route: <sip:192.168.2.90;lr=on;ftag=3410236415> i: CB3623BF-158D-4124-A1D6-877D2673BBD4(a)192.168.2.20 CSeq: 31544 BYE Max-Forwards: 70 User-Agent: X-Lite release 1103m l: 0 SEND TIME: 6604140 SEND >> 192.168.2.90:5060 BYE sip:101@61.17.248.68:5831 SIP/2.0 v: SIP/2.0/UDP 192.168.2.45:5060 ;rport;branch=z9hG4bK827A50D7ABED4E0ABA350E5487A52AB9 f: <sip:102@24.99.145.14>;tag=3539775680 t: siri <sip:101@24.99.145.14>;tag=3410236415 m: <sip:102@192.168.2.45:5060> Route: <sip:192.168.2.90;lr=on;ftag=3410236415> i: CB3623BF-158D-4124-A1D6-877D2673BBD4(a)192.168.2.20 CSeq: 31544 BYE Max-Forwards: 70 User-Agent: X-Lite release 1103m l: 0 ECEIVE TIME: 6606187 RECEIVE << 24.99.145.14:5060 SEND TIME: 6607390 SEND >> 192.168.2.90:5060 BYE sip:101@61.17.248.68:5831 SIP/2.0 v: SIP/2.0/UDP 192.168.2.45:5060 ;rport;branch=z9hG4bK827A50D7ABED4E0ABA350E5487A52AB9 f: <sip:102@24.99.145.14>;tag=3539775680 t: siri <sip:101@24.99.145.14>;tag=3410236415 m: <sip:102@192.168.2.45:5060> Route: <sip:192.168.2.90;lr=on;ftag=3410236415> i: CB3623BF-158D-4124-A1D6-877D2673BBD4(a)192.168.2.20 CSeq: 31544 BYE Max-Forwards: 70 User-Agent: X-Lite release 1103m l: 0 RECEIVE TIME: 6666312 RECEIVE << 24.99.145.14:5060 _ -- Thanks and Regards Ravi Prakash Sunkara ravi.sunkara(a)hyperion-tech.com M:+91 9985077535 O:+91 40 23114549 F:+91 40 40208727 ravi.sunkara(a)hyperion-tech.com www.hyperion-tech.com

1 0

[Serusers] SER database migration tool
by Jan Janak 17 Nov '06

17 Nov '06

Hello, A new SER database migration tool is available at: http://iptel.org/ser/migrate_db The tool can be used to migrate the contents of the old SER database used in releases 0.9.x into the new schema used in 0.10.x. Please report bugs to serdev(a)iptel.org Jan.

1 0

RE: [Users] Presence server with MySQL >=5.0.26
by Watkins, Bradley 16 Nov '06

16 Nov '06

> -----Original Message----- > From: users-bounces(a)openser.org > [mailto:users-bounces@openser.org] On Behalf Of Mike Williams > Sent: Thursday, November 16, 2006 12:31 PM > To: users(a)openser.org > Subject: Re: [Users] Presence server with MySQL >=5.0.26 > > All, > > I would still be in favor of moving all of the tables over to > having the primary key be an autoincremented unsigned int. > > > Mike Williams I'm certainluy not opposed to this, especially with the "oh yeah, UTF-8" clue bat Norman hit me with. ;) I was mostly pointing out that there is nothing inherent in MySQL 5.0.26 and up that precludes this table definition (unless you're using UTF-8, of course). - Brad The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

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