Q: Messages crashing / ichat video crashing

Hi,

For a long time now I have had IPv6 either turned Off or on the local only setting in versions of the OS where it seems you can't turn it off.

Where ISP offer both IPv4 and 6 iChat can "see" it as two Internet Connections and give you two IPs to the ISP which in turn causes issues for the Buddy in connecting.

8:56 pm      Thursday; July 16, 2015

Hi Dave,

I know this might seem pedantic but can I check I have understood correctly ?

You know that the ISP has been offering IPv6 already and you have had no issues  over the past five years with this ?

Does this mean you know that the other end has been having access to IPv6 services ?

It does seem odd that it has just started.

However I can't replicate it on my LAN even though the calls are via the Internet.

At the same time there are now a number of these threads across several Communities (iChat, Mavericks and Yosemite)

9:47 pm      Thursday; July 16, 2015

Hi,

Thanks for the extra info.

Many moons ago now I discovered that connecting to both Ethernet  and Wifi causes iChat some issues because it has to be very linear in it's connection.

The ISPs that I have here have not really been that forth coming as to when they started an IPv6 service.

As recent as November 2014 people were still asking at my current ISP:-

I posted it as a pic as I have to sign in to view the threads.

Another details that Trials took place and that was enough to have a thread closed in Feb 2015

The info not being clear IPv6 seemed like just another thing likely to upset the iChat app so I have made sure it is Off in th OS for a long time.

Despite my setting NO to Remote Access on my Router the ISP have managed to update it recently that I did not now about until I was looking for something only two days ago.

There are not lots of things that relate to IPv6.

Occasionally there have been issue with @mac.com and @me.com  IDs used as AIM Screen Names, mainly around the changes between older services and current ones.

For instance at the MobileMe to iCloud you could "register" your @me.com ID as your iCloud ID and later you also got given an @iCloud.com ID as well.

Since then the Apple ID used in early iChat 6 (not updated at all) and earlier cannot use the AIM service as those versions do not also log into Apple to verify the Login.  Basically the app (Mainly Late iChat 6 and Messages logs into Apple as well as AIM and this allows AIM to read the password.

It also prevents you from using this site https://settings.aim.com/ and changing the settings like the Display Name

I am not aware of Apple making any changes to the way Messages uses the Apple ID.

Some of this reminds me of the iChat 3 issue.

In OS X 10.4 Apple changed the Video protocol for the app.  This was based on the fact servers on the internet backbone were supposed to allow data through these ports.

Realistically not that many people in the Seed program seem to test iChat.

As a result the issue was not found out about until after the general release.

It seems that a large part of the the Eastern side of the United States was not ready.  (A rough line up the Mississippi to Chicago).

None of the ISPs or the backbone suppliers would do anything (claiming they did not know which servers needed doing) and so Apple released the only Standalone Update to iChat (other than making iChat 2 Video capable with the iChat 2.1 update) to back step the video production.

There are also similarities that look similar to when ISPs started to block the SIP port 5060-5063

Standalone items like Vonage adaptors and other Messing apps that were doing Video and Audio ran foul of ISPs suddenly blocking the SIP ports and then demanding extra payments for ports that were open when the contracts started and without notifying people.

Skype quickly moved to other non standard ports and Apple eventually followed as well at iChat 4.

I would guess this is going be silently solved again with no clear info on who or what was wrong.

8:38 pm      Friday; July 17, 2015

Hi,

This pic is a Bonjour Chat taken yesterday on my iMac which is running the said OS.

The left hand pic is a MacBook Pro running iChat 5.0.3 and the right hand (Ralph G4) is a G4 tower running Leopard and iChat 4.0.9

I have also made AIM based connections between the iMac using Yosemite and Messages 8 to the MacBook Pro  and this works.

Both these type of Connection are LAN based ones which does work as posted by other people as well as myself.

Since I posted in July above we have worked out the issues seems to be with the SNATMAP server that Apple run.

This connects the two ends (even for Bonjour) using the SIP (Session Initiation Protocol) text based protocol.

It seems as the outgoing Invite can contact the SNATMAP Server and get a response.  The difficulty seems to be with getting it to talk properly to the person over the internet when they are at a different location.  LAN connection seems to work as you have already made a "path" to the SNATMAP so the return is less difficult.

This is the feedback page for Messages and iChat

http://www.apple.com/feedback/ichat.html

It was never that well updated even when it was just iChat (it has never gotten to ichat 6 in the lower drop down and Messages is not even mentioned).

Add everything requested in the lower drop down in the Free Text Area.

8:56 p.m.      Wednesday; September 2, 2015