Leopard to Tiger iChat Video Fix! (maybe?)

I posted this in another thread, but thought I'd open this up in an attempt to help the seemingly many, many others who are having this similar issue. Ever since installing Leopard, I've been unable to video chat--either Leopard-to-Leopard or Leopard-to-Tiger. Recently, I went through numerous steps and was able to get Leopard-to-Leopard to work, but Tiger still wasn't working. I worked with Ralph Johns and we tried numerous things, but nothing seemed to work UNTIL I turned off the firewall on my machine. I'd done this before, but that was before I tweaked all of these other settings as well. Now, everything seems to be working. I've tested with buddies on different ISP's and with Apple's test bots.
These are some of the key things I've done:
Set QT STreaming to 1.5
Set bandwidth (in iChat) to 500kbps (Comcast)
Deleted iChat prefs and ichatagent prefs
Set parallels network connections to "off" in System Prefs>Network
Reset PRAM
Reset security port to 443 (in iChat prefs, server settings)
Turned off firewall on machine
Restart iChat (obviously)
As I mentioned elsewhere, I don't know which key thing made a difference, or what combination of things worked. I'm not excited about having my firewall off, but I'll leave it on unless I'm trying to video chat with someone on Tiger, then turn it off temporarily. I did not have to make any adjustments to my router (though I did try this), trigger ports, or anything like that.
I found testing with the apple buddy test bots was very helpful. Add these accounts to your buddy list as AIM buddies: appleu3test01, appleu3test02, appleu3test03. 01 and 03 are running Leopard, and 02 is running Tiger.
Obviously, some of these steps may not be necessary (if you don't have parallels installed, for instance). I don't know that this is THE fix, but it's what worked for me. Leopard's firewall has pretty much been a disaster, so I'm not surprised this was the issue for connecting to Tiger machines.
I hope it helps!

Following up on my own post: This is only a partial fix. I can now reliably iChat (or break iChat) with one Tiger machine, but I cannot iChat with my parents' Tiger machine.
I have 3 computers that I arranged for testing:
1. G4 1.6 GHz Leopard PowerBook
2. G4 1.6 GHz Tiger MacBook
3. Intel 2.4 GHz Leopard MacBook
4. G4 500 MHz Tiger Cube
The two Tiger machines always connect to my parents iMac. iChat works flawlessly, as it did on my Intel machine before I upgraded to Leopard.
The two Leopard machines chat just fine with each other on my LAN, but neither can connect to my parents' iMac.
The two Leopard machines can chat just fine with either Tiger machine on my LAN, but with the Intel machine, only if Parallels networking is turned off.
If anyone has any specific tests to suggest, I'd appreciate it.

Similar Messages

Go To Chat failure in mixed environment - Leopard and Tiger iChat

Hi there.
I've been using iChat on an OS X Tiger machine and using the "Go to chat" feature to communicate with several other people at work. It recently started failing when they all upgraded to Leopard. I am not sure if this is a Leopard issue or what, but since that seemed to be the only common change, it seems a good place to start.
The error I receive when trying to go to chat is:
AIM error:
Couldn’t request chatroom “MyChatRoom”. (An AIM service error occurred. The server message was: Serv:RequestTimeout)
The chatroom name has been changed to protect the innocent.
I've tried changing my port to 443 as some have suggested.
We're all on high speed connections.
Another data point is that around the time they all started upgrading to Leopard, some of us would drop out of the chatroom or become unable to send to chat - even after relogging, restarting, etc.
We can chat with each other one-on-one just fine. It's just the chatroom which seems to be...somewhat broken.
Thanks in advance for any tips here.
-T.

From what you post about trying different things I would delete com.apple.ichat.AIM.plist and restart iChat
2:50 PM Sunday; November 18, 2007

IChat Video - Leopard=NO, Tiger=YES. HELP PLEASE!!!

hi there.
can anyone help?
iChat video messaging is being a right old pain!!!
On my MacBook (Leopard 10.5.2), no joy whatsover....just errors.
it is being totally ok on my MacMini G4 (Tiger 10.4.11).....no errors.
can anyone suggest a fix for my MacBook?
My MacMini is getting it's internet feed from the Ethernet socket on my Macbook, which in turn is getting it's internet via Airprt from the Netgear DG834GT router connected to Sky Broadband here in the UK.
Router and Sky are obviously fine if the Mini will video-conference ok.
this has to be a Leopard/MacBook issue.
any help with resolving this greatly appreciated.
Richie x

Monty1945 wrote:
I use it (iChat) from Mac to Mac
Which version Mac were you chatting with? Tiger or Leopard? I can chat all day with Tiger users from my Leopard machine. I fail 19 out of 20 times with another Leopard machine. I can boot into Tiger and it all magically works.
Some folks may need to port map, but I just use UPnP, as do most of the folks I VC with. I use a AEBS N and the Motorola Surfboard cable modem - nothing unusual or weird. Normal firewall stuff, as well.
All that is a waste of time unless you are running Tiger. If you can't get Tiger iChat to run, then you need look into network settings, modems, etc. On Tiger, I never had to adjust anything. No amount of tweaking will get Leopard iChat to talk to another Leopard. I know it isn't Leopard firewall or any other particular setting because it does work very rarely. Then it will fail 5 times in a row with the same settings that worked once after the first set of 9 failures.

IChat Video Leopard to Tiger

I'm having trouble getting video chat to work within iChat. Video chatting works fine with people with Leopard, but my friend has Tiger and it won't work.
My iMac(with Leopard) will show her video feed, but she can only see herself. We both can hear each other, and I can see her. But for some reason she can't see me.
Anybody got any ideas?
P.S. - All ports are fine, firewalls off.

Have you or the other got Perian installed http://discussions.apple.com/thread.jspa?threadID=1894107&tstart=25

IChat video stopped working after installing leopard

I frequently use iChat to talk to my son in Madrid and other family members. He uses a mac G5 and while running OS 10.4 X all was well. We both have non Intel power PCs with external apple iSight cameras. I am still running OS 10.4.11, and as soon as he installed leopard we lost the video part of iChat. I get a message saying IP address invalid, but we have not made any addressing changes. I have a suspicion that leopard only supports the built in version of iSight and not the older external version of the camera. I can still use iChat with new Intel macs running leopard but with the internal camera. Please does anyone have any ideas or a work around?

Many thanks for your reply. After reading it my son fixed the problem by turning off internet sharing on leopard. Previously he shared his router with a Macbook via his airport card. However Apple please take note. This worked fine with Tiger and works ok with Skype so Leopard has regressed in this respect. However it is really great to have video back with iChat

Ichat Leopard to Tiger

I bought a new macbook with Leopard OS.. I used to be able to.. no matter what wireless network I was on.. be able to video/audio multi chat anyone.. Now with Leopard.. UNLESS the person on the other end has Leopard.. I can't initiate the chat. My firewall is OPEn and so is the receiver. I did a complete reinstall of the OS and I am still getting the error.. the person on the other end did not answer.. HELP.. Is it a Tiger/Leopard incompatibility? Is there an update that needs to happen?

Seeing we are waiting for the two original posters (apart from myself) to say how they are opening the ports in their modem or router there has been no further info posted on that subject.
If people set up Port Triggering for Tiger/iChat 3 then it may not work for iChat 4 in Leopard. (Outgoing calls would be an exception)
The only way anyone is going to g=find out why this happens is to list every setting in every device and see if anything pops up.
With Tuckerman contacting me Off Discussions we were able to try a few things on his device. He did have the same problem and nothing we did seemed to solve it.
I did tell me later that the 10.5.2 update cured the problem.
Now reinstalling a Combo version of an Update is known to sort some things out if a Delta "Software Update" version has not seemed to have updated properly.
But there is no Combo of the 10.5.1 update as it was the first one.
That does not mean though, that re-doing an update or COMBO, depending where you are in the updating stakes, is not worthwhile.
7:43 PM Thursday; February 28, 2008

IChat video/audio fails to work

iChat video/audio fails to work 90% of the time. The error message says the other party failed to respond, or some other, similar, bogus "communication error" message.
Invitation to video or audio chat fails 100% of the time with certain buddies of mine, and anywhere from 50% to 90% of the time with others, regardless of whether they invite me or I invite them. Changing ISPs, Macs, locations, or static/dynamic IP settings has made no difference.
This problem surfaced with Tiger in the summer of 2007, and progressively became worse, especially since Leopard, to the point where iChat video/audio fails 100% of the time, unless the other user happens to be in the same [home] network.
All of a sudden the problem went away since the upgrade to 10.5.6, and I was able to again use iChat video to communicate with friends I have not been able to "see" in a year and a half! However, the problem started again today, with the same bogus "communication error" message every time a video connection attempt is made.
Screen Sharing also fails to work, 100% of the time, regardless of how it is invoked, through iChat or not, unless, again, it is attempted between 2 macs in the same home network.
In the meantime, Skype video works fine all the time.

Hi,
Thomson-Alcatel by default do what is called Binding of SIP to port 5060
This means ANY SIP data is forced to that port. iChat 4 no longer uses this port for SIP. It caused problems in iChat 2 and 3 which could be resolved when the firmware was Version 4 or earlier.
How do I know ?
Personal Experience from a Speedtouch 510v4 (running version 4.2.5 firmware)
Hence the web page I linked you to.
Built up from comments on the iChat 3 forum and the iChat 2 forum since 2004
Search Results for iChat 3 (it will only go back to about Nov 14th 2005 when the software Apple Uses to run the forums changed - some active threads did cross over this date so occasional ones are older)
Smaller results from iChat 2
The work by iBoise in this forum and the ADSLGuide's Apple Forum
Known issues for the BT HOME HUB in Britain as it is a Thomson-Alcatel inside.
Because the fix on Page 4a in the orignal link I gave, worked until Version 5 firmware came out.
As I clearly said the results can be intermittent.
With non Speedtouches it tends to be a 10:10:30 split out of 50 Buddies
10 you can get all the time.
10 now and then Buddies and
30 Never successful.
The Original Version 4 Telnet command would make this 100% successful to non Speedtouch devices
In Version 5 it becomes about 15:10:25 which only marginally better.
Later versions of the firmware do not even seem to reach these figures.
Speedtouch to Speedtouch connections are better but still not 100%
I would guess you live some where where Speedtouch's are popular and have many Speedtouch to Speedtouch connections that fair slightly better than average.
Last time I had contact with iBoise on this the Firmware was at version 7 and he was in the process of evaluating it for any changes.
There has been no announcement. In this case I don't think No News is Good News.
I hope this helps.
10:42 PM Wednesday; January 21, 2009

Mom does not see my iChat video, but I see her, and my wife can see mine

When I iChat with Mom, I can see her, but she cannot see my iChat video. All she sees is herself as if she is still in iChat preview mode. Audio works fine. It is like a 1-way video chat with a 2-way audio chat, only we did not request this mode.
This was working for years (from when Mac OS X Panther first offered iChat video chats). Mom only seeing herself is a fairly new situation, but I can not pin down when it started, or what might have triggered it.
My wife can connect with my Mom, and again, my Mom's display stays in preview mode, but my wife can see my Mom, same as I see, only my wife is using her own MacBook Pro.
When I'm at Mom's using my MacBook, I can iChat with my wife. She can see me and I can see her. My wife and I can also successfully iChat video chat when she is away on business trips using the hotel's WiFi. I do not think it is my MacBook, nor my wife's MacBook Pro.
And also while at Mom's with my laptop right next to Mom's iMac G4 using a Bonjour local connection, I see what Mom is sending, but she stays in preview mode only seeing herself.
So I think I've eliminated the internet as a whole, and I've eliminated my MacBook as being the cause.
I really think it is Mom's iMac G4.
I've tried trashing all the iChat related .plist files, but I could have missed something.
Mom's Connection Doctor says it is getting stuff from me at between 13 and 15 frames/second, but all that is shown is her own iSight image.
Some configuration details:
o Mom's 1.25GHz G4 PowerPC iMac is Mac OS X Tiger (10.4.11) all the latest updates.
o Mom uses the original firewire iSight.
o While I think I've eliminated the router, it is an 802.11n Airport Extreme (single transmitter in 802.11b/g/n 2.4GHz mode, channel 1).
o Verizon DSL connection that has worked just fine in the past, beside same situation occurs when I'm sitting next to Mom using a Bonjour connection.
o Mom is 300 miles away, so I can not just drop in. However, I do have VNC access to Mom's system over an ssh tunnel.
o Firewall is Off
o My 2GHz intel Core 2 Duo white MacBook is Mac OS X Leopard (10.5.8) all the latest updates (w/build-in iSight camera).
o My wife has an intel 2.2GHz Core 2 Duo MacBook Pro running Mac OS X Leopard (10.5.8) all the latest updates (w/build-in iSight camera).
o My router is also an 802.11n Airport Extreme (single transmitter in 802.11n 5GHz only mode), with an older flying saucer Airport Extreme 802.11g in bridge mode to support older Macs and iPod Touchs.
o My broadband is also a Verizon DSL connection.
o Firewall is Off.
Events that have happened recently. I'm not saying they are the cause, but generally things that did work do not stop working for no reason at all.
o I've applied Apple's Software Updates.
o I've experimented with TeamViewer.com as an alternative to VNC for remote control (this did not involve video, but it was something new to the mix). NOTE: I DO NOT keep TeamViewer running. I find my VNC via OSXvnc to be satisfactory.
o My nephew moved back in with his Mom (my sister) and his Dad, which is where my Mom happens to live. However, my nephew has his own 12" G4 PowerBook, so he does not need to mess with Mom's. But then again, years ago, I found my Mom's previous Bondi Blue iMac had its web server enabed after a visit from my nephew. Of course now he is a college gradate and much more responsible. Oh yea my nephew was a College Quarterback for a Top Ten College, and I'm a bookworm type. I am not going to accuse my nephew of doing something to his grandmother's iMac unless I have absolute proof
o At one time I had the Chax plug-in installed on Mom's iMac G4. I used Chax to uninstall itself.
I'm stumped. I've tried all the problem isolation things I could think of, as well as the tried and true "Delete the .plist" trick (assuming I found the right .plist(s)).
Has anyone actually lived through this, solve it for someone else, other.

I would do the Latest Combo Installer for the OS level she is at.
That is going to have to wait until after Thanksgiving.
While I'm confident that applying/re-applying the latest Combo Update will not cause any problems, if anything goes wrong (and I know Murphy personally), I will not be able to drive the 300 miles to Mom's house until the weekend following the Thanksgiving weekend.
If I'm going to try doing something like this remotely, I'm not going to do it unless I can get in the car and be a Mom's house the next morning to clean up any mess I create.
So I will put your idea in my "To Do" list (I'll even create a Google Calendar event), to try this 4-Dec-2009.
Thank you for the idea. If I have not found a solution before the 4th, I will install the Combo update.
But I do have a question. Why would Mom's iChat display the video preview window showing what her iSight camera sees, if she was unable to display the remote video stream, just because there was a ColorSpace issue. Hay, I write software for a living, so I know that the left hand does not need to know what the right hand is doing, not the big toe, the elbow, an ear, etc... Software is full of paradoxes. But I figured I would just ask.
And I'm still going to give the Combo update a try on 4-Dec-2009.
But in the mean time. Other suggestions would be appreciated.
Does anyone have a laundry list of .plist files I should try deleting? I did try deleting some obvious ones, but maybe I missed something important, or maybe there is one that does not say iChat, but is just as important.
You never know, if I get enough ideas (tons of ideas), and they all still fail, and I'm frustrated beyond belief, maybe I'll break down and get Mom a nice 27" iMac for Christmas! But if I do that, I'm getting one for me first

IChat Video works without any manual port configuration

I'm posting this as a question and a true "discussion" with regards to iChat "video chat" operation with 2 users, both behind their own NAT router. I have seen several cases where iChat (ver3 and ver4) work just fine without any manual intervention. Of course, there are many other cases in these discussions where it seems a lot of complication and little positive result are part of the equation. Isn't iChat designed to work behind NAT routers ? Doesn't it use the SNATMAP server to get external (ie; public) IP and port number mappings ? If both users can login to the AIM server and initiate a Chat request, and contact the SNATMAP server, the next key requirement is to simply establish a point-to-point SIP session to the public IP/port of each endpoint.
It seems the first thing to check is that this is happening correctly. In other words, the iChat debug log for userA should show something similar to;
2008-01-29 18:59:21.739 iChat[2603] IPAndPortList: (
{ip = "x.y.z.w"; port = 63217; },
{ip = "a.b.c.d"; port = 16402; }
...where a.b.c.d represents the internal/private IP of a user (userB on Leopard iChat4 for example with 16402 representing all of the SIP, A/V, and A/V control ports) behind a NAT and x.y.z.w represents the external/public IP of userB. At least I think Leopard uses 16402 for the SIP. This shows that userA has the mapping for the SIP signaling port to send the SIP:invite to userB (ie; 63217).
There is also something like;
185912.819694 Sending SNATMAP heartbeat to 11FAF895:5678
185912.912199 SNATMAP heartbeat resulted in IP change (from: 0 to: mm.nn.kk.pp)
185912.912251 SNATMAP heartbeat resulted in port change (from: 0 to: 64999)
..where mm.nn.kk.pp represent the HEX values for the userA public IP address and the 64999 (in this example only) represents the SIP signaling port for userA
185921.738995 =========== OpenPorts!
185921.832238 Public mapping: m.n.k.p:64998
185921.923213 Public mapping: m.n.k.p:64991
185922.014215 Public mapping: m.n.k.p:65018
185922.104986 Public mapping: m.n.k.p:65098
...where m.n.k.p represents the public IP of userA (Tiger iChat3 in this case), and the 64xxx and 65xxx umbers represent the ports opened for A/V and A/V control. In other words, these are the mappings for the "typical" 16384, 16385, 16386, 16387 ports.
As long as both users have connectivity to the SNATMAP server, these "mappings" should proceed without problems, right ??
If both endpoints/users get these mappings, which appear to happen auto-magically between iChat and the SNATMAP server at "snatmap.mac.com:5678", iChat should move to the next phase which is to simply establish the point-to-point SIP call. Up to this point, I don't see why any port-mapping or for that matter, anything else needs to be done ?
Of course, AFTER this point, one does need to make sure no local computer "application" firewall is blocking 5190, 5060, 5678, 16384-16403 (Tiger) or 5190, 16384(or 16393?)-16402 (Leopard) .
If all is well to this point, and iChat actually sends a valid SIP:invite to the remote public SIP IP/port, with a valid SDP section, it's up to whether the endpoints can agree on the session parameters (ie; video codec, bitrate, frame-rate, etc..etc...)
Of course, there are many other things that could happen outside of iChat, like bad (or even good) installed software causing some weird problems, or running some application like virtualization or Internet Sharing that may have some "interop" issue...and maybe even a Service provider simply blocking the ports that the NAT has used (unlikely since they are probably different for every user and determined by each users NAT router)...but if you look at the iChat errorLogLevel7 debug output (preferably on both ends at the time of the call), you should be able to determine if iChat is sending a valid Invite...which is the prmary key in all of this.
Lastly, I have read about "symmetric" NAT routers which might actually pose a real problem even when using the SNATMAP server. This is because a symmetric NAT router will only allow traffic from the destination port that a source port was opened to...which in iChat's case is usualy the SNATMAP server. So it may not be possible to "open ports" via te SNATMAP server, but then get incoming SIP/video traffic from userB. In this case, then UPnP or NAT-PMP, or port-forwarding/triggering may help.
Just some thoughts for discussion.

Your totally right,
and from al the discussions here it seems that not every body knows that, and might be looking for the wrong answers. I wonder why Apple doesnot tell us how it is meant to work, and how to troubleshoot connections problems!
Ichat uses the SIP protocol and should work without any firewall/NAT configurations, for an explanation see http://en.wikipedia.org/wiki/SessionInitiationProtocol
I have seen it work out of the box for several installations (single iMac, OS X 10.5, behind one ADSL router). In one situation i had to switch of the SIP helper application in the router
My own home network has 2 macs however, and sometimes it works and sometimes not.
1) I found out that for local videochats i have to use the bonjour accounts, is that correct ? It should work with .MAC accounts too?
2) for external communications i found out it is best to to stick to one Mac. When I switch from one to the other, using the same account (after logging out first), it often doesnot work, although it should. Any idea how to troubleshoot this problem? (now I rember I have to check this SIP helper application first
3) when i setup a video chat to my mam who uses autoaccept, i am not able to take over the screen. Without autoaccept it works fine. So it looks like autoaccept won't allow you to share the screen.

IChat Video not working (Error -7/-8)

Another case of these strange iChat Video Issues (Error -8).
A friend of mine upgraded today from Tiger to Leopard. iChat 4 video is not working anymore. I thought it was my fault because of a recent router firmware upgrade. But I checked with another Buddy and it worked fine. So what to do? My friend did not change his setting since Autumn when we had the last chat (both using Tiger) and everything worked fine.
Following please find the protocols. Can anybody retrieve some useful Information?
I invited:
Date/Time: 2008-02-12 20:47:38.282 +0100
OS Version: 10.5.2 (Build 9C31)
Report Version: 4
iChat Connection Log:
2008-02-12 20:47:13 +0100: AVChat started with ID 3685851442.
2008-02-12 20:47:13 +0100: [email protected]: State change from AVChatNoState to AVChatStateWaiting.
2008-02-12 20:47:13 +0100: 0x1bb90b20: State change from AVChatNoState to AVChatStateInvited.
2008-02-12 20:47:24 +0100: 0x1bb90b20: State change from AVChatStateInvited to AVChatStateConnecting.
2008-02-12 20:47:24 +0100: [email protected]: State change from AVChatStateWaiting to AVChatStateConnecting.
2008-02-12 20:47:34 +0100: 0x1bb90b20: State change from AVChatStateConnecting to AVChatStateEnded.
2008-02-12 20:47:34 +0100: 0x1bb90b20: Error -7 (0x1bb90b20 cancelled the connection.)
2008-02-12 20:47:34 +0100: [email protected]: State change from AVChatStateConnecting to AVChatStateEnded.
2008-02-12 20:47:34 +0100: [email protected]: Error -7 (0x1bb90b20 cancelled the connection.)
Video Conference Error Report:
1023.455878 @SIP/SIP.c:2719 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1025.456573 @SIP/SIP.c:2719 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1025.957598 @SIP/SIP.c:2719 type=4 (900A002D/0)
[SIPConnectIPPort failed]
2209.113434 @SIP/SIP.c:2719 type=4 (900A0015/0)
[SIPConnectIPPort failed]
2211.114008 @SIP/SIP.c:2719 type=4 (900A0015/0)
[SIPConnectIPPort failed]
2211.114539 @SIP/SIP.c:2719 type=4 (900A002D/0)
[SIPConnectIPPort failed]
6537.202171 @SIP/SIP.c:2719 type=4 (900A0015/0)
[SIPConnectIPPort failed]
6539.202454 @SIP/SIP.c:2719 type=4 (900A0015/0)
[SIPConnectIPPort failed]
He sent me this protocol:
ate/Time: 2008-02-12 20:47:37.674 +0100
OS Version: 10.5.2 (Build 9C31)
Report Version: 4
iChat Connection Log:
2008-02-12 20:47:14 +0100: AVChat started with ID 3685851442.
2008-02-12 20:47:14 +0100: 0x1ccee7c0: State change from AVChatNoState to AVChatStateWaiting.
2008-02-12 20:47:14 +0100: [email protected]: State change from AVChatNoState to AVChatStateInvited.
2008-02-12 20:47:23 +0100: 0x1ccee7c0: State change from AVChatStateWaiting to AVChatStateConnecting.
2008-02-12 20:47:23 +0100: [email protected]: State change from AVChatStateInvited to AVChatStateConnecting.
2008-02-12 20:47:33 +0100: 0x1ccee7c0: State change from AVChatStateConnecting to AVChatStateEnded.
2008-02-12 20:47:33 +0100: 0x1ccee7c0: Error -8 (Did not receive a response from 0x1ccee7c0.)
2008-02-12 20:47:33 +0100: [email protected]: State change from AVChatStateConnecting to AVChatStateEnded.
2008-02-12 20:47:33 +0100: [email protected]: Error -8 (Did not receive a response from 0x1ccee7c0.)
Video Conference Error Report:
Video Conference Support Report:
9.535583 @Video Conference/VCInitiateConference.m:1582 type=2 (00000000/0)
[Connection Data for call id: 1 returns 1
10.868139 @Video Conference/VCInitiateConference.m:1597 type=2 (00000000/0)
[Prepare Connection With Remote Data - remote VCConnectionData: 1, local VCConnectionData: 1
Video Conference User Report:
0.000000 @:0 type=5 (00000000/16402)
[Local SIP port]
0.000031 @:0 type=5 (00000000/16402)
[Local SIP port]
0.000045 @:0 type=5 (00000000/16402)
[Local SIP port]
Any ideas? Help would be greatly appreciated.
Kind Regards,

NAT can be done - in the routing device - in different ways.
Apps like iChat that have to work with or through NAT have to predict what that is or what the data is going to come across as it goes through different devices.
We know that in iChat's case this does seem to effect the checksums that refer to the ports being used and that it can be seen in the Error logs.
This is not anything to do with the way Apple Does NAT.
The Base Stations are a different matter though.
These do DO NAT
Although they can be set to do Port Mapping which the Wiki page I linked above says in Miss-named as NAT - they actually do what Apple Calls NAT - PMP or NAT with Port Mapping Protocol which does something that looks like UPnP does, in that it is a One Setting that effects all connections with no setting of ports but allows multiple computers to use the ports.
Wiki Link
So it is NOT Leopard.
It IS the Base Stations.
It IS because there is not an International Standard (or if there is that defines NAT Well enough)
I hope this helps.
7:54 PM Thursday; February 28, 2008

General iChat video AIM Question.

Has anyone figured out what port settings your AIM has to be on in order to use the video chat feature? I am currently using port 1080 and my parents can see me, but I cant see them and I tried using these same ports with another friend and it wont work at all. Any help.

Hi,
Apple has 2 Articles on this now.
This came out for iChat 2 http://support.apple.com/kb/HT1507?viewlocale=en_US and was updated for iChat 3 and the Jabber parts (you need the info on Jabber and Bonjour form here)
Apple added this Article for Leopard (but did not include the Bonjour and Jabber Info)
The A/V ports are 5060 (if Tiger/iChat 3), 5678, 16384-16403 if Tiger/iChat 3 or just 16393-16402 if Leopard/iChat 4
(it does not really matter if you set the iChat 3 ports as the Leopard ones are inside that range).
2:19 PM Sunday; February 1, 2009

Bluetooth button missing from iChat Video Conference window

I normally use a bluetooth headset when in an iChat video conference. Tiger has a button on the bottom edge of the video screen to select or deselect the bluetooth headset. This button is missing in Leopard forcing you to go into the preferences panel and select the device there.
Did I miss an option somewhere?
Mike

Hi,
I have not heard of this in iChat 3.
As no-one else has answered I would guess it is a feature many others are unaware of.
6:40 PM Monday; October 29, 2007

Three new Macs ... iChat video won't work over WAN

Hi,
We just bought two iMacs and a MBP, all running Leopard. We can iChat when in the same house on the same wireless network, but when we go back to our homes, it doesn't work. Below is the error. We can use Skype video no problem. iChat text works works fine. We've reinstalled iChat, matched or unmatched the font, reduced the bandwidth in iChat, etc. We haven't altered the router settings. Hope someone has a suggestion. Thanks.
Date/Time: 2008-01-23 20:35:51.339 -0800
OS Version: 10.5.1 (Build 9B18)
Report Version: 4
iChat Connection Log:
2008-01-23 20:35:06 -0800: AVChat started with ID 4010006563.
2008-01-23 20:35:06 -0800: 0x1020e7f0: State change from AVChatNoState to AVChatStateWaiting.
2008-01-23 20:35:06 -0800: [email protected]: State change from AVChatNoState to AVChatStateInvited.
2008-01-23 20:35:38 -0800: 0x1020e7f0: State change from AVChatStateWaiting to AVChatStateConnecting.
2008-01-23 20:35:38 -0800: [email protected]: State change from AVChatStateInvited to AVChatStateConnecting.
2008-01-23 20:35:48 -0800: 0x1020e7f0: State change from AVChatStateConnecting to AVChatStateEnded.
2008-01-23 20:35:48 -0800: 0x1020e7f0: Error -8 (Did not receive a response from 0x1020e7f0.)
2008-01-23 20:35:48 -0800: [email protected]: State change from AVChatStateConnecting to AVChatStateEnded.
2008-01-23 20:35:48 -0800: [email protected]: Error -8 (Did not receive a response from 0x1020e7f0.)
Video Conference Error Report:
Video Conference Support Report:
0.000000 @SIP/Transport.c:2353 type=1 (00000000/0)
[SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.5;branch=z9hG4bK3b770bb024da23e4
To: 0 <sip:[email protected]:16402>;tag=396488263
From: u0 <sip:[email protected]>;tag=333292834
Call-ID: ea0f44a8-c7e1-11dc-92bd-db1e6e2c13c4@192-168-1-5
CSeq: 1 INVITE
Contact: <sip:[email protected]:16402>
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 430
v=0
o=sanaebingham 0 0 IN IP4 192.168.1.7
[email protected]
c=IN IP4 192.168.1.7
b=AS:2147483647
t=0 0
a=hwi:1056:2:2000
a=bandwidthDetection:YES
a=iChatEncryption:NO
m=audio 16402 RTP/AVP 12
a=rtcp:16402
a=rtpID:466551867
m=video 16402 RTP/AVP 126
a=rtcp:16402
a=rtpmap:126 X-H264/90000
a=RTCP:AUDIO 16402 VIDEO 16402
a=fmtp:126 imagesize 0 rules 20:320:240:640:480
a=framerate:20
a=rtpID:3880118170
0.006753 @SIP/Transport.c:347 type=2 (00000000/0)
[ACK sip:[email protected]:16402 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;branch=z9hG4bK7244f8cd57b3278a
Max-Forwards: 70
To: 0 <sip:[email protected]:16402>;tag=396488263
From: u0 <sip:[email protected]>;tag=333292834
Call-ID: ea0f44a8-c7e1-11dc-92bd-db1e6e2c13c4@192-168-1-5
CSeq: 1 ACK
User-Agent: Viceroy 1.2
Content-Length: 0
0.007382 @SIP/Transport.c:2353 type=1 (00000000/0)
[SUBSCRIBE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 192.168.1.7:16402;branch=z9hG4bK25d964740defe840
Max-Forwards: 70
To: u0 <sip:[email protected]>;tag=333292834
From: 0 <sip:[email protected]:16402>;tag=396488263
Call-ID: ea0f44a8-c7e1-11dc-92bd-db1e6e2c13c4@192-168-1-5
CSeq: 1 SUBSCRIBE
Contact: <sip:[email protected]:16402>
Event: conference
Expires: 3600
User-Agent: Viceroy 1.3
Content-Length: 0

We do agree that there is a good possibility that the log that was posted is from a Bonjour (ie; local) iChat session.
The 192.168.1.x subnet is part of an address block assigned by the authorized addressing body as Private addresses. They should not be advertised on the public Internet and are NOT routeable across the public Internet. Also, when you mention other logs in these discussions, aren't most of the logs and/or discussions here of scenarios when something does not work ?? Can you refer to a known, good, working iChat video-chat log going across a WAN/Internet (not a local LAN or Bonjour) that shows both the To: and From: IP addresses as 192.168.x.x ? The bottom line is if the actual transmitted SIP:invite packet (not some possibly inaccurate Log message) has a 192.168.1.x address as the destination IP, I do not think it will work. Some of the Logs that iChat provides do some processing or filtering such that I am not sure that it is an actual packet capture/decode.
Again, I am certainly open to learning something, but my understanding is if the packet put onto the wire is destined to be routed across the Internet to another user behind a NAT router, a destination IP (or a To: address) of 192.168.1.x will not work.
The process when going across the Internet , as I understand, is very simple;
- login to OSCAR server on "typical" port 5190
- after OSCAR authentication, login to BOS server, get Buddy List, "self info" such as publicly visible IP address, etc...
- initiate Chat request to a Buddy (example userB)
- send Chat request message to BOS server requesting Chat with userB, still on port 5190. Chat request includes data indicating the userA public IP address and public SIP signaling port number. UserA may have obtained this info via communication with the SNATMAP server, where it sends a message fom a private (ie; 192.168.x.x.) source IP address and private source port number to the SNATMAP server, which then sends back a message telling the userA what IP and Port were actually received...in other words, the publicly visible IP and port that the NAT router translated the private ones to. Typically the private ones would be 5060, 16384-16403..but others are possible.
- BOS server relays Chat request to userB, including "rendez vous" data which has userA IP address and SIP signalling port number.
- UserB may send back a message via the BOS server to the userA indicating its public IP and public SIP signaling port number as well.
- One end can now initiate the SIP:invite message with the Destination IP and port# equal to the PUBLIC IP/port that was sent in the Chat request
- The public port# should be open since the userA/B would have sent messages to the SNATMAP server so as the "open" the port on the NAT router.
- The SIP:invite message will have an SDP section that will indicate which port numbers to use for Audio, Video, Audio Contol, ad Video Control. Again, these should be the "publicly" visible (ie; Internet side of the NAT router) ports as learned via SNATMAP (or other methods such as UPnP..). The internal values for these ports are typically 16384,16385,16386,16387 for Tiger and 16402 for Leopard. The publicly visible values depend on the specific NAT router and how it translates internal address/port numbers.
- Once each end receives the SIP:invite and SIP:ok with the SDP session parameters, they will negotiate audio, video, etc..parameters..and if they agree, it should work.
The key n all of this is to get the correct SIP signaling port number, and then the correct SDP session attributes which include the A/V and A/V control (ie; RTP, RTCP) port numbers. And, finally these must be public, Internet routeable addresses in order to work across the Internet.

Power Mac G5 Dual 2.3 freezing from Archive Install of Leopard from Tiger

Just archived and installed Leopard from Tiger 10.4.10 and on all our Macs, but our only PPC system is having serious issues. The system boots up fine, faster than before, however the Finder and desktop freeze when booting into any of the two user accounts. Applications run from the dock, but the Menu Bar isn't loading fully (airport, bluetooth, clock, etc don't load). I have run Activity Monitor from the Dock and systemuiserver and finder both freeze. I have reset the PRAM and NVRAM, and in the one instance I was able to get into the files I deleted the systemuiserver and powermanagement plist's.
Upon many hours of research with Apple and at home, nothing seems to be the solution. If I can't resolve this I may have to install a copy of Tiger (or Leopard) on an external HDD, boot and attempt data recovery from the main HDD (if nothing is locked) as a lot of Quicken 2007 files are needed and perform a clean install. If any one is able to give any help I'd greatly appreciate it. Thanks!
Also, the Power Mac G5 is Dual 2.3 late 2005 model (specs: http://support.apple.com/specs/powermac/PowerMac_G5_Late2005.html ), with 1 GB RAM, ViewSonic VGA monitor, NVIDIA GeForce 7800 GT with 256MB of GDDR3 SDRAM, Airport + Bluetooth, and wired keyboard and mouse. Thanks again!

k7 wrote:
So, would you recommend to people having this same system (as I do) to wait for installing Leopard or maybe to take some precautions?
I would either:
A) Wait until 10.5.1 has been released (which may address such issues)
B) Take serious precautions. Back everything you need onto a separate HD and perform a clean install (which formats your HD), then move everything copied back into the system to ensure no data is lost and nothing corruptible is carried over into Leopard.
Performing the clean install seemed to take care of any conflicts and issues, but means more time will be spent manually backing up and reloading all personal data.
Hope this helps and good luck.

Will my new iMac come with Leopard or Tiger?

Hi,
I'm going to Uni on Monday and want to finally purchase my Mac now that Leopard has been released.
My question is: If I order my new Mac on Monday, will it come with Leopard or Tiger?
In the online store it still states that it will come with Tiger, but maybe this has just not been updated?
If people don't know the answer, would you happen to know an Apple contact email address or telephone number I can call (in the UK) to check prior to ordering?

Are you sure you want to get a Mac with Leopard preloaded?
It may actually not be compatible with some of the software you depend on, and will have no chance of being so (unless the product is updated) because Macs historically have only been able to use the operating system they ship with and newer operating systems, and we are still learning which products need updates for Leopard.
The online store has a phone number in the upper left hand corner:
http://store.apple.com/Apple/WebObjects/ukstore/
0800 039 1010
Message was edited by: a brody

Leopard to Tiger iChat Video Fix! (maybe?)

Similar Messages

Maybe you are looking for