Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(1) |
Jul
(1) |
Aug
(1) |
Sep
(11) |
Oct
(10) |
Nov
(10) |
Dec
(6) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(16) |
Feb
(4) |
Mar
(9) |
Apr
(17) |
May
(22) |
Jun
(6) |
Jul
(7) |
Aug
(7) |
Sep
(5) |
Oct
(7) |
Nov
(9) |
Dec
(7) |
| 2008 |
Jan
(11) |
Feb
(5) |
Mar
(7) |
Apr
(6) |
May
(5) |
Jun
(6) |
Jul
(16) |
Aug
(15) |
Sep
(14) |
Oct
(14) |
Nov
(17) |
Dec
(14) |
| 2009 |
Jan
(13) |
Feb
(24) |
Mar
(10) |
Apr
(9) |
May
(27) |
Jun
(30) |
Jul
(20) |
Aug
|
Sep
(4) |
Oct
(6) |
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
1
|
2
|
3
|
|
4
(1) |
5
|
6
|
7
|
8
|
9
(2) |
10
|
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
|
25
(1) |
26
|
27
(3) |
28
(1) |
29
|
30
(1) |
31
|
|
From: Edson Rodriguez <erodrigu@es...> - 2007-03-30 21:58:06
|
I have noticed terrible pixeling when connecting from xMeeting to = xMeeting (MacBook to Mac Mini). Has anyone seen this or know why this = happens? I have tried different speed configs and codecs H.261, H.263 and = H.264... All of them with same results.=20 Help! Edson ***************************************************************** Edson Rodriguez Network=A0Support Specialist, K-20 Video RITU erodrigu@... ***************************************************************** |
|
From: Edson Rodriguez <erodrigu@es...> - 2007-03-28 16:59:09
|
Does anyone have a list of cameras that are supported by xMeeting?... I'm looking for a good camera for my mac, but not an iSight that costs $350. Please let me know, thanks! ***************************************************************** Edson Rodriguez Network Support Specialist, K-20 Video ITU erodrigu@... ***************************************************************** -----Original Message----- From: xmeeting-application-bounces@... [mailto:xmeeting-application-bounces@...] On Behalf Of Hannes Friederich Sent: Tuesday, March 27, 2007 8:50 AM To: Terrence Durkin Cc: xmeeting-application@... Subject: Re: [Xmeeting-application] Call window disappears in non-primaryscreen. Hello, Thank you for your feedback. We will analyze this. With best regards, Hannes Friederich On 27. Mrz 2007, at 15:46, Terrence Durkin wrote: > Hello - > > I use two monitors. When I have the call window on my second screen=20 > and the XMeeting application looses focus, the call window disappears. > I can get it back by switching focus back to XMeeting. When I have=20 > the call window on my primary screen and the application looses focus, > the call window stays put. > > Thanks. > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT Join=20 > SourceForge.net's Techsay panel and you'll get the chance to share=20 > your opinions on IT & business topics through brief surveys-and earn=20 > cash http://www.techsay.com/default.php? > page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV > _______________________________________________ > Xmeeting-application mailing list > Xmeeting-application@... > https://lists.sourceforge.net/lists/listinfo/xmeeting-application ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ Xmeeting-application mailing list Xmeeting-application@... https://lists.sourceforge.net/lists/listinfo/xmeeting-application |
|
From: Hannes Friederich <hannesf@ee...> - 2007-03-27 15:49:53
|
Hello, Thank you for your feedback. We will analyze this. With best regards, Hannes Friederich On 27. Mrz 2007, at 15:46, Terrence Durkin wrote: > Hello - > > I use two monitors. When I have the call window on my second > screen and > the XMeeting application looses focus, the call window disappears. I > can get it back by switching focus back to XMeeting. When I have the > call window on my primary screen and the application looses focus, the > call window stays put. > > Thanks. > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Xmeeting-application mailing list > Xmeeting-application@... > https://lists.sourceforge.net/lists/listinfo/xmeeting-application |
|
From: Hannes Friederich <hannesf@ee...> - 2007-03-27 15:44:22
|
Hello, This is not possible at the moment. If such a feature ever will appear, is open. With best regards, Hannes Friederich On 25. Mrz 2007, at 21:40, Pierre Lemercier wrote: > Is it possible to connect a telephone (skype specific?, others?) to > a mac (USB ?. wifi?) and use it with Xmeeting? > regards > > Pierre > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV________________________________ > _______________ > Xmeeting-application mailing list > Xmeeting-application@... > https://lists.sourceforge.net/lists/listinfo/xmeeting-application |
|
From: Terrence Durkin <terry@te...> - 2007-03-27 13:48:18
|
Hello - I use two monitors. When I have the call window on my second screen and the XMeeting application looses focus, the call window disappears. I can get it back by switching focus back to XMeeting. When I have the call window on my primary screen and the application looses focus, the call window stays put. Thanks. |
|
From: Pierre Lemercier <pierre.lemercier@fr...> - 2007-03-25 19:40:35
|
Is it possible to connect a telephone (skype specific?, others?) to a mac (USB ?. wifi?) and use it with Xmeeting? regards Pierre |
|
From: Hannes Friederich <hannesf@ee...> - 2007-03-09 13:34:03
|
Hello, Please excuse the late replay, I was away the last days. The normal preferences are stored at the common place for preferences. For xmeeting this will be ~/Library/Preferences/net.sourceforge.xmeeting.XMeeting.plist Please note that passwords are stored in the system's keychain, =20 however. I suggest that you review / retype the password settings in =20 XMeeting. Also, I'm interested to see a debug log from such an unsuccessful =20 registration attempt. (Preferences->General->Generate debug log) Thanks Hannes Friederich On 4. Mrz 2007, at 22:20, silvain traynard wrote: > I can't understand: > In November, I was using XMeeting with SIP from provider Free on my > macBookPro (OS 10.8.4) No problem > > Due to water accident, I change og MacBookPro end I try again to =20 > connect > after synchronize between the two disk: > Now I have an error message: > Impossible de s'enregistrer sur le registrar SIP "freephonie.net" (403 > Forbidden). > > I tried to modify information on my providers page, on XMeeting > preferences, but nothing is doing. > > I tried to uninstall XMeeting, but I don't know where are the > informations: it always remember the connexion info when I re-=20 > intall it. > > Other users says to me that XMeeting still function with SIP of =20 > Free... > then, if you have any ideas... thanks > --=20 > Silvain Traynard > V=E9t=E9rinaire et Bases de donn=E9es 4D > Chiens Terre-neuves > Vend=E9e, France, Terre > http://dbtn.traynard.net > > ----------------------------------------------------------------------=20= > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to =20 > share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?=20 > page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV > _______________________________________________ > Xmeeting-application mailing list > Xmeeting-application@... > https://lists.sourceforge.net/lists/listinfo/xmeeting-application |
|
From: Hannes Friederich <hannesf@ee...> - 2007-03-09 13:21:46
|
Hello, Sorry for the late reply, I was away the last two weeks and couldn't =20 answer e-mail. Please note that the usual way to register is 1) To send REGISTER without authorization header 2) Receive 401 unauthorized, which contains the authorization realm 3) Send another REGISTER, this time with the complete authorization =20 header. So the registration process completes in a correct fashion. However, it looks like the GUI isn't notified properly. I'll have to =20 investigate this and contact you off-list Hannes Friederich On 27. Feb 2007, at 19:32, Brian T. Roy wrote: > I know what the problem is from logs, however I do no know if it can > be fixed without a code change: > > 1) Registering with an authenticating SIP proxy > 2) Registration filled out correctly > 3) XMeeting hangs at startup with "Setup. Please wait..." > > =46rom the logs (my SIP Server and XMeeting) it is clear that = XMeeting > sends a REGISTER with no Authorization header... which of course > generates a 401 unauthorized. > At nearly the same time XMeeting sends a REGISTER with an > Authorization header which generates a 200 OK. > > It appears XMeeting gets confused about which response to take as the > "correct" one for registration status. > > Even more weirdness ensues if a call is sent to the user... Invites > are received and processed by the SIP stack for XMeeting... > > Brian Roy > b.t.roy@... > > **********************************************************************=20= > ** > **********************************************************************=20= > ** > **************** > > Here is the XMeeting Debug Log: > > > > 0:00.221 XMeeting.app osutils.cxx(1004) XMeeting.app = Version > 0.3beta4 by XMeeting on Unix Darwin (8.8.2-i386) at 2007/2/27 > 11:24:01.250 > 0:00.221 XMeeting.app osutil.cxx(350) PWLib File = handle high > water mark set: 17 Thread unblock pipe > 0:00.221 XMeeting.app tlibthrd.cxx(837) PWLib Created = thread > 0x13269b0 OpalGarbage > 0:00.221 XMeeting.app tlibthrd.cxx(917) PWLib Thread = high > water mark set: 2 > 0:00.221 XMeeting.app manager.cxx(387) OpalMan Created =20= > manager. > 0:00.221 XMeeting.app endpoint.cxx(226) OpalEP Created > endpoint: xm > 0:00.221 XMeeting.app endpoint.cxx(226) OpalEP Created > endpoint: h323 > 0:00.221 XMeeting.app h4601.cxx(1498) H460 Endpoint = Attached > 0:00.221 XMeeting.app h323ep.cxx(194) H323 Created = endpoint. > 0:00.221 XMeeting.app endpoint.cxx(226) OpalEP Created > endpoint: sip > 0:00.222 XMeeting.app osutil.cxx(350) PWLib File = handle high > water mark set: 19 Thread unblock pipe > 0:00.222 XMeeting.app tlibthrd.cxx(837) PWLib Created = thread > 0x13e1ed0 Housekeeper > 0:00.222 XMeeting.app tlibthrd.cxx(917) PWLib Thread = high > water mark set: 3 > 0:00.222 XMeeting.app sipep.cxx(724) SIP Created = endpoint. > 0:00.222 XMeeting.app manager.cxx(918) OpalMan Added = route > "xm:.*=3Dh323:<da>" > 0:00.222 XMeeting.app manager.cxx(918) OpalMan Added = route > "h323:.*=3Dxm:<da>" > 0:00.222 XMeeting.app manager.cxx(918) OpalMan Added = route > "xm:.*=3Dsip:<da>" > 0:00.223 OpalGarbage tlibthrd.cxx(1338) PWLib Started = thread > 0x13269b0 OpalGarbage > 0:00.223 Housekeeper tlibthrd.cxx(1338) PWLib Started = thread > 0x13e1ed0 Housekeeper > 0:00.223 XMeeting.app manager.cxx(918) OpalMan Added = route > "sip:.*=3Dxm:<da>" > 0:00.450 ThreadID=3D0x0xa000cfc0 XMOpalManager.cpp(578) = 2007-02-27 > 11:24:01 Switched active location to "Home" > 0:00.606 ThreadID=3D0x0xa000cfc0 XMOpalManager.cpp(578) = 2007-02-27 > 11:24:01 Switched video device to "=0FBuilt-in iSight" > 0:00.609 XMeeting.app osutil.cxx(350) PWLib File = handle high > water mark set: 20 PTCPSocket > 0:00.609 XMeeting.app osutil.cxx(350) PWLib File = handle high > water mark set: 25 Thread unblock pipe > 0:00.609 XMeeting.app tlibthrd.cxx(837) PWLib Created = thread > 0x1326fc0 Opal Listener:%x > 0:00.609 XMeeting.app tlibthrd.cxx(917) PWLib Thread = high > water mark set: 4 > 0:00.609 Opal Liste...er:1326fc0 tlibthrd.cxx(1338) PWLib=09 > Started thread 0x1326fc0 Opal Listener:1326fc0 > 0:00.609 Opal Liste...er:1326fc0 transports.cxx(961) Listen=09= > Started listening thread on tcp$*:5060 > 0:00.609 XMeeting.app osutil.cxx(350) PWLib File = handle high > water mark set: 26 PUDPSocket > 0:00.609 Opal Liste...er:1326fc0 transports.cxx(1187) Listen=09= > Waiting on socket accept on tcp$*:5060 > 0:00.610 XMeeting.app osutil.cxx(350) PWLib File = handle high > water mark set: 27 PUDPSocket > 0:00.610 XMeeting.app transports.cxx(1241) Listen Error in = UDP > listen: Can't assign requested address > 0:00.610 XMeeting.app osutil.cxx(350) PWLib File = handle high > water mark set: 28 PUDPSocket > 0:00.610 XMeeting.app osutil.cxx(350) PWLib File = handle high > water mark set: 30 Thread unblock pipe > 0:00.610 XMeeting.app tlibthrd.cxx(837) PWLib Created = thread > 0xd87f030 Opal Listener:%x > 0:00.610 XMeeting.app tlibthrd.cxx(917) PWLib Thread = high > water mark set: 5 > 0:00.610 Opal Liste...er:d87f030 tlibthrd.cxx(1338) PWLib=09 > Started thread 0xd87f030 Opal Listener:d87f030 > 0:00.610 Opal Liste...er:d87f030 transports.cxx(961) Listen=09= > Started listening thread on udp$*:5060 > 0:00.610 Opal Liste...er:d87f030 transports.cxx(1303) Listen=09= > Waiting on UDP packet on udp$*:5060 > 0:00.611 XMeeting.app osutil.cxx(350) PWLib File = handle high > water mark set: 33 PUDPSocket > 0:00.611 XMeeting.app osutil.cxx(350) PWLib File = handle high > water mark set: 35 PUDPSocket > 0:00.611 XMeeting.app transports.cxx(1696) OpalUDP Binding = to > interface: 0.0.0.0:49402 > 0:00.611 XMeeting.app sipep.cxx(870) SIP Created = transport > udp$0.0.0.0<if=3Dudp$0.0.0.0:49402> > 0:00.612 XMeeting.app transports.cxx(1805) OpalUDP Started > connect to 192.168.0.4:5070 > 0:00.612 XMeeting.app osutil.cxx(350) PWLib File = handle high > water mark set: 36 PUDPSocket > 0:00.612 XMeeting.app transports.cxx(1841) OpalUDP = Connecting to > interfaces: > 127.0.0.1 (lo0) > 192.168.0.100 (en1) > > 0:00.612 XMeeting.app osutil.cxx(357) PWLib File = handle low > water mark set: 35 PUDPSocket > 0:00.612 XMeeting.app osutil.cxx(350) PWLib File = handle high > water mark set: 37 Thread unblock pipe > 0:00.612 XMeeting.app tlibthrd.cxx(837) PWLib Created = thread > 0xd8807a0 SIP Transport:%x > 0:00.612 XMeeting.app tlibthrd.cxx(917) PWLib Thread = high > water mark set: 6 > 0:00.612 SIP Transp...rt:d8807a0 tlibthrd.cxx(1338) PWLib=09 > Started thread 0xd8807a0 SIP Transport:d8807a0 > 0:00.612 SIP Transp...rt:d8807a0 sipep.cxx(778) SIP = Read > thread started. > 0:00.612 SIP Transp...rt:d8807a0 sipep.cxx(896) SIP = Waiting > for PDU on udp$192.168.0.4:5070<if=3Dudp$192.168.0.100:5000> > 0:00.613 XMeeting.app sippdu.cxx(1960) SIP Sending = PDU on udp > $192.168.0.4:5070<if=3Dudp$192.168.0.100:5000> > REGISTER sip:mainsip.brianandkelly.ws SIP/2.0 > CSeq: 1 REGISTER > Via: SIP/2.0/UDP 192.168.0.100:5000;branch=3Dz9hG4bKf878c35d-fdc4- > db11-90ae-ae707c2e5b3c;rport > User-Agent: XMeeting/0.3.4 > From: <sip:briantroy@...:5070>;tag=3D7272c35d-fdc4-= > db11-90ae-ae707c2e5b3c > Call-ID: 2e20c35d-fdc4-db11-90ae-ae707c2e5b3c@... > To: <sip:briantroy@...:5070> > Contact: <sip:briantroy@...:5000;transport=3Dudp> > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE,INFO,PING > Expires: 3600 > Content-Length: 0 > Max-Forwards: 70 > > > 0:00.624 SIP Transp...rt:d8807a0 sippdu.cxx(1923) SIP = PDU > Received on udp$192.168.0.4:5070<if=3Dudp$192.168.0.100:5000> > SIP/2.0 401 Unauthorized > CSeq: 1 REGISTER > Via: SIP/2.0/UDP 192.168.0.100:5000;branch=3Dz9hG4bKf878c35d-fdc4- > db11-90ae-ae707c2e5b3c;rport=3D5000 > Server: Sip EXpress router (0.9.6 (i386/linux)) > From: <sip:briantroy@...:5070>;tag=3D7272c35d-fdc4-= > db11-90ae-ae707c2e5b3c > Call-ID: 2e20c35d-fdc4-db11-90ae-ae707c2e5b3c@... > To: <sip:briantroy@...: > 5070>;tag=3D1afbd638d5ae94d730998f36ea78324c.c089 > Warning: 392 royhometel01.santan.brianandkelly.ws:5070 "Noisy > feedback tells: pid=3D26857 req_src_ip=3D192.168.0.100 = req_src_port=3D5000 > in_uri=3Dsip:mainsip.brianandkelly.ws > out_uri=3Dsip:mainsip.brianandkelly.ws via_cnt=3D=3D1" > Content-Length: 0 > WWW-Authenticate: Digest realm=3D"mainsip.brianandkelly.ws", > nonce=3D"45e47869f5ce7a7da58f91270f734f239bdf1097" > > > 0:00.625 SIP Transp...rt:d8807a0 sippdu.cxx(2169) SIP=09 > Transaction 1 REGISTER completed. > 0:00.625 SIP Transp...rt:d8807a0 transports.cxx(1916) OpalUDP=09= > Ended connect, selecting 192.168.0.100:5000 > 0:00.625 SIP Transp...rt:d8807a0 sipep.cxx(1216) SIP=09 > Received Authentication Required response > 0:00.625 SIP Transp...rt:d8807a0 sipep.cxx(1252) SIP=09 > Updated realm to mainsip.brianandkelly.ws > 0:00.626 SIP Transp...rt:d8807a0 sippdu.cxx(1366) SIP = Adding > authentication information > 0:00.626 SIP Transp...rt:d8807a0 sippdu.cxx(1960) SIP=09 > Sending PDU on udp$192.168.0.4:5070<if=3Dudp$192.168.0.100:5000> > REGISTER sip:mainsip.brianandkelly.ws SIP/2.0 > CSeq: 2 REGISTER > Via: SIP/2.0/UDP 192.168.0.100:5000;branch=3Dz9hG4bK7e6ec55d-fdc4- > db11-90ae-ae707c2e5b3c;rport > User-Agent: XMeeting/0.3.4 > Authorization: Digest username=3D"briantroy", > realm=3D"mainsip.brianandkelly.ws", > nonce=3D"45e47869f5ce7a7da58f91270f734f239bdf1097", > uri=3D"sip:mainsip.brianandkelly.ws", algorithm=3Dmd5, > response=3D"3ff88b165f195ecff4a4536ca1b8bfd2" > From: <sip:briantroy@...:5070>;tag=3D7272c35d-fdc4-= > db11-90ae-ae707c2e5b3c > Call-ID: 2e20c35d-fdc4-db11-90ae-ae707c2e5b3c@... > To: <sip:briantroy@...:5070> > Contact: <sip:briantroy@...:5000;transport=3Dudp> > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE,INFO,PING > Expires: 3600 > Content-Length: 0 > Max-Forwards: 70 > > > 0:00.627 SIP Transp...rt:d8807a0 sipep.cxx(896) SIP = Waiting > for PDU on udp$192.168.0.4:5070<if=3Dudp$192.168.0.100:5000> > 0:00.638 SIP Transp...rt:d8807a0 sippdu.cxx(1923) SIP = PDU > Received on udp$192.168.0.4:5070<if=3Dudp$192.168.0.100:5000> > SIP/2.0 200 OK > CSeq: 2 REGISTER > Via: SIP/2.0/UDP 192.168.0.100:5000;branch=3Dz9hG4bK7e6ec55d-fdc4- > db11-90ae-ae707c2e5b3c;rport=3D5000 > Server: Sip EXpress router (0.9.6 (i386/linux)) > From: <sip:briantroy@...:5070>;tag=3D7272c35d-fdc4-= > db11-90ae-ae707c2e5b3c > Call-ID: 2e20c35d-fdc4-db11-90ae-ae707c2e5b3c@... > To: <sip:briantroy@...: > 5070>;tag=3D1afbd638d5ae94d730998f36ea78324c.28e0 > Contact: <sip:briantroy@...>;expires=3D36, > <sip:briantroy@...:5000;transport=3Dudp>;expires=3D3600 > Warning: 392 royhometel01.santan.brianandkelly.ws:5070 "Noisy > feedback tells: pid=3D26860 req_src_ip=3D192.168.0.100 = req_src_port=3D5000 > in_uri=3Dsip:mainsip.brianandkelly.ws > out_uri=3Dsip:mainsip.brianandkelly.ws via_cnt=3D=3D1" > Content-Length: 0 > > > 0:00.638 SIP Transp...rt:d8807a0 sippdu.cxx(2169) SIP=09 > Transaction 2 REGISTER completed. > 0:00.638 SIP Transp...rt:d8807a0 sipep.cxx(896) SIP = Waiting > for PDU on udp$192.168.0.4:5070<if=3Dudp$192.168.0.100:5000> > 0:05.626 Housekeeper sippdu.cxx(2283) SIP Set = state > Terminated_Success for transaction 1 REGISTER > 0:05.639 Housekeeper sippdu.cxx(2283) SIP Set = state > Terminated_Success for transaction 2 REGISTER > ----------------------------------------------------------------------=20= > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to =20 > share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?=20 > page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV > _______________________________________________ > Xmeeting-application mailing list > Xmeeting-application@... > https://lists.sourceforge.net/lists/listinfo/xmeeting-application |
|
From: silvain traynard <silvain@tr...> - 2007-03-04 21:20:50
|
I can't understand: In November, I was using XMeeting with SIP from provider Free on my macBookPro (OS 10.8.4) No problem Due to water accident, I change og MacBookPro end I try again to connect after synchronize between the two disk: Now I have an error message: Impossible de s'enregistrer sur le registrar SIP "freephonie.net" (403 Forbidden). I tried to modify information on my providers page, on XMeeting preferences, but nothing is doing. I tried to uninstall XMeeting, but I don't know where are the informations: it always remember the connexion info when I re-intall it. Other users says to me that XMeeting still function with SIP of Free... then, if you have any ideas... thanks -- Silvain Traynard Vétérinaire et Bases de données 4D Chiens Terre-neuves Vendée, France, Terre http://dbtn.traynard.net |