AMSN & iSight & BT Voyager 205 - not working

Hi All,
I am wanting to use aMSN with my isight and using an ADSL router Voyager 205. However for some reasons (common i understand) the router needs the ports changing to allow the isight to work, checked out how to do it, called BT and still no luck, NOT WORKING. Need it to work to talk to my son in Brasil, and he on Windows!!!!! MSN
Keep getting the message:
type IP-Restrict-NAT
Listening - False
YOu are firewalled or behind a router
Webcam extention is loaded
Capture extention -QuicktimeTcl is loaded
IM not firewalled so it seems it is the router not finding the isight.
It gives a link to a Q & A with solution but doesnt work with my router for some reason.
CAN ANYONE HELP PLEASE.
[email protected] if you can please or [email protected] on MSN (or aMSN)

Hi
Dont Know about aMSN, first try upgrading the firmware on the 205 see http://www.zensupport.co.uk/KnowledgeBase/article.aspx?id=10453 please read carefully.
Also this is how to getting the 205 working in iChat http://discussions.apple.com/thread.jspa?messageID=2772641&#2772641
Also you might be better off using skype, Mac version http://www.skype.com/download/skype/macosx/20beta.html
Pc version http://www.skype.com/download/skype/windows/helloagain.html
Tony

Similar Messages

HT3964 my built-in isight camera will still not work on my macbook pro after completing smc reset. The green light comes on but no video.

my built-in isight camera will still not work on my macbook pro after completing smc reset. The green light comes on but no video.
Any Suggestions?

Restart the computer.

Bluetooth, iSight and Keyboard Backlight not working. Please help!

My Bluetooth stopped working along with my iSight and Keyboard Backlight. I first noticed the weird sign over the bluetooth icon, and it read "Bluetooth not available". I payed no attention to it for a while until I tried to take a picture with Photo Booth and I read "No camera found", for some reason I tried to dim the backlight on the keyboard and a blocked sign appeared under the brightness level, not letting me do anything (Later I was able to use the backlight with the LabTick app). I have tried everything. SMC, PRAM, NVRAM, logging as diferent and new users, booting in safe mode... every solution I have found on the internet has been tested by me. Then I read this about the Hardware Test solution, and surprisingly after performing the Hardware Test no problems were found! So basically my MacBook Pro (mid 2010) is not having any trouble of any sorts with anything. Then why can't I use Bluetooth, iSight or Key backlighting (which only works through LabTick). Given the fact that the hardware test shows no problems I am not comfortable with the idea of taking it to repair. There MUST be something I can actually do to fix these issues.
Does anybody have any idea? I repeat, these are NOT WORKING, NOT FOUND AND NOT AVAILABLE.
- Keyboard Backlight (Only works through LabTick)
- iSight Camera (Not found by any software)
- Bluetooth (No info appears on the system profile, the icon on the menu bar is completely gone)
All three issues happened at the same time, the night before everything was working perfectly fine.
If anyone could help... please!!!
Summary:
MacBook Pro Mid 2010 (http://support.apple.com/kb/SP583) Unibody, can't take out the battery.
Solutions tried:
- Reset SMC: Turning on while holding Shift + Ctrl + Option + Power Button (This makes my MacBook forget about the battery and start up with really loud fan noise, battery icon appears with an X on it, keyboard backlight buttons work, they show brightness level on screen, but the actual light won't work, no bluetooth, no isight)
-Reset PRAM and NVRAM: Turning on while holding Option + CMD + R + P (I have waited for 2 chimes, 3 chimes and 4 chimes at different times, nothing happens. Light, bluetooth and isight are still gone)
-Holding Power Button for 10 seconds, 20 seconds, longer... nothing changes.
-Creating and logging in as new admin user, nothing changes.
-Deleting the bluetooth.plist file and powering off and on again, also rebooting
-Deleting the SystemConfiguration folder, powering off and on again, also rebooting
-Installing "blueutil", didn't help at all, turned it off via terminal with command blueutil off.
-Performing Apple Hardware Test - Shows no erros or problems on any area after one full hour of testing (Performed the extended testing)
-Leaving it powered off overnight
Please anyone help meee!! I can't afford going crazy!
Thank you so much in advance!
Alvarock.

****UPDATE***
Hi guys i got across this forum after searching for bluetooth, front camera and the most ANNOYING no lost keyboard backligth.
After run all the test, procedures, tweeks and, and everything i remenbered that once i sent my MBP to repair at you bring i break, turns out that the little ribbon flex connector coming from the mother board ( from the rigth to left) was loose since the adhesive wich they used shrink do temp changes, anyhow y popped out the glas and found the flex cable totally sticked to the glass pulling out of the pcb board connector, reinstalled it smoothly and that FIXED the camera, bluetooth and keyboard backlight!..
thats it. hope i helped some frustraded owner.

Isight on macbook (internal) not working

okay, I reinstalled (full) the macbook and once I came onto the account picture screen, the camera box displays only green with a strip of static on the top. Once that was done, I decided to test photobooth but still the camera doesn't seem to be able to get any image, just green! Is this a software problem or hardware? Before reinstall, it worked.
Mac mini, MacBook Mac OS X (10.4.7) 1GB, 1.25GB Ram (respectively)

My macbook had the same problem. It began after I installed bootcamp, which I have since updated to 1.1. Whenever I boot into windows xp and then back into Os X, the isight stops working. In photobooth I get a blank green screen with a few scribbling lines of static at the top, but in ichat I get the "in use by other application" error.
I tried a system X reinstall, a bootcamp reinstall, zapping the PRAM, etc. etc. What really killed me was that the isight camera continued to work FINE in windows, but not at all in Os X (I could almost hear Bill Gates snickering).
The solution turned out to be resetting the power management unit by unplugging, removing the battery and holding down the power button for 5 seconds. Works without having to zap PRAM after.
The annoying thing is that I have to do this EVERY TIME after I have booted into windows if I want the camera to work in Os X.
As other users have pointed out, bootcamp now includes a package that updates the isight firmware.
Interestingly, this does NOT happen on my intel iMac, only the macbook.
I'm hoping for a more elegant fix.
Anyone else?
Jason

Built in iSight for Mac Book not working (Hardware related)

I've looked at the "How to troubleshoot iSight" page for the built in cameras, but haven't had any success.
The problem is not Application specific (tried it out with Photo Booth, iMovie, iChat and Address Book.
I haven't tried to see if it's user specific as I'm the only user on my computer, but I have backed up my Hard Disk on an external drive, booted from that, and it still doesn't work (the backup was from several months ago when it did work.) I had been using it yesterday and it worked.
I checked the system profiler, and it does not recognize the iSight.
I followed the instructions for resetting the SMC or PMU for Mac Book/Mac Book Pro (http://docs.info.apple.com/article.html?artnum=303319) and then checked the system profiler again. It still doesn't work.
I think I have a hardware issue that isn't easily solveable, but thought I would post here in case anybody has any more ideas. One thing I did notice however that seemed positive is that the built in microphone still seems to be working. I was under the impression the microphone and iSight were part of the same device, although it seems that may not be the case.

Hi PlentyofPaper654,
You have covered everything. Time for an engineer.
10:54 AM Saturday; January 27, 2007

ISight camera present but not working

System Report lists the camera but it's X'd out
in FaceTime and not present in Skype. After
re-setting NVRAM it appeared briefly then
vanished. Some advise re-setting the SMC
but Apple's own KB didn't support that.

Tom Meade1 wrote:... I followed all steps...
Good. Having eliminated several of the easiest things, we will try the next (more time consuming) things that may resolve your problem.
Tom Meade1 wrote: ... this is our faith, no?...
Not mine, no.
Tom Meade1 wrote:... System Report shows what I think is a camera...
You are correct that your SR report shows that your Mac recognized its inbuilt camera.
Tom Meade1 wrote:... Does it seem like a software issue that can be remedied...
Yes.
Tom Meade1 wrote:... does the Genius have methods beyond what we've done here?...
Yes. The Geniuses have access to proprietary Special Tools, Test Equipment, and Technical Data that allow them to fix things beyond what us users can do. That is why, if all else fails, or if you don't want to take the time to continue trying to resolve this yourself, I suggest you contact Apple or an Apple-Authorized Service Provider for service.
Tom Meade1 wrote:... FaceTime and PhotoBooth still show no camera or X'd out...
Because more than one up-to-date app fails in more than one user account, your Mac's system software may be damaged. The remedy for this is to reinstall OS X. Regardless of the reinstall method you use, backup your Mac before you reinstall OS X.
If your Mac shipped with OS X 10.7, you can use the backup installer that came with your Mac. Then apply the 10.7.5 Combo Update to return to the latest version in one update step. I recommend that you repair permissions before and after installing and updating.
If you do not have a 10.7.x installer, you can use the Lion Recovery HD method Kappy explains in http://discussions.apple.com/thread/3531813.
After reinstalling, test again using the How to Troubleshoot iSight method.
If the problem continues in more than one app and more than one user account, the only remaining thing I know that might remedy the problem is to zero your startup disk and do a clean install of your Apple software. If iSight works then, you know that some other software was causing a conflict. This is a time consuming process that I described in this topic: http://discussions.apple.com/message/18614637. (You will use the current 10.7.5 Combo Update vs. the 10.7.4 version that was current at the time of the referenced post.)
If none of the things recommended to this point resolve your iSight problem, the only remaining suggestion I can offer is to contact Apple or an Apple-Authorized Service Provider for service.
Tom Meade1 wrote:... Is a required to activate iSight?
No.
Message was edited by: EZ Jim
Mac OSX 10.9

2004 external iSight with G4 Ti not working

I've read through many of the comments here, and all seem to point me toward a firewire port failure. See what you think.
Both my external firewire iSight and G4 Ti PB are 2004. I'm running 10.4.11. I was using the iSight only occasionally for much of this time with no problems, then reconnected it and nothing. The curious thing is that when I connect it to the single firewire 400 port on the G4, the green light comes on briefly, then goes off. Here are the particulars.
First, and perhaps foremost, Profiler recognizes the firewire port, but neither iSight or a fairly new firewire drive are recognized (when I initially installed the drive, it was recognized using the firewire connection, and it is still recognized using a 4-pin-to-usb cable).
I can't change the cable on the camera because it is fixed on this model. I did purchase another firewire cable to test with the hard drive, and it was still not recognized by the G4.
iChat, Skype and iMovie now do not see iSight.
At some point I did upgrade from 10.3 to 10.4.X, but don't remember if this was before the G4 iSight.
Haven't installed much new software at all.
I have a 2004 G5 desktop, but it went south in many ways, including inability to see any of its firewire ports, which I have not been able to reset. The fact that system profiler doesn't see either iSight or the hard drive does point to a firewire port failure, but it's hard for me to believe that it would fail with such light use. I've read through the Apple and EZ's trouble shooting tips, tried restarting, fsck, safe boot, etc. Any suggestions?
Thanks,
Greg

macgreg wrote:
Thanks, EZ for taking the time to respond and share your expertise. You are truly a Mac Wiseman (not wiseguy, as we each have occasionally encountered).
I have been using Macs since 1984, and (at my place of work) DOS computers since shortly after that. From my experience, nothing happens by accident, i.e. there is a reason for each of us that we experience what we do. In-which-case, the “strange” failures of both my G5 and G4 must represent a problem for me to solve, a redirection, whatever. And in addition, my lightly-used Book terabyte hard drive failed, started to make a mechanical clicking sound and won’t boot (so this be sorta like the trials of Job)... (quote extracted for comment below)
I have done a clean install of 10.4 on the G5 and G4 separately. I have run diagnostics (TechTool Pro, etc.) that return no hardware problems.
Regarding longevity, when the G5 was about 3.5 or so years old, it began to get kernal panics, freeze, gray screen with reboot instructions, etc. I took it to the Apple store and they told me it was either the power supply or CPU. I asked them to fix it, said I’d pay. When I retrieved it, they said it was the power supply. I paid them several hundred dollars, took it home, and it began experiencing the same sorts of kernal panics, etc. just on the other side of the 90-day warranty.
Apparently, it wasn’t they who were at fault. It was, from all I have learned since on these and other discussion boards, a simple matter of longevity (I tried many of the recommendations, swapping ram, software stuff such as safe boot, fsck, all the usual and even odd remedies, etc.). Then the G4 PB began to fail, though not quite as seriously. Perhaps we have a waft of Radon coming up through the basement floor. I will have this checked.
In any case, I am not prone to trust the Apple store, especially if the situation is based on simple longevity, and finances are tight. We do have a Mac repair business in the neighborhood, and I believe in supporting local business.
As I mentioned, I now have no firewire on either computer, although the G4 at least recognizes its firewire port. I tried the firewire reset on both computers without success. I have used the camera to connect to two important people – my son and his family in D.C., and my longtime friend in Japan, Go figure! I still have Skype and Jajah voice, but ya just can’t beat video.
Ever see the film “The Ghost in the Machine”? . . .
Thanks again for your time,
Greg
You're welcome, Greg
Thanks for the additional info.
It is apparent from your latest post that you are an experienced user who can make whatever possible meaningful use of the info I shared in my previous post without further input from me. I will offer only a few responses regarding your latest post:
My iSight camera came directly from Apple and does have a cable “hard-wired” to its. It must be one of the first models. It has a dome base with a bendable goose neck about 2’ high and the actual camera piece plugs in to a firewire connection at the top of the goose neck. It hasn’t been stored, just sitting on the table by the computer with a lens cap on to protect it, with all plugged into an industrial-strength surge protector.
(1) Between the above quote and your exchange with Defcom regarding Sightflex versus iSight, I am confused.
I cannot understand how a "base that can't be disconnected" can have "the actual camera piece plugs in to a firewire connection at the top of the goose neck". Connections that plug in would seem to be directly contrary to anything that cannot be disconnected.
Moreover, although you may have bought them at the same time, the Sightflex base is NOT an Apple product, nor is it part of iSight.
Perhaps your meaning for "iSight" either interchanges or combines the Apple iSight camera with the Sightflex mounting stand from Flex Cable.
Notwithstanding the above, it should be easy to use the testing suggestions I offered in my previous post to verify whether your external iSight will work on another Mac that has known working Firewire connections. That test will tell you whether you must consider repairing your iSight itself, and possibly the SightFlex cables or connections, in addition to your Macs' Firewire problems.
(2) Regarding longevity, my previous Tower Mac (Power Mac G5 Dual-Processor) served me daily for more than 5 years without any problem. Of course, like yours, it never ran except "plugged into an industrial-strength surge protector."
Although I sold my G5 when I got my new iNtel Macs, my external iSights still work with all my Firewire equipped Macs.
My old G3 iBook SE is so old that it did not ever have Firewire. It traveled with me for several years, including many cross-country trips in the saddlebags of my motorcycles! Nowadays, my wife knows it so well she does not want to give it up, so I keep replacing the battery every couple of years, and she keeps using it every day. The iBook will NOT quit.
Based on the difference in our longevity experiences, you may be wise to check for radon.
(3) You have done a lot of research and troubleshooting, but, if you have not already seen these articles, you might want to consider whether they have anything you might find useful:
http://www.ralphjohns.co.uk/EZJim/EZJimpage22.html
http://www.ralphjohns.co.uk/EZJim/EZJimpage19.html
(Other readers note that OS X 10.5 and later do NOT require manually running Chrons.)
http://www.ralphjohns.co.uk/EZJim/EZJimpage20.html
(4) If none of the ideas suggested here help you, an external UVC (USB) webcam might be the easiest way for you to get video chat capability back. Note: In order for UVC devices to work without additional drivers, you will need to update to at least Mac OS X 10.4.9:
http://support.apple.com/kb/DL267
The latest version, OS X 10.4.11, would be better: http://support.apple.com/kb/DL170
EZ Jim
Mac Pro Quad Core (Early 2009) 2.93Ghz w/Mac OS X (10.6.2) MacBook Pro (13 inch, Mid 2009) 2.26GHz (10.6.2)
LED Cinema Display G4 PowerBook 1.67GHz (10.4.11) iBookSE 366MHz (10.3.9) External iSight

Isight built-in is not working with imovies6 in OS 10.4.9

my built-in isight camera was working fine with imovie6 till the time my Mac OS was 10.4.6,after updating my Mac OS to 10.4.9 my isight stop working with imovie.I updated my Mac OS with combo update

Hi Harinder,
Have you Repaired Permissions since doing the Update ?
4:44 PM Monday; June 11, 2007

ISight built in flash not working

I took pictures on the photo booth last week and the built in flash was working just fine.. it would do the countdown and it would brighten up the image. Today, I tried taking a picture and the flash would go off (screen turn bright white) but the image would look as if my flash did not go off. the images are dark.. is this a software issue or a hardware issue? should I take it in to get checked??

• If Apple's http://support.apple.com/kb/HT2090
   suggestions do not help you, (the "reset" suggested there
   often restores normal function,) continue with the following.
• Use Disk Utility to repair permissions and then
   download and apply the 10.7.2 Combo Update:
     http://support.apple.com/kb/DL1459
• Repair permissions again immediately following the system restart
   that completes the Combo update.
The Combo version of updates can sometimes correct
strange problems like yours.

ISight and Windows (AIM) not working?

so i have a macbook pro, and am trying to video chat with a friend on a windows machine back home. He has AIM, and it says the connection was interrupted or that he declined the invitation. Why doesn't it work across platforms? Ive looked thru these forums, and tried all the trobulshooting and googling answers until my fingers bleed, but to no avail. any suggestions?
And I dont want to use skype unless absolutely necessary.

You might be better off using Skype.
Mac version http://www.skype.com/intl/en-gb/download/skype/macosx/
Pc http://www.skype.com/intl/en-gb/download/skype/windows/
Or web based http://www.mebeam.com/

Isight firewire cam not working in iChat on Leopard.

After installing Leopard on my Powerbook G4 867 dvi, my Isight Firewire Cam is not working anymore
in Ichat on Leopard.
Any solutions, it worked fine under Tiger.
Isight firewire cam works fine wirh Skype, Amsn , Photobooth and Quicktime.

Alright. I've done quite a bit of testing now.
My system is (as stated below,) a 12" PowerBook G4, 867 MHz, 640 MB RAM, 40 GB hard drive, Combo drive, AirPort Extreme. It was purchased in Summer 2003, and while the OS has been reloaded, it hasn't been for a long time, and at present, the OS was an install of Jaguar that was upgraded to Panther to Tigard, finally to Leopard.
I was experiencing the issue mentioned. In my case, I use a FireWire miniDV camcorder for video in iChat. It has worked fine in the iChat AV beta in Jaguar, and iChat AV in Panther and Tiger.
Upon upgrading to Leopard, I get the "Slow Network" explanation for why I cannot use video (or hosting multiperson audio, or screen sharing.)
My research shows the following:
This occurs both on the upgraded install, and a fresh install. (To an external hard drive.)
Using Ecamm's PowerBoost allows me to use every option that isn't barred outright by lack of hardware (video effects.) This includes both "Slow Network" issues and "Insufficient CPU" issues (essentially just multiperson video.)
So my guess is that the "Slow Network" is indeed a "bug", and will be fixed by an update from Apple.

Charging problems Macbook Pro 13 not MagSafe related + isight not working

Having weird problems with my MacBook Pro 13 (MacBookPro5,5). I bought this needing repair and replaced the LCD, the LCD Glass, the Camera/mic cable, and bought a used battery because the old one showed "Service Now". Just when I thought putting all this work in would get me going, I ran into two different problems that are driving me crazy.
The battery will not charge with any magsafe attached (I have quite a few). The only way I can get it to finally charge is to remove the bottom cover, unplug the battery, and use a new, l-shape 85W Power supply to get it to charge again, It charges ONLY until I remove it. Once I remove the power suppy...even for a second, I will not light up again and it will go on battery power until it disappates (then I start all over ). I've tried every reset in the book, so it has nothing to do with the PMR or SMC (or however they are named). Also, before anyone asks...the old "Service Now" battery behaves exactly the same way .
The isight camera STILL does not work, even with the new cable. Furthermore, I had another cover for the same unit with a camera in it and its own cable and tried to use the camera with that setup, and it still did not work. My guess is there is either an issue with logic board or the cable connector on the logic board.
The Apple Hardware test passes perfectly every time I run it (quick and extended). Disk is fine...checked it with drive genius and disk drill. I am open to suggestions if anyone has them. I'm guessing this is out of warantee, nor was I the original owner. Anyone have any ideas? Open to anything at this point.

The DC-In board doesn't look like much (I'm looking at http://www.ifixit.com/MacBook-Parts/MacBook-Pro-13-Inch-Unibody-MagSafe-DC-In-Bo ard/IF163-011 -- the zoomed in version). There's hardly any intelligence on there (in the form of an IC). I'd rather expect this to be something on the logic board, but you could test it with a multimeter, see if there's still a voltage measurable after reconnecting the magsafe.

BT Voyager 205 & iChat - How to make it all work! (repost)

First posted by Solidsilver, reposting for reference just in case we loss it.
Tony
I have just been going through ** to get iChat working with a BT Voyager 205 modem/router.
In the end I contacted Apple and an extremely helpful iChat Engineer from Apple contacted me. With his patient advice and tutor-ship we succeeded in making it all work perfectly.
And what you have to do is a 2 minute job. This is a direct cut n paste of his email to me less my IP address, you just put in yours. No port forwarding or port triggering nonsense. No static IP rubbish. It's all in the Voyager.
Here you go:
Open up a web browser and access the 205 control panel at http://192.168.1.1
Select the 'Advanced' option on the left of the screen to open up the advanced configuration page and then click the 'Advanced....' option.
Enter your username and password when prompted, the default username is 'admin' and the default password is also 'admin'.
Select the 'IP Routing' option in the menu on the left and then choose 'NAT Virtual Server/DMZ' from the NAT Options.
Left click on the 'Add' button and then select 'DMZ' from the rule flavour menu.
Enter a number not previously used by another rule into the 'Rule ID' box, '60' should be fine for most people.
In the 'LAN IP Address' enter the IP address of the Mac found in Network Prefs(I guess it is 192.168.1.XX)
Left click on the 'Apply' button and then left click on the red 'Save' button on the left.
You should then get a confirmation window which you can just close.
All done.
You have now put your Mac in front of the Voyagers Firewall in something called the DMZ or DeMilitarized Zone. If you don't want anymore tinkering, turn your Firewall off in Sharing Prefs and you are good to go.
If you feel insecure you then need to open a few ports in your Mac's Firewall in Sharing prefs.
Click Add and a sheet opens.
In the Port Name select Other
TCP Ports add 5190, 5298 (type them in exactly as I write them here)
UDP Port Numbers add 5060, 5190, 5297, 5298, 5353, 5678, 16384-16403 (type them in exactly as I write them here)
Description add iChat AV to give it a name.
Click OK
Then turn your Mac Firewall on. What you have just done means that though your Mac is not protected by the Voyagers Firewall, it is protecting itself. However, opening those ports allows iChat to communicate through the Mac's Firewall.
Now enjoy iChat.
This tutorial assumes you are using Tiger and Panther.

Hi People,
TCP Ports add 5190, 5220, 5222, 5223, 5298 (type them in exactly as I write them here)
UDP Port Numbers add 5060, 5190, 5297, 5298, 5353, 5678, 16384-16403 (type them in exactly as I write them here)
I have re-posted the port info here Adding Jabber ports
The others are colour coded for emphasis
iChat Login, text Chat and File sending
A/V Ports
And Bonjour
8:08 PM Friday; May 11, 2007

BT Voyager 205 & iChat - How to make it all work!

I have just been going through **** to get iChat working with a BT Voyager 205 modem/router.
In the end I contacted Apple and an extremely helpful iChat Engineer from Apple contacted me. With his patient advice and tutor-ship we succeeded in making it all work perfectly.
And what you have to do is a 2 minute job. This is a direct cut n paste of his email to me less my IP address, you just put in yours. No port forwarding or port triggering nonsense. No static IP rubbish. It's all in the Voyager.
Here you go:
Open up a web browser and access the 205 control panel at http://192.168.1.1
Select the 'Advanced' option on the left of the screen to open up the advanced configuration page and then click the 'Advanced....' option.
Enter your username and password when prompted, the default username is 'admin' and the default password is also 'admin'.
Select the 'IP Routing' option in the menu on the left and then choose 'NAT Virtual Server/DMZ' from the NAT Options.
Left click on the 'Add' button and then select 'DMZ' from the rule flavour menu.
Enter a number not previously used by another rule into the 'Rule ID' box, '60' should be fine for most people.
In the 'LAN IP Address' enter the IP address of the Mac found in Network Prefs(I guess it is 192.168.1.XX)
Left click on the 'Apply' button and then left click on the red 'Save' button on the left.
You should then get a confirmation window which you can just close.
All done.
You have now put your Mac in front of the Voyagers Firewall in something called the DMZ or DeMilitarized Zone. If you don't want anymore tinkering, turn your Firewall off in Sharing Prefs and you are good to go.
If you feel insecure you then need to open a few ports in your Mac's Firewall in Sharing prefs.
Click Add and a sheet opens.
In the Port Name select Other
TCP Ports add 5190, 5298 (type them in exactly as I write them here)
UDP Port Numbers add 5060, 5190, 5297, 5298, 5353, 5678, 16384-16403 (type them in exactly as I write them here)
Description add iChat AV to give it a name.
Click OK
Then turn your Mac Firewall on. What you have just done means that though your Mac is not protected by the Voyagers Firewall, it is protecting itself. However, opening those ports allows iChat to communicate through the Mac's Firewall.
Now enjoy iChat.
This tutorial assumes you are using Tiger and Panther.

Hi SolidSilver,
That's a different way of doing things.
He has led you through this
http://portforward.com/english/routers/port_forwarding/BT/Voyager205/iChat.htm
but has gone for DMZ rather than the 23 ports that need to be set up. (the pics only show port 5190 and you need more to AV chat)
If you do fancy the tinkering to get the 205 to be a Firewall as well you have to follow the page to set up port 5190 fo both TCP and UDP
Next you need to do the other 22 ports on UDP
They have to be entered one at a time in the 205 so it is time consuming.
5060
5678
16384
16385
16386...
and the others in between
....16402
16403
The above form your post and this will only work if your computer always gets the smae IP address from the 205 each time it is turned on.
If you have any connection problems check the System Preferences > Network for your current IP and see if that is where the 205 is send ing the data and amend as required.
Ralph

I have recently upgraded my iMac Intel G5 iSight to OS 10.6.8 and now the internal mic does not work with skype or facebook. I can here static when playing back clips. Do I need to update firmware or reload old sys parts

I have recently upgraded my iMac Intel G5 iSight (iMac5,1) to OS 10.6.8 and now the internal mic does not work with skype or facebook. I can here static when playing back clips. Do I need to update firmware or reload old system parts. I have zapped PRAM. The blue indicator in system audio panel will appear for a second as I slide the bar for internal mic but then it disappears. Is there a fix?

The sound seems very faint but can here static on playback.

AMSN & iSight & BT Voyager 205 - not working

Similar Messages

Maybe you are looking for