Restore iChat!

No advance notice, huh?

This is from April of 2014:

http://www.ibtimes.com/apple-end-ichat-login-support-aim-mac-osx-1071-below-user s-encouraged-upgrade-mavericks-1574279

I went through Apple help, 4 different experts trying to get it to work and they finally told me to use Skype! Apple really let us down.

Hi,

There is an issue that Apple and none of here have any idea on how to solve at the moment.

It effects all versions of iChat (from iChat 5.0.3 in Snow leopard at least) to the latest version of Messages in Yosemite.

It stops All A/V chats including Screen Sharing across all AIM and Jabber accounts (which includes Google).

That means as there has not been updates to Snow Leopard or anything before Yosemite that is nothing Apple have done.

Also as it effect both AIM to AIM and Jabber to Jabber connections it has nothing to do with AIM or Google as the most popular Jabber account in use.

That leaves something on the internet as a whole.

This is also completely separate from the issue that @mac.com names will not work as AIM Screen Names at base level OS X 10.7 and earlier (which means iChat)

Later versions of OS X 10.7 update iChat 6 enough that they do work.

If you have kept an @me.com account Live by connecting it to iCloud it suffers from the same issue.

The reason for this was changes at AIM to improve security.

iChat 6.0.3 and later have a dual login to both Apple and AIM and this allows the @mac.com and @me.com names to work (the Login to Apple confirms that AIM can read the Password).

It also means that @icloud.com names also will not work in the same versions.

To be clear, the split is part way through the Update life of OS X 10.7 and therefore iChat 6.

8:43 p.m. Friday; July 31, 2015

Ralph - I have read many of your posts on this subject as I have been having problems on AIM to AIM video + screen share.

In the end, I have the buddy list visible in Messages on a Yosemite (10.10.4) system and it has no problem doing AM to AIM video + screen share with a Snow Leopard (10.6.8) machine OVER LAN.

In fact, I have tested the following combinations on 2 different LANS:

- LAN #1 - Snow Leopard <==> Mavericks (video only tested)

- LAN #1 - Mavericks <==> Yosemite (video only tested)

- LAN #2 - Snow Leopard <==> Snow Leopard (video + screen sharing)

- LAN #2 - Snow Leopard <==> Yosemite (video + screen sharing)

Over the Internet it just doesn't work ANYMORE... it used to a little over a month ago. Which makes me wonder - knowing full well that Apple has made changes to Messages/iChat and how they integrate in newer versions of OS X - if this issue is an Apple issue or an AIM server issue?

So I had started believing that it is an AOL issue. Then I tried signing in to AIM and initiating a video session from within Chrome over the Internet and surprisingly it WORKED! Now this doesn't prove that screen sharing would work in such a case but video did not work at all previously over the Internet.

I think there is some combo effect going on here. Wondering if I should try contacting AOL... though the AIM account is free... perhaps sign up for a trial and see if they can figure it out. Doesn't sound that promising though.

Any other ideas anyone????

Correction: Just tested both ends of an AIM video session in chrome and interestingly enough Messages launches a web browser on the receiving end so it isn't using ichat anyways. Turns out this is a red herring as it proves nothing really. Back to this being an AIM server issue... possibly... but no clue... 😟

Hi,

AS you say, two LAN based computers this will work for.

I have it working for Yosemite (So Called Versions 8) to iChat 5.0.3 in Snow Leopard using AIM accounts at both ends.

I have not specifically tested but as Bonjour is LAN based anyway I am presuming that works as well.

AS the reports from others say Google/Jabber and AIM both don't work then I am sure Jabber will work as well (I have only a Google account right this minute).

The various reports are spread over Yosemite and mention both OS 10.10.3 and .4 as being "responsible" although I can't see Messages had an update in either.

There are more in Mavericks and in iChat forums (where this Thread is) iChat 5.0.3 at both ends is mentioned as well as virtually every combination of versions since.

This means it is nothing that Apple have done.

Being it is Jabber and AIM it is nothing AIM have done (or Google as the most popular Jabber IDs used in Messages and iChat).

That leaves the internet as whole.

Using the Network Utility app in the Utilities folder one cause maybe the SNATMAP server (Even Bonjour Chats use this server)

It is contacted and mediates the connections on port 5678 and drops out once the connections goes Peer-to-Peer.

Pinging it gets no response. (not unreasonable for a busy server that might get brought down by such an attack)

Traceroute info is very long and ponderous with many servers not being identified but it does have quite long times for each intermediary servers and eventually passes the 64 hop limit.

AS all calls including Bonjour go through SNATMAP it may be something about this server that is the issue.

10:06 p.m. Saturday; August 1, 2015

BTW I can confirm that Yosemite 10.10.2 does not work and Mavericks (version unknown at the moment) both do not work so I don't think 10.10.3 or 10.10.4 are responsible. It just might be the TIMING of these updates (and track record of some bad minor updates) that makes people point their finger.

Your theory makes sense. It really appears like something on the Internet stopped working.

Also what I notice that is VERY interesting is that the invitee receives and accepts the invite and about 10 or so seconds into the start of the session when you expect the dialog box to go away and the session to start the spinner (not Apple disc - but actual tick spinner in the dialog box) pauses for a few seconds and then resumes and doesn't result in an error for quite some time.

So its almost as if some handoff was attempt and failed and the dialog box just keep spinning and the person inviting just kept waiting.

I dug into the SNATMAP and offhand: "The SNATMAP service on port 5678 is used to determine the external Internet address of hosts so that connections between iChat users can properly function behind network address translation (NAT). The SNATMAP service simply communicates to clients the Internet address that connected to it. This service runs on an Apple server, but does not send personal information to Apple."

So there servers are in Apples control. Perhaps this is a way to try to get people like me to abandon Snow Leopard and jump to Yosemite as Snow Leopard has become the Windows XP of the Mac OS X line IMHO 😁

I found this thread but am unsure how I can go about doing more level testing to determine what is going on w.r.t. SNATMAP but an issue here would make sense... it also would explain why things work on a local LAN (i.e. no need for NAT):

iChat AV SNATMAP broken at Apple *WITH LOG*

There has to be a solution somewhere. Any way to raise this to Apples attention to verify the operation of these SNATMAP servers?

Thoughts???

My family has been using iChat/iMessage/Messages for years. As the "resident tech support", I've kept my parents', my sister's, and our two family computers synchronized with the OS updates (trying Yosemite but falling back to Mavericks.) My sister's Messages video connections failed back in April, with my parent's connection faltering and finally failing three weeks ago. Numerous Apple Genius and online searches failed to correct, or even diagnose, the problem. Unlike the reference above to the announcement on International Business Times for iChat support ending, we have not been in that affected demographic, having all been updated to Mavericks/Messages. I recently ran a local test video connection from our church to home, and again from the Apple Store to home. All failed the same way, with the video call initiation being accepted, but without ever completing the connection. I tried the same thing at home, and connected within the home network. There is obviously an internet service/required support that was terminated, and there was no notice given. Nor is there any documentation of the issue outside of these community forum posts. It doesn't matter whether it is AOL or Apple, it is under Apple's control for notification/documentation, and they have absolutely failed, setting another poor post-Jobs status check.

On the possible solutions front, is port forwarding (with appropriate setup on all desired connections) a possible fix, and is it port 5678 for SNATMAP, ports 16384-16403 for the AV connections, a combination or none of the above?

Hi,

At present I can't "prove" it is the Snatmap servers.

Having said that you used to be able to Ping the server and get a response (I can see why that has been stopped).

Apple's own Network Utility does not check UDP port items.

Messages (and iChat) uses port 5678 on UDP to contact Snapmap.

I tired checking it with IPNetworkMonitorX but also drew a blank on this.

Those poster who have reached Level 6 and above can post in the Lounge that does have a section for "New Technical Issues"

I can post there once I have more definite info that it is likely to be this.

9:11 p.m. Wednesday; August 5, 2015

Hi,

Port Forwarding opens the ports but only for the device listed in the routing table by it's IP.

You need and the login port of the Service you are using.

443 for AIM as we are talking iChat and the way that app's method of A/V chants is still used in Messages.

Depending on your Jabber server it is 5223 when using SSL and 5222 if not.

To the do an A/V chat including Screen Sharing you need 5678 on the UDP Protocol (if stated) to connect to SNAPMAP.

The process then moves to port 16402 (from the group of 10, 16393-16402) that later versions of iChat and Messages use.

This has the SIP (Session Initiation Protocol) bit that acts like two ends of an old telephone exchange connection. Once this is negotiated via the SNAPMAP server that server drops out and you should be Peer-to-Peer on port 16402.

If you don't use Port Forwarding then UPnP is the simplest and allows Multiple devices at one end to use the same ports.

IN this case you may seem random port showing up in Failed connection Logs (Messages and iChat are supposed to work though the groups of 10 before trying random ports) The Logs always seems to go to random Ports directly.

Using /Applications/Messages.app/Contents/MacOS/Messages -errorLogLevel 7 or
/Applications/iChat.app/Contents/MacOS/iChat -errorLogLevel 7

In Terminal for your relevant app used to open the app and create a Log of doing so.

This log can be very long just to show the Login part. This will show use of port 5678 to get the Bandwidth Speed you have.

9:24 p.m. Wednesday; August 5, 2015

Hi Ralph,

Sorry it took so long to get this info. Here it is. Like you said it is long. Hopefully there is a clue as to the issue 🙂

(mac0) ~ # /Applications/iChat.app/Contents/MacOS/iChat -errorLogLevel 7

205155.945842 ER_AddFilter (0): Adding [Nikolaos G@127.0.0.1]->[0]

205155.945868 setLocalUserName: Nikolaos G@127.0.0.1

205155.949221 Default video size is (640 x 480)

205155.950970 H264: (640 x 480) @ 20 fps

205155.954425 H264: (320 x 240) @ 30 fps

205155.957956 H263: (352 x 288) @ 30 fps

205155.959707 H263: (176 x 144) @ 30 fps

205155.959772 ######################################

205155.959779 # SoundDec_Create(16000 --> 3) #

205155.959784 ######################################

205156.018980 Leaving SoundDec_Create

205156.040036 Audio Unit Parameter List = 7, result = 0

205156.040064 CurrentFormatmSampleRate 44100.000000

205156.040075 CurrentFormatmFormatID lpcm

205156.040080 CurrentFormatmFormatFlags 0x00000029

205156.040084 CurrentFormatmBytesPerPacket 4

205156.040088 CurrentFormatmFramesPerPacket 1

205156.040092 CurrentFormatmBytesPerFrame 4

205156.040096 CurrentFormatmChannelsPerFrame 2

205156.040100 CurrentFormatmBitsPerChannel 32

205156.040104 OurFormatmSampleRate 16000.000000

205156.040109 OurFormatmFormatID lpcm

205156.040113 OurFormatmFormatFlags 0x00000029

205156.040117 OurFormatmBytesPerPacket 4

205156.040121 OurFormatmFramesPerPacket 1

205156.040125 OurFormatmBytesPerFrame 4

205156.040128 OurFormatmChannelsPerFrame 1

205156.040132 OurFormatmBitsPerChannel 32

205156.040139 Reached err = 4294956417, 459

205156.040143 Reached err = 4294956417, 467

205156.043365 ### NEW STATE: to: VC_INIT, from: VC_INVALID

205156.043403 ### NEW STATE: to: VC_IDLE, from: VC_INIT

205156.043422 ++++++++++ confStatusMapRemoveAll

205156.043428 ( ) -- mapUserIDToSecurityInfo cleared --

205156.043720 dispatch_CommNATProc

205156.052566 selectedCamera: no camera has been set yet.

205156.052675 Selected microphone is the null device microphone.

205156.052778 vcCapabilitiesOfCPU returns: 0x00000fff

205156.052933 BWD: GotBandwidth: 10193642/63249727 (up/down) @[168.0.168.192:0.255.255.255]

205156.053001 BWD bandwidth: 10193 kbits up, 63249 kbits down.

205156.053055 videoNetworkCapable: 1 -- 3 max participants.

205156.053107 audioNetworkCapable: 1 -- 9 max participants.

205156.053132 Supports PCMU wideband for audio: 1 / video: 1

205156.053153 vcCapabilitiesOfNetwork returns: 0x00000fff

205156.053161 vcCapabilitiesOfRouter returns: 0x00000000

205156.053166 vcCapabilities returns: 0x00000fff

205156.054267 Found 2 cameras:

205156.054361 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)

205156.054474 Built-in iSight - 0xfd40000005ac8502 (0x104, 0x104)

205156.054551 selectedCamera: no camera has been set yet.

205156.054634 selectCameraWithTundraDeviceID: 0x104 returned 1

205156.058940 Microphone devices:

205156.059408 Internal microphone

205156.059528 Line In

205156.059872 Selected mic: Built-in Microphone / imic

205156.060016 Found 2 cameras:

205156.060092 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)

205156.060176 Built-in iSight - 0xfd40000005ac8502 (0x104, 0x104)

205156.060261 selectedCamera2 GUID returned Built-in iSight

205156.060330 selectCameraWithTundraDeviceID: 0x104 returned 1

205156.064181 Microphone devices:

205156.064368 Internal microphone

205156.064483 Line In

205156.065819 Selected mic: Built-in Microphone / imic

205156.562547 Received VCHardwareCapsChangeNotification

2015-08-07 20:51:56.562 iChat[65031:903] Hardware Caps Dictionary: {

HasCamera = 1;

HasDV = 0;

HasMic = 0;

HasQ8 = 0;

Q8List = (

{

FirmwareVersion = 0;

GUID = 0xfd40000005ac8502;

IrisState = 1;

}

);

}

205156.563618 Found 2 cameras:

205156.563692 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)

205156.563782 Built-in iSight - 0xfd40000005ac8502 (0x104, 0x104)

205156.574530 Microphone devices:

205156.574917 Internal microphone

205156.575040 Line In

205156.577378 selectedCamera2 GUID returned Built-in iSight

205156.577860 Selected microphone is Internal microphone.

205156.578052 vcCapabilitiesOfCPU returns: 0x00000fff

205156.578252 BWD: GotBandwidth: 10193642/63249727 (up/down) @[168.0.168.192:0.255.255.255]

205156.578322 BWD bandwidth: 10193 kbits up, 63249 kbits down.

205156.578379 videoNetworkCapable: 1 -- 3 max participants.

205156.578435 audioNetworkCapable: 1 -- 9 max participants.

205156.578488 Supports PCMU wideband for audio: 1 / video: 1

205156.578554 vcCapabilitiesOfNetwork returns: 0x00000fff

205156.578612 vcCapabilitiesOfRouter returns: 0x00000000

205156.578667 vcCapabilities returns: 0x00000fff

205156.580782 Found 2 cameras:

205156.580920 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)

205156.581027 Built-in iSight - 0xfd40000005ac8502 (0x104, 0x104)

205156.581117 selectedCamera2 GUID returned Built-in iSight

205156.581200 selectCameraWithTundraDeviceID: 0x104 returned 1

205156.586574 Microphone devices:

205156.586986 Internal microphone

205156.587340 Line In

205156.588787 Selected mic: Built-in Microphone / imic

205156.590754 Found 2 cameras:

205156.590856 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)

205156.590951 Built-in iSight - 0xfd40000005ac8502 (0x104, 0x104)

205156.591341 selectedCamera2 GUID returned Built-in iSight

205156.591412 selectCameraWithTundraDeviceID: 0x104 returned 1

205156.595637 Microphone devices:

205156.595736 Internal microphone

205156.595798 Line In

205156.596024 Selected mic: Built-in Microphone / imic

205156.606156 Selected microphone is Internal microphone.

205156.606466 Selected microphone is Internal microphone.

205156.607019 Selected microphone is Internal microphone.

205156.607350 Selected microphone is Internal microphone.

205156.609395 Found 2 cameras:

205156.609424 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)

205156.609471 Built-in iSight - 0xfd40000005ac8502 (0x104, 0x104)

205156.609502 selectedCamera2 GUID returned Built-in iSight

205156.609517 selectCameraWithTundraDeviceID: 0x104 returned 1

205156.613924 Microphone devices:

205156.614020 Internal microphone

205156.614084 Line In

205156.614300 Selected mic: Built-in Microphone / imic

205156.638398 Selected microphone is Internal microphone.

205211.331639 CommNAT no result

205214.024652 TundraCapture_SetImageSize: requested size (640x480) new size (640x480:30.000030) vide:2vuy

205214.097649 Microphone: callback thread: STANDARD; EXTENDED timeshare: 0; PRECEDENCE importance: 17

205214.097871 Microphone: null device thread: STANDARD; EXTENDED timeshare: 0; PRECEDENCE importance: 17

205215.118040 Microphone devices:

205215.118181 Internal microphone

205215.118254 Line In

205215.118629 Selected mic: Built-in Microphone / imic

205215.118995 VTPRecvProc thread(412135424) started...

205215.119040 SIPManager init with protocol: 0.

205215.119127 1 interfaces found.

205215.119199 VTP set fd(11) buf size send[9216->225000] recv[42080->225000]

205215.119339 Start listening on 192.168.0.168:16402(en1) sock 100

205215.119351 1 valid interfaces found.

205215.119437 Transport checking map for interface = en1, port = 16402

205215.119472 [0]Creating a port mapping from on interface 0 from external port 55693 to local port16402...

205215.119567 Transport(UDP) Thread start...

205215.119755 TPListen on port 16402

205215.120064 dispatch_AcquireSNATMAPConfigurationProc

205215.122542 selectedCamera2 GUID returned Built-in iSight

205215.186108 SNATMAP Configuration: snatmap.apple.com:5678

205215.259559 vcCapabilitiesOfCPU returns: 0x00000fff

205215.259691 BWD: GotBandwidth: 10193642/63249727 (up/down) @[168.0.168.192:0.255.255.255]

205215.259706 BWD bandwidth: 10193 kbits up, 63249 kbits down.

205215.259712 videoNetworkCapable: 1 -- 3 max participants.

205215.259716 audioNetworkCapable: 1 -- 9 max participants.

205215.259720 Supports PCMU wideband for audio: 1 / video: 1

205215.259732 vcCapabilitiesOfNetwork returns: 0x00000fff

205215.259738 vcCapabilitiesOfRouter returns: 0x00000000

205215.259742 vcCapabilities returns: 0x00000fff

205215.273746 Diffusion prefilter disabled

205215.273776 Temporal prefilter disabled

2015-08-07 20:52:15.273 iChat[65031:12f03] ------ startPreview: previewing: 2

205215.274030 startPreview returned 0

205215.304304 Video size change from 0x0 to 640x480(1280)

205215.465350 VCDelegate conforms to VideoConferenceDelegate protocol.

205215.465385 ER_AddFilter (1): Adding [ngsun1]->[0]

205215.465398 setLocalUserName: ngsun1

205215.465411 ( ) setValidatedIdentity: [00000000]

205215.543387 [[** sMT - MTHelper_Relay] retCode = 3, desc = ]

205215.543421 VCConnectionDataWithAttributes has no relay key

2015-08-07 20:52:15.543 iChat[65031:12d07] attribute = {

VCSupportARDAudioMux = 1;

shouldFindExternalIP = 1;

}

205215.543680 [[** sMT - MTHelper_SetRemoteSL :: SnowLeopard]]

205215.543697 candidate collection start : 19.440440

205215.546673 Resolved SNATMAP server [17.164.2.15:5678]

205215.546777 sent SNATMAP request for [192.168.0.168:16402]

205215.664309 Found 2 cameras:

205215.664346 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)

205215.664396 Built-in iSight - 0xfd40000005ac8502 (0x104, 0x104)

205215.664435 selectedCamera2 GUID returned Built-in iSight

205215.664471 selectCameraWithTundraDeviceID: 0x104 returned 1

205215.670140 Microphone devices:

205215.670424 Internal microphone

205215.670542 Line In

205215.670939 Selected mic: Built-in Microphone / imic

205215.681938 Selected microphone is Internal microphone.

205216.546015 ReXmit collection request for [192.168.0.168:16402]

205217.545254 ReXmit collection request for [192.168.0.168:16402]

205218.544513 ReXmit collection request for [192.168.0.168:16402]

205218.631052 in callback

205218.631083 -sdRef 0x117135370 ?

205218.631088 -flags = 00000000

205218.631093 -IFIndex 0 ?

205218.631097 -errorCode == 00000000

205218.631104 -publicAddr == 0.0.0.0

205218.631108 -proto == 16

205218.631112 -privPort == 16402

205218.631115 -publPort == 0

205218.631119 -ttl == 0

205219.543808 ReXmit collection request for [192.168.0.168:16402]

205220.543079 ReXmit collection request for [192.168.0.168:16402]

205221.542220 candidate collection done : 25.438781

205221.542294 add LOCAL candidate [192.168.0.168:16402]

205221.542434 Adding [en1] to DNSSD ip port list:[0.0.0.0:55693], [0 == 4]

205221.542449 1 candidate(s) added

205221.542730 VCConnectionData for call id: 1 returns 0x1c810150

205232.114901 vcCapabilitiesOfCPU returns: 0x00000fff

205232.115023 BWD: GotBandwidth: 10193642/63249727 (up/down) @[168.0.168.192:0.255.255.255]

205232.115039 BWD bandwidth: 10193 kbits up, 63249 kbits down.

205232.115044 videoNetworkCapable: 1 -- 3 max participants.

205232.115049 audioNetworkCapable: 1 -- 9 max participants.

205232.115053 Supports PCMU wideband for audio: 1 / video: 1

205232.115064 vcCapabilitiesOfNetwork returns: 0x00000fff

205232.115071 vcCapabilitiesOfRouter returns: 0x00000000

205232.115075 vcCapabilities returns: 0x00000fff

205232.117142 prepareConnection - remote VCConnectionData: 14095610, local VCConnectionData: 1408d4b0

205232.117295 Remote CommNAT Result: 0x000000d0

CNAT_BADTEST ....... 0

CNAT_ISFULLCONE .... 0

CNAT_ISPAT ......... 0

CNAT_ISPATHOST ..... 0

CNAT_TRYPRESERVE ... 1

CNAT_PATINORDER .... 0

CNAT_BLOCKIP ....... 1

CNAT_BLOCKPORT ..... 1

CNAT_LOOPBACK ...... 0

205232.117617 ICEStartConnectivityCheck(id[local:1 remote:2] count[local:1 remote:3] candidate[local:0x14083480 remote:0x018DEEC0] pair[0x01153C00]

205232.117657 connectivity check thread start...(488632320)

205232.118393 ***** Insert conn check events *****

205232.118413 event 192.168.0.168:16402->192.168.1.161:16402 expires 36.014637

205232.118423 event 192.168.0.168:16402->192.168.1.161:16402 expires 36.114637

205232.118432 event 192.168.0.168:16402->192.168.1.161:16402 expires 36.314637

205232.118440 event 192.168.0.168:16402->192.168.1.161:16402 expires 36.714637

205232.118448 event 192.168.0.168:16402->192.168.1.161:16402 expires 37.514637

205232.118455 event 192.168.0.168:16402->192.168.1.161:16402 expires 39.114637

205232.118463 event 192.168.0.168:16402->192.168.1.161:43172 expires 36.064637

205232.118471 event 192.168.0.168:16402->192.168.1.161:43172 expires 36.164637

205232.118479 event 192.168.0.168:16402->192.168.1.161:43172 expires 36.364637

205232.118486 event 192.168.0.168:16402->192.168.1.161:43172 expires 36.764637

205232.118494 event 192.168.0.168:16402->192.168.1.161:43172 expires 37.564637

205232.118501 event 192.168.0.168:16402->192.168.1.161:43172 expires 39.164637

205232.118509 ***** event (192.168.0.168:16402->192.168.1.161:16402) fired *****

205232.118636 ** BINDING_REQUEST to [192.168.1.161:16402] USERNAME[5C2A588E000000001-71B18AA9250000001]

205232.118643 OLD STATE(WAITING)->NEW STATE(TESTING)

205232.119686 [[** sMT - MTHelper_AttemptCall] [0][user:dianc2][Caller] [total_current user = 0][SnowLeopard][remoteCommNAT 208][isRelay 3]

205232.119716 Invoke delegate method vcc:initiateConferenceStartedForParty:(dianc2)

205232.119728 ### NEW STATE: to: VC_SIGNALING, from: VC_IDLE

205232.119736 initiateConferenceCallUsingConnectionDataWithErrorInfoToUser - start

205232.119750 Callee connection data 699 bytes. Caller connection data 375 bytes.

205232.119762 ( )( )( ) ---- <nil> valid returned 0

205232.119846 =========== OpenPorts!

205232.126779 selectedCamera2 GUID returned Built-in iSight

205232.127209 *** Caller SDP ***

205232.127387 v=0

o=nikolaos 0 0 IN %RTP-IP-AF% %RTP-IP%

s=ngsun1

c=IN %RTP-IP-AF% %RTP-IP%

b=AS:2147483647

t=0 0

a=hwi:17412:2:2500

a=iChatEncryption:NO

m=audio %ARTP-PORT% RTP/AVP 110 12 124 3 0

a=rtcp:%ARTCP-PORT%

a=rtpmap:110 X-AAC_LD/22050

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:124 iLBC/8000

a=fmtp:124 mode=30

a=rtpID:3925646946

m=video %VRTP-PORT% RTP/AVP 123 126 34

a=rtcp:%VRTCP-PORT%

a=rtpmap:123 H264/90000

a=rtpmap:126 X-H264/90000

a=rtpmap:34 H263/90000

a=fmtp:34 imagesize 1 rules 30:352:288

a=framerate:30

a=RTCP:AUDIO %ARTCP-PORT% VIDEO %VRTCP-PORT%

a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20

a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20

a=rtpID:660467533

205232.127967 <<<<<<<<<< Conference initiation API version 2 >>>>>>>>>

205232.129426 Join connectivity check thread(488632320).

205232.168417 ***** event (192.168.0.168:16402->192.168.1.161:43172) fired *****

205232.168525 ** BINDING_REQUEST to [192.168.1.161:43172] USERNAME[05A24FF1000000001-71B18AA9250000001]

205232.168533 OLD STATE(WAITING)->NEW STATE(TESTING)

205232.218414 ***** event (192.168.0.168:16402->192.168.1.161:16402) fired *****

205232.218544 ** BINDING_REQUEST to [192.168.1.161:16402] USERNAME[5C2A588E000000001-71B18AA9250000001]

205232.218551 OLD STATE(TESTING)->NEW STATE(TESTING)

205232.268417 ***** event (192.168.0.168:16402->192.168.1.161:43172) fired *****

205232.268537 ** BINDING_REQUEST to [192.168.1.161:43172] USERNAME[05A24FF1000000001-71B18AA9250000001]

205232.268544 OLD STATE(TESTING)->NEW STATE(TESTING)

205232.418414 ***** event (192.168.0.168:16402->192.168.1.161:16402) fired *****

205232.418521 ** BINDING_REQUEST to [192.168.1.161:16402] USERNAME[5C2A588E000000001-71B18AA9250000001]

205232.418528 OLD STATE(TESTING)->NEW STATE(TESTING)

205232.468417 ***** event (192.168.0.168:16402->192.168.1.161:43172) fired *****

205232.468537 ** BINDING_REQUEST to [192.168.1.161:43172] USERNAME[05A24FF1000000001-71B18AA9250000001]

205232.468544 OLD STATE(TESTING)->NEW STATE(TESTING)

205232.818414 ***** event (192.168.0.168:16402->192.168.1.161:16402) fired *****

205232.818518 ** BINDING_REQUEST to [192.168.1.161:16402] USERNAME[5C2A588E000000001-71B18AA9250000001]

205232.818525 OLD STATE(TESTING)->NEW STATE(TESTING)

205232.868414 ***** event (192.168.0.168:16402->192.168.1.161:43172) fired *****

205232.868517 ** BINDING_REQUEST to [192.168.1.161:43172] USERNAME[05A24FF1000000001-71B18AA9250000001]

205232.868524 OLD STATE(TESTING)->NEW STATE(TESTING)

205233.618443 ***** event (192.168.0.168:16402->192.168.1.161:16402) fired *****

205233.618542 ** BINDING_REQUEST to [192.168.1.161:16402] USERNAME[5C2A588E000000001-71B18AA9250000001]

205233.618549 OLD STATE(TESTING)->NEW STATE(TESTING)

205233.668447 ***** event (192.168.0.168:16402->192.168.1.161:43172) fired *****

205233.668563 ** BINDING_REQUEST to [192.168.1.161:43172] USERNAME[05A24FF1000000001-71B18AA9250000001]

205233.668580 OLD STATE(TESTING)->NEW STATE(TESTING)

205235.218502 ***** event (192.168.0.168:16402->192.168.1.161:16402) fired *****

205235.218609 ** BINDING_REQUEST to [192.168.1.161:16402] USERNAME[5C2A588E000000001-71B18AA9250000001]

205235.218616 OLD STATE(TESTING)->NEW STATE(TESTING)

205235.268507 ***** event (192.168.0.168:16402->192.168.1.161:43172) fired *****

205235.268620 ** BINDING_REQUEST to [192.168.1.161:43172] USERNAME[05A24FF1000000001-71B18AA9250000001]

205235.268627 OLD STATE(TESTING)->NEW STATE(TESTING)

205238.118687 (ICEConnCheck.c:178) connectivity check timed out...

205238.118717 (ICEConnCheck.c:669) RecvAndProcess failed (80150017)

205238.118725 (ICEConnCheck.c:711) Connectivity check returned (80150017)

205238.119055 connectivity check thread(488632320) end.(80150017)

205238.119072 Retry using classic invitation sequence.

205238.119192 <<<<<<<<<< Conference initiation API version 1 >>>>>>>>>

205238.119223 [ipAndPortData length] = 120

205238.119229 Length is valid: YES

205238.119254 CALLEE: ifname=[en1], IP=[192.168.1.161:16402]

205238.119269 CALLEE: ifname=[en1], IP=[192.168.1.161:43172]

205238.119282 CALLEE: ifname=[en1], IP=[99.226.145.207:43172]

2015-08-07 20:52:38.119 iChat[65031:1a0b] IPAndPortList: (

{

ip = "192.168.1.161";

port = 16402;

},

{

ip = "192.168.1.161";

port = 43172;

},

{

ip = "99.226.145.207";

port = 43172;

}

)

205238.119711 SIPConnect start...

205238.119721 ER_AddFilter (2): Adding [dianc2]->[u0]

205238.119845 SIP IPPort: local=[192.168.0.168:16402] src=[192.168.0.168:16402] remote=[192.168.1.161:16402] dst=[192.168.1.161:16402]

205238.119856 ER_AddFilter (3): Adding [192.168.0.168]->[lip]

205238.119912 ER_AddFilter (4): Adding [192-168-0-168]->[lip]

205238.119922 ER_AddFilter (5): Adding [192.168.1.161]->[rip]

205238.119928 ER_AddFilter (6): Adding [192-168-1-161]->[rip]

205238.120038 TAInviteClientProc Thread start...

205238.120073 ( )( )( )( )( ) TP IS BINARY? (0)

205238.120085 RTP using 192.168.0.168:16402 and 192.168.0.168:16402 as hints

205238.120157 RTP vfd (102) accepts pkt (0010)

205238.120166 RTCP vfd (103) accepts pkt (0040)

205238.120171 RTP/RTCP ports for PayloadType 1 are 16402(102) and 16402(103)

205238.120216 RTP vfd (104) accepts pkt (0008)

205238.120222 RTCP vfd (105) accepts pkt (0020)

205238.120226 RTP/RTCP ports for PayloadType 0 are 16402(104) and 16402(105)

205238.120247 Send to 192.168.1.161:16402 [INVITE sip:user@192.168.1.161:16402 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.168:16402;branch=z9hG4bK15b795d3634c8b86

Max-Forwards: 70

To: "dianc2" <sip:user@192.168.1.161:16402>

From: "ngsun1" <sip:user@192.168.0.168:16402>;tag=47095274

Call-ID: 1e53d67c3d65c00-3d67-11e5-b343-d1cc059c4012@192-168-0-168

CSeq: 1 INVITE

Contact: <sip:user@192.168.0.168:16402>;isfocus

User-Agent: Viceroy 1.4

Content-Type: application/sdp

Content-Length: 692

v=0

o=nikolaos 0 0 IN IP4 192.168.0.168

s=ngsun1

c=IN IP4 192.168.0.168

b=AS:2147483647

t=0 0

a=hwi:17412:2:2500

a=iChatEncryption:NO

a=bandwidthDetection:YES

m=audio 16402 RTP/AVP 110 12 124 3 0

a=rtcp:16402

a=rtpmap:110 X-AAC_LD/22050

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:124 iLBC/8000

a=fmtp:124 mode=30

a=rtpID:3925646946

m=video 16402 RTP/AVP 123 126 34

a=rtcp:16402

a=rtpmap:123 H264/90000

a=rtpmap:126 X-H264/90000

a=rtpmap:34 H263/90000

a=fmtp:34 imagesize 1 rules 30:352:288

a=framerate:30

a=RTCP:AUDIO 16402 VIDEO 16402

a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20

a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20

a=rtpID:660467533

]

205238.620512 ( )( )( )( )( ) TP IS BINARY? (0)

205238.620573 Send to 192.168.1.161:16402 [INVITE sip:user@192.168.1.161:16402 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.168:16402;branch=z9hG4bK15b795d3634c8b86

Max-Forwards: 70

To: "dianc2" <sip:user@192.168.1.161:16402>

From: "ngsun1" <sip:user@192.168.0.168:16402>;tag=47095274

Call-ID: 1e53d67c3d65c00-3d67-11e5-b343-d1cc059c4012@192-168-0-168

CSeq: 1 INVITE

Contact: <sip:user@192.168.0.168:16402>;isfocus

User-Agent: Viceroy 1.4

Content-Type: application/sdp

Content-Length: 692

v=0

o=nikolaos 0 0 IN IP4 192.168.0.168

s=ngsun1

c=IN IP4 192.168.0.168

b=AS:2147483647

t=0 0

a=hwi:17412:2:2500

a=iChatEncryption:NO

a=bandwidthDetection:YES

m=audio 16402 RTP/AVP 110 12 124 3 0

a=rtcp:16402

a=rtpmap:110 X-AAC_LD/22050

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:124 iLBC/8000

a=fmtp:124 mode=30

a=rtpID:3925646946

m=video 16402 RTP/AVP 123 126 34

a=rtcp:16402

a=rtpmap:123 H264/90000

a=rtpmap:126 X-H264/90000

a=rtpmap:34 H263/90000

a=fmtp:34 imagesize 1 rules 30:352:288

a=framerate:30

a=RTCP:AUDIO 16402 VIDEO 16402

a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20

a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20

a=rtpID:660467533

]

205239.622171 ( )( )( )( )( ) TP IS BINARY? (0)

205239.622254 Send to 192.168.1.161:16402 [INVITE sip:user@192.168.1.161:16402 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.168:16402;branch=z9hG4bK15b795d3634c8b86

Max-Forwards: 70

To: "dianc2" <sip:user@192.168.1.161:16402>

From: "ngsun1" <sip:user@192.168.0.168:16402>;tag=47095274

Call-ID: 1e53d67c3d65c00-3d67-11e5-b343-d1cc059c4012@192-168-0-168

CSeq: 1 INVITE

Contact: <sip:user@192.168.0.168:16402>;isfocus

User-Agent: Viceroy 1.4

Content-Type: application/sdp

Content-Length: 692

v=0

o=nikolaos 0 0 IN IP4 192.168.0.168

s=ngsun1

c=IN IP4 192.168.0.168

b=AS:2147483647

t=0 0

a=hwi:17412:2:2500

a=iChatEncryption:NO

a=bandwidthDetection:YES

m=audio 16402 RTP/AVP 110 12 124 3 0

a=rtcp:16402

a=rtpmap:110 X-AAC_LD/22050

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:124 iLBC/8000

a=fmtp:124 mode=30

a=rtpID:3925646946

m=video 16402 RTP/AVP 123 126 34

a=rtcp:16402

a=rtpmap:123 H264/90000

a=rtpmap:126 X-H264/90000

a=rtpmap:34 H263/90000

a=fmtp:34 imagesize 1 rules 30:352:288

a=framerate:30

a=RTCP:AUDIO 16402 VIDEO 16402

a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20

a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20

a=rtpID:660467533

]

205240.120505 Dialog(CREATED) Match(STATUS) [1e53d67c3d65c00-3d67-11e5-b343-d1cc059c4012@192-168-0-168]=[1e53d67c3d65c00-3d 67-11e5-b343-d1cc059c4012@192-168-0-168], [47095274]=[47095274]

205240.120536 TAInviteClientProc Thread end(800B0017)...

205240.120690 SIPConnect stop(900A0015)...

205240.120707 SIPConnect start...

205240.120855 SIP IPPort: local=[192.168.0.168:16402] src=[192.168.0.168:16402] remote=[192.168.1.161:43172] dst=[192.168.1.161:43172]

205240.121101 TAInviteClientProc Thread start...

205240.121136 ( )( )( )( )( ) TP IS BINARY? (0)

205240.121162 RTP using 192.168.0.168:16402 and 192.168.0.168:16402 as hints

205240.121186 Send to 192.168.1.161:43172 [INVITE sip:user@192.168.1.161:43172 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.168:16402;branch=z9hG4bK7debd265380706b4

Max-Forwards: 70

To: "dianc2" <sip:user@192.168.1.161:43172>

From: "ngsun1" <sip:user@192.168.0.168:16402>;tag=316459449

Call-ID: 1e53d67c507ad86-3d67-11e5-b343-d50f52904012@192-168-0-168

CSeq: 1 INVITE

Contact: <sip:user@192.168.0.168:16402>;isfocus

User-Agent: Viceroy 1.4

Content-Type: application/sdp

Content-Length: 692

v=0

o=nikolaos 0 0 IN IP4 192.168.0.168

s=ngsun1

c=IN IP4 192.168.0.168

b=AS:2147483647

t=0 0

a=hwi:17412:2:2500

a=iChatEncryption:NO

a=bandwidthDetection:YES

m=audio 16402 RTP/AVP 110 12 124 3 0

a=rtcp:16402

a=rtpmap:110 X-AAC_LD/22050

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:124 iLBC/8000

a=fmtp:124 mode=30

a=rtpID:3925646946

m=video 16402 RTP/AVP 123 126 34

a=rtcp:16402

a=rtpmap:123 H264/90000

a=rtpmap:126 X-H264/90000

a=rtpmap:34 H263/90000

a=fmtp:34 imagesize 1 rules 30:352:288

a=framerate:30

a=RTCP:AUDIO 16402 VIDEO 16402

a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20

a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20

a=rtpID:660467533

]

205240.621435 ( )( )( )( )( ) TP IS BINARY? (0)

205240.621476 Send to 192.168.1.161:43172 [INVITE sip:user@192.168.1.161:43172 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.168:16402;branch=z9hG4bK7debd265380706b4

Max-Forwards: 70

To: "dianc2" <sip:user@192.168.1.161:43172>

From: "ngsun1" <sip:user@192.168.0.168:16402>;tag=316459449

Call-ID: 1e53d67c507ad86-3d67-11e5-b343-d50f52904012@192-168-0-168

CSeq: 1 INVITE

Contact: <sip:user@192.168.0.168:16402>;isfocus

User-Agent: Viceroy 1.4

Content-Type: application/sdp

Content-Length: 692

v=0

o=nikolaos 0 0 IN IP4 192.168.0.168

s=ngsun1

c=IN IP4 192.168.0.168

b=AS:2147483647

t=0 0

a=hwi:17412:2:2500

a=iChatEncryption:NO

a=bandwidthDetection:YES

m=audio 16402 RTP/AVP 110 12 124 3 0

a=rtcp:16402

a=rtpmap:110 X-AAC_LD/22050

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:124 iLBC/8000

a=fmtp:124 mode=30

a=rtpID:3925646946

m=video 16402 RTP/AVP 123 126 34

a=rtcp:16402

a=rtpmap:123 H264/90000

a=rtpmap:126 X-H264/90000

a=rtpmap:34 H263/90000

a=fmtp:34 imagesize 1 rules 30:352:288

a=framerate:30

a=RTCP:AUDIO 16402 VIDEO 16402

a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20

a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20

a=rtpID:660467533

]

205241.621969 ( )( )( )( )( ) TP IS BINARY? (0)

205241.622052 Send to 192.168.1.161:43172 [INVITE sip:user@192.168.1.161:43172 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.168:16402;branch=z9hG4bK7debd265380706b4

Max-Forwards: 70

To: "dianc2" <sip:user@192.168.1.161:43172>

From: "ngsun1" <sip:user@192.168.0.168:16402>;tag=316459449

Call-ID: 1e53d67c507ad86-3d67-11e5-b343-d50f52904012@192-168-0-168

CSeq: 1 INVITE

Contact: <sip:user@192.168.0.168:16402>;isfocus

User-Agent: Viceroy 1.4

Content-Type: application/sdp

Content-Length: 692

v=0

o=nikolaos 0 0 IN IP4 192.168.0.168

s=ngsun1

c=IN IP4 192.168.0.168

b=AS:2147483647

t=0 0

a=hwi:17412:2:2500

a=iChatEncryption:NO

a=bandwidthDetection:YES

m=audio 16402 RTP/AVP 110 12 124 3 0

a=rtcp:16402

a=rtpmap:110 X-AAC_LD/22050

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:124 iLBC/8000

a=fmtp:124 mode=30

a=rtpID:3925646946

m=video 16402 RTP/AVP 123 126 34

a=rtcp:16402

a=rtpmap:123 H264/90000

a=rtpmap:126 X-H264/90000

a=rtpmap:34 H263/90000

a=fmtp:34 imagesize 1 rules 30:352:288

a=framerate:30

a=RTCP:AUDIO 16402 VIDEO 16402

a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20

a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20

a=rtpID:660467533

]

205242.121318 Dialog(CREATED) Match(STATUS) [1e53d67c507ad86-3d67-11e5-b343-d50f52904012@192-168-0-168]=[1e53d67c507ad86-3d 67-11e5-b343-d50f52904012@192-168-0-168], [316459449]=[316459449]

205242.121398 TAInviteClientProc Thread end(800B0017)...

205242.121564 SIPConnect stop(900A0015)...

205242.121572 SIPConnect start...

205242.121989 sent SNATMAP request for [192.168.0.168:16402]

205243.122221 ReXmit collection request for [192.168.0.168:16402]

205244.122465 ReXmit collection request for [192.168.0.168:16402]

205245.122695 ReXmit collection request for [192.168.0.168:16402]

205246.122993 ReXmit collection request for [192.168.0.168:16402]

205247.123228 ReXmit collection request for [192.168.0.168:16402]

205247.123251 (ICE.c:2270) ICEGetExtIPPorts timed out...

205247.123263 SIP IPPort: local=[192.168.0.168:16402] src=[192.168.0.168:16402] remote=[99.226.145.207:43172] dst=[99.226.145.207:43172]

205247.123280 ER_AddFilter (7): Adding [99.226.145.207]->[rip]

205247.123287 ER_AddFilter (8): Adding [99-226-145-207]->[rip]

205247.123446 TAInviteClientProc Thread start...

205247.123485 ( )( )( )( )( ) TP IS BINARY? (0)

205247.123499 RTP using 192.168.0.168:16402 and 192.168.0.168:16402 as hints

205247.123521 Send to 99.226.145.207:43172 [INVITE sip:user@99.226.145.207:43172 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.168:16402;branch=z9hG4bK33f0dc3547fa8f5e

Max-Forwards: 70

To: "dianc2" <sip:user@99.226.145.207:43172>

From: "ngsun1" <sip:user@192.168.0.168:16402>;tag=1267343648

Call-ID: 1e53d67c93429b6-3d67-11e5-b343-9e6f50d44012@192-168-0-168

CSeq: 1 INVITE

Contact: <sip:user@192.168.0.168:16402>;isfocus

User-Agent: Viceroy 1.4

Content-Type: application/sdp

Content-Length: 692

v=0

o=nikolaos 0 0 IN IP4 192.168.0.168

s=ngsun1

c=IN IP4 192.168.0.168

b=AS:2147483647

t=0 0

a=hwi:17412:2:2500

a=iChatEncryption:NO

a=bandwidthDetection:YES

m=audio 16402 RTP/AVP 110 12 124 3 0

a=rtcp:16402

a=rtpmap:110 X-AAC_LD/22050

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:124 iLBC/8000

a=fmtp:124 mode=30

a=rtpID:3925646946

m=video 16402 RTP/AVP 123 126 34

a=rtcp:16402

a=rtpmap:123 H264/90000

a=rtpmap:126 X-H264/90000

a=rtpmap:34 H263/90000

a=fmtp:34 imagesize 1 rules 30:352:288

a=framerate:30

a=RTCP:AUDIO 16402 VIDEO 16402

a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20

a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20

a=rtpID:660467533

]

205247.623722 ( )( )( )( )( ) TP IS BINARY? (0)

205247.623804 Send to 99.226.145.207:43172 [INVITE sip:user@99.226.145.207:43172 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.168:16402;branch=z9hG4bK33f0dc3547fa8f5e

Max-Forwards: 70

To: "dianc2" <sip:user@99.226.145.207:43172>

From: "ngsun1" <sip:user@192.168.0.168:16402>;tag=1267343648

Call-ID: 1e53d67c93429b6-3d67-11e5-b343-9e6f50d44012@192-168-0-168

CSeq: 1 INVITE

Contact: <sip:user@192.168.0.168:16402>;isfocus

User-Agent: Viceroy 1.4

Content-Type: application/sdp

Content-Length: 692

v=0

o=nikolaos 0 0 IN IP4 192.168.0.168

s=ngsun1

c=IN IP4 192.168.0.168

b=AS:2147483647

t=0 0

a=hwi:17412:2:2500

a=iChatEncryption:NO

a=bandwidthDetection:YES

m=audio 16402 RTP/AVP 110 12 124 3 0

a=rtcp:16402

a=rtpmap:110 X-AAC_LD/22050

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:124 iLBC/8000

a=fmtp:124 mode=30

a=rtpID:3925646946

m=video 16402 RTP/AVP 123 126 34

a=rtcp:16402

a=rtpmap:123 H264/90000

a=rtpmap:126 X-H264/90000

a=rtpmap:34 H263/90000

a=fmtp:34 imagesize 1 rules 30:352:288

a=framerate:30

a=RTCP:AUDIO 16402 VIDEO 16402

a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20

a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20

a=rtpID:660467533

]

205248.624025 ( )( )( )( )( ) TP IS BINARY? (0)

205248.624061 Send to 99.226.145.207:43172 [INVITE sip:user@99.226.145.207:43172 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.168:16402;branch=z9hG4bK33f0dc3547fa8f5e

Max-Forwards: 70

To: "dianc2" <sip:user@99.226.145.207:43172>

From: "ngsun1" <sip:user@192.168.0.168:16402>;tag=1267343648

Call-ID: 1e53d67c93429b6-3d67-11e5-b343-9e6f50d44012@192-168-0-168

CSeq: 1 INVITE

Contact: <sip:user@192.168.0.168:16402>;isfocus

User-Agent: Viceroy 1.4

Content-Type: application/sdp

Content-Length: 692

v=0

o=nikolaos 0 0 IN IP4 192.168.0.168

s=ngsun1

c=IN IP4 192.168.0.168

b=AS:2147483647

t=0 0

a=hwi:17412:2:2500

a=iChatEncryption:NO

a=bandwidthDetection:YES

m=audio 16402 RTP/AVP 110 12 124 3 0

a=rtcp:16402

a=rtpmap:110 X-AAC_LD/22050

a=rtpmap:3 GSM/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:124 iLBC/8000

a=fmtp:124 mode=30

a=rtpID:3925646946

m=video 16402 RTP/AVP 123 126 34

a=rtcp:16402

a=rtpmap:123 H264/90000

a=rtpmap:126 X-H264/90000

a=rtpmap:34 H263/90000

a=fmtp:34 imagesize 1 rules 30:352:288

a=framerate:30

a=RTCP:AUDIO 16402 VIDEO 16402

a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20

a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20

a=rtpID:660467533

]

205249.124283 Dialog(CREATED) Match(STATUS) [1e53d67c93429b6-3d67-11e5-b343-9e6f50d44012@192-168-0-168]=[1e53d67c93429b6-3d 67-11e5-b343-9e6f50d44012@192-168-0-168], [1267343648]=[1267343648]

205249.124324 TAInviteClientProc Thread end(800B0017)...

205249.125600 SIPConnect stop(900A0015)...

205249.125619 SIP connect returned 21

205249.125730 SIPCloseCall start...

205249.125738 (SIP.c:4279) Cannot find call ID(2)

205249.125744 SIPCloseCall stop(800C0016)...

205249.125891 [[** sMT - MTHelper_Early_End_Call] [0][user:dianc2][RemoteUA:(RemoteUA - unknown)][SnowLeopard]

205249.125917 ### NEW STATE: to: VC_IDLE, from: VC_SIGNALING

205249.125933 ++++++++++ confStatusMapRemoveAll

205249.125938 ( ) -- mapUserIDToSecurityInfo cleared --

205249.125956 [[** sMT - MTHelper_Relay] retCode = 0, desc = SIP Message Exchange (-8)]

205249.125962 Preparing to send VCInitiateConferenceCompleted

205249.125985 Invoke delegate method vcc:initiateConferenceCompletedForParty:(dianc2) - retcode: -8

205249.395527 endConference with userIDToCallIDMap count = 0

205249.655553 cancelPreview returned 0

205249.658606 Found 2 cameras:

205249.658665 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)

205249.658724 Built-in iSight - 0xfd40000005ac8502 (0x104, 0x104)

205249.658763 selectedCamera2 GUID returned Built-in iSight

205249.658796 selectCameraWithTundraDeviceID: 0x104 returned 1

205249.663238 Microphone devices:

205249.663348 Internal microphone

205249.663408 Line In

205249.663661 Selected mic: Built-in Microphone / imic

205249.673569 Selected microphone is Internal microphone.

Hi,

This looks all fine at the top.

You might want to change the Bandwidth Limit to 500kbps

205156.052933 BWD: GotBandwidth: 10193642/63249727 (up/down) @[168.0.168.192:0.255.255.255]

205156.053001 BWD bandwidth: 10193 kbits up, 63249 kbits down.

In round terms you have 10Mbps upload and around 63Mbps download.

Although it looks like a LAN connection you cannot guarantee that you are getting equal amounts of the bandwidth.

It is set in Preferences > Video section and in the Bandwidth Limit drop down.

On internet connections it is almost as if the fast end thinks the other end has not replied.

500kbps is fast enough for 4 way Video chats.

This section is a bit off as well.

205232.117142 prepareConnection - remote VCConnectionData: 14095610, local VCConnectionData: 1408d4b0

205232.117295 Remote CommNAT Result: 0x000000d0

CNAT_BADTEST ....... 0

CNAT_ISFULLCONE .... 0

CNAT_ISPAT ......... 0

CNAT_ISPATHOST ..... 0

CNAT_TRYPRESERVE ... 1

CNAT_PATINORDER .... 0

CNAT_BLOCKIP ....... 1

CNAT_BLOCKPORT ..... 1

CNAT_LOOPBACK ...... 0

0 is Off

1 is ON

Full Cone is preferred but not critical.

However Blocked IP and Blocked Ports are not good.

It is strange as it then tries to connect.

It lists your LAN IP (192.168.0.168) and the other end's LAN IP

205232.127967 <<<<<<<<<< Conference initiation API version 2 >>>>>>>>>

205232.129426 Join connectivity check thread(488632320).

205232.168417 ***** event (192.168.0.168:16402->192.168.1.161:43172) fired *****

205232.168525 ** BINDING_REQUEST to [192.168.1.161:43172] USERNAME[05A24FF1000000001-71B18AA9250000001]

205232.168533 OLD STATE(WAITING)->NEW STATE(TESTING)

Their IP looks very similar to yours however the 1 in the third section is the difference (192.168.1.161)

At first I thought they were on the same LAN.

You can see here though that the port being used (the number after the IP address) is not in the Group that Apple says they should be in (although there is allowance for random ports).

After that it continues to try the CSeq INVITE for several attempts.

It moves from the 16402 to the random port on dianc's 192.168.1.161 IP address and then it reveals the Public IP address (Expected)

205247.123251 (ICE.c:2270) ICEGetExtIPPorts timed out...

205247.123263 SIP IPPort: local=[192.168.0.168:16402] src=[192.168.0.168:16402] remote=[99.226.145.207:43172] dst=[99.226.145.207:43172]

Now if your Public IP address is the 99.226 and so on as well as it being the other end then there is something wrong with your LAN (it is in at least two Subnets)

if it is your Buddies Public IP address then the call is making progress.

What is worry here is that the info line above says it Timed Out.

Try the speed change I suggested (At both ends).

Th last bit seesm very mixed in the info.

205249.124283 Dialog(CREATED) Match(STATUS) [1e53d67c93429b6-3d67-11e5-b343-9e6f50d44012@192-168-0-168]=[1e53d67c93429b6-3d 67-11e5-b343-9e6f50d44012@192-168-0-168], [1267343648]=[1267343648]

205249.124324 TAInviteClientProc Thread end(800B0017)...

205249.125600 SIPConnect stop(900A0015)...

205249.125619 SIP connect returned 21

205249.125730 SIPCloseCall start...

205249.125738 (SIP.c:4279) Cannot find call ID(2)

205249.125744 SIPCloseCall stop(800C0016)...

205249.125891 [[** sMT - MTHelper_Early_End_Call] [0][user:dianc2][RemoteUA:(RemoteUA - unknown)][SnowLeopard]

205249.125917 ### NEW STATE: to: VC_IDLE, from: VC_SIGNALING

205249.125933 ++++++++++ confStatusMapRemoveAll

205249.125938 ( ) -- mapUserIDToSecurityInfo cleared --

205249.125956 [[** sMT - MTHelper_Relay] retCode = 0, desc = SIP Message Exchange (-8)]

205249.125962 Preparing to send VCInitiateConferenceCompleted

205249.125985 Invoke delegate method vcc:initiateConferenceCompletedForParty:(dianc2) - retcode: -8

205249.395527 endConference with userIDToCallIDMap count = 0

205249.655553 cancelPreview returned 0

205249.658606 Found 2 cameras:

205249.658665 Apple Screen Input Device - 0-Apple ScreenInputDevice (0x101, 0x200)

205249.658724 Built-in iSight - 0xfd40000005ac8502 (0x104, 0x104)

205249.658763 selectedCamera2 GUID returned Built-in iSight

205249.658796 selectCameraWithTundraDeviceID: 0x104 returned 1

205249.663238 Microphone devices:

205249.663348 Internal microphone

205249.663408 Line In

205249.663661 Selected mic: Built-in Microphone / imic

205249.673569 Selected microphone is Internal microphone.

It seems to be suggesting on one hand the SIP bit has not succeeded and it is going to "close" the chat. On the other it seems to be listing all the things it needs to make the connection.

The fact that the SIP bit is confused at this point suggests to me that the SNAPMAP server is losing info on which two people it is is connecting and for Security reasons it ends the chat/connection.

One other thing.

205215.543421 VCConnectionDataWithAttributes has no relay key

2015-08-07 20:52:15.543 iChat[65031:12d07] attribute = {

VCSupportARDAudioMux = 1;

shouldFindExternalIP = 1;

}

This bit says you are not relaying through AIM (it is an option in the video section of the Preferences)

The ARD AudioMux things tells me this is Screen Sharing (the IDs tell me it is AIM)

The suggests it is the SIP bit, which is the bit that goes through SNATMAP.

It may be that the server farm has failed in some way and is overrun or it might have suffered an attack of sorts.

We are probably going to have to wait on Apple for this.

In the meantime let them know http://www.apple.com/feedback/ichat.html

It is the right page. However it was never updated that well at the best of times.

Add all the info it asks for in the drop downs in the Free text area.

9:47 p.m. Saturday; August 8, 2015

I tested with limiting bandwidth to 500kbps and the results were very similar... except instead of spinning seemingly forever... it fails sooner with send report to Apple.

These are 2 geographically distinct LANS with about 400KM+ separating the 2 cities. My LAN is on 192.168.0.x and the other is indeed on 192.168.1.x. Both have a 150MB/15MB cable connection (i.e. the 60MB/10MB observed are more real world and make sense).

You mentioned that the following was odd. What does it mean?

CNAT_BLOCKIP ....... 1

CNAT_BLOCKPORT ..... 1

99.226.145.207 is indeed the other ends WAN IP.

You are correct that I accidentally had unchecked "Allow AOL's server to relay video chats". I imagine I will need to run another test again.

Hi,

Regarding the blocked IP and port.

That section of the Log does not make it clear whether it is testing to the SNAPMAP server or the Buddy or in fact whether they are open at your end.

As the Log has started then the Buddy's IP cannot be blocked as they have responded (you don't get a log in they don't).

Almost no matter how you set up your routing ports opened via Outgoing traffic will allow responses on that port.

Your end reports it is calling out on port 16402.

Testing of the SNATMAP server shows it will respond once in 4 attempts by some utilities.

It used to respond to PINGs but no longer does (but that is understandable in today's climate).

However if we all go testing it that will also look like an Attack.

I am not sure that allowing the AIM Relay part is actually going to help.

At one level it just adds into the number of servers the connection is going through.

If the two sites have multiple computers then speeds much less than the paid for speed are likely to be seen.

As the bandwidth can vary across all those computers Limiting iChat and/or Messages can smooth that issue out.

I had posted about this issue in the Lounge for the Attention of the Hosts.

After 2 and a bit weeks (plus the help of other posters in that area bring it to their attention) the Hosts have responded that they have passed the info on.

It is possible that Apple think the use of SNATMAP will drop off in favour of the iMessages Video (FaceTime Invocation) and Screen Sharing Invocation.

If the server is under attack then the number could still be less than iChat at it's peak.

We also have governments that don't like the fact Apple Don't let them read the iMessages

http://www.bbc.co.uk/news/uk-politics-30778424

Not that text Chats in this case have a lot to do with the Video chat side but it will be another part of the app that cannot be "seen" by them.

8:35 p.m. Tuesday; August 11, 2015